x***@gmail.com
2018-12-03 07:34:39 UTC
We have setup jenkins to listen to gerrit event "patchset Created" and
"change merged" on 2.11, that works well. "Patchset Created" will trigger
Jenkins for build and post "verfiied" flag on gerrit code inspection.
"Change Merged" events is to trigger final integration on jenkins to see
if final change passes basic test.
now we would like to monitor all TAG creation, so we add "Ref UPdated"
events on Jenkins, but prolem is when developer commit one code, will have
two events to Jenkins triggering build.
one is change merged event, another is "ref updated". this will cause
Jenkins almost run duplicate build at same time.
We would like to keep both "Change Merged" and "Ref Updated" event, is
there any way to avoid duplicate build on Jenkins when commit code.
we would like to filter RerUpdated in pipeline script and return
directly, but would cause jenkins mark job as failed.
thanks for help.
[image: test.png] <about:invalid#zClosurez>
"change merged" on 2.11, that works well. "Patchset Created" will trigger
Jenkins for build and post "verfiied" flag on gerrit code inspection.
"Change Merged" events is to trigger final integration on jenkins to see
if final change passes basic test.
now we would like to monitor all TAG creation, so we add "Ref UPdated"
events on Jenkins, but prolem is when developer commit one code, will have
two events to Jenkins triggering build.
one is change merged event, another is "ref updated". this will cause
Jenkins almost run duplicate build at same time.
We would like to keep both "Change Merged" and "Ref Updated" event, is
there any way to avoid duplicate build on Jenkins when commit code.
we would like to filter RerUpdated in pipeline script and return
directly, but would cause jenkins mark job as failed.
thanks for help.
[image: test.png] <about:invalid#zClosurez>
--
--
To unsubscribe, email repo-discuss+***@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en
---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
To unsubscribe, email repo-discuss+***@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en
---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.