1.
07th May 2022
Noida MuleSoft Meetup Group
CI/CD Pipelines using Azure Devops

2.
2
● Introductions
● Continuous Integration/Continuous Delivery
● Intro to Azure DevOps
● Using Azure DevOps to implement CI/CD
● Hands-On
● Networking time
Agenda

3.
3
Introductions
A SHOW OF HANDS:
Who is new to this Meetup?
Organizer: Shiva Sahu
Speakers
Kushagra Kakkar Rahul Kumar

4.
Continuous Integration/ Continuous Delivery

5.
5
● CI, short for Continuous Integration, is a software development practice in which all
developers merge code changes in a central repository multiple times a day. CD stands for
Continuous Delivery, which on top of Continuous Integration adds the practice of automating
the entire software release process.
What is CI/CD?

6.
6
● A CI/CD pipeline may sound like overhead, but it isn’t. It’s essentially a runnable specification of
the steps that any developer needs to perform to deliver a new version of a software product. In
the absence of an automated pipeline, engineers would still need to perform these steps
manually, and hence far less productively.
Need of CI/CD

7.
7
● Smaller Code Changes
● Fault isolation
● Faster Release Rate
● Customer Satisfaction
● Increase Team Transparency and Accountability
● Easy Maintenance and Updates
Benefits of CI/CD

8.
8
● Jenkins
● Azure DevOps
● AWS CodeCommit/CodePipeline
● GitLab
● BitBucket etc.
Tools used for implementing CI/CD

9.
9
QnA

10.
Introduction to Azure DevOps

11.
11
● Azure DevOps provides developer services for allowing teams to plan work, collaborate on
code development, and build and deploy applications.
● Azure DevOps provides following integrated features that you can access through your web
browser or IDE client:
○ Azure Repos
○ Azure Boards
○ Azure Pipelines
○ Azure Artifacts
○ Azure Test Plans
Intro to Azure DevOps

12.
12
● Azure devops has a simple user interface which makes it easier to go with this tool.
● Azure devops has a built-in Git based source code repository.
● It has a lot of build-in tasks, and a wide variety of extensions/tasks that can be downloaded
from the Azure DevOps marketplace.
● Analytics are provided at the end of each run with parameters like rate and duration of run.
Features of Azure DevOps

13.
13
QnA

14.
Implementing CI/CD using Azure DevOps

15.
15
● As the word repository implies, it is a storage place. So, a code repository is a place to store
code! Now that’s not special. You can simply create a folder on your computer called Source
Code and put it all in there. What’s the point in giving this storage place a fancy name?
● The code repository holds the source code while the version system software that archives
the code. You can archive all your files in a repository, keeping any other versions or files,
even if you aren’t using them at the moment. Code repositories also give you a way to name
or tag the different versions, keeping records of changes within the same project.
● Nexus, Azure Artifacts, chocolatey, npm etc. are some of the Repositories.
● Git and SVN are the major players in Version Control Systems (VCS) area.
What is a Repository?

16.
16
● A DevOps pipeline is a set of automated processes and tools that allows both developers and
operations professionals to work cohesively to build and deploy code to a production
environment. While a DevOps pipeline can differ by organization, it typically includes build
automation/continuous integration, automation testing, validation, and reporting. It may also
include one or more manual gates that require human intervention before code is allowed to
proceed.
What is DevOps Pipeline?

17.
17
● An Azure DevOps Account with permission for hosted parallelism.
● A working Anypoint Platform account.
● Maven and Git Installed on your machine.
Prerequisites for our implementation

18.
18
QnA

19.
Demo

20.
20
QnA

21.
21
● Share:
○ Tweet using the hashtag #MuleSoftMeetups
○ Invite your network to join: https://meetups.mulesoft.com/noida/
● Feedback:
○ Fill out the survey feedback and suggest topics for upcoming events
○ Contact MuleSoft at meetups@mulesoft.com for ways to improve the program
What’s next?

22.
Networking time

23.
Thank you