Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-41156

[Pipeline] Have shell and batch steps be renameable

    Details

    • Similar Issues:

      Description

      Our build process typically requires a series of batch calls into our build system. However, in looking at the steps of a build in pipeline, this results in a bunch of steps which are just "Windows Batch Script". This makes them difficult to differentiate from eachother, and provides a poor reporting experience overall.

      Could we have an optional second argument to the batch step (and the shell step as well) to specify a name for the step, which would get added as a LabelAction?

        Attachments

          Issue Links

            Activity

            Hide
            rhutchison Ryan Hutchison added a comment -

            Jesse Glick I don't believe it's supported within parallel steps?

            Show
            rhutchison Ryan Hutchison added a comment - Jesse Glick I don't believe it's supported within parallel steps?
            Hide
            jglick Jesse Glick added a comment -

            You can put stage wherever you want (except when using Declarative). What a particular visualization plugin in its current implementation will or will not render is another matter. Pipeline Steps will show it.

            Show
            jglick Jesse Glick added a comment - You can put stage wherever you want (except when using Declarative). What a particular visualization plugin in its current implementation will or will not render is another matter. Pipeline Steps will show it.
            Hide
            philmcardlecg Phil McArdle added a comment - - edited

            Is there a separate bug for Blue Ocean not being able to visualize this, then?

            node() {
                stage('Run Everything') {
                    parallel firstBranch: {
                        stage('Get Current Working Directory') {
                            sh(script: 'pwd')
                        }        
                    }, secondBranch: {
                        stage('Test') {
                            println 'Second Branch Test'
                        }        
                    }
                }
            }
            

            Show
            philmcardlecg Phil McArdle added a comment - - edited Is there a separate bug for Blue Ocean not being able to visualize this, then? node() { stage( 'Run Everything' ) { parallel firstBranch: { stage( 'Get Current Working Directory' ) { sh(script: 'pwd' ) } }, secondBranch: { stage( 'Test' ) { println 'Second Branch Test' } } } }
            Hide
            jglick Jesse Glick added a comment -

            Yes there is. I do not have time to look it up unfortunately.

            Show
            jglick Jesse Glick added a comment - Yes there is. I do not have time to look it up unfortunately.
            Hide
            philmcardlecg Phil McArdle added a comment -

            Looks like I wanted JENKINS-38442

            Show
            philmcardlecg Phil McArdle added a comment - Looks like I wanted JENKINS-38442

              People

              • Assignee:
                Unassigned
                Reporter:
                ssutherland Sean Sutherland
              • Votes:
                2 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: