-
Notifications
You must be signed in to change notification settings - Fork 101
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
Enable repository_dispatcher trigger in functional test" #5640
Conversation
Radius functional test overview
Click here to see the list of tools in the current test run
Test Status⌛ Building Radius and pushing container images for functional tests... |
Test Results2 750 tests ±0 2 743 ✔️ ±0 1m 54s ⏱️ -1s Results for commit c943da8. ± Comparison against base commit 381c73f. This pull request removes 2 and adds 2 tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
@vinayada1 can you please change the title to be more specific? for example, "Enable repository_dispatcher trigger in functional test" |
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.
Before merging the PR, please change the title to be more specific. e.g. Enable repository_dispatch trigger for functional test
github-token: ${{ secrets.GH_RAD_CI_BOT_PAT }} | ||
script: | | ||
const testPayload = context.payload.client_payload; | ||
if (testPayload && testPayload.command == "ok-to-test") { |
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.
if (testPayload && testPayload.command == "ok-to-test") { | |
if (testPayload && testPayload.command === "ok-to-test") { |
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.
What's the purpose of checking the command here? It should have already been checked before this workflow starts right?
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.
Yes it will be checked before as well. Just to make sure we are processing the right repository event and if we want to add more commands later
Radius functional test overview
Click here to see the list of tools in the current test run
Test Status⌛ Building Radius and pushing container images for functional tests... |
Trigger e2e tests on repository_dispatch event
16adee3
to
c943da8
Compare
Radius functional test overview
Click here to see the list of tools in the current test run
Test Status⌛ Building Radius and pushing container images for functional tests... |
Trigger e2e tests on repository_dispatch event
Description
Trigger e2e tests on repository_dispatch event. The remaining changes to create the repository_dispatch event will be made in a separate PR for testing purpose
#5618
Fixes: #issue_number
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:
Auto-generated summary
🤖 Generated by Copilot at 9485678
Summary
🧪🍴📥
Enable functional-test workflow to run on external pull requests from forks. Add step to read
e2e-test
event payload and set fork branch and issue number variables.Walkthrough
repository_dispatch
event and set environment variables for the forked pull request (link)