We have seen the Continuous Delivery workflow in the previous question, now let's see the step by step process of why Jenkins is being called as a Continuous Delivery Tool:
Developers work on their local environment for making changes in the source code and push it into the code repository.
When a change is detected, Jenkins performs several tests and code standards to check whether the changes are good to deploy or not.
Upon a successful build, it is being viewed by the developers.
Then the change is deployed manually on a staging environment where the client can have a look at it.
When all the changes get approved by the developers, testers, and clients, the final outcome is saved manually on the production server to be used by the end users of the product.
In this way, Jenkins follows a Continuous Delivery approach and is called the Continuous
Delivery Tool.
