Summary

In this chapter, we discussed different migration strategies from existing build tools to Gradle, which could be very handy for users who are planning to migrate their existing Ant and Maven scripts to Gradle. We also discussed how to publish artifacts to repositories, which is a key functionality of any build tool, which help the users to always fetch the latest artifacts from the repositories. We discussed CI framework with the help of Jenkins and how Gradle fits into this flow, while automating the build and deployment solution. Finally, we discussed how to generate documents for the Java code.

In the next chapter, we will be discussing how to integrate TestNG with Gradle, which would help the user to run test cases as a part of the Gradle build. We will also be discussing integration testing strategies and Gradle integration with code analysis and code coverage tools.