Jenkins CI design  

Almost every organization creates one before they even begin to explore the CI and DevOps tools. In this section, we will go through a very general CI design.

Continuous Integration includes not only Jenkins or any other similar CI tool for that matter, but it also deals with how you version control your code, the branching strategy you follow, and so on.

Various organizations may follow different kinds of strategies to achieve CI, since it all depends on the requirement and type of the project.

Branching strategy

It's always good to have a branching strategy. Branching helps you organize your code. It is a way to isolate your working code from the code that is under development. In our CI design, we will start with three types of branches:

• The master branch
• The integration branch
• The feature branch

This branching strategy is a slimmer version of the GitFlow workflow branching model.

The master branch

One can also call it a production branch. It holds the working copy of the code...