News for hackers. Stuff that matters.

A comment on GitLab Container Registry. Parent comment

Re:GitLab Container Registry by tostaki on Monday May 23, 2016 @06:37PM (#11757590)
At my work, we have a setup close to this. On a successful build of jenkins (after build action), a deb is generated with FPM (awesome piece of software btw) and uploaded to an s3 bucket. Then on another machine, a cron that run every minutes sync the s3 bucket to a local aptly repository and publish it to another s3 bucket which is the real debian repository.

This works well but the s3+cron part is probably not the smartest way and publication can take some time (like 5-10min).

[ Parent | on HN ]
Re:GitLab Container Registry by voltagex_ on Tuesday May 24, 2016 @12:54AM (#11759064)
I know it probably doesn't matter too much for internal use, but what does Lintian say about your packages?
[ Parent | on HN ]
Re:GitLab Container Registry by tostaki on Tuesday May 24, 2016 @07:38AM (#11760680)
Many bad things! I didn't check until now but it's a bunch of "non-standard-dir-perm" and "dir-or-file-in-var-www" and things like "maintainer-name-missing". I think it's possible to build correct debian package with FPM but for our use, we just want to build easily native deb package.
[ Parent | on HN ]
Re:GitLab Container Registry by dozzie on Tuesday May 24, 2016 @07:50AM (#11760742)
> I think it's possible to build correct debian package with FPM [...]

Of course it is possible, it's just ridiculous amount of work. It's much easier to build package with proper tools in the first place.

[ Parent | on HN ]