|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Code changed in jenkins
User: Daniel Beck
Path:
core/src/main/java/hudson/model/queue/CauseOfBlockage.java
core/src/main/resources/hudson/model/Messages.properties
core/src/main/resources/hudson/model/queue/CauseOfBlockage/BecauseLabelIsOffline/summary.jelly
core/src/main/resources/hudson/model/queue/CauseOfBlockage/BecauseLabelIsOffline/summary.properties
http://jenkins-ci.org/commit/jenkins/5aa32c8681410eccfabf68397692f2402e615a48
Log:
[FIX JENKINS-17114] Distinguish 'nodes offline' from 'no nodes'
Jenkins currently does not distinguish between 'All nodes for a
label are offline' and 'There are no nodes for a label'. This is
exacerbated by the current wording:
All nodes of label 'foo' are offline
Instead of just changing the wording to something not seeming to
imply existence of such nodes, add a second wording that clearly
states that there are no such nodes.