[CI] add staging server CICD and prod
branch workflow
#2351
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.
tl;dr:
master
doesn't deploy to prod anymore,prod
does.master
deploys to staging. Never merge anything other thanmaster
intoprod
. Or else.Okay, we will now will have a staging server that we can test changes before we deploy to prod. Here is our new workflow (new steps in bold)
master
and pushed tow3f/polkadot-wiki
master
. Once approved etc, the changes are merged tomaster
master
viewable at https://w3f.github.io/polkadot-wiki-staging and https://w3f.github.io/kusama-guide-staging (these will be switched to https://staging.guide.kusama.network and https://staging.wiki.polkadot.network once I get DNS permissions). These changes will not be reflected on https://wiki.polkadot.network or https://guide.kusama.network yet.prod
. This can be most simply done via a PR frommaster
toprod
(also the best way if the rest of the team needs to see it), or this can just be merged and pushed locally.prod
andmaster
branches, mergemaster
intoprod
, and pushprod
. CICD will pickup this change onprod
, and build appropriately.**I have created a new repo called w3f/polkadot-wiki-staging that handles the hosting of the test server (just like how w3f/kusama-guide-hosting hosts the Kusama Guide).
Still todo (but not blocking merge):