Arvados

We should still build and test them, but uploading them all to the public apt repository takes a ton of disk space on the server and increases contention for the aptly database.

One side effect of this would be: the package build code tries to avoid rebuilds by checking whether a package is already in the apt repository, and if it is, downloading that instead of rebuilding. Doing this naively would lead to more redundant package builds. On net I feel like that's probably still a good trade-off, but if it's a problem I'd suggest we look at implementing some simpler disk-based cache. Or heck, maybe we could even just upload recently-built packages to /var/www but not put them in the aptly database (our package code looks for the package file directly, it doesn't go through the repository Packages file). That would still reduce contention on aptly and be much easier to clean up: we could just create a job to delete packages more than a month old or something.