Migrate to Zuulv3 - Update legacy jobs
After Zuulv3 migration, project-specific jobs are migrated to jobs prefixed with legacy-. This makes them easy to spot as jobs that were not written for v3 but instead were auto-converted.
With in-repo config, the best place for most of these jobs is actually in the project repositories themselves so that the project cores are the ones who review the jobs and not the Infra team. Moving the jobs from their migrated location to the project will be a good opportunity to clean them up and rewrite them to use the new Zuul v3 features [1]
For all of the jobs specific to a particular project, teams should move the auto-converted legacy- jobs to their own repos and rework them to stop using the legacy interfaces. There are two fundamental steps [2]:
1. Move the jobs to your repo
2. Rework the jobs to be native v3 jobs
[1] https:/
[2] https:/
Blueprint information
- Status:
- Complete
- Approver:
- Alexander Chadin
- Priority:
- High
- Drafter:
- Alexander Chadin
- Direction:
- Needs approval
- Assignee:
- Alexander Chadin
- Definition:
- Approved
- Series goal:
- Accepted for rocky
- Implementation:
- Implemented
- Milestone target:
- rocky-1
- Started by
- Alexander Chadin
- Completed by
- Alexander Chadin
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
[WiP] Migrate to Zuul v3
Gerrit topic: https:/
Addressed by: https:/
ZuulV3 jobs