-
Notifications
You must be signed in to change notification settings - Fork 2
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
Fix Staging Deployment #311
Conversation
Component Test Results
Tests run stats
Failed testsClick to revealSkipped testsClick to revealSkipped tests by CypressClick to reveal |
Component Test Results
Tests run stats
Failed testsClick to revealSkipped testsClick to revealSkipped tests by CypressClick to reveal |
…Js server so the cypress setup file can read them
Component Test Results
Tests run stats
Failed testsClick to revealSkipped testsClick to revealSkipped tests by CypressClick to reveal |
Component Test Results
Tests run stats
Failed testsClick to revealSkipped testsClick to revealSkipped tests by CypressClick to reveal |
Component Test Results
Tests run stats
Failed testsClick to revealSkipped testsClick to revealSkipped tests by CypressClick to reveal |
E2E Test Results
Tests run stats
Failed testsClick to reveal
Skipped testsClick to revealSkipped tests by CypressClick to reveal |
Component Test Results
Tests run stats
Failed testsClick to revealSkipped testsClick to revealSkipped tests by CypressClick to reveal |
Component Test Results
Tests run stats
Failed testsClick to revealSkipped testsClick to revealSkipped tests by CypressClick to reveal |
Component Test Results
Tests run stats
Failed testsClick to revealSkipped testsClick to revealSkipped tests by CypressClick to reveal |
Component Test Results
Tests run stats
Failed testsClick to revealSkipped testsClick to revealSkipped tests by CypressClick to reveal |
Component Test Results
Tests run stats
Failed testsClick to revealSkipped testsClick to revealSkipped tests by CypressClick to reveal |
Component Test Results
Tests run stats
Failed testsClick to revealSkipped testsClick to revealSkipped tests by CypressClick to reveal |
…ber instead of the issue number
Component Test Results
Tests run stats
Failed testsClick to revealSkipped testsClick to revealSkipped tests by CypressClick to reveal |
Component Test Results
Tests run stats
Failed testsClick to revealSkipped testsClick to revealSkipped tests by CypressClick to reveal |
Component Test Results
Tests run stats
Failed testsClick to revealSkipped testsClick to revealSkipped tests by CypressClick to reveal |
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.
🧙♂️Seth, you're a wizard, how did you figure this out???🧙♂️
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.
Seth, you are actually a wizard. You not only move the deployment move from Vercel to AWS, but also make tests run. My only demand is to update the AWS architecture to show off this new cool pipeline
Wiill do |
Description:
Fixes the GitHub Actions to deploy and run Cypress tests on the newly set up staging environment on AWS.
Related Issues:
#307
Checklist:
Before submitting this pull request, please make sure of the following:
master
branch.Screenshots or Visual Changes (if applicable):
N/A
Documentation
To be added