Historically, Blue ocean and Pipeline-graph showed all the build stages (including ones that were skipped and any that ran). This behavior was consistent between main branch or any PRs.
However, in last few weeks we noticed that only subset of the stages are shown, and the entire parallel, multi-stage "Build" stage shows as only a single, skipped stage. This means we can't actually use Jenkins to see what happened with a PR build.
Originally reported by vudayagiri01, imported from: Jenkins PipelineGraph does not show skipped stages in pipeline on PRs unlike builds on main
- status: Open
- priority: Major
- component(s): pipeline-graph-analysis-plugin
- resolution: Unresolved
- votes: 0
- watchers: 1
- imported: 20251223-222157
Raw content of original issue
Historically, Blue ocean and Pipeline-graph showed all the build stages (including ones that were skipped and any that ran). This behavior was consistent between main branch or any PRs.
However, in last few weeks we noticed that only subset of the stages are shown, and the entire parallel, multi-stage "Build" stage shows as only a single, skipped stage. This means we can't actually use Jenkins to see what happened with a PR build.
Historically, Blue ocean and Pipeline-graph showed all the build stages (including ones that were skipped and any that ran). This behavior was consistent between main branch or any PRs.
However, in last few weeks we noticed that only subset of the stages are shown, and the entire parallel, multi-stage "Build" stage shows as only a single, skipped stage. This means we can't actually use Jenkins to see what happened with a PR build.
Originally reported by vudayagiri01, imported from: Jenkins PipelineGraph does not show skipped stages in pipeline on PRs unlike builds on main
Raw content of original issue