Add GH workflow to trigger redeploy after new packages are published #2493
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
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.
I'm working on a new staging environment that will be automatically redeployed whenever changes are made to the main branch of the maproulette3 or maproulette-backend repos.
The deployment code lives in maproulette/maproulette-deploy (private for now but I will make this public soon, just need to audit for secret leaks first). This PR adds a workflow to the frontend repo which is triggered when new packages are published (there's an existing repo which builds and publishes packages to GHCR whenever code changes are made). The workflow sends a webhook to the deploy repo to trigger its workflow, which is responsible for deploying the new package version onto the staging server.
I haven't tested this yet (GH actions are hard to test locally) so it may need some iteration, but I'm pretty sure this approach will work.