Since 2.0, resource locks are broken in multi configuration projects about lockable-resources-plugin HOT 5 CLOSED

Is there any activity on this issue? GitHub doesn't show any referent PRs.

I also see this bug with two entirely distinct freestyle jobs locking on the same resource.

I'm currently living with the fact that I have to carefully remember to not upgrade this plugin because it will break half of our builds.

from lockable-resources-plugin.

Downgrading only helps if you save the job afterwards.

More specifically the issue is present when the job config looks like this:

    <org.jenkins.plugins.lockableresources.RequiredResourcesProperty plugin="[email protected]">
      <resourceNames>ResX ResY</resourceNames>
      <resourceNamesVar></resourceNamesVar>
      <resourceNumber></resourceNumber>
      <labelName></labelName>
    </org.jenkins.plugins.lockableresources.RequiredResourcesProperty>

But this works fine:

    <org.jenkins.plugins.lockableresources.RequiredResourcesProperty plugin="[email protected]">
      <resourceNames>ResX ResY</resourceNames>
    </org.jenkins.plugins.lockableresources.RequiredResourcesProperty>

from lockable-resources-plugin.

This should have been fixed with #89 (?) - so since 2.2 (March 2018) this should work as expected...

from lockable-resources-plugin.

IIRC, we tested the 2.2 release when it came out and confirmed that it fixed the issue for us. At the very least, we upgraded and nobody in our team has complained in the past year.

We've also stopped relying on this plugin so much for our builds, so it's possible that we wouldn't catch it in our organization if it were still happening in rare cases.

from lockable-resources-plugin.

@sirosen Thanks for the feedback, I'm closing this issue then - Feel free to reopen if the issue reappears.

from lockable-resources-plugin.