Open Stack

Hi Josh,

Just a heads up that you shouldn't use this list for any discussion. We've moved
all of the discussion off this list into openstack-dev. The only reason we
haven't removed the openstack-qa list is so we have a separate address for the
periodic job results. (which honestly hasn't been the most effective approach
for handling those jobs)

On Wed, Oct 01, 2014 at 07:39:44PM +1000, Joshua Hesketh wrote:
> Hello QA team,
> 
> When a job fails in the post queue (which have jobs that are triggered on a
> change being merged) no warning or failure message is sent anywhere so it
> does so silently. This has caused an issue in the past[0] and there are
> likely more cases we don't know about.
> 
> We should report failures somewhere but since post jobs don't come from
> gerrit they can't be reported back to gerrit trivially. And even if we could
> it would be a comment on a closed change.

So I actually think as a first pass this would be the best way to handle it. You
can leave comments on a closed gerrit changes, it would still generate the same
notifications for people who have that enabled. It also would be picked up in
the ci results table on the top which I think might be convenient.

Long term I'm thinking we might need to make a separate dashboard view for all
of these jobs so we can track the results over time. I don't think instantaneous
reporting is actually important for post or periodic jobs because if it were
they'd be running in check or gate then. Back in the days when there was a
single jenkins, the jenkins dashboard could be used for this to a certain extent
which was useful. 

> 
> My feeling is an easy solution is to email somewhere when a post job fails.
> However I'm not sure where might be an appropriate location for that. Would
> this mailing list, for example, be a good place to start and then see how we
> go?

I really don't think this is the right approach. The issue is that most of these
things are a project specific failure and you'd either be spamming everyone 
that it failed or small set of people who aren't interested. I also feel that we
run the post jobs far too frequently to have it be sent to any ML.
> 
> I've set up the change here: https://review.openstack.org/#/c/125298/
> 
> Cheers,
> Josh
> 
> [0]
> http://lists.openstack.org/pipermail/openstack-dev/2014-September/046481.html
> 

-Matt Treinish
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141001/3529e5ba/attachment.pgp>