Remove steps that repeat work an earlier job already did
Jobs that each rebuild what a previous job already built, wired to share artefacts instead.
The ticket
Remove pipeline steps that repeat work an earlier job already completed.
Acceptance criteria
- The job graph is attached before and after
- Artefacts are passed between jobs rather than rebuilt
- Total pipeline minutes are recorded either side
- Job independence needed for reliability is preserved deliberately
What lands as proof
Before and after job graphs plus the minutes saved, so the change is visible rather than asserted.
Why teams defer it
- Each job was written to be self-contained, which was the right call in isolation.
- Sharing artefacts couples jobs together, which trades reliability for speed and needs a decision.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: remove pipeline steps that repeat work an earlier job already completed. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means job graph attached before and after, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- The run stops for the plan, and the review bar is raised afterwards so that smaller suggestions block the merge too, not only serious findings.