where the release process is automated. Every software change is automatically built, tested, and deployed to production. Source: Amazon Before the final push to production, a person, an automated test, or a business rule decides when the final push should occur. Although every successful software change can be immediately released to production with continuous delivery, not all changes need to be released right away.
practice where members of a team use a version control system and integrate their work frequently to the same location, such as a master branch. Each change is built and verified by tests and other verifications in order to detect any integration errors as quickly as possible
portal.azure.com or create an account. Step 5 Procedure A Git & Azure Create a repo on github, name it forloop-asaba, clone repo on local PC Open your favorite Terminal, create a new file (index.php) Git add, commit & push Click on Create new Web App.
Select your branch *master* Step 5 Configure your web App: name, subscription, resource group, App Service plan & OS. Select your App from dashboard, select deployment options Choose your VCS where you code lives Click OK. Browse your app and it should be live. Procedure B - AZURE
B STEP 3 Step 5 Create a new branch on your repo and push some edit code there Go back to azure, select deployment slots -> click Add slot Configure the slot same way you did for the App step 1 and select configuration source as your previous App Click OK.Browse your app and it should be live with the modification you’ve made and Swap slots Procedure C - Git & Azure