Change not enqueued into gate when existing "Jenkins" +1 is replaced

Bug #1397481 reported by wanghong
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Core Infrastructure

Bug Description

This happened in this review:

Revision history for this message
Jeremy Stanley (fungi) wrote :

The way our Zuul configuration is currently written, it looks for the "Jenkins" user leaving a +1 comment as a trigger to enqueue a change into the gate pipeline. Unfortunately this is based on parsing Gerrit comments from the event stream, and leaving a +1 vote in a comment when the same account already has a +1 present results in the +1 not being echoed into the comment text. The workarounds for this are to add another approval vote (workflow +1, removing the existing workflow +1 if needed), or remove the vote from the "Jenkins" account and recheck.

summary: - Jenkins does not start gate jobs
+ Change not enqueued into gate when existing "Jenkins" +1 is replaced
Changed in openstack-ci:
status: New → Confirmed
milestone: none → kilo
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.