![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Affects Versions:
|
current |
|
Assignee:
|
rsandell
|
|
Components:
|
gerrit-trigger |
|
Created:
|
18/Jul/14 12:40 PM
|
|
Description:
|
Use case: Jenkins become unavailable. In the meantime, there are a number of Gerrit events occurring which are missed. When Jenkins restarts, these missed events should be replayed.
E.g. a designer submits a patch set during a Jenkins outage. Since Gerrit trigger is not firing, the patch will never be verified and merged, or will need to be done manually. There is a facility in Gerrit trigger to "manually" query events during a given period, but this will not scale as need to be done for each job.
The requirement would be:
1. It shall be possible to replay all "missing" Gerrit events for a given Jenkins master following a downtime of the master
2. It shall be possible to have #1 trigger automatically i.e. that when Jenkins restart, all events that happened since last time it ran will be replayed.
3. It shall be possible to trigger #1 manually. This capability shall be available only to the administrator role
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Christian Lague
|
|
|
|
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.
