Continuous

Integration
Sainath Sapa, M.Tech [ SE ] - 513
Table of contents
01 Agile Principles →

02 What is CI →

03 Why CI→

04 Components →

05 Benefits →

06 Tools →
Agile Principles

Agile is method of discovery and solutions

improvement through the collaborative effort of
self-organizing and cross-functional teams with
their customer/end use

● Individuals and Interactions over Processes

and Tools.
● Working Software over Comprehensive
Documentation.
● Customer Collaboration over Contract
Negotiation.
● Responding to Change over Following a Plan.
Introduction

Continuous
Integration →
What is C.I. ?
Software Development practice where developers
regularly merge their code changes into a central
repository, after which automated builds and tests
are run.

● Automated tool process and long chain

● Come into picture after code push
● Builds and test the software product
● One part of deployment process
● Checks and resolves dependency issue
Why Continuous Integration.!
Fast
CI improves the build process of
any software product by
implementing multi merging
branching strategies, advance
tool chaining and other factors.
Reliable
CI always checks for
dependency issues in any
application and script it should
run. CI is responsible for making
sure application is runnable.
Tracking
CI raises the bug report and
build issue with any ticketing
platform and gather information
to resolve issue. With help of CI
it's easy to track any bugs.
Components of C.I.

Version Controlling Automated Building

Practice of tracking and managing changes Series of automated steps designed to alert
to software code. Help software teams you as early as possible to any issues in code
manage changes to source code over time. caused by your latest changes.

Automated Testing Deployment

Process is an ideal point to run a number of Every change that passes all stages of your
other checks on your code, such as unit production pipeline is released to your
tests, and linting and static code analysis. customers into VM or Any means of product.
Continuous Integration

Benefits →
Early Detection of Bugs

Vulnerabilities Maintenance
Testing identifies critical Reduced maintenance by
security vulnerabilities. addressing issues early

Bug resolution Code quality

Feedback to developers Catches edge cases
accelerates bug issues and unforeseen
scenarios
Faster Time to Market

Quicker release Ahead of others

Frequent integrations Enabled rapid response to
lead to quicker cycles market demands,

Deployment Flexible project

Reduced time between Facilitated the adoption of
development and deployment. an agile approach
Improved Collaboration

Enhances Work Creative solutions

Collaboration on the Understanding of the project,
same codebase fostering creative solutions.

Productivity Shared knowledge

Reduced communication Knowledge sharing among
barriers for productivity team members.
Enterprises usage of

Tools →
Azure DevOps
Microsoft Powered Cloud Services

AWS Code PipeLines

Amazon Launched Amazon Web Services

GCP DataFlow
Google also has its own Cloud Platform
Azure CI / CD
Pipeline Flow
Continuous Integration

Conclusion →
Code Quality →
Improved Code Quality & Reliable product
with Testing and Bug Fixing

Faster Release →
Communication between developers & Testers
makes this possible

Anywhere Deployment →
Can deploy to any end services from VM to
Container Services
Thanks!
Do you have any questions?

Sainath Sapa, M.Tech [ SE ] - 513

sainath.sit@gmail.com