-
Task
-
Resolution: Fixed
-
Minor
-
None
-
-
pacific, 1.0-b05/b-06, arctic, tasman
Depends on JENKINS-38152
- Use the Declarative Pipeline model to get the state of the expected pipeline
- When we have the model we should not use the history to calculate the expected state
- Expected state includes the stages and parallels
- is blocked by
-
-
- Closed
-
[JENKINS-38330] Use the declarative model to show all stages and parallels to be executed
jamesdumay With https://issues.jenkins-ci.org/browse/JENKINS-39463, complete pipeline graph is going to be presented even if its partially executed. Maybe we should close this.
vivek though I am confused - where is the work for tag actions being tracked? You made this comment yesterday https://issues.jenkins-ci.org/browse/JENKINS-39463?focusedCommentId=278010&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-278010
jamesdumay Ah, I see. You are referring to these 'not build' stage/parallels as skipped where I was referring to skipped stage support thats coming up using TagAction (its still in PR stage, https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/47). declarative plugin has new stage status 'SKIPPED_FOR_CONDITIONAL', its represented as SKIPPED run state in corresponding blueocean PR - https://github.com/jenkinsci/blueocean-plugin/pull/608.
vivek is there a ticket tracking that in the blue ocean component? If not, can you create one when you have a chance?
jamesdumay you mean ticket to handle skipped stages (SKIPPED_FOR_CONDITIONAL) in UI?
vivek NM - I am confused and you should ignore me (I was looking for https://issues.jenkins-ci.org/browse/JENKINS-38150)
vivek looks like the supporting work was completed by abayer so this one is coming up on the next sprint