Jenkins part 3

1. Jenkins Continuous Build System
Jenkins With Example

2. Jenkins by example – Main Page
• The main page provides a summary oftheprojects
• Quick view of
• What’sbuilding(“Nobuilds inthe queue”)
• Build ExecutorStatus (both“Idle”)
• Status ofthe projects

3. Jenkins by example – Project Status
• Projectstatuspagesprovidemoredetailsabouta
given project
• The status ofthe last severalbuilds
• Charting(depending onplugins)
• Dependencies

4. Jenkins by example – Project Status

5. Jenkins by example – New Project

6. Enhancing Jenkins
•  Jenkinspluginsystem can enable awide range offeatures including(but certainly
not limitedto)
• SCM
•  Mercurial,Git, Subversion
• Testing
•  Selenium,Windmill,TestLink
• Notifications
•  IRC,Twitter,Jabber
• Reporting
•  Doxygen,PMD,Findbugs
• Artifact Saving
•  Artifactory,AmazonS3, SCP
• Triggers
•  Jabber,DirectoryWatchers
• ExternalIntegration
•  GitHub, Bugzilla,JIRA
• Andmost importantly– TheCI Game
•  A pointsbasedgame where developerscompeteagainst each othertodevelopthe most stable,well-
testedcode

7. Who uses Jenkins?

8. Running Jenkins yourself
Jenkinsis packaged asaWAR, so you can drop itintowhicheverservlet
containeryou preferto use
Jenkinscomes pre-packaged withaservletifyou justwant alight-
weightimplementation
Native/Supportedpackages exist for
Windows
Ubuntu/Debian
Redhat/Fedora/CentOS
MacOSX
openSUSE
FreeBSD
OpenBSD
Solaris/OpenIndiana
Gentoo

9. Running Jenkins yourself – Updates
• Jenkins has two releaselines
• Standardreleases
• Weekly bug fixesandfeatures
• Long-Term Supportreleases
• Updatesabout every 3months
• Usesa“Stablebut older”version fromthe standard release line
• Changes are limitedtobackported,well-tested modifications

10. Letting someone else run Jenkins
• Therearealsocloud-basedsolutionsthatcanprovide
a Jenkins instance
• Cloudbees- http://www.cloudbees.com/
• ShiningPanda - https://www.shiningpanda.com/

11. Tying it into Agile
ForanAgileteam,Jenkinsprovideseverythingneededfora
robust continuous buildsystem
JenkinssupportsAgileprinciplesbyconstantlyproviding
access toworking copies ofsoftware
Jenkins’extensibilityallowsthesystemtoadapttomany
differentpre-existing environments

12. Putting it all together
WhileanintegralpartofaCI system,Jenkinsisbynomeans
theonly component
InorderforaCI systemtofunction,acommonrepository
forthe codebase needstoexist
A databaseofartifactsneedstoexist,sodeliveriescanbe
madeat pastiterations
ThelaststepinaCI processisthedeploymentofthe
componentsbuilt
…and noneofthismattersifthedevelopersdon’tusethe
system;proceduresneedtoensurethesystemisusedas
intended

13. Conclusion
Continuous integration is anecessity on complex projects
due to the benefits it provides regarding early detection of
problems
A goodcontinuousbuildsystemshouldbeflexibleenoughto
fitintopre-existingdevelopmentenvironmentsandprovide all
the features ateam expectsfromsuch a system
Jenkins, acontinuous build system, can beanintegral part of
anycontinuous integration system due to it’s core feature set
andextensibilitythrough aplugin system

14. References
 ContinuousIntegration– Martin Fowler
http://www.martinfowler.com/articles/continuousIntegration.html
 Hudson
http://hudson-ci.org/
 Hudson ContinuousIntegrationServer
http://www.code-magazine.com/articleprint.aspx?quickid=0906071&printmode=true
 TheHudson Book
http://www.eclipse.org/hudson/the-hudson-book/book-hudson.pdf
 Jenkins
https://wiki.jenkins-ci.org
 MonkeyImage
http://corrines-corner2006.blogspot.com/2011/09/freebie-monday_26.html
 Whatis ContinuousIntegration
http://confluence.public.thoughtworks.org/display/CCNET/What+is+Continuous
+Integration