until I updated Jenkins to 2.32.1

Doesn't mean anything unless you mention what version you were running before.

Any reason to not use the version 2.14 ?

danielbeck until I updated Jenkins to 2.32.1
Doesn't mean anything unless you mention what version you were running before.

Unfortunately, in updating from 2.32.1 to 2.32.2, any evidence as to the version that was installed prior to 2.32.1 was destroyed, because 2.32.2 overwrote jenkins.war.bak. I can't find any kind of installation history in the UI under 'Manage Jenkins', nor does there appear to be any kind of installation log file, nor is there any mention of 2.32.* in any of the error logs. It's a shame that Jenkins does not record these version bumps anywhere given that this is apparently vital diagnostic information.

I seem to recall doing another such update a few months ago, but there I'm not aware of any way to discover exactly when that was. Sorry I can't be any more precise than this.

aheritier I'd prefer not to downgrade if at all possible, as this can lead to loss of configuration information and/or plug-in compatibility problems.

adrianp I was talking about the maven plugin . You are using the version 2.13 and 2.14 is out for a several months. 2.15 is in progress

2.15.1 is out. If you can tell me if you have the same issue with it ...

I hope it's not related to our upgrade to guice but it is strange it was already in 2.32.1
https://github.com/jenkinsci/jenkins/commit/f64a2231396ad8de1d164bce20dc31751714b607

https://github.com/google/guice/issues/899 was closed but I don't understand if the fix was done in guice 4 final or sisu cc jglick

Perhaps the upgrade/cleanup of the maven-plugin 2.15 could help here

I don't understand if the fix was done in guice 4 final or sisu

Neither—the bug was on the Jenkins side, using an old component.

thanks jglick
Let us know adrianp if you have the problem with Jenkins 2.32.1 and maven plugin 2.15.1 please

One detail I didn't include in my original description: on Jenkins 2.32.2, I had actually been able to resolve the issue by specifying explicit values for Source Code Management > Subversion > Modules > Local module directory. These were originally blank, relying on the behaviour described in the embedded help panel whereby a blank local module directory is checked out to a directory whose name is the last path segment. Configured thus, the job was working fine prior to Maven 2.32.1 but broke in that release. Subsequently, I was able to get the job building again by specifying an explicit local module directory value for each repository URL.

Now, running Jenkins 2.32.1 and Maven Integration Plugin 2.15.1, with the explicit local module directory settings once again blank, the job now runs. So whatever the problem was, it now appears to be resolved with the latest and greatest of everything installed. Many thanks for your assistance.

Sum-up:

• OK with Jenkins 2.32.1 and Maven plugin 2.13
• KO with Jenkins 2.32.2 and Maven plugin 2.13
• OK with Jenkins 2.32.2 and Maven plugin 2.13 + workaround: specifying explicit values for Source Code Management > Subversion > Modules > Local module directory.
• OK with Jenkins 2.32.2 and Maven plugin 2.15.1

• KO with Jenkins 2.41 and Maven plugin 2.9
• OK with Jenkins 2.41 and Maven plugin 2.15.1

In my case, Maven plugin 2.15.1 solves this issue, thanks.

Last week when I upgraded to Maven Integration Plugin 2.14 I also upgraded all the other plug-ins, which included Subversion Plugin 2.7.1. But before I got a chance to test that combination I was called off to do some other work, then this morning I saw the comments about 2.15.1 being available so I once again upgraded all plug-ins, which fixed the problem and obviated the need for the workaround.

The sum-up should be:

• OK with Jenkins < 2.32.1 (not sure which) and the Maven plug-in which came with that version
• KO with Jenkins 2.32.1 and Maven plugin 2.13
• KO with Jenkins 2.32.2 and Maven plugin 2.13
• OK with Jenkins 2.32.2 and Maven plugin 2.13 + workaround: specifying explicit values for Source Code Management > Subversion > Modules > Local module directory.
• OK with Jenkins 2.32.2 and Maven plugin 2.15.1

thx for you feedback sebg73
Maven plugin users don't hesitate to comment here like Sébastien if you have also this error. It may help us to better identify the the change/issue even if it is fixed by the latest version of the plugin (from my POV it smells the issue related to the guice/sisu update in core and maven plugin cc oleg_nenashev)

The sum-up:

• OK with Jenkins < 2.32.1 (not sure which) and the Maven plug-in which came with that version
• KO with Jenkins 2.32.1 and Maven plugin 2.13
• KO with Jenkins 2.32.2 and Maven plugin 2.13
• OK with Jenkins 2.32.2 and Maven plugin 2.13 + workaround: specifying explicit values for Source Code Management > Subversion > Modules > Local module directory.
• OK with Jenkins 2.32.2 and Maven plugin 2.15.1
• KO with Jenkins 2.41 and Maven plugin 2.9
• OK with Jenkins 2.41 and Maven plugin 2.15.1

Upgrade to Guice Final 4.0 was done in Jenkins 2.28

Added in 2.15.1 changelog

This issue is still exist and can be re-produced in:

Jenkins-2.46.2 and Maven Integration plugin v2.17