[
https://ovirt-jira.atlassian.net/browse/OVIRT-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
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)
_______________________________________________
Infra mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/infra
