DevOps Services

CONTINUOUS
INTEGRATION
Presented by Group 2
 CI Process

Develop and compile

Perform unit tests

INTRODUCTION Integrate with databases

Perform preproduction
deployment activities

Perform functional tests and

code labeling

Generate reports and analyze

 SIGNIFICANCE

Reduce Better High Reduced Enables Enables

Risk Communication Product Waiting Better Self
Quality Time Transparency Testing
 HOW DOES IT WORK?
Developers commit to a shared repository using a version control system

Run local unit tests on the code for verification before integration

CI service automatically builds and runs test on new code changes

DIFFERENCE BETWEEN
CI AND CD
Often used interchangeably

CD - Continuous Delivery

CD - Continuous Deployment

All 3 practices are connected

 WAYS TO MEASURE CI
Code commits trigger a build of the
software
The percentage of code commits that result in a
software build without manual intervention.
Code commits trigger a series of
automated tests
The percentage of code commits that result in a
suite of automated tests being run without manual
intervention.
Automated builds and tests are
executed successfully every day
The percentage of automated builds and the
percentage of automated tests that are executed
successfully every day.
Current builds are available to testers
for exploratory testing
The availability of builds to testers, or its inverse,
namely the unavailability of builds to testers.
Developers get feedback from the
acceptance and performance tests
every day
The availability of feedback to developers from
acceptance and performance tests— that is, the
percentage of tests that provide feedback that is
available to developers within a day.
Broken builds are fixed immediately
The time it takes between the build breaking and
having it fixed, either with a check-in that fixes
the problem, or by reverting the breaking change.

Test Driven Development
Constantly develop and improve
the test coverage. Each new
feature should have an
accompanying set of tests.
BEST PRACTICES
Pull Requests & Code Review
A pull request is created when a
developer is ready to merge new
code into the main codebase. It
notifies other developers of the
new set of changes.
Optimize Pipeline Speed
Any small delay in the CI workflow
will compound exponentially as the
rate of feature releases team size,
and codebase size grows.
 LIST OF TOOLS
1 Bitbucket Pipelines 2 Azure Pipelines 3 AWS CodePipeline

4 Jenkins 5 GitLab 6 CircleCI

7 Atlassian Bamboo

CHOOSING THE BEST TOOL

Version Control System Support Container Support

On-Premises vs cloud Plugins and 3rd party integrations

 CHALLENGES

Organizational Culture Changes: Version Control: The changes

Organizations may be resistant to can force to rewrite the process.
Continuous Integration.

Difficult to Maintain: It is not easy to Numerous Error Messages:

set up an automatic code Teams may encounter CI error
repository. notifications and tend to ignore
as they are occupied with other
tasks.
CONCLUSION
Execute quicker and more
effectively

Standard fixture of modern high

efficiency

Third-party tools

Benefits and Challenges

THANK YOU!

FARZEEN KHAN
BINISHA SHAH
SHUBHAM KUMAR
SHIVAM BANSAL
ROHIT BIRWATKAR
NAGESH SIRSAT
JAI UPADHYAY
JAISON JACOB