Jenkins Continuous Build System
Jenkins Continuous Build
• Jenkins, acontinuousbuildtool, enablesteamsto
focuson theirworkbyautomatingthebuild, artifact
management, and deploymentprocesses
• Jenkins’corefunctionalityandflexibility allowitto
fit ina varietyofenvironmentsandcanhelpstreamline
the development process forallstakeholders involved
Wheredoes itfit in?
Why should Iuseit?
What can itdo?
How does itwork?
Whereis it used?
How can Igetstarted?
CI - Defined
errors asquickly aspossible”– MartinFowler
CI – What does it really mean?
Allchanges upuntilthat point arecombined intotheproject
Thecodeis compiledintoanexecutableor package
Automated testsuites arerun
Versioned andstored so itcan be distributedasis, ifdesired
Loaded ontoasystem where the developers caninteractwithit
CI - Workflow
CI – Benefits
• Immediate bugdetection
• No integration step in thelifecycle
• A deployable system at any givenpoint
• Recordofevolution ofthe project
CI – The tools
• Code Repositories
• SVN, Mercurial,Git
• ContinuousBuild Systems
• Jenkins,Bamboo,Cruise Control
• Artifact Repositories
Java basedContinuousBuild System
Runs in servletcontainer
Supported byover 400plugins
Underdevelopment since 2005