![]() |
|
|
|
|
Change By:
|
Monique Maker
(24/Jun/14 11:55 AM)
|
|
Description:
|
This is not quite a bug but is a consequence of current CVS Plugin tagging start policy.
Once the tagging is not part of a build job Jenkins can not consider it in its restart constraints. Therefore when you upgrade Jenkins or some of its plugins, checking the "Restart once no jobs are running" ignores the running (manually started) tagging (if there is no job running in parallel)
and restarts regardless of the running tagging, thus breaking the tagging process
.
|
|
|
|
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.
