Open Stack

jenkins at openstack.org writes:

> Build failed.
>
> - periodic-neutron-docs-grizzly http://logs.openstack.org/periodic-stable/periodic-neutron-docs-grizzly/98472d2 : SUCCESS in 3m 30s
> - periodic-neutron-python26-grizzly http://logs.openstack.org/periodic-stable/periodic-neutron-python26-grizzly/a071fd4 : SUCCESS in 31m 18s
> - periodic-neutron-python27-grizzly http://logs.openstack.org/periodic-stable/periodic-neutron-python27-grizzly/9a35cd4 : SUCCESS in 17m 20s
> - periodic-neutron-docs-havana http://logs.openstack.org/periodic-stable/periodic-neutron-docs-havana/0ca4a08 : SUCCESS in 1m 20s
> - periodic-neutron-python26-havana http://logs.openstack.org/periodic-stable/periodic-neutron-python26-havana/268da58 : FAILURE in 40m 30s
> - periodic-neutron-python27-havana http://logs.openstack.org/periodic-stable/periodic-neutron-python27-havana/c8a9caf : SUCCESS in 18m 13s

Hi,

Thanks to a feature Joshua Hesketh added a while ago, Zuul has grown the
ability to send email.  It doesn't read email yet, so as a program, it's
clearly not complete ;).  But we can use it to send, I hope, somewhat
more useful emails about periodic jobs.

Instead of emails for individual jobs, they are now grouped by project,
so you'll get a summary email about each project that has a failing job.
Only projects with a failing job send email; not successful jobs.
Currently all stable branches tested for that project are included in
each email.  Similarly, the QA team gets emails for periodic jobs that
run on tempest (if at least one fails).

You'll note the format of the message is the same as what is supplied to
Gerrit for change reviews (or nearly so, we actually have Gerrit
configured to munge them slightly and turn them into hyperlinks; what
you'll see in email is the raw text sent to Gerrit).  At any rate, the
upshot is that you won't receive 1000 lines of truncated log output in
your email, but you will receive a bullet list of the jobs run, time
taken, result, and a link to the logs.

Part of the motivation for this is our continued long-term plan to
reduce our dependence on Jenkins, but also a recent simplification of
the devstack-gate jobs.  We have eliminated the duplicate versions of
jenkins job builder templates for devstack-gate that existed only to
instantiate the periodic jobs.  Now they are built from the same
templates as the normal devstack-gate jobs, meaning that we don't have
to worry about synchronizing changes in both templates.

-Jim