Integrate Jira issue creation/update #35
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
kimpaller
reviewed
Nov 9, 2021
kimpaller
force-pushed
the
adgt-test-harness
branch
2 times, most recently
from
4c45d4b to
2c95365
Compare
tagoylo
reviewed
Nov 18, 2021
jpineda3
force-pushed
the
fix-jira-calls
branch
from
3840875 to
170eb8d
Compare
jpineda3
force-pushed
the
fix-jira-calls
branch
from
98e1999 to
fe303dc
Compare
kimpaller
reviewed
Jan 26, 2022
jpineda3
force-pushed
the
fix-jira-calls
branch
2 times, most recently
from
6898769 to
1e5a759
Compare
Signed-off-by: Julia Pineda <[email protected]>
Signed-off-by: Julia Pineda <[email protected]>
Signed-off-by: Julia Pineda <[email protected]>
Signed-off-by: Julia Pineda <[email protected]>
Signed-off-by: Julia Pineda <[email protected]>
Signed-off-by: Julia Pineda <[email protected]>
Signed-off-by: Julia Pineda <[email protected]>
Signed-off-by: Julia Pineda <[email protected]>
Signed-off-by: Julia Pineda <[email protected]>
Signed-off-by: Julia Pineda <[email protected]>
Signed-off-by: Julia Pineda <[email protected]>
Signed-off-by: Julia Pineda <[email protected]>
kimpaller
pushed a commit
that referenced
this pull request
Apr 25, 2022
* Define logJira and var defaults Signed-off-by: Julia Pineda <[email protected]> * get_gitsha: return hash map Signed-off-by: Julia Pineda <[email protected]> * UpdateBOOTFiles: Parse failing_msg outside if send_results Signed-off-by: Julia Pineda <[email protected]> * UpdateBOOTFiles: Call logJira Signed-off-by: Julia Pineda <[email protected]> * LinuxTests: Call logJira Signed-off-by: Julia Pineda <[email protected]> * PyADITests: Call logJira Signed-off-by: Julia Pineda <[email protected]> * Libad9361Tests: Call logJira * MATLABTests: Call logJira Signed-off-by: Julia Pineda <[email protected]> * Move common jiraArgs update inside logJira Signed-off-by: Julia Pineda <[email protected]> * Revert get_gitsha definition Signed-off-by: Julia Pineda <[email protected]> * Enclose Jira site access in try-catch Signed-off-by: Julia Pineda <[email protected]> * logJira cleanup Signed-off-by: Julia Pineda <[email protected]> * LinuxTests: Attach dmesg.log Signed-off-by: Julia Pineda <[email protected]>
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.
logJira(jiraArgs) method first checks if an issue with summary in the form "[carrier-daughter] Stage failure message" exists in the project. Carrier and daughter board names are read from nebula-config, requiring these changes sdgtt/nebula-config#2
A comment is added if the issue exists. Otherwise, an issue is created.
jiraArgs is a map for Jira issue fields. The only hard requirement is the issue summary. Default values are assigned to relevant fields which are overwritten when listed in jiraArgs. If an issue exists and description is included in jiraArgs, the description appears in the added comment.
The attachment key in jiraArgs should have a list value. Attachments are uploaded for all stages other than the libad9361, work in progress.
The log_jira Gauntenv var should be true to enable Jira issue creation/updates. This is false by default.
log_jira_stages Gauntenv var should contain the stage names wherein Jira issue creation/update is allowed. By default this is an empty list such that if the log_jira flag is true, Jira will be accessed wherever logJira method is called.
See https://jira.analog.com/projects/HTH/summary for examples of created issues.