4 ms·
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) an
by tostaki 10y ago
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).
- voltagex_ 10y agoI know it probably doesn't matter too much for internal use, but what does Lintian say about your packages?
- tostaki 10y agoMany 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.
- dozzie 10y ago> 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.