I am currently working to setup a Jenkins server for continuous integration.
One area of Jenkins maintenance I am looking at is Jenkins upgrades.
As gaining access to new Jenkins features is less important to our setup than
receiving important bug fixes and general system stability, I am considering
upgrading our Jenkins instance on the LTS release schedule. It should be noted
that we are currently working with Jenkins version 2.46.3 and would start this
schedule by upgrading to Jenkins version 2.60.1.
In looking at the documentation for [Jenkins LTS Release Line][1], it looks
like this would involve upgrading our Jenkins from the previous LTS version to
the new LTS version every 6 - 9 weeks:
> The cycle starts with picking an LTS baseline at week 0. Then, there
> is a two week period for backporting followed by two weeks for testing
> the release candidate resulting in the release of X.1. Backporting and
> RC testing is repeated twice, producing X.2 and X.3. This concludes
> the cycle for a given baseline and the new one is started immediately.
>
> The baseline release is typically between 2-5 weeks old when it is
> chosen, so X.1 LTS releases are published about 6-9 weeks after their
> baseline.
Am I correct in this understanding that if we were to keep up with the LTS
release schedule we would be upgrading our Jenkins instance about every 6 - 9
weeks?
Also, from what I have seen, if your Jenkins instance is installed via Jenkins
WAR file, then the process for upgrading the Jenkins instance to the most
recent Jenkins LTS version is:
1. Stop Jenkins running as a service.
2. Back up the Jenkins $HOME_DIRECTORY.
3. Download the latest LTS WAR file.
4. Replace the WAR file currently in $JENKINS_HOME directory with the
newest LTS WAR.
5. Start Jenkins running as a service.
6. Upgrade any plugins if necessary.
7. Restart Jenkins as a service if necessary for plugin installation.
7. Work out any Jenkins job issues caused by upgraded plugins.
Is there anything here I'm missing as far as getting our Jenkins instance onto
the LTS release schedule? Is this generally best practice? Just wanted to get
some input and advice from those with experience maintaining a Jenkins instance
on the LTS release schedule.
[1]: https://jenkins.io/download/lts/
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/BY2PR12MB0599FFD3DBC9C44D93D0E8C589D60%40BY2PR12MB0599.namprd12.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.
