Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/marcusfelling/demo.spacegame
My own spin on Tailspin's Space game, with the addition of CI/CD for Azure PaaS.
https://github.com/marcusfelling/demo.spacegame
arm-templates azure bicep ci-cd iac pipelines pipelines-as-code
Last synced: 22 days ago
JSON representation
My own spin on Tailspin's Space game, with the addition of CI/CD for Azure PaaS.
- Host: GitHub
- URL: https://github.com/marcusfelling/demo.spacegame
- Owner: MarcusFelling
- Created: 2020-03-25T20:53:45.000Z (over 4 years ago)
- Default Branch: main
- Last Pushed: 2022-12-11T06:28:06.000Z (almost 2 years ago)
- Last Synced: 2023-03-06T18:33:40.657Z (over 1 year ago)
- Topics: arm-templates, azure, bicep, ci-cd, iac, pipelines, pipelines-as-code
- Language: C#
- Homepage: https://demo.myspacegame.com/
- Size: 1.07 MB
- Stars: 4
- Watchers: 0
- Forks: 2
- Open Issues: 7
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Demo.SpaceGame
My own spin on [Tailspin's Space game](https://github.com/MicrosoftDocs/mslearn-tailspin-spacegame-web), with the addition of CI/CD.
The Space Game website is a .NET Core app written in C# that's deployed to Azure App Services, and a SQL Server backend that's deployed to Azure SQL.
# CI/CD
[](https://dev.azure.com/MSFT-MarcusFelling/Demo/_build/latest?definitionId=77&repoName=MarcusFelling%2FDemo.SpaceGame&branchName=master)
1. The main branch is set up with a [branch protection rule](https://docs.github.com/en/github/administering-a-repository/managing-a-branch-protection-rule#:~:text=You%20can%20create%20a%20branch,merged%20into%20the%20protected%20branch.) that requires [TailSpin.SpaceGame.Pipeline](https://github.com/MarcusFelling/Demo.SpaceGame/blob/main/TailSpin.SpaceGame.Pipeline.yml). This means the topic branch that is targeting main, will need to successfully make it through the entirety of the pipeline before the PR can be completed and merged into main.
2. The build stage of the pipeline ensures all projects successfully compile and unit tests pass.
3. The pipeline will then add a comment to your PR with the URL to a new Azure Web App containing your changes, that can be used for exploratory testing or remote debugging.
3. Meanwhile, the pipeline will execute UI and load tests in a testing environment.
4. If all tests are successful, the pipeline will wait for manual approval before deploying to production.
5. After the production deployment is complete, a final stage will run to clean up the development environment, then the PR can be completed.
Note: If DB schema changes containing CREATE, ALTER, or DELETES are detected, a manual review will be required.
