|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
Jesse Glick;
I'm willing to pair with you to reproduce (and even fixing the bug).
It appears that the "Query and Trigger Gerrit" thingy actually produces a slightly different bug.
I think what we can do is point it at a Gerrit repository and have the job trigger on any Gerrit change... but we have to find a Gerrit repository you have permission to "listen to the event streams" on.