Leveraging Continuous Integration For Fun And Profit!
Download as PPTX, PDF0 likes1,304 views
The document discusses continuous integration (CI) as a software development practice where team members frequently integrate their work, leading to fewer integration problems and accelerated software development. It covers the implementation of CI, best practices for maintaining code quality, and examples of build scripts using various tools. It also emphasizes the importance of communication and regular updates on build status to ensure a smooth CI process.
Leveraging Continuous Integration For Fun And Profit!
- 1. Leveraging Continuous Integration for Fun and Profit!Jess ChadwickIndependent Consultanthttp://blog.jesschadwick.com
- 2. AgendaWhat is Continuous Integration?How does it fit in to the Agile lifecycle?How do I implement it?Best Practices
- 3. What is Continuous Integration?Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day. Each integration is verified by an automated build (including tests) to detect integration errors as quickly as possible.Many teams find that this approach leads to significantly reduced integration problemsand allows a team to develop software more rapidly.Martin Fowler, September 2000
- 4. Layers of Quality Assurance
- 6. Benefits of Continuous Integration
- 8. Components
- 9. CI Servers
- 10. Covert OperationCan’t get your team to buy in?Run it on your own box!
- 11. Build Scripts – NAnt<?xml version="1.0"?><project name="Hello World" default="build" basedir="."> <description>The Hello World of build files.</description> <property name="debug" value="true" overwrite="false" /> <target name="clean" description="remove all generated files"> <delete file="HelloWorld.exe" failonerror="false" /> <delete file="HelloWorld.pdb" failonerror="false" /> </target> <target name="build" description="compiles the source code"> <csc target="exe" output="HelloWorld.exe" debug="${debug}"> <sources> <includes name="HelloWorld.cs" /> </sources> </csc> </target></project>
- 12. Build Scripts – MSBuild<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003"> <PropertyGroup> <OutputPath>.\bin</OutputPath> </PropertyGroup> <Target Name="FooCompilation"> <MakeDir Directories= "$(OutputPath)"/> <Copy SourceFiles="Image.jpg" DestinationFiles="$(OutputPath)\Image.jpg"/> <Csc Sources="Foo2.cs" TargetType="module"OutputAssembly="$(OutputPath)\Foo2.netmodule" /> <Csc Sources="Foo1.cs" TargetType="exe"AddModules="$(OutputPath)\Foo2.netmodule" LinkResources="Image.jpg" OutputAssembly="$(OutputPath)\Foo1.exe" /> </Target></Project>
- 13. Build Scripts – psakeproperties { $testMessage = 'Executed Test!' $compileMessage = 'Executed Compile!' $cleanMessage = 'Executed Clean!' }task default -depends Testtask Test -depends Compile, Clean { Write-Host $testMessage}task Compile -depends Clean { Write-Host $compileMessage}task Clean { Write-Host $cleanMessage}
- 14. Build Scripts – rake#!/usr/bin/env rubyrequire 'ftools'def make_directoriesFile.makedirs "html"File.makedirs "html/images"Enddef generate_html system %{./runwpbrake.wpb}enddef buildmake_directoriesgenerate_htmlendbuild
- 15. DEMOLet’s see it in action!
- 16. Notifications
- 17. Notifications – Lava Lampshttp://agileworks.blogspot.com/2009/02/lava-lamp-with-cruisecontrol.html
- 18. Notifications – iPhone appYeah – there’s an app for that.
- 19. Notifications – Brian the Build BunnyBrian Woodward: http://www.woodwardweb.com/gadgets/000434.html
- 20. Best PracticesBuild must be green at the end of the dayNever check in code and leave office (ninja commit)Stay and fix the code OR revert the check inCheck in oftenLess chance of merge conflictAlways have the latest codeNever check in or check out of a broken build
- 21. Best Practices – cont’dCommunicateBe informed. Keep up-to-date with build statusIf you broke the build, tell the teamMerge conflict? Talk to - don’temail - the other team member(s)Be familiar with the build processDon’t have to be the ‘build master’ but need to know how to troubleshoot and fix
- 22. Various Build TypesContinuous: Run on every commit (give or take)Lean & FastVery basic validationTimed: Hourly, Nightly, etc.LongerMore in-depthDeploymentUtilityMuch like scheduled tasksFor ease of use
- 23. But there’s more!Post-BuildDatabase upgradeCode analysis (coverage, quality metrics, compliance)PackagingDeployment
- 24. Continuous DeploymentShrink the ‘Last Mile’ (QA, UAT, Production)Reduce riskExercise deployment process earlySoftware always ready for deployment
- 25. Discussion TimeViewpointsExperiences & TipsValueshttp://blog.jesschadwick.comTwitter: jchadwickjchadwick@gmail.com