Skip to content
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
merged 8 commits into from
Jan 23, 2016
Merged

Conversation

maxandersen
Copy link
Owner

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.

Resolves:
JBIDE-21363

@alexeykazakov
Copy link
Collaborator

should we use bug.product + '-' + bug.compnent for component name ?

I think adding bug.component as a label is enough for now.

maxandersen and others added 6 commits January 22, 2016 18:41
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
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants