-
Notifications
You must be signed in to change notification settings - Fork 187
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
ConcurrentModificationException when serializing LockedResourcesBuildAction#lockedResources #703
Comments
Oh no, pls not again. :-( We use the changes over 3 mounts and does not find some side effects. When you agree, I can merge the PR (without review again :-( ) and you need just update the plugin. Back to your question. This is failure in this plugin, and you does not need to update some other plugins. It will be great, when you install this version on your Jenkins instance Anyway: just give me feadback and I will try to merge it into master, so our issues will be fixed ASAP ;-) |
Ok, will give it a try, thanks |
|
Let me know next week. When it works over few days without issues on your side, I will megre it into official master. Thx for your feadback |
No, We does not save the LRM state. It cost too much time for us. |
I analysed the changes now. I does not see reason, why it might fail the save() function. |
Yes, somebody constantly resets ownership of this file. If I change owner:group to jenkins:jenkins, the error goes away, however very soon the permissions are reset to root:jenkins. I'll try to figure out who can it be, but the thing is that we have the same root:jenkins permissions on other jenkins instances with older plugins and this doesn't lead to any problems. One more point is that in order to update LR, we had to update a bunch of other plugins, maybe some of that update influences our scenario. Will check. But as for original problem with serialization - likely yes, the new version solves it, never seen it again. |
Great news, I will merge it now into master. |
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
Debian 12
Reproduction steps
Run a pipeline consuming several dozens of lockable resources.
Several hundreds such pipelines a day often trigger such an issue
Expected Results
Pipeline works fine
Actual Results
From time to time, pipeline fails and we see the following in the end of console log:
Unfortunately this breaks BlueOcean representation for the pipelines.
Anything else?
#597 was about the same problem but with older plugin version.
We updated to
1246.v28b_e4cc6fa_16
since we were able to update to it without touching any other plugins, so plugin version list from the description of this bug is still valid. This version should have all fixes mentioned in #597Do you think that it makes sense to update some other plugins, as well? Or the reason still lies somewhere in lockable-resources itself?
Are you interested in contributing a fix?
No response
The text was updated successfully, but these errors were encountered: