[JIRA] (OVIRT-1911) RFE: Add relevant git commit messages as comments in the relevant Bugzillas

Sunday, 25 February 2018

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

------------=_1519573284-30715-140
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

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

eyal edri reassigned OVIRT-1911:
--------------------------------

    Assignee: Anton Marchukov  (was: infra)

Anton, how much effort do you think this will need to add it to Gerrit Hooks? 

[~ykaul] I also think this should be communicated before adding, people sometimes
don't like new automatic info added to bugs without a good reason.

We'll also need to think what do you do in case there are multiple external trackers
attached to the bug, which is the case most of the time, do you start "spamming"
the bug with commit messages from each tracker? sometimes it can be as much as 10
different patches. 

What about if there are trackers from multiple projects, a quite common scenario with
oVirt bugs (e.g vdsm + engine + jsonrpc) , do you add all the commit messages then? 

We've seen issues with current new comments added to bugs when they can't move to
ON_QA, it has the potential of causing more noise than good, so we really need to think if
and how we want to implement this before moving forward.

cc [~dfodor]

...
 RFE: Add relevant git commit messages as comments in the relevant
Bugzillas
 ---------------------------------------------------------------------------

                 Key: OVIRT-1911
                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1911
             Project: oVirt - virtualization made easy
          Issue Type: New Feature
          Components: Gerrit/git
            Reporter: Yaniv Kaul
            Assignee: Anton Marchukov

 When a bug moves to MODIFIED, can we add the relevant commit message(s) to the bug?
 I see it happening in RHEL from time to time, and I think it's easier (for us and QE)
then clicking on the link to Gerrit. 

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

------------=_1519573284-30715-140
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

<html><body>
<pre>[
https://ovirt-jira.atlassian.net/browse/OVIRT-1911?page=com.atlassian.jir...
]</pre>
<h3>eyal edri reassigned OVIRT-1911:</h3>
<pre>Assignee: Anton Marchukov  (was: infra)</pre>
<p>Anton, how much effort do you think this will need to add it to Gerrit
Hooks?</p>
<p>[~ykaul] I also think this should be communicated before adding, people sometimes
don't like new automatic info added to bugs without a good reason.</p>
<p>We'll also need to think what do you do in case there are multiple external
trackers attached to the bug, which is the case most of the time, do you start
&ldquo;spamming&rdquo; the bug with commit messages from each tracker? sometimes
it can be as much as 10 different patches.</p>
<p>What about if there are trackers from multiple projects, a quite common scenario
with oVirt bugs (e.g vdsm + engine + jsonrpc) , do you add all the commit messages
then?</p>
<p>We've seen issues with current new comments added to bugs when they can't
move to ON_QA, it has the potential of causing more noise than good, so we really need to
think if and how we want to implement this before moving forward.</p>
<p>cc [~dfodor]</p>
<blockquote><h3>RFE: Add relevant git commit messages as comments in the
relevant Bugzillas</h3>
<pre>     Key: OVIRT-1911
     URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1911
 Project: oVirt - virtualization made easy
         Issue Type: New Feature
         Components: Gerrit/git
Reporter: Yaniv Kaul
Assignee: Anton Marchukov</pre>
<p>When a bug moves to MODIFIED, can we add the relevant commit message(s) to the
bug? I see it happening in RHEL from time to time, and I think it's easier (for us and
QE) then clicking on the link to Gerrit.</p></blockquote>
<p>&mdash; This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100080)</p>

------------=_1519573284-30715-140--

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011