-
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
Run e2e tests on merge to main #91
Open
rylew1
wants to merge
5
commits into
main
Choose a base branch
from
rylew/run-e2e-on-merge-to-main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
name: CI app E2E tests on main | ||
|
||
on: | ||
push: | ||
branches: | ||
- main | ||
workflow_dispatch: | ||
inputs: | ||
service_endpoint: | ||
description: "The service endpoint URL for the E2E tests" | ||
required: true | ||
type: string | ||
app_name: | ||
description: "The application name" | ||
required: true | ||
type: string | ||
|
||
jobs: | ||
call-e2e-tests: | ||
name: " " # GitHub UI is noisy when calling reusable workflows, so use whitespace for name to reduce noise | ||
uses: ./.github/workflows/e2e-tests.yml | ||
with: | ||
service_endpoint: ${{ inputs.service_endpoint || 'http://app-dev-2093346449.us-east-1.elb.amazonaws.com' }} | ||
app_name: ${{ inputs.app_name || 'app' }} | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
@lorenyu - I think we need to have this workflow on the default branch / main to run it manually
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.
Here's a way to run it manually:
pull_request
trigger to the workflow. This will cause the workflow to run once on your branch.pull_request
trigger from the workflow.gh workflow run ci-app-e2e-tests.yml --ref rylew/run-e2e-on-merge-to-main
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.
Oh interesting, haven't used the cli yet. I will hold off on this for now though.
Will the CLI paradigm allow for a
service_endpoint
to be passed in? - I see it's kind of unclear in the current paradigm - seems like the only way to set it up ontemplate-infra
now would be to have the user potentially hardcode their dev environment and app name