10:07 a.m.
This is a multi-part message in MIME format...
------------=_1504768054-18385-248
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[
https://ovirt-jira.atlassian.net/browse/OVIRT-1639?page=com.atlassian.jir...
]
Barak Korren updated OVIRT-1639:
--------------------------------
Epic Link: OVIRT-400
Get a solution to the CI Gerrit vote "race condition"
-----------------------------------------------------
Key: OVIRT-1639
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1639
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: oVirt CI
Reporter: Barak Korren
Assignee: infra
Labels: gerrit, jenkins
We have a certain scenario that repeats itself in our system:
# Developer sends a patch
# CI jobs start running
# Developer send a new patch-set with a trivial change (e.g. commit message fix)
# CI jobs complete and send results to Gerrit
# Gerrit ignores the Jenkins vote because it was made on the older patch-set.
# No vote is made by Jenkins on the new patch-set because it is configured to nor run
jobs on trivial patches.
We've seen developers encounter this many times. I suspect this because even more
frequent recently because PolyGerrit provides a UI for quickly editing commit messages.
We need to open tickets to the Gerrit developers and the Gerrit Trigger Plugin authors
and see of they will be willing to help with this.
--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100059)
------------=_1504768054-18385-248
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[
https://ovirt-jira.atlassian.net/browse/OVIRT-1639?page=com.atlassian.jir...
]</pre>
<h3>Barak Korren updated OVIRT-1639:</h3>
<pre>Epic Link: OVIRT-400</pre>
<blockquote><h3>Get a solution to the CI Gerrit vote “race
condition”</h3>
<pre> Key: OVIRT-1639
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1639
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: oVirt CI
Reporter: Barak Korren
Assignee: infra
Labels: gerrit, jenkins</pre>
<p>We have a certain scenario that repeats itself in our system: # Developer sends a
patch # CI jobs start running # Developer send a new patch-set with a trivial change (e.g.
commit message fix) # CI jobs complete and send results to Gerrit # Gerrit ignores the
Jenkins vote because it was made on the older patch-set. # No vote is made by Jenkins on
the new patch-set because it is configured to nor run jobs on trivial patches. We've
seen developers encounter this many times. I suspect this because even more frequent
recently because PolyGerrit provides a UI for quickly editing commit messages. We need to
open tickets to the Gerrit developers and the Gerrit Trigger Plugin authors and see of
they will be willing to help with this.</p></blockquote>
<p>— This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100059)</p>
<img
src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpS...
alt="" width="1" height="1" border="0"
style="height:1px !important;width:1px !important;border-width:0
!important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0
!important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0
!important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>
------------=_1504768054-18385-248--
2671
days inactive
2671
days old
0 comments
1 participants
participants (1)
-
Barak Korren (oVirt JIRA)