Michael Neale
added a comment - 2016-08-15 00:23 Can labelled blocks be nested? if so, why? What is the concrete use case for this? (if they are allowed, it has made things more complicated than they were before, when there were no block scoping).
cc Andrew Bayer

Ryan Campbell
added a comment - 2016-09-07 22:11 For those like me who are confused: the story is called "labeled block" but was actually fixed by allowing the stage step to accept a block (which we call 'block-scoped stage step').

I've tried out something which seems to have broken blue ocean, and i thought that I will be able to have a specific label for the shell script but this didn't happen. Also the support for this in stage view doesn't seem to be pretty good.

Here is the code I've created
def test = [:]

test["a"] = {
stage ("a") {
stage ("ab")

{
sh "echo stage abc"
}

stage ("xyz")

{
sh "echo stage xyz"
}

}
}

test["b"] = {
stage ("b") {
stage ("bb")

{
sh "echo stage bb"
}

stage ("bxz")

{
sh "echo stage bxz"
}

}
}
node {
//stage 'start'
parallel test
stage ('middle')

{
sh "echo middle"
}

}

This code actually breaks blue-ocean from showing the workflow, and it shows now the log only as attached basically i wanted to group each shell script in a separate label since it seems there are no way to change "Shell Script" from showing up. This also shows multiple stages inside stage view which is really ugly as attached

mohamed badran can you put that in a differnet ticket under the "blueocean-plugin" component? It fails to showing just the log so you see something. nested stages aren't well supported yet, so would need to decide how to lay that out.

Michael Neale
added a comment - 2016-09-22 10:37 mohamed badran can you put that in a differnet ticket under the "blueocean-plugin" component? It fails to showing just the log so you see something. nested stages aren't well supported yet, so would need to decide how to lay that out.

Kyle Flavin
added a comment - 2016-10-04 00:13 Is the concurrency parameter no longer available? I'm converting some legacy code to use the new format. We have a lot of stuff that looks like this:
stage name: 's1: do something', concurrency: 1
...
stage name: 's2: do something else', concurrency: 1
...
Maybe it's not necessary since we're setting the concurrency to "1" anyway?

Owen Mehegan
added a comment - 2016-10-25 22:41 Kyle Flavin concurrency as a parameter to the stage step is deprecated, in favor of the milestone step. See https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Stage+Step+Plugin and https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Milestone+Step+Plugin

Yes, possibly. But you generally wouldn't "label a command", probably more a couple of them to produce not just a serie of staged named after the called commands, but that stage is actually doing ("checking code coverage" or whatever).

Baptiste Mathus
added a comment - 2018-02-16 16:14 Yes, possibly. But you generally wouldn't "label a command", probably more a couple of them to produce not just a serie of staged named after the called commands, but that stage is actually doing ("checking code coverage" or whatever).