Unattended-upgrades for Jenkins 2.x
written on Monday, July 18, 2016
With the release of Jenkins 2.0, the project moved to a new domain: Jenkins.io. Unfortunately, the Debian repository was moved as well and broke our unattended-upgrades configuration for Jenkins. Luckily, this is rather easy to debug using (unattended-upgrade --debug). The command prints all the required details to fix the unattended-upgrades configuration.
The following unattended-upgrade configuration works with Jenkins 2.x:
Unattended-Upgrade::Origins-Pattern {
"origin=jenkins.io,suite=binary";
};