PackageCI

Differences between revisions 5 and 6
Revision 5 as of 2016-06-08 13:40:51
Size: 1770
Editor: corey.bryant
Comment:
Revision 6 as of 2016-06-08 13:41:57
Size: 1801
Editor: corey.bryant
Comment:
Deletions are marked like this. Additions are marked like this.
Line 14: Line 14:
   * 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]]).

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:

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/ddellav

jamespage

ddellav

OpenStack/PackageCI (last edited 2018-09-06 15:36:36 by corey.bryant)