Zun

Migrate to Zuulv3 - Update legacy jobs

Registered by Kien Nguyen

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://docs.openstack.org/infra/manual/zuulv3.html#legacy-job-migration-details
[2] https://docs.openstack.org/infra/manual/zuulv3.html#howto-update-legacy-jobs

Blueprint information

Status:
Complete
Approver:
hongbin
Priority:
High
Drafter:
Kien Nguyen
Direction:
Approved
Assignee:
Kien Nguyen
Definition:
New
Series goal:
Accepted for rocky
Implementation:
Implemented
Milestone target:
None
Started by
hongbin
Completed by
hongbin

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/migrate-to-zuulv3,n,z

Addressed by: https://review.openstack.org/508935
    [WIP] Migration to Zuul v3

Gerrit topic: https://review.openstack.org/#q,topic:migrate-to-zuulv3,n,z

Addressed by: https://review.openstack.org/512209
    [WIP] Migrate to Zuulv3

Addressed by: https://review.openstack.org/515226
    Migrate to Zuul v3

Addressed by: https://review.openstack.org/538752
    Migrate to Zuul v3

(hongbin 2018-07-08): It looks this BP is implemented since all the patches are merged. I am going to mark this BP as implemented but feel free to amend the status if it is wrong.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.