-
Notifications
You must be signed in to change notification settings - Fork 70
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
chore: add canary to run client e2e tests #845
Conversation
c435b7d
to
1a1b259
Compare
1a1b259
to
08c02ba
Compare
08c02ba
to
187dcb2
Compare
@@ -25,6 +28,17 @@ executors: | |||
AMPLIFY_DIR: /home/circleci/repo/out | |||
AMPLIFY_PATH: /home/circleci/repo/out/amplify-pkg-linux-x64 | |||
|
|||
install_cli_from_local_registry: &install_cli_from_local_registry |
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.
Note: this steps is cloned over from config.base.yml
@@ -106,6 +120,73 @@ jobs: | |||
when: always | |||
- store_artifacts: | |||
path: ~/repo/packages/amplify-e2e-tests/amplify-e2e-reports | |||
publish_to_local_registry: |
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.
Note: this steps is cloned over from config.base.yml
, though I've hard-coded the platform to linux, and removed the parameter as input.
|
||
commands: | ||
scan_e2e_test_artifacts: |
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.
This was cloned over, but made to only operate on linux as a simplifier, same w/ the run_client_tests command.
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
Description of changes
add canary to run client e2e tests, these can be triggered either by the schedule (4 times daily), or kicked off manually by setting the
canary
parameter.N.B. To support running both scheduled and from a manual kickoff I've had to redeclare the workflow in both
config.yml
andconfig.base.yml
, and duplicate a few workflow steps and commands intoconfig.yml
. I'd rather have this duplication and the ability to trigger manual canary runs, at the cost of possible divergence.Publishing metrics to CW will come as a separate PR.
Issue #, if available
N/A
Description of how you validated changes
Verified the manual job in CCI, but still need to verify the scheduling. Because the job is running against main for scheduling, it's not finding the config on that branch, so I'll need to verify once this is merged. I have manually run a canary workflow here https://app.circleci.com/pipelines/github/aws-amplify/amplify-category-api/1320/workflows/d1b3cba7-b950-4cde-b2ea-937c52429312
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.