Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
None
-
Pipeline Model Definition 0.8.2
-
-
tethys, pannonian
Description
Steps to reproduce
- Build the Pipeline from the source code at https://github.com/i386/app-store-demo (Declarative Jenkinsfile) - or see below to copy and paste
- Watch as the parallels completely disappear and then reappear
- The "Build" stage also flashes to be "Declarative: Checkout"
This works fine if it is NOT declarative (so may be worth looking at the data), but I know there was a desire to revisit some of the problem areas in karaoke so I think this is a good chance.
Ideally we could have this test in the ATH and check for the appearance of nodes correctly.
Simlified pipeline to use as non multibranch for testing and ATH:
pipeline { agent any stages { stage ('Build') { steps { sh 'echo this stage yo' } } stage ('Browser Tests') { steps { parallel ( 'Firefox': { sh "echo 'setting up selenium environment'" sh 'ping -c 5 localhost' }, 'Safari': { sh "echo 'setting up selenium environment'" sh 'ping -c 8 localhost' }, 'Chrome': { sh "echo 'setting up selenium environment'" sh 'ping -c 3 localhost' }, 'Internet Explorer': { sh "echo 'setting up selenium environment'" sh 'ping -c 4 localhost' } ) } } stage ('Static Analysis') { steps { sh 'echo findbugs' } } stage ('Package') { steps { sh 'echo package > foo.txt' } } } post { always { archive '**/*.txt' } } }
see how Array[4] switches to Array[1] After the events with pipeline_stage_is_parallel: "true" are coming in. That is just after the refetching, so vivek the REST is returning "old" data.
That is what Karaoke displays. ...now to see how we can workaround that