Automating Distro Updates in CI
paretosecurity.com
Automating Distro Updates in CI
1–7 of 7 posts
Re: Automating Distro Updates in CI
#2Renovatebot would solve this consistently and is more broadly applicable.
Re: Automating Distro Updates in CI
#3Renovatebot would solve this consistently and is more broadly applicable.
Renovatebot (GitLab)/dependabot (GitHub) tends to update versions rather than add new entries.
Re: Automating Distro Updates in CI
#4i don't think distro updates belong in CI.
Re: Automating Distro Updates in CI
#5> remember to bump Ubuntu when a new LTS comes out
I'm sorry... what?
https://ubuntu.com/about/release-cycle
> LTS or ‘Long Term Support’ releases are published every two years in April
I wouldn't want to work somewhere that can't plan around something as simple as this.
Re: Automating Distro Updates in CI
#6> remember to bump Ubuntu when a new LTS comes out I'm sorry... what? https://ubuntu.com/about/release-cycle > LTS or ‘Long Term Support’ releases are published every two years in April I wouldn't want to work somewhere that can't plan around something as simple as this.
Places can plan around this, but it seems silly to have calendar invitations and project management and manual work when you can just automate it. I wouldn't want to work anywhere that couldn't automate it this if it became the top of the automation priority list.
Re: Automating Distro Updates in CI
#7i don't think distro updates belong in CI.
To be fair, it’s versions of Linux distros they test against in their CI.