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

[Pipeline] Have shell and batch steps be renameable

    XMLWordPrintable

Details

    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

          duplicates

          Task - A task that needs to be done. JENKINS-37324 We would like a more meaningful description of a step

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed
          is related to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. JENKINS-38442 View sequential stages in the pipeline visualization graph

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            View 5 older comments
            rhutchison Ryan Hutchison added a comment -

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

            rhutchison Ryan Hutchison added a comment - jglick I don't believe it's supported within parallel steps?
            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.

            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.
            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'
            }        
        }
    }
}

            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' } } } }
            jglick Jesse Glick added a comment -

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

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

            Looks like I wanted JENKINS-38442

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

            People

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

              Dates

                Created:
                Updated:
                Resolved: