Building a Continuous Delivery Pipeline with Gradle and Jenkins

Track: User Experience + Tools
Skill Level: Intermediate
Room: Room 102
Time Slot: Wed 3/11, 4:00 PM
Tags: automation , groovy , continuous delivery , agile , continuous integration
Presentation Link

Getting software from a developer’s machine to a production environment without a fully automated process is time-consuming and error-prone. Continuous Delivery enables building, testing and deploying of software through build pipelines with well-defined quality gates. In this session, we will discuss how to build such a pipeline with the help of Gradle and Jenkins.

With Jenkins as the centerpiece of our build pipeline, we will model our way from build to deployment. We will start by introducing an example application and learn how to build it with Gradle. Step by step, we will touch on topics like automating unit, integration and functional tests, incorporating popular code quality tools, as well as packaging, publishing and deploying the deliverable.

Gary Hale

Gary is a software engineer focused on creating efficient software delivery practices. He is an IT generalist with over 15 years experience in software development, operations, architecture and everything in between.

Gary is a Principal Engineer at Gradle Inc. and is the author of the Gradle Jenkins plugin and the Gradle Glu plugin. He regularly conducts training classes on Gradle and speaks on topics related to devops, software development, and project automation.