Jenkins2

1. Jenkins Continuous Build System
Jenkins History

2. Jenkins
Branched fromHudson
Java basedContinuousBuild System
Runs in servletcontainer
Glassfish,Tomcat
Supported byover 400plugins
SCM,Testing,Notifications,Reporting,
ArtifactSaving,Triggers,External
Integration
Underdevelopment since 2005
http://jenkins-ci.org/

3. Jenkins - History
• 2005- HudsonwasfirstreleasebyKohsuke
Kawaguchiof SunMicrosystems
• 2010 – Oraclebought SunMicrosystems
• Duetoanaming dispute,Hudson wasrenamed to Jenkins
• OraclecontinueddevelopmentofHudson(asabranchofthe original)

4. Jenkins – Fitting in
Code
Repository
Developers
Artifact
Repository
Test
Reports
Deployment
Source&Tests
Regular
Interval Executable/
Package
TestingResults

5. Why Jenkins? Flexibility!
• Jenkinsis a highly configurablesystem by itself
• Theadditionalcommunitydevelopedpluginsprovide
even moreflexibility
• BycombiningJenkinswithAnt, Gradle, orother
Build Automationtools, the possibilitiesare
limitless

6. Why Jenkins? Award winning!
InfoWorld BossiesAward,2011
O'ReillyOpen-SourceAward, 2011
ALM&SCM, SDTimes100,2010, 2011
GlassFish CommunityInnovationAward 2008
Duke's ChoiceAward2008

7. Why Jenkins? Free/OSS
• Jenkinsis released under the MITLicense
• Thereisalargesupportcommunityandthorough
documentation
• It’seasy towrite plugins
• Thinksomethingiswrong withit? You can fix it!

8. What can Jenkins do?
• Generatetest reports
• Integratewith many differentVersion Control
Systems
• Push tovarious artifact repositories
• Deploys directlytoproduction ortest environments
• Notifystakeholders ofbuild status
• …and much more

9. How Jenkins works - Setup
WhensettingupaprojectinJenkins,outoftheboxyouhave
the followinggeneraloptions:
Associatingwithaversion control server
Triggeringbuilds
Polling,Periodic,Building basedon otherprojects
Executionofshellscripts,bashscripts,Anttargets,andMaven
targets
Artifactarchival
Publish JUnit test results andJavadocs
Emailnotifications
Asstatedearlier,pluginsexpandthefunctionalityeven
further

10. How Jenkins works - Building
• Once aprojectissuccessfullycreatedinJenkins, all
future builds areautomatic
• Building
• Jenkinsexecutesthe buildinan executer
• By default,Jenkinsgives one executerper coreon the buildserver
• Jenkins also hasthe concept ofslavebuildservers
• Usefulforbuilding on different architectures
• Distributionof load

11. How Jenkins works - Reporting
• Jenkinscomes withbasic reporting features
• Keeping track ofbuildstatus
• Last success andfailure
• “Weather”– Build trend
• Thesecanbegreatlyenhancedwiththeuseofpre-
build plugins
• Unittest coverage
• Testresulttrending
• Findbugs,Checkstyle,PMD