I’m in the middle of some conversations about Debian/Ubuntu repositories, and I’m curious how others are handling this.
How are people maintaining repos for an organization? Are you integrating them with a git/CI (github/gitlab, jenkins/travis, etc) workflow? How do packages propagate into repos? How do you separate prod from testing? Is anyone running buildd locally, or integrating with more common CI tools?
I’m also interested in how people handle local modifications of packages — anything from newer versions of C libraries to newer interpreters. Do you just use the regular Debian toolchain, packaging them up for (potentially) the multiple distros/versions that you have in production? Pin them in apt?
Just curious what’s out there.
Some Googling has so far turned up just one relevant hit: Michael Prokop’s DebConf15 slides, “Continuous Delivery of Debian packages”. Looks very interesting, and discusses jenkins-debian-glue.
Some tangentially-related but interesting items:
- jenkins.debian.net is a thing
- And so is openqa.debian.net
- travis.debian.net is there for people that host Debian packaging on Github.
Edit 2018-02-02: I should have also mentioned BuildStream