NOISSUE: Add jira auto clone tool to scripts - #1513
Conversation
openshift-ci
Bot
added
the
approved
|
/cc @ggiguash @dhellmann |
|
So this is a tool 1 person can use to manage all of the bug tickets? Rather than something an individual needs to run with 1 bug ticket they are working on? |
Python tool to automate bug handling: - Checks Fix versions and mismatches for original and cloned bugs. - Checks Target version mismatches with Fix versions. - Checks gaps in Target version against Fix versions and creates clones for those that are not present. - Automatically creates blocks links between clones and originals. - Automatically synchronize clones with originals for Fix versions. - Alert about manual actions required, such as setting Target version/Fix versions.
Added some more stuff now if compared to the original commit.
You can have it fix/setup your own bugs with -i option, or have it run widespread on the whole MicroShift bugs filter. |
dhellmann
left a comment
dhellmann
left a comment
There was a problem hiding this comment.
/lgtm
/retest-required
|
|
||
| fix_versions_missing = set(fix_versions[1:]) | ||
| clones = get_clone_by_issues(issue, connection) | ||
| for clone in clones: |
There was a problem hiding this comment.
The body of this loop has a lot of conditionals and exception handling. We can land this version, but you might be able to simplify this by creating a "command" abstraction so that this function can be split between building a list of commands to run and another function that actually runs them (or not, if dry-run is set).
| finally: | ||
| actions.append([JIRA_URL_PREFIX+clone.key, JIRA_URL_PREFIX+issue.key, "Fix versions updated to match original"]) | ||
|
|
||
| if clone_fix_versions != fix_versions: |
There was a problem hiding this comment.
Does the order of the versions matter here? I don't know if Jira sorts the values or if we might fail to recognize "4.13.0, 4.12.z" being the same as "4.12.z, 4.13.0", for example.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dhellmann, pacevedom The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@pacevedom: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
3 participants
Python tool to automate bug handling:
Which issue(s) this PR addresses:
Closes #