- Challenge 4 - Run the app on Azure should be done successfully.
In a previous challenge we manually deployed the app on Azure. Now with this challenge you will be able to build an entire CI/CD pipeline with Azure DevOps.
- Create a Build definition with Azure Pipelines to build your Docker images and push it to your Azure Container Registry (ACR). Furthermore, enable the
Continuous Integration
feature for this Build definition. - Create a Release definition with Azure Pipelines to run your images on your Azure Web App Service for Containers previously provisionned. Furthermore, enable the
Continuous Devivery
feature for the Release definition. - Update one file on your
master
branch and commit this change, it should trigger automatically the Build and the Release definitions to deploy the new version of your app. - Once deployed, test the app as an end-user, and play a game once deployed there.
- In Azure Cloud Shell, make sure
az webapp list
is showing your Azure services properly. - In Azure Cloud Shell, make sure
az acr repository show-tags
is showing your new container image properly. - In your web browser, navigate to the app and play a game, make sure it's working without any error and that your update is here.
- In Azure DevOps (Boards), from the Boards view, you could now drag and drop the user story associated to this Challenge to the
Resolved
orClosed
column, congrats! ;)
- Deploy to an Azure Web App for Containers - Define your CI build pipeline
- Deploy to an Azure Web App for Containers - Create a release pipeline
Too comfortable? Eager to do more? Try this:
- Instead of using the graphical definition of your Azure Pipelines (Builds), you could use the YAML file definition.
- Instead of building your containers images on the VSTS Hosted agent, you could use the Azure Container Registry (ACR) Build Task feature.
- Instead of leveraging Azure Pipelines (Builds) for buidling your containers images, you could use Jenkins and generate an artifact as input of the Azure Pipelines (Releases) definition.