-
Notifications
You must be signed in to change notification settings - Fork 0
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
[GH-62] Show scheduled test runs in Teams #63
Conversation
|
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.
Thanks @goulter, great work! I’ve left a few comments, but nothing major. I’m looking forward to hearing your thoughts on them.
Please let me know if we should remove the following files. Ideally, the main branch should contain only code that is actively deployed and used, which we can easily retrieve via GitHub if needed:
Thanks again!
inputs: | ||
target-idp-env: | ||
description: > | ||
NOTE: Running this workflows manually via this form will allow you to test the yaml of this workflow file and it will run the same tests as found in "No Slack - Run UW IdP Web Tests." | ||
For "normal" on demand running of the idp tests, the "No Slack - Run UW IdP Web Tests" can be used. | ||
|
||
target-idp-env. Acceptable values are `eval`, `prod`. The idp environment | ||
you want to test against. | ||
required: true | ||
default: eval | ||
|
||
target-idp-host: | ||
description: > | ||
target-idp-host. Optional. If provided, will add an /etc/hosts entry | ||
targeting this host. | ||
required: false |
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.
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.
Ah, right. The main branch in this case is a little misleading. I changed the scheduled task when I merged the an older PR I created for the run on demand workflow. I put the workflow_dispatch
it in there originally just to run the scheduled one on demand. The finished version (the one in this PR) strips out most of the form fields I introduced. I can clarify more if you'd like.
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.
description: > | ||
pytest-args. Any args you want to send to pytest. You do not ever need to | ||
supply `log_cli` arguments. | ||
required: false |
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.
Same comment as above.
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.
see above
|
|
|
|
|
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.
Thanks, Glen, for addressing my comments and making the updates! I believe we're all set now and good to go. 😊
This change brings the old slack notification of the scheduled tests over to teams. Documentation also updated.
Closes GH-62
When this runs on its schedule, the reason will read "Scheduled run"