Gerrit does not emit events on draft publication
Bug #1255166 reported by
Pablo Andres Fuente
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Core Infrastructure |
Fix Released
|
Medium
|
Khai Do |
Bug Description
If a review is submitted using the -D option, after you click on the Publish button, Jenkins don't start automatically the check process.
As an example: https:/
Changed in openstack-ci: | |
status: | New → Fix Committed |
importance: | Undecided → Medium |
tags: | added: gerrit |
summary: |
- Jenkins check don't run automatically when the review is published + Gerrit does not emit events on draft publication |
Changed in openstack-ci: | |
assignee: | nobody → Khai Do (zaro0508) |
Changed in openstack-ci: | |
status: | Fix Committed → In Progress |
Changed in openstack-ci: | |
assignee: | nobody → Khai Do (zaro0508) |
status: | Invalid → In Progress |
To post a comment you must log in.
Gerrit 2.4, running on review. openstack. org, does not emit events for draft publication, so there is nothing for Zuul to act on. Later Gerrit releases (which we eventually hope to run) have added an event to the stream for this, thus the "fix committed" status... we won't be backporting this fix but we do eventually hope to upgrade once we can reach upstream feature parity with our current fork. There are two workarounds:
1. (preferred) Do not use drafts. On a public code review system for free software, there is little benefit to Gerrit's "draft" feature. Drafts are not actually private, so if something is not ready for review mark it "work in progress" instead.
2. (you used the draft feature anyway) Either push a new patchset such as a trivial rebase, or leave a review comment which says only "recheck no bug" and nothing else. Either of these actions should cause Zuul to see an event which will trigger check tests.