Scribd
Upload
207 views25 pages

Azure DevOps CI-CD

This document provides an overview of continuous integration (CI) and continuous delivery (CD) pipelines using Azure DevOps. It describes how CI automates code integration and builds, while CD automates code deployment. The Azure build pipeline is triggered on code commits to run unit tests and package artifacts. The Azure release pipeline is then used to deploy packaged artifacts through development, testing, and production stages using variable substitution and approval gates.

Uploaded by

mennsu zen
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
207 views25 pages

Azure DevOps CI-CD

This document provides an overview of continuous integration (CI) and continuous delivery (CD) pipelines using Azure DevOps. It describes how CI automates code integration and builds, while CD automates code deployment. The Azure build pipeline is triggered on code commits to run unit tests and package artifacts. The Azure release pipeline is then used to deploy packaged artifacts through development, testing, and production stages using variable substitution and approval gates.

Uploaded by

mennsu zen
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 25

CI/CD

Presented By:
Evans Edem Ladzagla
OUTLINE
 DevOps Methodology

 Overview of CI/CD

 CI PIPELINE

 CD PIPELINE
DEVOPS METHODOLOGY

Software Development Cycle


 Plan
 Code
 Build
 Test
 Release
 Deploy
 Operate
 Monitor C
CI D
OVERVIEW OF CI/CD
 Continuous Integration (CI) is a development
practice that automates continuous integrate of code
into a single shared repository.

 Continuous delivery (CD) is automating the ability to


deploy your integrated code into production.

 Hence CI/CD is a way to automate both the


Development and Operation (DevOps) of the
Software Development Cycle
Azure Build Pipeline (CI)

• Write codes
• Commits codes
• Pushes Codes to Azure Repos
Developer

• Triggers Build
• Build Codes
• Run Unit Test
Azure • Packages Artifacts
• Publish Artifacts
Repo
Azure Release Pipeline (CD)
• Pull Artifacts
• Update Release Variables
Azure Artifacts • Publish To Staging

• Deploy To Development Stage


• Deploy To Testing Stage
Staging

• Approval and Gates


Production • Deploy To Production
Stage
KNUST STAGING
• Automatically Triggered
• DNS: www.appsd.knust.edu.gh
DEVELOPTMENT • IP: 192.168.1.190

• Manually Triggered
• DNS: www.appst.knust.edu.gh
TESTING • IP: 192.168.1.121

• Automatically Triggered
• Require Approval and Gates
• DNS: www.appsp.knust.edu.gh
PRODUCTION • IP: 192.168.1.177
CREATING BUILD PIPELINE
CREATE BUILD PIPELINE

1. Click on Create Pipeline


CONFIGURE BUILD PIPELINE

1. Choose The Classic Editor


SELECT CODE SOURCE

1. Select The Repo Source


2. Select The Repo
3. Select The Project
4. Select The Branch
BUILD PIPELINE TEMPATE

1. Choose ASP.NET Core


CLASSIC BUILD PIPELINE EDITOR

1. Enter The name of the


Pipeline
2. Select Agent Pool
3. Specify the path to the
project to Build
4. Save Pipeline
BUILD PIPELINE TRIGGER

1. Select The Triggers Tab


2. Check The Enable
Continues Integration
3. Specify the Include /
Exclude Branches Where
applicable
4. Specify the Include
/Exclude paths Where
applicable
CREATING RELEASE PIPELINE
CREATE RELEASE PIPELINE

1. Click on Release Under


Pipelines Menu Item
2. Click on New
3. Click on New Release
Pipeline
RELEASE PIPELINE TEMPLATE

1. Select IIS Web


Deployment
ARTIFACT

1. Click on add Artifact


2. Select Build as source type
3. Select Project
4. Select Build Pipeline
source
5. Select Default Version as
Latest
6. Click on Add
CONTINUOUS DEPLOYMENT TRIGGER

1. Click on the thunder bolt


at the right top corner of
the artifact
2. Check Enable continuous
deployment trigger
PRE-DEPLOYMENT CONDITIONS

1. Click on the thunder bolt


at the right top corner of
the stage
2. Check Enable Pre-
deployment approvals
3. Add users to the
Approvers list
4. Choose appropriate
Approval Order
CONFIGURE STAGE

1. Click on a stage to edit it


2. Enter the stage name
3. Select IIS Website as
Configuration type
4. Select Start as Action
5. Enter Website name
DEPLOYMENT GROUP JOB – IIS DEPLOYMENT

1. Click on the IIS


Deployment Job
2. Select Deployment Group
3. Enter required tags where
applicable
IIS WEB APP DEPLOY

1. Select IIS Web App Deploy


job
2. Enter the virtual
Application path where
applicable
3. Check XML transformation
if applicable
4. Check XML variable
substitution if applicable
5. Enter the Path of all json
file for variable
substitution
VARIABLE SUBTITUTION

1. Click on Variables Tab


2. Enter the name, value
scope where needed
3. Click Save to save the
pipeline
THANK YOU

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy