Jenkins
Software integration may not be necessary for stable projects, but it is essential for projects with frequent changes. After all, waiting to integrate often results in integration conflicts and can take too much time to resolve, leading to project delays.
To keep your current customers happy, Jenkins creates a fast and effective process of getting your product to market before your competition as well as releasing new features and bug fixes.
What you will learn?
- What is Jenkins?
- What is CI/CD?
- Why Jenkins — Features of Jenkins
- Jenkins Pipeline
- Jenkins Architecture
What is Jenkins?
Jenkins is an open-source automation server helping automate the parts of software development related to building, testing, and deploying, facilitating continuous integration and continuous delivery. Specifically, Jenkins is used to build and test your product continuously, so developers can continuously integrate changes into the build.
What is CI/CD?
Continuous integration (CI) helps ensure that software components work together, allowing you to continuously integrate code into a single shared and access repository easily. Integration should be completed frequently.
Continuous delivery (CD) picks up where continuous integration ends. While CI is the process to build and test automatically, CD deploys all code changes in a build to the testing or staging environment, letting you take the code stored in the repository and continuously deliver it to production.
Why Jenkins — Features of Jenkins
Jenkins helps developers ensure that their code changes in parallel can be integrated without errors. Without Jenkins, manual integration testing would happen infrequently and would be time-consuming. Also, Jenkins provides a standardized build and test environment for developers. Let’s have a look at what features Jenkins has.
Easy Installation
The installation requires Java commands on the earlier version of Jenkins — Hudson. However, nowadays Jenkins is ready to run with packages for Windows, Mac OS X, and Unix-like OS, which means that it’s installation-friendly for those who do not know how to use the command line.
Easy Configuration
Jenkins can be easily set up and configured via its web interface which includes error checks and built-in help.
Plugins
It has hundreds of plugins in the Update Center and integrates with every tool in the CI and CD toolchain. In addition, it is super flexible for you to create your own plugins if needed.
Get Eileen Chu’s stories in your inbox
Join Medium for free to get updates from this writer.
Some useful functions as the following:
- RSS/Email integration notification → Jenkins provides the function of RSS subscription or Email notification. We can notify users when a problem occurs during the construction process. Moreover, to maintain the high availability of code in version control systems, this function indirectly prevents users from accidentally checking in unfinished code or programs that fail to pass the test.
- Reports generation → Jenkins supports the presentation of test results, test coverage, or various static analysis data through reports. It is also convenient for users to view various facets of the project, for example, confirming whether all tests have been completed, or making sure whether following the company’s coding style. Consequently, this will invisibly improve the quality of the software and increase developers’ sense of achievement.
Extensible
Jenkins can be extended via its plugin architecture and provides nearly infinite possibilities for what it can do.
Distributed
Jenkins can easily distribute work across multiple machines, helping in faster builds, tests, and deployments across multiple platforms.
Jenkins Pipeline
We can say a Jenkins pipeline is a path for delivering a unit of change starting from development to production. Particularly, it will help the software move efficiently from the development phase to the production phase by using automation tools. It is used to incorporate continuous delivery in our software development workflow.
Jenkins Architecture
- Developers commit changes to the source code.
- CI server → Jenkins server checks the repository at regular intervals and pulls any newly available code.
- Build server → Build server builds the code into an executable file. Developers would receive feedback from the build server if the build fails.
- Test Server → For testing, Jenkins then deploys the build application on to the test server. If the test fails, feedback is immediately sent back to the developers.
- Production server → If there are no errors, the tested application is then deployed onto the production server.


![[新北市] The Edge 邊緣咖啡|充滿秘密基地的座位。熱紅酒](https://miro.medium.com/v2/resize:fit:1358/format:webp/1*7RABg4jyKLpOVmpOLnn12g.png)

![[新北市] Cafe & Me | Hidden Cafe。鬆餅。復古鄉村](https://miro.medium.com/v2/resize:fit:1358/format:webp/1*g7WMPmXgOcrzJeFJFG2ttw.png)




