Highlight Jenkins +1 votes functionality
Bug #1516110 reported by
Apoorva Deshpande
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ciwatch |
Fix Released
|
Undecided
|
Apoorva Deshpande | ||
Bug Description
Currently ciwatch highlights Jenkins -1 votes, but many driver CIs pick up Gerrit events only when Jenkins has voted +1.
Hence it is important to highlight vendor CI failures when Jenkins has verified the change set.
| Changed in ciwatch: | |
| assignee: | nobody → Apoorva Deshpande (apoorvad) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to ciwatch (master) | #1 |
| Changed in ciwatch: | |
| status: | New → Fix Committed |
| Changed in ciwatch: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit f52b39f483e28f2
Author: apoorvad <email address hidden>
Date: Fri Nov 13 10:09:44 2015 -0800
Add highlight Jenkins +1 functionality
Currently ciwatch highlights Jenkins -1 votes, but many
third party CIs pick up Gerrit events only when Jenkins
has voted +1. Hence it is important to highlight vendor
CI failures when Jenkins has verified the change set.
Closes-Bug: #1516110
Change-Id: I5635d344404c21