1. Continuous Integration
Sandip Jadhav

2. Agenda Introduction of Continuous Integration
Need of Continuous Integration
Details of Continuous Integration
Workflow
Values and Advantages
Practices 
Available Tools
Jenkins / Hudson
References
Summary
16 February 2019

3. Introduction of Continuous Integration
Continuous Integration (CI) is a software development practice where members of a team integrate their work frequently.
Continuous integration (CI) can help reduce assumptions on a project by rebuilding software whenever a change occurs in a version-control system.
16 February 2019

4. Need of Continuous Integration: Integration hell
Engineer 2 checked-in code and miss one required file .
Base version code is in failure state (build will fail ).
Engineer 1 …n , took update and checked-in codes.
Weekly build is triggered and build failed .
Difficult to find the reason of build fail.
Difficult to resolve build fail issue because many changes by different developers on code .
16 February 2019

5. Details of Continuous Integration Workflow
16 February 2019

6. Details of Continuous Integration Value of CI
Reduce risks
Reduce repetitive manual processes
Generate deployable software at any time and at any place
Enable better project visibility
Establish greater confidence in the software product from the development team
16 February 2019

7. Details of Continuous Integration Advantages
early warning of broken/incompatible code
early warning of conflicting changes
immediate unit testing of all changes
constant availability of a "current" build for testing, demo, or release purposes
immediate feedback to developers on the quality, functionality, or system-wide impact of code they are writing
frequent code check-in pushes developers to create modular, less complex code
metrics generated from automated testing and CI (such as metrics for code coverage, code complexity, and features complete) focus developers on developing functional, quality code, and help develop momentum in a team
16 February 2019

8. Details of Continuous Integration Practices
Commit code frequently
Don't commit broken code
Fix broken builds immediately
Write automated developer tests
All tests and inspections must pass
Run private builds
Avoid getting broken code
16 February 2019

9. Available Tools CI tools Build-tools Cruise Control Jenkins / Hudson
Build Master
Teamcity
Build-tools
Make
Ant
Maven
MSBuild
16 February 2019

10. Jenkins / Hudson
16 February 2019

11. Enter the correct footer
Jenkins / Hudson
16 February 2019
Enter the correct footer

12. References http://martinfowler.com/articles/continuousIntegration.html
16 February 2019

13. Summary
Continuous integration (CI) practice of rebuilding software whenever a change occurs in a version-control system.
Workflow
Monitor version-control system .
Trigger build if change in version-control .
Send feedback if required .
Advantages
early warning of broken/incompatible code
early warning of conflicting changes
immediate unit testing of all changes
Work on principle “Pay in installments or pay lump sum with interest”
16 February 2019

14. Thank you
Any questions?