|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-15209) Only update perforce lab... Verbitan (JIRA)
- [JIRA] (JENKINS-15209) Only update perforc... [email protected] (JIRA)
- [JIRA] (JENKINS-15209) Only update perforc... Verbitan (JIRA)
- [JIRA] (JENKINS-15209) Only update perforc... [email protected] (JIRA)
- [JIRA] (JENKINS-15209) Only update perforc... [email protected] (JIRA)

That would also work. Currently if the label is locked, the plugin just goes and unlocks it for you.
What would the desired behaviour be when the plugin tries to update a locked label? Failing the entire build seems a little draconian, however you'd still want to know if the labelling failed...