[JIRA] (OVIRT-1750) CI +1 doesn't carry forward on commit message updated while previous build is running

Thursday, 9 November 2017

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

------------=_1510254493-14930-288
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Greg Sheremeta created OVIRT-1750:
-------------------------------------

             Summary: CI +1 doesn't carry forward on commit message updated while
previous build is running
                 Key: OVIRT-1750
                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1750
             Project: oVirt - virtualization made easy
          Issue Type: Bug
          Components: Gerrit/git
            Reporter: Greg Sheremeta
            Assignee: infra
            Priority: Low

See https://gerrit.ovirt.org/#/c/83871/ for an example

While patchset 3 was running, I updated the commit message. PS3 gets CI+1, but PS4 does
not. I must add it manually.

--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100070)

------------=_1510254493-14930-288
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

<html><body>
<h3>Greg Sheremeta created OVIRT-1750:</h3>
<pre>   Summary: CI +1 doesn't carry forward on commit message updated while
previous build is running
       Key: OVIRT-1750
       URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1750
   Project: oVirt - virtualization made easy
Issue Type: Bug
Components: Gerrit/git
  Reporter: Greg Sheremeta
  Assignee: infra
  Priority: Low</pre>
<p>See <a
href="https://gerrit.ovirt.org/#/c/83871/">https://gerrit.ov...
for an example</p>
<p>While patchset 3 was running, I updated the commit message. PS3 gets CI+1, but
PS4 does not. I must add it manually.</p>
<p>&mdash; This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100070)</p>

------------=_1510254493-14930-288--

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

[JIRA] (OVIRT-1750) CI +1 doesn't carry forward on commit message updated while previous build is running