This was originally added to help docs projects trigger a docs
update when a tag is deployed. Unfortunately ref-update appears to
trigger even for comments in Gerrit now. Not sure why but likely due
to Gerrit NoteDB. The Jenkins Gerrit Trigger configuration for
ref-update unfortunately does not provide any configuration for
specifying specific refs to trigger on.
Until there's an alternative it's better to disable this so that
Jenkins does not get flooded with queued jobs for Gerrit code
reviews that have active comments.
Issue: IT-18792
Signed-off-by: Thanh Ha <zxiiro@gmail.com>
Change-Id: I417e53d698e1454deb28b30d87e97147ce8d3038
- change-merged-event
- comment-added-contains-event:
comment-contains-value: '^Patch Set\s+\d+:\s+remerge\s*$'
- - ref-updated-event
#####################
# Job Configuration #
--- /dev/null
+---
+issues:
+ - |
+ Removes ref-update from rtd-merge jobs which is triggering unnecessary
+ jobs to be queued in Jenkins. This ref-update was originally added to
+ enable Jenkins to trigger builds when a release tag is pushed to update
+ the docs however it's now triggering many unnecessary jobs wasting
+ project CI resources.