BHARATI VIDYAPEETH
COLLEGE OF ENGINEERING
DEPARTMENT OF INFORMATION TECHNOLOGY
ACADEMIC YEAR: 2021-2022
COURSE NAME: DevOps Lab
COURSE CODE ITL504
EXPERIMENT NO. 04
To understand Continuous Integration, install and
EXPERIMENT Title
configure Jenkins with Maven/Ant/Gradle to setup a
build Job.
NAME OF STUDENT Prathamesh S Sable
ROLL NO. 60
CLASS TE-IT
SEMESTER V
GIVEN DATE
SUBMISSION DATE
CORRECTION DATE
REMARK
TIMELY PRESENTATION UNDERSTANDING
TOTAL MARKS
SUBMISSION
NAME& SIGN.
Prof.H.A.Chavan
OF FACULTY
Aim: To understand Continuous Integration, install and configure
Jenkins with Maven/Ant/Gradle to setup a build Job.
Theory:
Continuous integration (CI) is the practice of automating the integration
of code changes from multiple contributors into a single software project.
It’s a primary DevOps best practice, allowing developers to frequently
merge code changes into a central repository where builds and tests
then run. Automated tools are used to assert the new code’s correctness
before integration.
A source code version control system is the crux of the CI process. The
version control system is also supplemented with other checks like
automated code quality tests, syntax style review tools, and more.
The importance of continuous integration
In order to understand the importance of CI, it’s helpful to first discuss
some pain points that often arise due to the absence of CI. Without CI,
developers must manually coordinate and communicate when they are
contributing code to the end product. This coordination extends beyond
the development teams to operations and the rest of the organization.
Product teams must coordinate when to sequentially launch features and
fixes and which team members will be responsible.
The communication overhead of a non-CI environment can become a
complex and entangled synchronization chore, which adds unnecessary
bureaucratic cost to projects. This causes slower code releases with
higher rates of failure, as it requires developers to be sensitive and
thoughtful towards the integrations. These risks grow exponentially as
the engineering team and codebase sizes increase.
Without a robust CI pipeline, a disconnect between the engineering team
and the rest of the organization can form. Communication between
product and engineering can be cumbersome. Engineering becomes a
black box which the rest of the team inputs requirements and features
and maybe gets expected results back. It will make it harder for
engineering to estimate time of delivery on requests because the time to
integrate new changes becomes an unknown risk.
Installation of Jenkins
1.make sure you have java and maven is installed and set the path for
JAVA_HOME, MAVEN_HOME
2.download Jenkins from https://www.jenkins.io/download/
3.setup further installation using java -jar
4.Open Jenkins on localhost:8080.
5.Paste authentication password which is available on security folder
in .jenkins
7.installation of Jenkins
9. Jenkins is successfully installed
11. Go to global tool configuration to config Maven and jdk.
ADD JDK
Conclusion: install and configure Jenkins with Maven is successfully
done.