Chapter 13. Continuous integration
This chapter covers
- The benefits of continuous integration
- Using Jenkins to build a Gradle project
- Exploring cloud-based CI solutions
- Modeling a build pipeline with Jenkins
If you’re working as a member of a software development team, you inevitably will have to interface with code written by your peers. Before working on a change, a developer retrieves a copy of the code from a central source code repository, but the local copy of this code on the developer’s machine can quickly diverge from the version in the repository. While working on the code, other developers may commit changes to existing code or add new artifacts like resource files and dependencies. The longer you wait to commit your source code ...
Get Gradle in Action now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
