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

Handle skipped stages and parallels in the Pipeline Graph

    XMLWordPrintable

    Details

    • Similar Issues:
    • Sprint:
      Blue Ocean 1.2-beta3, Blue Ocean 1.2-beta4

      Description

      Ready for release

      This improvement is completed and scheduled for release in 1.2. Check the roadmap page for updates.

      Context
      The Pipeline team have added the ability to "skip" stages in the Pipeline (JENKINS-37781).

      Scope

      • Skipped stages are shown as not built
      • Declarative Pipeline will not provide flow nodes for skipped parallels so we can always assume that there won't be any skipped parallels.
      • If the first stage is skipped then the pipeline should start from a "Start" node.
      • If the last stage is skipped then the pipeline should end with a "End" node.
      • Ensure that the editors start/end nodes match the style in this mockup

      Mockup

        Attachments

          Issue Links

            Activity

            jamesdumay James Dumay created issue -
            jamesdumay James Dumay made changes -
            Field Original Value New Value
            Epic Link JENKINS-35750 [ 171713 ]
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            Hide
            jamesdumay James Dumay added a comment -

            Brody Maclean we've got to come up with a way of demonstrating this.

            Show
            jamesdumay James Dumay added a comment - Brody Maclean we've got to come up with a way of demonstrating this.
            jamesdumay James Dumay made changes -
            Remote Link This issue links to "Example Jenkinsfile (Web Link)" [ 15037 ]
            brody Brody Maclean made changes -
            Attachment screenshot-1.png [ 34793 ]
            Hide
            brody Brody Maclean added a comment -

            James Dumay – Initial idea

            Show
            brody Brody Maclean added a comment - James Dumay – Initial idea
            jamesdumay James Dumay made changes -
            Sprint tasman [ 136 ] arctic [ 131 ]
            jamesdumay James Dumay made changes -
            Rank Ranked lower
            brody Brody Maclean made changes -
            Attachment Skipped Step.png [ 34817 ]
            Hide
            brody Brody Maclean added a comment - - edited

            Zeplin https://zpl.io/Z2m0Q0l

            Start / End nodes are added when First / Last stages are skipped. (see bottom of mockup)
            Example of skipping 2 stages also at the bottom of the mockup

            Show
            brody Brody Maclean added a comment - - edited Zeplin https://zpl.io/Z2m0Q0l Start / End nodes are added when First / Last stages are skipped. (see bottom of mockup) Example of skipping 2 stages also at the bottom of the mockup
            fmiedniak Florian Miedniak made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            brody Brody Maclean made changes -
            Attachment Skipped Step.png [ 34817 ]
            brody Brody Maclean made changes -
            Attachment Skipped Step.png [ 34840 ]
            jamesdumay James Dumay made changes -
            Description The Pipeline team are adding the ability to "skip" stages in the Pipeline (JENKINS-37781) and we will need some way to show these on the pipeline graph. The Pipeline team are adding the ability to "skip" stages in the Pipeline (JENKINS-37781).

            In Scope
            * Skipped stages are shown as not built
            * Declarative Pipeline will not provide flow nodes for skipped parallels so we can always assume that there won't be any skipped parallels.
            * If the first stage is skipped then the pipeline should start from a "Start" node.
            * If the last stage is skipped then the pipeline should end with a "End" node.
            * Ensure that the editors start/end nodes match the style in this mockup
            jamesdumay James Dumay made changes -
            Assignee Brody Maclean [ brody ]
            jamesdumay James Dumay made changes -
            Status In Progress [ 3 ] Open [ 1 ]
            jamesdumay James Dumay made changes -
            Sprint arctic [ 131 ]
            jamesdumay James Dumay made changes -
            Sprint tasman [ 136 ]
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay made changes -
            Link This issue is duplicated by JENKINS-39464 [ JENKINS-39464 ]
            jamesdumay James Dumay made changes -
            Description The Pipeline team are adding the ability to "skip" stages in the Pipeline (JENKINS-37781).

            In Scope
            * Skipped stages are shown as not built
            * Declarative Pipeline will not provide flow nodes for skipped parallels so we can always assume that there won't be any skipped parallels.
            * If the first stage is skipped then the pipeline should start from a "Start" node.
            * If the last stage is skipped then the pipeline should end with a "End" node.
            * Ensure that the editors start/end nodes match the style in this mockup
            The Pipeline team are adding the ability to "skip" stages in the Pipeline (JENKINS-37781).

            In Scope
            * Skipped stages are shown as not built
            * Declarative Pipeline will not provide flow nodes for skipped parallels so we can always assume that there won't be any skipped parallels.
            * If the first stage is skipped then the pipeline should start from a "Start" node.
            * If the last stage is skipped then the pipeline should end with a "End" node.
            * Ensure that the editors start/end nodes match the style in this mockup

            Hide
            sophistifunk Josh McDonald added a comment -

            Couple of questions:

            1. Is there a compelling reason to only show start/end nodes when the first/last is skipped?
            2. Do we want to visually discriminate between "skipped because of new skip method" and "not run because previous stage failed"?
            3. Related to #2, let's say I have 10 parallel stages, but my infrastructure can only schedule 3 at a time, and one of the first 3 fails. Does Jenkins "skip" the other 7? If so, how do we want them to look?
            Show
            sophistifunk Josh McDonald added a comment - Couple of questions: Is there a compelling reason to only show start/end nodes when the first/last is skipped? Do we want to visually discriminate between "skipped because of new skip method" and "not run because previous stage failed"? Related to #2, let's say I have 10 parallel stages, but my infrastructure can only schedule 3 at a time, and one of the first 3 fails. Does Jenkins "skip" the other 7? If so, how do we want them to look?
            jamesdumay James Dumay made changes -
            Sprint tasman [ 136 ] frank [ 156 ]
            jamesdumay James Dumay made changes -
            Rank Ranked lower
            jamesdumay James Dumay made changes -
            Sprint frank [ 156 ] frank 2 [ 161 ]
            Hide
            brody Brody Maclean added a comment -

            Josh McDonald
            1. I'm happy to them shown consistently, as long as we have a fallback if width starts becoming an issue.
            2. IMO a stage that hasn't run, is a stage that hasn't run, regardless of it being skipped or not run because of previous failure.
            3. If they're in "parallel" i'd run them all even if an earlier one fails, as the user would expect them all to be run

            Show
            brody Brody Maclean added a comment - Josh McDonald 1. I'm happy to them shown consistently, as long as we have a fallback if width starts becoming an issue. 2. IMO a stage that hasn't run, is a stage that hasn't run, regardless of it being skipped or not run because of previous failure. 3. If they're in "parallel" i'd run them all even if an earlier one fails, as the user would expect them all to be run
            jamesdumay James Dumay made changes -
            Assignee Josh McDonald [ sophistifunk ]
            jamesdumay James Dumay made changes -
            Sprint tethys [ 161 ] kraken [ 166 ]
            jamesdumay James Dumay made changes -
            Rank Ranked lower
            jamesdumay James Dumay made changes -
            Link This issue is duplicated by JENKINS-39464 [ JENKINS-39464 ]
            jamesdumay James Dumay made changes -
            Sprint kraken [ 166 ] release candidate [ 171 ]
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay made changes -
            Rank Ranked lower
            jamesdumay James Dumay made changes -
            Assignee Josh McDonald [ sophistifunk ]
            jamesdumay James Dumay made changes -
            Sprint release candidate [ 171 ]
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay made changes -
            Sprint 1.1 [ 251 ]
            jamesdumay James Dumay made changes -
            Rank Ranked lower
            jamesdumay James Dumay made changes -
            Description The Pipeline team are adding the ability to "skip" stages in the Pipeline (JENKINS-37781).

            In Scope
            * Skipped stages are shown as not built
            * Declarative Pipeline will not provide flow nodes for skipped parallels so we can always assume that there won't be any skipped parallels.
            * If the first stage is skipped then the pipeline should start from a "Start" node.
            * If the last stage is skipped then the pipeline should end with a "End" node.
            * Ensure that the editors start/end nodes match the style in this mockup

            The Pipeline team are adding the ability to "skip" stages in the Pipeline (JENKINS-37781).

            In Scope
            * Skipped stages are shown as not built
            * Declarative Pipeline will not provide flow nodes for skipped parallels so we can always assume that there won't be any skipped parallels.
            * If the first stage is skipped then the pipeline should start from a "Start" node.
            * If the last stage is skipped then the pipeline should end with a "End" node.
            * Ensure that the editors start/end nodes match the style in this mockup

            *Mockup*
             !Skipped Step.png|thumbnail!
            jamesdumay James Dumay made changes -
            Description The Pipeline team are adding the ability to "skip" stages in the Pipeline (JENKINS-37781).

            In Scope
            * Skipped stages are shown as not built
            * Declarative Pipeline will not provide flow nodes for skipped parallels so we can always assume that there won't be any skipped parallels.
            * If the first stage is skipped then the pipeline should start from a "Start" node.
            * If the last stage is skipped then the pipeline should end with a "End" node.
            * Ensure that the editors start/end nodes match the style in this mockup

            *Mockup*
             !Skipped Step.png|thumbnail!
            *Context*
            The Pipeline team have added the ability to "skip" stages in the Pipeline (JENKINS-37781).

            *Scope*
            * Skipped stages are shown as not built
            * Declarative Pipeline will not provide flow nodes for skipped parallels so we can always assume that there won't be any skipped parallels.
            * If the first stage is skipped then the pipeline should start from a "Start" node.
            * If the last stage is skipped then the pipeline should end with a "End" node.
            * Ensure that the editors start/end nodes match the style in this mockup

            *Mockup*
             !Skipped Step.png|thumbnail!
            michaelneale Michael Neale made changes -
            Priority Minor [ 4 ] Major [ 3 ]
            Hide
            michaelneale Michael Neale added a comment -

            Bumped this up a bit - as a few people are asking for this as it is a most useful feature when they migrate to pipeline. This looks like a non trivial bit of work, so perhaps could be split so that a first pass just shows the node correctly as some skipped visual state before the svg code is changed - thoughts James Dumay

            Show
            michaelneale Michael Neale added a comment - Bumped this up a bit - as a few people are asking for this as it is a most useful feature when they migrate to pipeline. This looks like a non trivial bit of work, so perhaps could be split so that a first pass just shows the node correctly as some skipped visual state before the svg code is changed - thoughts James Dumay
            jamesdumay James Dumay made changes -
            Labels pipeline-improvement
            jamesdumay James Dumay made changes -
            Sprint Blue Ocean up next [ 251 ] Blue Ocean 1.2 [ 296 ]
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay made changes -
            Sprint Blue Ocean 1.2 [ 296 ] Blue Ocean 1.3 [ 311 ]
            Hide
            jamesdumay James Dumay added a comment -

            Michael Neale this is on the plan for the pipeline papercuts post-editor work.

            Show
            jamesdumay James Dumay added a comment - Michael Neale this is on the plan for the pipeline papercuts post-editor work.
            jamesdumay James Dumay made changes -
            Epic Link JENKINS-35750 [ 171713 ] JENKINS-43952 [ 181484 ]
            jamesdumay James Dumay made changes -
            Epic Link JENKINS-43952 [ 181484 ] JENKINS-43953 [ 181485 ]
            jamesdumay James Dumay made changes -
            Link This issue is duplicated by JENKINS-44464 [ JENKINS-44464 ]
            jamesdumay James Dumay made changes -
            Sprint Blue Ocean 1.4 [ 311 ] Blue Ocean 1.3 [ 296 ]
            jamesdumay James Dumay made changes -
            Rank Ranked lower
            Hide
            reinholdfuereder Reinhold Füreder added a comment -

            Since I also just stumbled over the linked issue JENKINS-44464 reported by Rob White – (a) confusing/surprising colour and (b) "Unknow" typo in title, where ideally even the reason should be stated – maybe a more pragmatic (first?) approach could be:

            • replace purple with white colour (i.e. just a black circle with no/white filling)
            • replace title message "Unknow" with "Skipped due to [expression|branch|...]" (to give a reason, but presumably avoiding giving too many details)
            • leave the stage connecting lines as is
            Show
            reinholdfuereder Reinhold Füreder added a comment - Since I also just stumbled over the linked issue JENKINS-44464 reported by Rob White – (a) confusing/surprising colour and (b) "Unknow" typo in title, where ideally even the reason should be stated – maybe a more pragmatic (first?) approach could be: replace purple with white colour (i.e. just a black circle with no/white filling) replace title message "Unknow" with "Skipped due to [expression|branch|...] " (to give a reason, but presumably avoiding giving too many details) leave the stage connecting lines as is
            Hide
            sophistifunk Josh McDonald added a comment -

            Purple isn't "skipped", it's "unknown status" - it's meant to stand out because it means either the UI needs to be updated or the server is sending bad data.

            Show
            sophistifunk Josh McDonald added a comment - Purple isn't "skipped", it's "unknown status" - it's meant to stand out because it means either the UI needs to be updated or the server is sending bad data.
            Hide
            wimnat Rob White added a comment -

             I would like to be able to completely hide skipped stages.

            I have a pipeline that does a different build depending on branch - i don't really want to see something like this:

            Checkout -> Build (develop) (SKIPPED) -> Build (master) -> Build (feature) (SKIPPED) -> Deploy

            It would be great if there was a per project toggle that would hide the skipped steps.  With this toggle on it would look something like:

            Checkout -> Build (master) -> Deploy

            Show
            wimnat Rob White added a comment -  I would like to be able to completely hide skipped stages. I have a pipeline that does a different build depending on branch - i don't really want to see something like this: Checkout -> Build (develop) (SKIPPED) -> Build (master) -> Build (feature) (SKIPPED) -> Deploy It would be great if there was a per project toggle that would hide the skipped steps.  With this toggle on it would look something like: Checkout -> Build (master) -> Deploy
            jamesdumay James Dumay made changes -
            Description *Context*
            The Pipeline team have added the ability to "skip" stages in the Pipeline (JENKINS-37781).

            *Scope*
            * Skipped stages are shown as not built
            * Declarative Pipeline will not provide flow nodes for skipped parallels so we can always assume that there won't be any skipped parallels.
            * If the first stage is skipped then the pipeline should start from a "Start" node.
            * If the last stage is skipped then the pipeline should end with a "End" node.
            * Ensure that the editors start/end nodes match the style in this mockup

            *Mockup*
             !Skipped Step.png|thumbnail!
            {panel:title=Improvement on roadmap|titleBGColor=#3878de|titleColor=white}
            This improvement is on the Blue Ocean project roadmap. Check the [roadmap page|https://jenkins.io/projects/blueocean/roadmap/] for updates.
            {panel}

            *Context*
            The Pipeline team have added the ability to "skip" stages in the Pipeline (JENKINS-37781).

            *Scope*
            * Skipped stages are shown as not built
            * Declarative Pipeline will not provide flow nodes for skipped parallels so we can always assume that there won't be any skipped parallels.
            * If the first stage is skipped then the pipeline should start from a "Start" node.
            * If the last stage is skipped then the pipeline should end with a "End" node.
            * Ensure that the editors start/end nodes match the style in this mockup

            *Mockup*
             !Skipped Step.png|thumbnail!
            jamesdumay James Dumay made changes -
            Assignee Josh McDonald [ sophistifunk ]
            jamesdumay James Dumay made changes -
            Sprint Blue Ocean 1.3 [ 296 ] Blue Ocean 1.2-beta3 [ 346 ]
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay made changes -
            Priority Major [ 3 ] Critical [ 2 ]
            sophistifunk Josh McDonald made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            jamesdumay James Dumay made changes -
            Sprint Blue Ocean 1.2-beta3 [ 346 ] Blue Ocean 1.2-beta3, Blue Ocean 1.2-beta4 [ 346, 361 ]
            jamesdumay James Dumay made changes -
            Status In Progress [ 3 ] In Review [ 10005 ]
            michaelneale Michael Neale made changes -
            Resolution Fixed [ 1 ]
            Status In Review [ 10005 ] Resolved [ 5 ]
            jamesdumay James Dumay made changes -
            Description {panel:title=Improvement on roadmap|titleBGColor=#3878de|titleColor=white}
            This improvement is on the Blue Ocean project roadmap. Check the [roadmap page|https://jenkins.io/projects/blueocean/roadmap/] for updates.
            {panel}

            *Context*
            The Pipeline team have added the ability to "skip" stages in the Pipeline (JENKINS-37781).

            *Scope*
            * Skipped stages are shown as not built
            * Declarative Pipeline will not provide flow nodes for skipped parallels so we can always assume that there won't be any skipped parallels.
            * If the first stage is skipped then the pipeline should start from a "Start" node.
            * If the last stage is skipped then the pipeline should end with a "End" node.
            * Ensure that the editors start/end nodes match the style in this mockup

            *Mockup*
             !Skipped Step.png|thumbnail!
            {panel:title=Ready for release|titleBGColor=#8CC04F|titleColor=white}
            This improvement is completed and scheduled for release in 1.2. Check the [roadmap page|https://jenkins.io/projects/blueocean/roadmap/] for updates.
            {panel}

            *Context*
            The Pipeline team have added the ability to "skip" stages in the Pipeline (JENKINS-37781).

            *Scope*
            * Skipped stages are shown as not built
            * Declarative Pipeline will not provide flow nodes for skipped parallels so we can always assume that there won't be any skipped parallels.
            * If the first stage is skipped then the pipeline should start from a "Start" node.
            * If the last stage is skipped then the pipeline should end with a "End" node.
            * Ensure that the editors start/end nodes match the style in this mockup

            *Mockup*
             !Skipped Step.png|thumbnail!
            jbochenski Jakub Bochenski made changes -
            Link This issue relates to JENKINS-47897 [ JENKINS-47897 ]
            Hide
            thuybdojenkins Thuy Do added a comment - - edited

            I second Mr. White.  In my work, I have a pipeline that contains more than 20 stages.  Some can be executed in parallel and some have to be sequential.  Each stage is executed based on a condition.  I would like to hide the stage that is not executed.  See below screenshot. 

             

            For this pipeline, I have to scroll to the right often to see the status of the stage.  It would be nice if the skipped stages either collapsed into "skipped stages" to not display at all.  I prefer not to display them at all.  Collapsing the skipped stages may not work if every other stage is skipped.

             

             

            Show
            thuybdojenkins Thuy Do added a comment - - edited I second Mr. White.  In my work, I have a pipeline that contains more than 20 stages.  Some can be executed in parallel and some have to be sequential.  Each stage is executed based on a condition.  I would like to hide the stage that is not executed.  See below screenshot.    For this pipeline, I have to scroll to the right often to see the status of the stage.  It would be nice if the skipped stages either collapsed into "skipped stages" to not display at all.  I prefer not to display them at all.  Collapsing the skipped stages may not work if every other stage is skipped.    
            thuybdojenkins Thuy Do made changes -
            Attachment Blue Ocean Skipped Stage.PNG [ 40409 ]
            Hide
            michaelneale Michael Neale added a comment -

            Thuy Do Rob White could I see a sanitised sample of your pipelines if possible? 

            Show
            michaelneale Michael Neale added a comment - Thuy Do Rob White could I see a sanitised sample of your pipelines if possible? 
            Hide
            jamesdumay James Dumay added a comment - - edited

            Thuy Do could you please open up a new feature request for skipping with an example Pipeline? Reiterating the use case you have here would be good (generally we do not accept feature requests on already resolved tickets for other features)

            Show
            jamesdumay James Dumay added a comment - - edited Thuy Do could you please open up a new feature request for skipping with an example Pipeline? Reiterating the use case you have here would be good (generally we do not accept feature requests on already resolved tickets for other features)
            Hide
            thuybdojenkins Thuy Do added a comment -

            Michael Neale I attached the pipeline view in my comment.  Do you need the groovy script I use?  If so, I will include in the new feature request as suggested by James Dumay.

            Here is a snippet of a stage in my pipeline.  Other stages are similar.

            stage("dps") {

                when {
                    expression { return params.enableDps }
                }

                steps {
                    timeout(time: 10, unit: 'HOURS') {
                        ecdmItestRun(
                            vmIp : "${params.vmIp}",
                            itestPath : "itests/restapi/dps",
                            itestName : "DPS",
                            additionalArgs : "-Prun-its,run-its-irvine"
                            )
                    }
                }
            }

            Show
            thuybdojenkins Thuy Do added a comment - Michael Neale I attached the pipeline view in my comment.  Do you need the groovy script I use?  If so, I will include in the new feature request as suggested by James Dumay . Here is a snippet of a stage in my pipeline.  Other stages are similar. stage("dps") {     when {         expression { return params.enableDps }     }     steps {         timeout(time: 10, unit: 'HOURS') {             ecdmItestRun(                 vmIp : "${params.vmIp}",                 itestPath : "itests/restapi/dps",                 itestName : "DPS",                 additionalArgs : "-Prun-its,run-its-irvine"                 )         }     } }
            Hide
            ruudp Ruud P added a comment -

            Is this working also for Parallel stages on different nodes?  I am facing at this moment some strange behavior,

            if  one of the when statements is false:

            Blue ocean shows "Queued Waiting for next available executor on ....." until the end of the complete parallel execution,  but i see in the console everything is running

            If all when statements are true i dont see anny issue

            below a small example code

             parallel {

                    stage(A') {
                      when {expression {params.A}}
                        steps {node(label: 'A') {bla bla }}}
                    stage('Bt') {
                      when {expression {params.B}}
                        steps {node(label: 'B') {bla bla}}}
                    stage('C') {
                      when {expression {params.C}}
                        steps {node(label: 'C') {bla bla}}}

            }

             

            Show
            ruudp Ruud P added a comment - Is this working also for Parallel stages on different nodes?  I am facing at this moment some strange behavior, if  one of the when statements is false: Blue ocean shows "Queued Waiting for next available executor on ....." until the end of the complete parallel execution,  but i see in the console everything is running If all when statements are true i dont see anny issue below a small example code  parallel {         stage(A') {           when {expression {params.A}}             steps {node(label: 'A') {bla bla }}}         stage('Bt') {           when {expression {params.B}}             steps {node(label: 'B') {bla bla}}}         stage('C') {           when {expression {params.C}}             steps {node(label: 'C') {bla bla}}} }  
            pixman20 pixman20 made changes -
            Assignee Josh McDonald [ sophistifunk ] pixman20 [ pixman20 ]
            Hide
            michaelneale Michael Neale added a comment -

            Ruud P I don't think it works in parallel yet (feel free to open a new ticket though)

            Show
            michaelneale Michael Neale added a comment - Ruud P I don't think it works in parallel yet (feel free to open a new ticket though)
            pixman20 pixman20 made changes -
            Assignee pixman20 [ pixman20 ]
            pixman20 pixman20 made changes -
            Assignee Josh McDonald [ sophistifunk ]
            Hide
            comscience15 Nat Sr added a comment -

            James Dumay Josh McDonald Hi guys, I wonder instead of adding "when{....}" to determine whether the stage will be skipped or not, can we have user input feature to ask if they want to skip the stage or not. Do we have this feature too?

            Show
            comscience15 Nat Sr added a comment - James Dumay Josh McDonald Hi guys, I wonder instead of adding "when{....}" to determine whether the stage will be skipped or not, can we have user input feature to ask if they want to skip the stage or not. Do we have this feature too?
            Hide
            sophistifunk Josh McDonald added a comment -

            I imagine you'd achieve that easily enough with an input step to set a variable?

            Show
            sophistifunk Josh McDonald added a comment - I imagine you'd achieve that easily enough with an input step to set a variable?
            Hide
            michaelneale Michael Neale added a comment -

            Nat Sr not explicitly no - but like Josh says, could have an input step in an earlier stage that captures some environment variable that is then referred to in 'when'. A parametrised job could also provide the same variable I think. Can't put an input inside a 'when' (I think). 

            Show
            michaelneale Michael Neale added a comment - Nat Sr not explicitly no - but like Josh says, could have an input step in an earlier stage that captures some environment variable that is then referred to in 'when'. A parametrised job could also provide the same variable I think. Can't put an input inside a 'when' (I think). 
            Hide
            ruudp Ruud P added a comment -

            it is fixed with an update of jenkins, at this moment this works fine for me

            Show
            ruudp Ruud P added a comment - it is fixed with an update of jenkins, at this moment this works fine for me
            Hide
            comscience15 Nat Sr added a comment -

            Josh McDonald Michael Neale Thanks for your feedback. Yes, it is easy to set a variable. My thought is just about if there is a complicated case which is sometimes is outside the set up variable. So if we can get it with user input too, it would be great. 

            Show
            comscience15 Nat Sr added a comment - Josh McDonald Michael Neale Thanks for your feedback. Yes, it is easy to set a variable. My thought is just about if there is a complicated case which is sometimes is outside the set up variable. So if we can get it with user input too, it would be great. 

              People

              Assignee:
              sophistifunk Josh McDonald
              Reporter:
              jamesdumay James Dumay
              Votes:
              10 Vote for this issue
              Watchers:
              20 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: