|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
This is still an issue in version 1.550. We have a matrix job where often only one column of configurations is built in a single build. The next time the job is run, a different column might be built, and then the previous build gets locked, I'm assuming because it's being referenced (as "skipped") in the new build. But what this means for our matrix job is that almost every single build ends up locked.
I would like to be able to unlock these builds so that I can delete them. Rather than forcing a build to be implicitly locked because it's being referenced in a later build, why can't the reference be removed/updated if the build is deleted?