-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JBIDE-21363 create bugzilla importer for JIRA #9
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
maxandersen
force-pushed
the
JBIDE-21363
branch
from
January 5, 2016 14:06
8a572a3
to
e3f9054
Compare
I think adding bug.component as a label is enough for now. |
Why: * we do more and more eclipse upstream work at eclipse. We need to be able to track them without having to jump through too many hoops. * previous attempts of syncing bugzilla been trying to keep things in sync - we don't need this so much. We just want the bugzillas to show up in jira for use in sprint planning and overview. The actual work will still happen in bugzilla for Eclipse. This change addreses the need by: * created a `bzira.py` script that will take a given bugzilla query and make sure its resulting bugzillias are listed in jira (a so called proxy-jira). * Currently assumes the following: - There is just one jira project name and it is ERT (Eclipse Release Train) - The proxy-jira title has the format: `<eclipse title> [EBZ#bzid]' ex. `Add JSON Editor contribution into maven build and include into features [EBZ#484762]` - eclipse product is used for component (automatically created if not present) TODO: - should we use bug.product + '-' + bug.compnent for component name ? - how do we handle updates to description/fixversions/title ? - does not handle versions, needs map from product+versions to Eclipse release train - bugzilla query hardcoded to RHT keyword query. - bugzilla for python for some reason cannot read comments so description is empty Resolves: JBIDE-21363
…ly processing issues changed in the last X days; clean up normal/verbose logging; add missing details to readme; add TODO markers
… the BZ queries are smaller and faster; only prompt to accept jiras if dryrun = None
maxandersen
force-pushed
the
JBIDE-21363
branch
from
January 22, 2016 22:38
6a8b8dc
to
edf1015
Compare
Why: * code was getting a bit unwildly This change addreses the need by: * do basic logging by default * details only in verbose mode * removed manual date calculation * removed a few redundant lines especially around query and version calculation * added basic map for Linux tools * added NO_VERSION special object to not mix up with actual UNKNOWN version from eclipse bz.
maxandersen
force-pushed
the
JBIDE-21363
branch
from
January 23, 2016 00:17
895e4b2
to
538ab2a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why:
to be able to track them without having to jump through too
many hoops.
in sync - we don't need this so much. We just want the bugzillas
to show up in jira for use in sprint planning and overview.
The actual work will still happen in bugzilla for Eclipse.
This change addreses the need by:
created a
bzira.py
script that will take a given bugzillaquery and make sure its resulting bugzillias are listed in
jira (a so called proxy-jira).
Currently assumes the following:
(Eclipse Release Train)
<eclipse title> [EBZ#bzid]' ex.
Add JSON Editor contribution into maven build and include into features [EBZ#484762]`created if not present)
TODO:
Resolves:
JBIDE-21363