Continuous Integration
Download as PPTX, PDF0 likes381 views
Continuous integration (CI) is a software development practice where developers regularly merge their code changes into a central repository. This allows every change to be tested in an automated build. The key benefits of CI include avoiding bugs by testing early and often, enhancing collaboration through greater visibility of the project's state, and creating deployable software through automated testing and builds. CI helps developers write better code through practices like testing in a production-like environment and keeping builds fast.
Continuous Integration
- 2. What is Continuous Integration?CI is a software development practice invented to:Ease integrationSelf test buildsReduce bug build upIncrease automationGive greater project state visibilityAllow developers to concentrate on coding
- 3. How is this achieved?It’s achieved by continually integrating(in other words checking in with the main branchfrequently)and then having every integration verifiedby automatically kicking off a tested build
- 5. Avoiding late bugsBy integrating continually you know about more bugs in code ahead of time rather than just before release
- 6. Creating a more cohesive teamEverybody integrates with everyone else frequentlyAvoid development ‘islands’Know about merging difficulties ahead of timeAvoid people saying“When did we decide to upgrade that jar to 2.0-alpha pre-release?”“I thought you fixed that months ago”
- 7. Enhancing project visibilityEveryone (even non-developers!) can see the state of a project at any given time; now or in the pastGenerated reports for projects for things such as code test coverage, code style/warnings, change logs, bug checking etcKnow what made (and broke!) a particular version of a deployed release
- 8. Create deployable softwareSoftware should, as much as possible, workCI helps developers keep their software deployableWhich keeps release cycles shortWhich is good for businessStops “Well, it works on my machine”
- 9. Create better softwareCode is tested early and oftenReports can show progress in meeting coding standardsTest are done in parallel, not at the endNo integration pointsBuilds become a no-brainerDefects are identified earlierDefects are fixed when less costlyEasily repeatable testing
- 10. This is the cool dude that came up with it: Martin Fowlerhttp://www.martinfowler.com/articles/continuousIntegration.html
- 11. Martin Fowler’s 10 Principles of CIMaintain a single source repositoryAutomate the buildMake your build self testingEveryone commits all day, every dayEvery commit is built
- 12. Martin Fowler’s Principles cont…Keep the build fastTest in a clone of the production environmentMake it easy for anyone to get the latest executableEveryone can see what is happeningAutomate deployment
- 13. Maintaining a Single Source RepositoryA version control repository has to include ALL needed sources to buildAnd nothing elseCVS, SVN, Git, etc…Issue: external dependenciesKeep in repository, orDependency management with repository of referenced binaries, e.g. maven, ivy
- 14. Hang on, what’s in a build?
- 15. When to do a buildAt every check-inNot simply over night!Whenever a dependency changes
- 16. How to do a buildUsing a single build script Could use AntMavenMake…Should be able to be run from the command lineShould have no external dependency such as an IDE
- 17. When the build fails…Make sure it fails fastFix it immediately!The world will continue to turn
- 18. Code inspectionsTest coverage tools reports highlight where to focus testing effortsCloverCoberturaStatic Analysis tools read source code to check for best practices and identify weak spotsCheckstyleFindbugsCI helps you track these over timeMetrics can be established to ensure quality
- 19. Generating documentationCI can automatically generate documentation for every buildEnsuring it is always currentRemoves the burden from developersCode inspection reports add to documentation
- 20. CI Mantra
- 21. That’s it really