What we will cover at the end ● What is Continuous Integration & Continuous Delivery ● Staging/Pipeline/Slots workflow ● Git & Versioning ● Various cloud hosting Platforms ● Sample web Application on this methodology Objective:
Hello World! ❖ Wale Ayandiran ❖ Web developer and Solution Consultant ❖ Web development Learning Facilitator @ekobits ❖ Bits Academy Trainer ❖ Writer at medium.com/justcodenow ❖ Medium @waleloud
Continuous Delivery Defined Continuous delivery is a software development methodology 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.
Continuous Integration CI - Continuous integration is a software development 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
CI / CD Continuous integration (CI) is focused on automatically building and testing code, as compared to CD Continuous delivery (CD), which automates the entire software release process up to production.
Step 1 Step 2 Step 3 Step 4 Login to 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.
Step 1 Step 2 Step 3 Step 4 Authenticate and 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
Step 1 Step 2 Step 3 Step 4 GOTO Procedure 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
STEP 5 Swaps the feature slot to production and Viola! Now you can always test new features on the feature and swap to production when it’s tested & ready.
walecloud
maroon1st
makomakok
.png){kind=avatar}
headwaters
gpsnmeajp
n1215
ogijun2018
o0h
utgwkk
77web
os1ma
alexandresalome
mkeeda
malarkey
thekraken
kneath
paulrobertlloyd
rocio
ufuk
samanthasiow
colly
orderedlist
jonrohan
cherdarchuk
shpigford