Feature #11940
Consider removing apt-cacher-ng usage from our Jenkins build jobs
0%
Description
Our apt-cacher-ng would need some tweaks to be a bit more smart regarding building in Jenkins, but at the same time it does not make much sense to use an APT cache on the isobuilders while all the packages they are downloading are already hosted on lizard.
So we should probably just remove the apt cache configuration from our isobuilders. We need to test to see if it breaks something or improve the build time though.
A couple things were already attempted in this area, see https://git.tails.boum.org/puppet-tails/log/files/apt-cacher-ng/isobuilds.conf as a starting point.
Subtasks
History
#1 Updated by intrigeri 2019-09-20 10:35:47
- Description updated
#2 Updated by intrigeri 2019-09-20 10:36:13
- Category changed from Infrastructure to Continuous Integration
#3 Updated by intrigeri 2019-09-20 10:38:33
- Description updated
#4 Updated by intrigeri 2019-09-20 10:41:16
- Subject changed from Consider removing apt-cacher-ng usage from our isobuilders to Consider removing apt-cacher-ng usage from our Jenkins build jobs
This lives in macros/builders.yaml in jenkins-jobs.git: look for http_proxy and extproxy there. To test the idea this ticket is about:
- remove the
http_proxybits - replace
extproxywithnoproxy
#5 Updated by intrigeri 2019-09-20 10:44:05
- Assignee set to intrigeri
We’ve announced a Jenkins maintenance window this week (Thu-Sun) so it seems to be a good time to try this: developers are aware that things may break.
#6 Updated by intrigeri 2019-09-20 11:35:47
- Assignee deleted (
intrigeri)
https://git.tails.boum.org/jenkins-jobs/commit/?id=0b52c1b2ef496ca4aa7538c32a26818734d23434
This works fine for the initial APT operations but 10-tbb fails with noproxy. So next step is: fix the noproxy build option. I’ll file a ticket for that.
#7 Updated by intrigeri 2019-09-20 11:39:15
- blocked by Bug #17075: noproxy build option is broken added