Continuous Integration (CI) is one of the most important tenets of agile practices. And Continuous Delivery (CD) is impossible without continuous integration. All practices are good and enhance productivity when other good practices and tools back them. For example CI & CD without proper automation test cases can be a killer. It kills the team productivity and puts deliver on risk. Via this session I will try to share my experiences of how CI and CD can be done in optimized fashion (specifically for feature branch based development approach) We will discuss the best practices and ways of ensuring proper CI and CD in feature branch based development approach. I will showcase an automated Jenkins based setup, which is geared to ensure that all feature branches and master remain in cohesive harmony. At the end we will conclude on what are the essential components for ensuring successful CI and CD. We will also discuss what are the associated must haves to make it a success. Take away for participants 1. Understanding of CI and CD and how CI can lead to CD. 2. How a devops engineer can leverage Jenkins and scripting to automate the CI and CD for feature branch based development. 3. Demo of CI setup devloped on Jenkins. 4. Generic understanding and Q&A related to CI and CD. 5. Learning of how docker can be used in such scenarios. Session at the IndicThreads.com Confence held in Pune India on 27-28 Feb 2015 http://www.indicthreads.com http://pune15.indicthreads.com

1. Continuous Integration with Jenkins &
Docker
Sandeep Rawat
Opstree Solutions

2. 2
Agenda

Continuous Integration

CI Components

CI for multiple feature branches

Demo

Code Walkthrough

Questions

3. 3
Continuous Integration

4. 4
CI Components
Poll VCS Initicate CI
Feedback

5. 5
CI for multiple features

6. 6
CI for multiple features
Feature 1 Environment
Feature 2
Environment
Feature 3 Environment

7. 7
CI for multiple features
Feature 1 Container
Feature 2 Container
Feature 3 Container

8. 8
Demo

Creation of a new feature branch

Code commit in a feature branch

Code commit in master branch

Cleanup of feature branch

9. 9
New feature branch

Identify new feature branch in system.

Actions items

Create jenkins jobs.

Update CI Dashboard.

Create & setup Docker containers

10. 10
Code commit in feature branch

Inititiate CI process on feature branch.

Update dashboard.

Put a gate on further CI process.

11. 11
Code commit in master branch

Auto merge with feature branch.

Intiate CI process on newly merged code in feature branch.

Dashboard updation.

12. 12
Cleanup of feature branch

Deletion of Jenkins jobs.

Tagging & Deletion of feature branch.

CI Dashboard updation.

Docker container cleanup.

13. 13
Questions