Building a Continuous Delivery Pipeline with Gradle and Jenkins
summary
Builds a continuous delivery pipeline that actually produces one immutable WAR per commit, using Gradle wrapper to standardize builds and Jenkins pipeline jobs to chain stages. Commit stage aims for 5–10 minutes: compile, unit tests, integration tests (separate sourceSet), JaCoCo coverage, static analysis, then publish to Artifactory. Deployment uses Cargo/Tomcat, Liquibase or Flyway for DB migrations, SonarQube for history, and manual UAT → production promotion in Jenkins.
AI-written summary · about
chapters (25)
- 0:00Intro
- 2:27principles
- 8:22The "revolutionary" sample application
- 9:08Multi-project dependencies
- 9:39Project hierarchy
- 16:41Project artifacts
- 17:06Stages in build pipeline
- 21:32Commit stage: Compile/unit tests
- 22:17Commit stage: Integration tests
- 23:04Separate tests in project layout
- 24:05Separate tests with SourceSets
- 27:21Database integration tests
- 31:32Picking the "right" code coverage tool
- 33:52JACOCO Java Code Coverage
- 35:05Generating coverage reports
- 36:19Code coverage with JaCoCo
- 38:02Commit stage: Code analysis
- 38:28Static code analysis tools
- 43:44Measure quality over time with Sonar
- 45:17Applying the Sonar Runner plugin
- 50:07Commit stage: Assemble distribution
- 54:47Packaging the deployable artifact
- 56:55Commit stage: Publish binaries
- 57:15Defining build configuration
- 59:28Reading build configuration
related talks
52mContinuous Delivery of Microservices using Jenkins and Gradle
04mContinuous Delivery with Jenkins' New Declarative Pipeline & Artifactory
34mContinuous Delivery with Jenkins Workflow
34mTDD for jenkins pipelines
37mImport Continuous Delivery
30mImplementing Continuous Deployment with Jenkins & Gerritt
29mFrom scheduled builds to commit triggered pipelines
44mStairway to Heaven: 10 Best Practices for Enterprise Cont. Delivery w/ Jenkins