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

HPCC-31397 Jirabot improvements / Cloud Jira support #18408

Merged
merged 1 commit into from
Mar 26, 2024

Conversation

jpmcmu
Copy link
Contributor

@jpmcmu jpmcmu commented Mar 13, 2024

  • Externalized variables that differ between the Jira versions
  • Externalized variables that change such as user mappings
  • Added support for addtional workflow transitions
  • Added support for Cloud Jira
  • Changed PR attachment logic to post additional PRs in a Jira comment
  • Changed comment code to use Jira API to post comments

Signed-off-by: James McMullan [email protected]

Type of change:

  • This change is a bug fix (non-breaking change which fixes an issue).
  • This change is a new feature (non-breaking change which adds functionality).
  • This change improves the code (refactor or other change that does not change the functionality)
  • This change fixes warnings (the fix does not alter the functionality or the generated code)
  • This change is a breaking change (fix or feature that will cause existing behavior to change).
  • This change alters the query API (existing queries will have to be recompiled)

Checklist:

  • My code follows the code style of this project.
    • My code does not create any new warnings from compiler, build system, or lint.
  • The commit message is properly formatted and free of typos.
    • The commit message title makes sense in a changelog, by itself.
    • The commit is signed.
  • My change requires a change to the documentation.
    • I have updated the documentation accordingly, or...
    • I have created a JIRA ticket to update the documentation.
    • Any new interfaces or exported functions are appropriately commented.
  • I have read the CONTRIBUTORS document.
  • The change has been fully tested:
    • I have added tests to cover my changes.
    • All new and existing tests passed.
    • I have checked that this change does not introduce memory leaks.
    • I have used Valgrind or similar tools to check for potential issues.
  • I have given due consideration to all of the following potential concerns:
    • Scalability
    • Performance
    • Security
    • Thread-safety
    • Cloud-compatibility
    • Premature optimization
    • Existing deployed queries will not be broken
    • This change fixes the problem, not just the symptom
    • The target branch of this pull request is appropriate for such a change.
  • There are no similar instances of the same problem that should be addressed
    • I have addressed them here
    • I have raised JIRA issues to address them separately
  • This is a user interface / front-end modification
    • I have tested my changes in multiple modern browsers
    • The component(s) render as expected

Smoketest:

  • Send notifications about my Pull Request position in Smoketest queue.
  • Test my draft Pull Request.

Testing:

Copy link

@jpmcmu jpmcmu requested review from ghalliday and GordonSmith March 13, 2024 13:19
@jpmcmu
Copy link
Contributor Author

jpmcmu commented Mar 13, 2024

@ghalliday @GordonSmith Please review. Note: we will need to create some new Github Action variables before this gets merged.

@@ -14,7 +14,7 @@ jobs:
jirabot:
runs-on: ubuntu-20.04
steps:
- uses: "actions/setup-python@v5"
- uses: "actions/setup-python@v2"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the downgrade intentional? - it will very likely trigger a bunch of dependabot reports

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch, no that wasn't intentional

@jpmcmu
Copy link
Contributor Author

jpmcmu commented Mar 15, 2024

@ghalliday Please review

@ghalliday
Copy link
Member

Change looks reasonable. Please can you add documentation to the jira - what variables are required, typical example of the format for those variables. etc.

@ghalliday
Copy link
Member

@jpmcmu please can we get this merged - waiting on confirmation the symbols are defined, documented and version picked up by gordon is fixed.

- Externalized variables that differ between the Jira versions
- Externalized variables that change such as user mappings
- Added support for addtional workflow transitions
- Added support for Cloud Jira
- Changed PR attachment logic to post additional PRs in a Jira comment
- Changed comment code to use Jira API to post comments

Signed-off-by: James McMullan [email protected]
@jpmcmu
Copy link
Contributor Author

jpmcmu commented Mar 22, 2024

@ghalliday @GordonSmith Code review changes have been pushed up. Required Github Action Vars are on the Jira ticket.

Note: In my testing against the live Jira today, there appears to be an issue either with Cloud Jira or python Jira libraries support of Cloud Jira where authentication of the service account will intermittently fail. I added some code to retry the authentication but this will likely need a better solution in the future as this isn't full proof in my testing.

@jpmcmu
Copy link
Contributor Author

jpmcmu commented Mar 22, 2024

@ghalliday Gordon confirmed the Github vars have been added

@jpmcmu
Copy link
Contributor Author

jpmcmu commented Mar 25, 2024

@ghalliday Any concerns or issues blocking this from being merged I can address? The Jira issue documents the required Github Action vars, Gordon added those vars to the Github repo config, python env script version has also been updated as per Gordon's code review.

@ghalliday ghalliday merged commit 5df4157 into hpcc-systems:candidate-8.12.x Mar 26, 2024
50 of 51 checks passed
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.

3 participants