[
https://issues.jboss.org/browse/JBIDE-22966?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-22966:
------------------------------------
Agreed, we could tweak bzira.py so that BOTH ERT / Eclipse bz AND RHECLIPSE / RH bz
options exist.
I haven't looked yet whether mixing the mapping rules for Eclipse and RH bugzilla will
cause problems - initially I was thinking that we'd control the mappings in separate
files rather than mismashing them into the same .py script.
Maybe we should externalize these rules into separate .py files, which are called
depending on which commandline flags are used?
Thinking this:
http://stackoverflow.com/questions/2349991/python-how-to-import-other-pyt...
create bzira fork that supports scraping RH bugzilla
----------------------------------------------------
Key: JBIDE-22966
URL:
https://issues.jboss.org/browse/JBIDE-22966
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: build
Affects Versions: 4.4.1.AM3
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.4.1.Final
Sample issue to scrape:
https://bugzilla.redhat.com/show_bug.cgi?id=1363849
More issues:
https://bugzilla.redhat.com/buglist.cgi?component=rh-eclipse46&list_i...
Target method:
* look for whiteboard = RHT (then filter by date since last change, as current bzira.py
[1] does)
Mappings:
* BZ Product = Red Hat Software Collections --> RHECLIPSE jira
* BZ component = rh-eclipse46 (maybe others in future, eg., eclipse-cdt, eclipse-docker)
--> same component in jira (python script will generate new components automatically)
* Version = rh-eclipse46 --> "rh-eclipse46" version in JIRA
* Target Milestone --> label in JIRA
* Target Release -> label in JIRA
[1]
https://github.com/maxandersen/jiralint/blob/master/bzira.py
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)