Jenkins Tutorial23 Dec 2020 | Jenkins
Jenkins is used for automated continuous integration and continuous deployment. And it is an open-source continuous integration in support of DevOps. In Jenkins, you can set up an automated CI/CD process in a stable, convenient, and fast way.
Let us assume a scenario that many developers commit and push their codes into the project repository. Then a test team continuously tests the codes. If codes pass the test, it will be integrated into the project, otherwise it will be sent back to the developer again for bugs fixing. The development team may push codes several times a day, and the test team may need to test the codes over and over again. This will be tedious for testers, as they do the same test repeatedly. As well as, the deployers also do the same tedious process (such as: same build and deploy operation).
With Jenkins, all of these processes test, build, and deploy can be configured for automated actions. So once developers push their codes into the repository, the Jenkin will automatically pull the latest codes from the same repository, build these codes, test them, and deploy them(if the test passed) for your web application.
Let us dive into Jenkins’s journey!