openstack/glance
Code Issues Proposed changes

Update Release CPL doc about periodic jobs

Browse Source 
At the weekly Glance meeting on 2018-05-17 it was agreed that the
Release CPL will monitor the periodic "tips" test jobs and report
on their status at the weekly meeting.  This patch updates the
appropriate section of the Glance Contributor's Guide.

Change-Id: Ieeab3e3a42b8197f8b0544e97748ffdb8f620f13
This commit is contained in:
Brian Rosmaita 2018-06-05 17:59:24 -04:00
parent 3b2da73490
commit bc80aad4f3
1 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
doc/source/contributor/release-cpl.rst
View File

@ -143,6 +143,24 @@ ship a better product. You can also then focus on bug fixing reviews in the
interim between your project priorities deadline and the actual release
deadline.
There are periodic "tips" test jobs set up for each of glance, glance_store,
and python-glanceclient. These jobs test our current masters (which use
the released versions of dependencies) against the master branches of our
dependencies. This way we can get a heads-up if a dependency merges a change
that will break us. In order for this to work, someone has to keep an eye
on these jobs ... and that person is you. Part of your job is to report on
the status of the periodic jobs at the weekly glance meeting.
You can see the output of these jobs by going to the Zuul Builds Page,
``http://zuul.openstack.org/builds.html``. (Note: it takes a minute or so
for the page to populate.) You can filter the results by Pipeline (you
want ``periodic``) and Project (use ``openstack/glance``,
``openstack/glance_store``, or ``openstack/python-glanceclient``). You
can find a link to the logs of each job from that page. (Note: your
responsibility as Release CPL is limited to monitoring and notifying the
team about the status of the jobs. But feel free to fix them if you want
to!)
Checklist
=========