Jesse Glick For what it's worth, I'm using Blue Ocean and I agree with Eloy Lafuente that this particular feature is not equivalent to https://issues.jenkins-ci.org/browse/JENKINS-26107.
For example, I have a pipeline with 7 stages that builds an ionic 2 app, and ultimately pushes it iTunes TestFlight. 7 stages is honestly more than I want already, and so a solution that adds more stages does not meet my need.
Some of these stages are rather complicated, with 5-10 steps. These are mostly shell scripts that delegate to CLI tools like fastlane and npm. It would be nice if the blue ocean UI gave me the ability to label these steps, so I don't get 10 blocks that all say "shell script."
Of course I could write custom steps for all of these and provide my own labeling mechanism, but that is much more work than I want to do and these seems like a simple enough usecase that the out of the box shell step should support it. I'm also in favor of the syntax proposed (maybe use label instead of name?)
sh cmd: "command here", name: "label here"