PackageCI
|
Size: 1741
Comment:
|
Size: 2629
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| === Overview === The Ubuntu !OpenStack team uses automated packaging CI to build the core !OpenStack packages against a tarball generated for each upstream commit to core !OpenStack projects. === Published PPAs === CI packages are published to the following PPAs: * [[https://launchpad.net/~openstack-ubuntu-testing/+archive/ubuntu/rocky|Rocky Testing PPA]] * [[https://launchpad.net/~openstack-ubuntu-testing/+archive/ubuntu/queens|Queens Testing PPA]] * [[https://launchpad.net/~openstack-ubuntu-testing/+archive/ubuntu/pike|Pike Testing PPA]] * [[https://launchpad.net/~openstack-ubuntu-testing/+archive/ubuntu/ocata|Ocata Testing PPA]] * [[https://launchpad.net/~openstack-ubuntu-testing/+archive/ubuntu/newton|Mitaka Testing PPA]] |
|
| Line 3: | Line 17: |
| 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. | 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. |
| Line 7: | Line 21: |
| * http://10.245.168.2:8080/view/Newton/ | * http://10.245.168.2:8080/view/Rocky/ * http://10.245.168.2:8080/view/Queens/ * http://10.245.168.2:8080/view/Pike/ * http://10.245.168.2:8080/view/Ocata/ |
| Line 9: | Line 26: |
| * http://10.245.168.2:8080/view/Liberty/ | |
| Line 12: | Line 28: |
| * If a stable dependency needs an update to fix a daily build issue, backport a version to the ppa under ~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). |
| Line 14: | Line 30: |
| * 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. [[https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/newton-staging|newton-staging]]) and the trunk testing PPA (e.g. [[https://launchpad.net/~openstack-ubuntu-testing/+archive/ubuntu/newton|newton]]). | * 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 the corresponding UCA staging PPA (e.g. [[https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/newton-staging|newton-staging]]) and the corresponding trunk testing PPA (e.g. [[https://launchpad.net/~openstack-ubuntu-testing/+archive/ubuntu/newton|newton]]). |
| Line 19: | Line 35: |
| Each of the !OpenStack team members have chosen days of the week when they spend some time focusing on daily CI build failures. | Each of the !OpenStack team members have chosen days of the week when they spend some time focusing on fixing up daily CI build failures. |
| Line 22: | Line 38: |
| || coreycb|| jamespage || coreycb/ddellav || jamespage || ddellav || | || coreycb|| jamespage || coreycb || jamespage || || |
Overview
The Ubuntu OpenStack team uses automated packaging CI to build the core OpenStack packages against a tarball generated for each upstream commit to core OpenStack projects.
Published PPAs
CI packages are published to the following PPAs:
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 the corresponding UCA staging PPA (e.g. newton-staging) and the corresponding 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 fixing up daily CI build failures.
Mon |
Tues |
Wed |
Thurs |
Fri |
coreycb |
jamespage |
coreycb |
jamespage |
|
OpenStack/PackageCI (last edited 2020-06-05 18:25:47 by corey.bryant)