-
Notifications
You must be signed in to change notification settings - Fork 19
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
Add workflow_dispatch github event handling and upgrade rpc #81
Add workflow_dispatch github event handling and upgrade rpc #81
Conversation
Maybe this is relevant too #82 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work!
I didn't see the triggering of the workflow dispatch during the e2e tests? |
Yes it's not triggered as I was not sure if it should be added there. On it! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
2e90c63
to
f2fadd6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll put a comment here just as a note, please modify the e2e tests to trigger workflow dispatch and check that it worked
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, I just talked with David, would you like to merge the current workflow_dispatch feature as it has been tested manually already. And I will revive an old discarded e2e test that include the workflow_dispatch test in another pull request. In that case we don't need to repeat implementing the same test twice.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok. I will clean up the commits first. I will remove those I used to attempt to make the tests work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@weiiwang01 done!
Allowing the workflow with content:
(sha256sum: 1e27bd8a2ebddedbc0d609c8bd804f6a2076e577ca8499ec8f8ac79aa340af77) to be run. /canonical/self-hosted-runners/run-workflows 99a30536ed9311cfa0b7b89af94326d97f91b5cd |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM :-)
04b7766
to
6232241
Compare
Test coverage for 6232241
Static code analysis report
|
This PR was "moved" to #84 as it could not use the secrets when running the workflows. The reason was that this was an external (read: from my own account) one. Closing |
Requirements:
This PR modifies pre-job.j2 allowing it to differentiate between different github events, handles workflow_dispatch and logs useful variables to syslog.
Also the repo-policy-compliance package is upgraded on upgrade_charm.