forked from backstage/backstage
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request backstage#7 from thefrontside/mk/notes
Add document to lay out overview of the deployment steps
- Loading branch information
Showing
2 changed files
with
30 additions
and
4 deletions.
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
# Backstage Deployment Workflow Overview | ||
|
||
The file for this workflow is located [here](https://github.com/thefrontside/backstage/blob/main/.github/workflows/release.yaml). | ||
|
||
Runs on commits to the main branch (pull request merge commits): | ||
|
||
1. Authenticate workflow runner to GCP | ||
|
||
2. Install Cloud SDK | ||
- This is so we can run `gcloud` commands to submit a build to `Cloud Build` | ||
|
||
3. Run yarn install, tsc, and build | ||
|
||
4. Build Backstage image using `Cloud Build` and push to `Artifacts Registry` | ||
- Uses the git commit SHA as image tag | ||
|
||
5. Authenticate to GKE cluster to upgrade deployments | ||
|
||
6. Upgrade [postgres chart](https://github.com/thefrontside/backstage/tree/main/charts/postgres) | ||
|
||
7. Upgrade [backstage chart](https://github.com/thefrontside/backstage/tree/main/charts/backstage) | ||
- The deployment chart will use the new Backstage image that was just pushed to the Artifacts Registry | ||
|
||
8. Confirm the new deployment of Backstage is successful | ||
- If unsuccessful the deployment will rollback to the previous revision |