Continuous Delivery

Jez Humble's Continuous Delivery Web site

Common Pain Points (highest to lowest) [from DZone]:

1. Environment Configuration and setup

2. Deployment Process

3. Supply Chain Management

4. Requirements Issues

5. User Acceptance Test

6. Build And Compile

7. Automated Tests

8. Coordination of teams, users and resources

9. Untidiness in changes

10. Delivery and Rollout

11. Regression Test

12. Performance Test

13. Integration Test

Notes From YouTube Video: Building a Continuous Delivery Pipeline with Gradle and Jenkins

Principals:

1. Every commit can result in a release candidate

2. Automate Everything

3. Automated test are essential

4. 'Done' means released

Build Pipeline: Automated manifestation of delivery process

Build Quality in: Establish automated quality gates

Pipeline:

• 1. Build Stage (Automated)

     1. Git Checkout

     2. Compile/Unit Tests

     3. Integration Tests

     4. Code Analysis

     5. Package

     6. Publish Binaries

  2. Acceptance Stage (Automated)

• • 1. Deploy to Test Envs

• 3. Functional Test

  4. Non-Functional Test

  5. User Acceptance Stage (Manual trigger)

  6. Deploy to Test Envs

  7. User Acceptance Tests

  8. Release Stage

• • 1. Deploy to Production (Manual trigger)

Database SetUp and TearDown:

Use tools like dbdeploy.

It stores incremental changes to the database and keeps a record in the database about what has already been applied.

Java Code Coverage:

1. Cobertura: Offline byte-code instrumentation

2. EMMA: Offline byte-code instrumentation

3. Clover: Source-code Instrumentation

4. JACOCO: On the fly byte-code instrumentation

Java Static Code Analysis:

1. PMD

2. CodeNarc

3. FindBugs

4. CheckStyle

5. JDepend

SonarQube provides a centralised way of doing Code Coverage, Static analysis and reports

Packaging Delivery Artifacts

1. Exclude Environment specific configuration (tokenise them)

2. Include build information for trace-ability

3. Choose a versioning strategy

Publish Artifacts

1. Version Artefacts

2. Use Binary Repository

   1. Nexus

   2. Artifactory

   3. Apache Archiva

3. Publish once, deploy many

Jenkins plugins

• Parameterised Trigger Plugin

• Build Name Setter

• Gradle Plugin

• Clone Workspace SCM

• JaCoCo

• Build Pipeline