PackageCI
Size: 1746
Comment:
|
Size: 1760
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 12: | Line 12: |
* If a stable dependency needs an update to fix a daily build issue, backport a version to the ppa under lp:~openstack-ubuntu-testing as well (because the actual SRU upload will take some time). | * If a stable dependency needs an update to fix a daily build issue, backport a version to the corresponding ppa under lp:~openstack-ubuntu-testing as well (because the actual SRU upload will take some time). |
Daily Package CI process
The Ubuntu OpenStack team uses packaging CI to build the core OpenStack packages against a tarball generated for each upstream commit to core OpenStack projects.
Following is the general process for fixing build failures:
- Check Jenkins for build failures:
- If a core package needs a fix:
- If a stable dependency needs an update to fix a daily build issue, backport a version to the corresponding ppa under lp:~openstack-ubuntu-testing as well (because the actual SRU upload will take some time).
- If a new release dependency needs an update to fix a daily build issue:
If it is an existing package, then upload it to the archive. Also backport it with the backport_package job, which will place it in <series>-staging (e.g. newton-staging) and the trunk testing PPA (e.g. newton).
If a new package is required, go through the ITP process and create the package, then backport it to the testing PPA (e.g. newton).
Daily CI Rotation
Each of the OpenStack team members have chosen days of the week when they spend some time focusing on daily CI build failures.
Mon |
Tues |
Wed |
Thurs |
Fri |
coreycb |
jamespage |
coreycb/ddellav |
jamespage |
ddellav |
OpenStack/PackageCI (last edited 2020-06-05 18:25:47 by corey.bryant)