Status: Resolved (View Workflow)
This improvement is completed and scheduled for release in 1.2. Check the roadmap page for updates.
The Pipeline team have added the ability to "skip" stages in the Pipeline (
- 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
- is duplicated by
JENKINS-44464 Blue Ocean shows 'Unknow' status for skipped Stages
- relates to
JENKINS-47897 Blue Ocean pipeline view shows stages and steps from previous build, until given step starts
- links to
comscience15 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).
it is fixed with an update of jenkins, at this moment this works fine for me
sophistifunk michaelneale 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.
The graph in scripted pipelines does not show the line flowing around the skipped stage, but through it, like executed steps.
The steps are shown as "No steps" and the full job log is displayed.
I imagine you'd achieve that easily enough with an input step to set a variable?