Nir Soffer created OVIRT-2669:
---------------------------------
Summary: CI scripts try to modify unrelated bugs
Key: OVIRT-2669
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2669
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: Nir Soffer
Assignee: infra
If a commit message mention another bug, the CI script try to add the patch
to the bug in the commit message, and change the bug to POST.
Mentioning another bug in a commit message is good practice, making it
easier to follow, and avoiding unclear forms like "bug 1000000" or
"BZ#1000000",
or even worse shortened urls like https://goo.gl/bPuFGo.
Does it make sense that we cannot link to Red Hat bugzilla like god
intended?
Here is a proof:
https://gerrit.ovirt.org/c/97568/
gerrit-hooks
Patch Set 1:
Check Bug-Url::10000000::WARN, failed to get bug info (private bug or
bug doesn't exist
Check Product::IGNORE, not relevant for branch: master
Check TM::IGNORE, not relevant for branch: master
Check Backport::IGNORE, not relevant for branch: master
Set POST::#10000000::WARN, failed to get bug info (private bug or bug
doesn't exist)
Update Tracker::#10000000::WARN, failed to get bug info (private bug or
bug doesn't exist)
CI scripts should process urls only inside Bug-Url: tag.
Expected behavior:
Extract bug urls *only* from Bug-Url: label.
The same issue exists with Related-To: label.
This is not a new bug. I reported it few years ago but for some reason the
issue
was not understood.
Nir
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100098)
_______________________________________________
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/CZT4LZNCLHU4SFEQ62HFBVLARNMQIPYC/
