-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins 2.73.1
blueocean 1.2.4
blueocean-autofavorite 1.0.0
blueocean-bitbucket-pipeline 1.2.4
blueocean-commons 1.2.4
blueocean-config 1.2.4
blueocean-dashboard 1.2.4
blueocean-display-url 2.1.0
blueocean-events 1.2.4
blueocean-git-pipeline 1.2.4
blueocean-github-pipeline 1.2.4
blueocean-i18n 1.2.4
blueocean-jira 1.2.4
blueocean-jwt 1.2.4
blueocean-personalization 1.2.4
blueocean-pipeline-api-impl 1.2.4
blueocean-pipeline-editor 1.2.4
blueocean-pipeline-scm-api 1.2.4
blueocean-rest 1.2.4
blueocean-rest-impl 1.2.4
blueocean-web 1.2.4Jenkins 2.73.1 blueocean 1.2.4 blueocean-autofavorite 1.0.0 blueocean-bitbucket-pipeline 1.2.4 blueocean-commons 1.2.4 blueocean-config 1.2.4 blueocean-dashboard 1.2.4 blueocean-display-url 2.1.0 blueocean-events 1.2.4 blueocean-git-pipeline 1.2.4 blueocean-github-pipeline 1.2.4 blueocean-i18n 1.2.4 blueocean-jira 1.2.4 blueocean-jwt 1.2.4 blueocean-personalization 1.2.4 blueocean-pipeline-api-impl 1.2.4 blueocean-pipeline-editor 1.2.4 blueocean-pipeline-scm-api 1.2.4 blueocean-rest 1.2.4 blueocean-rest-impl 1.2.4 blueocean-web 1.2.4
When my build starts (using the pipeline global library) the blue ocean pipeline view displays the message:
Jenkins doesn’t have label stable&&docker&&ubuntu1604&&sudo&&"language:groovy"&&env&&jdk
However, that label exists and is serviced by a cloud. My job eventually populates after the node is provisioned. It would be nice if the message was a little more clear for users so that it states something along the lines of:
Jenkins is waiting on N cloud(s) to provision nodes for label stable&&docker&&ubuntu1604&&sudo&&"language:groovy"&&env&&jdk