Scribd
Upload
41 views

What Is Continuous Integration

Continuous integration is a software development method where team members integrate their work daily by committing code changes to a shared repository. Each commit triggers an automated build and test to detect errors. If tests pass and deployment is successful, the code is pushed to production. Continuous integration aims to integrate work frequently and catch errors early by automating the build, test and deploy process.

Uploaded by

Sandip Bankar
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
41 views

What Is Continuous Integration

Continuous integration is a software development method where team members integrate their work daily by committing code changes to a shared repository. Each commit triggers an automated build and test to detect errors. If tests pass and deployment is successful, the code is pushed to production. Continuous integration aims to integrate work frequently and catch errors early by automating the build, test and deploy process.

Uploaded by

Sandip Bankar
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

What is Continuous Integration?

Continuous Integration  is a software development method where team members


integrate their work at least once a day.
In this method, every integration is checked by an automated build to detect errors.
In Continuous Integration after a code commit, the software is built and tested
immediately.
In a large project with many developers, commits are made many times during a
day.
With each commit code is built and tested.
If the test is passed, build is tested for deployment.
If the deployment is a success, the code is pushed to Production.
This commit, build, test, and deploy is a continuous process, and hence the name
continuous integration/deployment.
Continuous integration (CI) is one of the most vital parts of DevOps.

It is primarily used to integrate various stages of DevOps together.

In other words, it is a coding practice that essentially enables the development


team to make and implement small changes in the code and version control
methods quite frequently.

Continuous integration is usually done in the form where all developers push
the code onto a shared repository mostly multiple times a day.

Why use Continuous Integration?

 Reduction of integration links: All projects employ more than one


person to develop and it greatly increases the risk of errors during
integration. Depending on the complexity of the code, it is possible
that a lot of changes would have to be made. Here comes CI to the
rescue and helps alleviate the issues as it allows for regular
integration.
 Higher quality of code: As the risks drastically reduce, a lot of the
time and manpower can be diverted to creating a much more
functionality-oriented code.
 Code in version control works: Committing something that breaks
the build immediately triggers a notification thereby preventing
anyone from pulling a broken code.
 Ease of testers: Retaining the different versions and builds of the
code eases the work of QAs to understand, locate, and trace bugs
efficiently.
 Decreased deployment time: Automating the process of
deployment eases and frees up a lot of time and manpower.
 Increased confidence: The absence of a possible failure or
breakdown gives developers peace of mind and thereby helps in
delivering greater productivity and higher quality products.

How Continuous integration work?


Nokia used to implement a procedure called nightly build.

After multiple commits from diverse developers during the day, the software built
every night.

Since the software was built only once in a day, it's a huge pain to isolate, identify,
and fix the errors in a large codebase.

Later, they adopted the Continuous Integration approach.

The software was built and tested as soon as a developer committed code.

If any error is detected, the respective developer can quickly fix the defect.

What is Jenkins? How is Jenkins used for Continuous Integration?

Jenkins is an automation tool written in Java with built-in plugins for continuous
integration tasks.

It is used to continuously build and test projects

making it easier to integrate the changing codes to it.

Jenkins allows for faster delivery of software by working with a large number of
deployment and testing technologies.

It also accelerates the development phase via the automation of tasks.


If a team is developing a project, then Jenkins will constantly check and evaluate
the code thereby returning any possible error/failure early in the development
phase.

Creating Jenkins Builds


A build is often called when the source code is converted into a usable and
runnable form.

It allows compiling the code into an executable form.

The process of building is typically handled by the build tool.

Builds are usually done when we reach a critical standpoint such as the
integration of a feature or so on.

As Jenkins is CI-based, we have a powerful feature where we can automate the


build process to happen at a particular time or event. This is called as ‘scheduled
builds.’

You might also like