Bug-Url is not recognized properly

Description

Example:
Check Bug-Url::WARN, no bug url/s found <== !!!!
Check Public Bug::#1373573::OK, public bug <== But OK here

Example changes:
https://gerrit.ovirt.org/#/c/66723/
https://gerrit.ovirt.org/#/c/66774/

Activity

Show:

Former user November 21, 2016 at 2:19 PM
Edited

patch #67127 is ready.

currently status: merged

Former user November 15, 2016 at 1:02 PM

Probably you are right but the check public hook is an old hook that will be removed (not used).
In the current situation it is a little bit tricky.
Example:
https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=VERIFIED&bug_status=ASSIGNED&bug_status=MODIFIED&bug_status=ON_DEV&bug_status=ON_QA&bug_status=RELEASE_PENDING&bug_status=POST&emailassigned_to1=1&emailcc1=1&emailreporter1=1&emailtype1=exact&list_id=6648964

How you'll enforce the situation when it ends with a number but it return a list of bug urls?
That is why there is a convention that developers are adding bug-urls.

Former user November 15, 2016 at 12:47 PM

Yes. I found the reason however show_bug is valid URL and it can be simply copy-pasted from the URL.
As it works in one place (check public) and doesn't work in another (check_bug_url) I think it's a bug just because of inconsistency ("No bug-url found but the bug is public" sounds like a bug. doesn't it?)

Former user November 15, 2016 at 12:41 PM

Hi Pavel,

It is not a bug, the user added the bug-url with wrong convention: https://bugzilla.redhat.com/*show_bug.cgi?id=*1335642
While it should be added as: https://bugzilla.redhat.com/1335642

Fixed

Details

Assignee

Reporter

Priority

Created November 15, 2016 at 12:36 PM
Updated January 3, 2017 at 7:33 AM
Resolved November 30, 2016 at 10:34 AM