[JIRA] [gerrit-trigger] (JENKINS-25047) Draft Published and ChangeMerged events not handled correctly when using replication to slaves

Wed, 15 Oct 2014 06:21:12 -0700

Code changed in jenkins
User: escoheb
Path:
pom.xml
src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/replication/ReplicationQueueTaskDispatcher.java
src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ParameterExpanderTest.java
src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/mock/Setup.java
src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/replication/ReplicationQueueTaskDispatcherTest.java
http://jenkins-ci.org/commit/gerrit-trigger-plugin/8c7d0e84d5dc4bf6433cff85b9c61f4373e56366
Log:
Fix DraftPublished and ChangeMerged -> Replication

The Draft Published event is now handled correctly by ensuring that
Gerrit Trigger does not wait for a replicaton event from the slave.

The Change Merged event is now handled correctly by ensuring that we
wait for the replication event for the included patchset on the slave.

These use cases were covered:

  • The user merges his/her change to master and there is no change in SHA1
    • The replication has already occurred.
  • The user merges his/her change to master and there is a change in SHA1
    since there already other changes merged after the patchset was created.
    • a new replication takes place and must be waited for.

[FIXED JENKINS-25047]
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.

Reply via email to