ConcurrentModificationException-at-LockedResourcesBuildAction

[mPokornyETM]

Using many parallel locks at the same time in the same job (like parallel stages does) leads to java.util.ConcurrentModificationException in the org.jenkins.plugins.lockableresources.actions.LockedResourcesBuildAction#lockedResources

Testing done

Writing tests for this scenario is too hard, because no body can really simulate it. It happens sometimes on our environment.

Proposed upgrade guidelines

N/A

Localizations

N/A

Submitter checklist

• [ ] The Jira / Github issue, if it exists, is well-described.
• [x] The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples).
  • The changelog generator for plugins uses the pull request title as the changelog entry.
  • Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during the upgrade.
• [x] There is automated testing or an explanation that explains why this change has no tests.
• [ ] New public functions for internal use only are annotated with @NoExternalUse. In case it is used by non java code the Used by {@code <panel>.jelly} Javadocs are annotated.
• [ ] New or substantially changed JavaScript is not defined inline and does not call eval to ease the future introduction of Content Security Policy (CSP) directives (see documentation).
• [ ] For dependency updates, there are links to external changelogs and, if possible, full differentials.
• [ ] For new APIs and extension points, there is a link to at least one consumer.
• [ ] Any localizations are transferred to *.properties files.
• [ ] Changes in the interface are documented also as examples.

[jamoralp]

Is it known when this issue started? We're facing it once in a while now (hoping this fix is merged soon!) but we've been using in our company Jenkins lockable resources for a couple of years and never ran into this before. Would be great to know which version introduced the issue to at least downgrade to a previous one until this is merged and released

[mPokornyETM]

Is it known when this issue started? We're facing it once in a while now (hoping this fix is merged soon!) but we've been using in our company Jenkins lockable resources for a couple of years and never ran into this before. Would be great to know which version introduced the issue to at least downgrade to a previous one until this is merged and released

I think you mean #623 This failure might happens, when parallel stages in the same job are running at the same time. Not on jenkins start up. Anyway u will merge it assap. One fix more is still better, then no fix