[JIRA] (OVIRT-1639) Get a solution to the CI Gerrit vote "race condition"

7 Sep 2017


      This is a multi-part message in MIME format...

------------=_1504768061-20929-206
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


     [ https://ovirt-jira.atlassian.net/browse/OVIRT-1639?page=com.atlassian.jira.p... ]

Barak Korren reassigned OVIRT-1639:
-----------------------------------

    Assignee: Barak Korren  (was: infra)
...
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: Barak Korren
             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)

------------=_1504768061-20929-206
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.jira.p... ]</pre>
<h3>Barak Korren reassigned OVIRT-1639:</h3>
<pre>Assignee: Barak Korren  (was: infra)</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: Barak Korren
  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=i5TMWGV99amJbNxJpSp2-2BCmpYLyzY..." 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>

------------=_1504768061-20929-206--

Barak Korren (oVirt JIRA)

tags

participants (1)