Continuous Deployment – PaaS Compute Options

Continuous Deployment – PaaS Compute Options

Azure App Services have out-of-the-box support for continuous integration and deployment from a variety of providers. You can continue using your favorite source control program, be it Azure DevOps, GitHub, BitBucket, or any local Git; you can seamlessly integrate this with Azure App Services. No complex configuration is required; all you need do is connect the repository to the Azure App Service. Whenever there is a code change, the Azure App Service will automatically sync all changes from the code repository. Furthermore, if you are already using Azure DevOps, you can create your build and release process, run the tests, build the release, and automatically deploy the code to the App Service every time your developers commit the code. The best part is all this happens seamlessly and implicitly without any sort of manual intervention.

In Figure 9.1, you can see an example of how the code commits are logged in the App Service and deployment is done. This example uses Azure Repos as the source control for storing the code.

FIGURE 9.1 Continuous deployment from Azure Repos

The deployment options can be classified into automated deployment and manual deployment. Let’s see the set of tools or options available under each of these deployment options.

Automated Deployment

Automated deployment is also called continuous integration. In this process, the code will be updated with new code changes as soon as the developers commit. This process is ideal for pushing for new features and bug fixes in a repetitive and fast manner. During the process, the impact will be minimal on the end users. The following options are supported:

• Azure DevOps: You can push your code to Azure DevOps, and you can create our build and release process, run the tests, build the release, and automatically deploy the code to the App Service every time the developers commit the code.
• GitHub: Being one of the popular source control programs, Azure App Service supports continuous integration from GitHub directly. Any changes pushed to the main branch will be automatically deployed.
• BitBucket: This is another remote repository like GitHub. Based on the commits made in the repository, changes will be automatically pushed to the App Service.
• Local Git: If you are maintaining a local Git repository, you can connect that to Azure App Service. All committed changes will be reflected automatically.