|
||||||||
|
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/groups/opt_out.
https://github.com/jenkinsci/jenkins/commit/7bbe2c8 (in 1.481) improved the behavior. A matrix build may still be locked, but only if there is a subsequent build which built fewer configurations than this one, so that this one is the source of the “last known complete” builds of certain configurations.
I have also improved the UI in the trunk for 1.510 with several fixes in https://github.com/jenkinsci/jenkins/compare/57900a235514...5b6be91d9237 to properly display the reason that a build is locked, when the locking is implicit rather than due to an explicit toggle.