ci: move ci/cd pipeline to repo #131
Merged
Conversation
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
|
erlendoksvoll
approved these changes
Aug 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
#130
The deploy pipeline in the deploy-actions repo has a setting for running e2e tests which is really only used by core.
Copied that pipeline here, might consider moving the e2e pipelines too if it's only core that uses it.
Looked into having e2e tests run after staging is deployed without needing approval again for that, but looking at a response here: https://github.com/orgs/community/discussions/68403, I'm not sure how straight forward that is. Let's just start with getting the pipeline working as expected in core for now?
Documentation