An example I forgot to add to previous post, when I was upgrading 2.204.6 to latest LTS on one of my instance: Do upgrade of:
1. Compatible plugins 2. Core to 2.222.4 3. Compatible plugins 4. Core to 2.263.4 5. Compatible plugins 6. Plugin matrix-auth to 2.6.11 <https://updates.jenkins.io/download/plugins/matrix-auth/2.6.11/matrix-auth.hpi> with wget 7. Plugin role-strategy to 3.1.1 <https://updates.jenkins.io/download/plugins/role-strategy/3.1.1/role-strategy.hpi> with wget 8. Enable backup account in security settings, because LDAP will not work, update plugin active-ditrectory to 2.20 <https://updates.jenkins.io/download/plugins/active-directory/2.20/active-directory.hpi> with wget 9. Core to 2.277.1 10. Compatible plugins 11. Core to 2.289.1 12. Compatible plugins via GUI, except role-strategy and matrix-auth 13. Update AD plugin setting to “Require TLS”, remove forceLdaps=true runtime parameter 14. Core to 2.289.3 Jenkins restart was applied after every step, so it took a little downtime. piątek, 16 września 2022 o 09:17:49 UTC+2 djez...@gmail.com napisał(a): > I noticed that transisiton between 2.263.4 and 2.277.1 is very problematic > because of backwards compatibility breaking changes. > > https://www.jenkins.io/doc/upgrade-guide/2.277/#upgrading-to-jenkins-lts-2-277-1 > > When I have to do it on instances I manage, I create a copy and by trial > and error method I determine which versions to upgrade to, which plugins to > keep, and which can be safely upgraded to latest compatible versions. > > Sorry for not being specific, but every instance is different and how to > proceed heavily depends on your configuration. > > środa, 14 września 2022 o 04:05:09 UTC+2 Mark Waite napisał(a): > >> On Tuesday, September 13, 2022 at 5:31:07 PM UTC-6 Robert wrote: >> >>> Currently I see this in the system log >>> >>> It appears whenever you look at a job from the dashboard and it needs to >>> show it’s build history. >>> >>> Kind of puzzling why this happens for some jobs and not others. >>> >>> The jobs appear under a Folder. >>> >>> java.lang.NoSuchMethodError: com.google >>> .common.util.concurrent.MoreExecutors.sameThreadExecutor()com/google/common/util/concurrent/ListeningExecutorService >>> >>> >> The instructions in the upgrade guides for the intervening versions >> between 2..263 and 2.346.2 will help with this issue. Your upgrade crosses >> several major changes in Jenkins. The upgrade guides provide critical >> instructions. >> >> Specifically, be sure that you have upgraded all the plugins to their >> most recent releases. >> >> >>> this all is in a stack where it looks like it’s calling getLastBuild on >>> LazyBuildMixIn >>> >>> deeper down it’s doing >>> AbstractFolder.getBuildHealthReports(AbstractFolder.java:925) >>> >>> It’s using idk 1.8.0_121 on the controller >>> >>> >> Please upgrade to a newer version of Java 8. Eclipse Temurin provides >> JDK 1.8.0_345 at no charge. Other Java providers (Red Hat, Azul, Amazon) >> also provide similar versions at no charge. >> >> Even better to upgrade to a Java 11 version. The Jenkins project no >> longer support Java 8 on the controller. See the >> https://www.jenkins.io/blog/2022/06/28/require-java-11/ for the >> announcement from June 2022. >> >> >>> It’s noticeable that >>> >>> Some jobs are able to show their build history >>> >>> Some jobs cannot and error with >>> >>> “A problem occurred while processing the request” >>> >>> I’m using Folders plugin 6.4 >>> >>> >> Folders plugin was released 4 years ago. Upgrade the plugins. >> >> Mark Waite >> > -- 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/64cfffd8-d49b-4b9a-ae11-40a28b7966c3n%40googlegroups.com.
