-
Notifications
You must be signed in to change notification settings - Fork 186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NullPointerException after upgrade to 1156.v5e9f897ece02 #507
Comments
Do you knwo, what was the version before update? |
Yes, we were on I could not configure lockable resources because of JENKINS-70630, but today I disabled HTTP/2 to try and solve the issue. After I that I was able to add a new lockable resource and saving it seems to have triggered an update of the configuration file, which added the missing attribute and the NPE does not occur anymore: diff --git a/org.jenkins.plugins.lockableresources.LockableResourcesManager.xml b/org.jenkins.plugins.lockableresources.LockableResourcesManager.xml
index ae5ba585a5..f2a6111750 100644
--- a/org.jenkins.plugins.lockableresources.LockableResourcesManager.xml
+++ b/org.jenkins.plugins.lockableresources.LockableResourcesManager.xml
@@ -1,5 +1,5 @@
<?xml version='1.1' encoding='UTF-8'?>
-<org.jenkins.plugins.lockableresources.LockableResourcesManager plugin="[email protected]_ff25">
+<org.jenkins.plugins.lockableresources.LockableResourcesManager plugin="[email protected]">
<resources>
<org.jenkins.plugins.lockableresources.LockableResource>
<name>tests-integration-installation-0</name>
@@ -8,6 +8,7 @@
<note></note>
<stolen>false</stolen>
<ephemeral>false</ephemeral>
+ <properties/>
<queueItemId>0</queueItemId>
<queuingStarted>0</queuingStarted>
<queuedContexts/>
@@ -21,6 +22,7 @@
... I think a null check here should restore backwards compatibility. |
This has also affected us. Thank you for the workaround. Adding a new "lockable resource" caused the plugin to re-generate the XML file and add an empty |
Thx for reporting, I thinkg we need little more tests for .xml config files. My local tests was done only with JCaC, because we use it in my company and general it is the best way (currently). I will check it an try to fix it in the next release |
Bumped into this well, thanks for the suggested workaround(s), that did the trick! If desired I can dig out the previous version (from the backup) that was installed |
Ran into this issue today, thanks @andreyakostovsap for the workaround! It saved me splitting my hair trying to figure out build will fail even though it would print that lock was acquired. |
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
Debian 11
Reproduction steps
1156.v5e9f897ece02
.test
.1156.v5e9f897ece02
.Expected Results
The pipeline to succeed.
Actual Results
Anything else?
I think it is probably caused by #394. It looks like a similar situation to 434#issuecomment-1379559915 - a change to the XML format of the lockable resources configuration file causes existing resources defined in the previous version to stop working after upgrading to the latest version.
The text was updated successfully, but these errors were encountered: