Use GitHub actions for continuous integration (CI) #53
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
Bye bye Travis CI, you've served us well.
|
I've also set this up so the workflow can be triggered manually. This is particularly useful because we don't currently have a workflow that triggers a website rebuild when a new component release is tagged. For now, this can be triggered in the actions tab like this: https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow In the future, we should create additional workflows for each of our components that would then trigger a rebuild of the website deployment workflow (see also #44). I'll look into this together with @SimonFrings some time in the future once this PR is in. |
jsor
approved these changes
Jul 8, 2021
WyriHaximus
approved these changes
Jul 8, 2021
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.
Bye bye Travis CI, you've served us well.
With these changes applied, the website will now build and deploy using GitHub actions. Unlike the previous Travis CI setup which used a number of built-ins, I've also updated the documentation to describe the manual deployment process in case this automatic behavior should ever break again.
This (manual) deployment process required a number of minor updates to make sure the deployed website behaves exactly like the original site. You're looking at ~8 hours of various attempts to get this to be identical to the previous deployment.
Refs reactphp/reactphp#442