For continuous integration to work, you need a CI server like Jenkins, which is able to monitor your source code repository for new changes and respond in configurable ways. In a continuous Integration process, code that has been checked into a source code repository can be automatically checked out, built, tested in a variety of ways, and published to a repository.

You'll also install and run a handful of popular Jenkins plugins for static code analysis testing and reporting. You'll learn how to build and unit test the project in Jenkins with JUnit, as well as how to troubleshoot build failures. We'll begin with an overview of the CI and CD process, then setup a Java web project using Maven and Jenkins. This installment of Open source Java projects introduces continuous integration with Jenkins, a leading automation server for CI/CD. Whatever the designation, CD is a process that moves software from code check-in to staging, or even production deployments.

These days many dev teams have moved beyond CI to CD, which stands for either continuous delivery or continuous deployment. It's no exaggeration to say that CI tamed the 'build' side of the build-and-deploy cycle. With continuous integration we could detect errors more quickly and release code much faster than we had done in previous years.

Many test-driven developers also started doing integration testing and performance testing in a secondary CI process. With these techniques we could automatically build source code whenever a developer checked it into a source repository, executing an exhaustive unit test suite to ensure that an application was working properly. Over a decade ago, agile developers began to embrace and promote test-driven development and continuous integration (CI). The most consistent thing about this style of development was inconsistency-in process and in results. When the dev team was satisfied with the build, we would manually deploy the application into production. In those days, a software development lifecycle consisted of running builds on a local machine, manually copying the artifacts to a staging server, and manually testing each application through multiple iterations.

Looking back at how software was built and deployed even 15 years ago, it seems surprising that our applications actually worked.

Download jenkins teamcity