![]() |
|
|
|
|
Change By:
|
Hugo Ares
(17/Feb/14 2:05 PM)
|
|
Summary:
|
Build to be kept in the queue until replication is complete to gerrit
mirror
slave
(s)
|
|
Description:
|
This feature will allow an administrator to configure gerrit-trigger to wait for the replication to one or more gerrit
mirror(
slave
(mirror
) to be completed before the build get assigned to an executor.
Problematic:
If gerrit-trigger is used in a setup where there is a Gerrit master and mirror(s), gerrit-trigger is listening for Gerrit event on the master and triggering the build accordingly but, most of the time, the build will be executed and will try to pull the change from the mirror before Gerrit is done replicating the change to the mirror which is causing the build to fail.
Solution:
If gerrit-trigger is configured to wait for one or more
mirror
slave
, the gerrit event will create the build and it will get queued but gerrit-trigger will also veto if the build can run depending if the replication is done to that
mirror
slave
. The user would see that the build is in queue and a message like: waiting for replication to <
mirror_name
slave_name
>. Not all types of gerrit event need to be replicated to mirror, here is the list of event that do need to wait replication: patchset create, change merger and ref updated.
Gerrit currently does not publish replication event but I am working on adding this feature to gerrit.
|
|
|
|
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/groups/opt_out.
