-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Tweak readme, update multi-module support.
- Loading branch information
Showing
6 changed files
with
30 additions
and
315 deletions.
There are no files selected for viewing
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
This file was deleted.
Oops, something went wrong.
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,25 @@ | ||
Generates a JQL query to find JIRA issues that are done, but the GitHub issue is open. | ||
There are three applications in here to facilitate our JIRA/GitHub interaction | ||
|
||
1. io.dockstore.jira.ResolutionChecker - used to help find issues open in GitHub that are closed in JIRA. This was to diagnose an issue where | ||
Unito was seemingly mysteriously closing JIRA issues at random. It turned out to be because we hadn't properly configured | ||
a GitHub and JIRA user in Unito -- it's the Unito intended behavior. We currently don't need to run this, although if we have | ||
a configuration issue again, it could be useful in the future. | ||
2. io.dockstore.jira.MilestoneChecker - generates GitHub and JQL queries to find mismatches in the JIRA fix version and GitHub milestone. The JIRA fix version is | ||
a multi-value field; the GitHub milestone is a single-value field, so Unito doesn't sync them. We have to remember to manually | ||
keep them in sync; this program identifies cases we've missed. | ||
3. SprintStart - an barely started work in progress to automatically generate review tickets at the beginning of a sprint, which | ||
is currently a manual and tedious process. | ||
|
||
# Auth | ||
|
||
* ResolutionChecker and MilestoneCheck require environment variable `GITHUB_TOKEN` be set to a GitHub personal access token. | ||
* SprintStart requires the environment variable `JIRA_TOKEN` be set to a JIRA token. | ||
|
||
# Usage | ||
|
||
I usually run in IntelliJ with a Run Configuration | ||
|
||
1. In Run Configuration, set the main class to io.dockstore.jira.MilestoneChecker or io.dockstore.jira.ResolutionChecker | ||
2. Add the environment variable `GITHUB_TOKEN` to your GitHub token. | ||
3. The console will print out generated queries, which you then paste into your browser. | ||
|
||
Set the environment variable `GITHUB_TOKEN` to a personal access token prior to running it, or you'll likely hit the | ||
GitHub rate limit. |
This file was deleted.
Oops, something went wrong.
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
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