INTRODUCTRION TO CI/CD

The CI process runs an automated process that builds the framework, whenever a change is
made to the source repository in a version control system. It runs a series of tests to ensure
the recent code update integrates with the existing code in the repository. If it doesn’t, then a
conflict error occurs.

The importance of CI/CD:

 Successful implementation of CI practices can boost confidence in software

development, such that the team will know that test checks are passed, project code
and design follow development standards, and the result is a functioning testable
product with each build.
Jenkins as a CI/CD Tool

Jenkins is a server-side continuous integration tool developed with the Java programming
language.

To use Jenkins with your software, you can either build a git repository or use an existing one
for your CI/CD. The development team is in charge of committing the code to the Dev-
Branch.

When changes are adequately committed to the Dev-Branch, Jenkins can download the
source code from Github and map it to a configured job for a particular role. Once a job is
configured, you must ensure that continuous integration and continuous development are
completed for the job/task.

On successful completion of a job, Jenkins will fetch the code from the Github repository,
and then it starts the task’s commit process. Jenkins will proceed to a new phase called the
task’s construct phase.

The task construct phase is the phase where Jenkins will compile the code and have it
deployed after the DevOps team merges it to the Master branch, then the code is ready for
deployment.
The deployment process is activated once Jenkins has deployed the code. It is then deployed
to the server using a Docker container.