Continuous Delivery Tool
Let’s take a look at the process of continuous delivery in more detail now that we’ve seen it in the previous question. Jenkins is referred to as a continuous delivery tool because of the following reasons:
- Developers modify the source code locally before pushing the changes into the code repository.
- When a change is discovered, Jenkins runs a number of tests and code standards to determine whether or not the change is ready for deployment.
- The developers inspect it following a successful build.
- Following that, the modification is manually deployed on a staging environment so the client can review it.
- The final result is manually saved on the production server so that it may be utilized by the product’s end users when all the modifications have been accepted by the developers, testers, and clients.
Jenkins is referred to be the Continuous Delivery Tool since it adopts this methodology.
