2. Why this talk?
• Logical step from previous unit test topic
• I’m a Jenkins fanboy :)
• Maybe I can inspire you!?
2
Thursday, October 10, 13
3. Why talk about Jenkins?
• First Jenkins installation in 2008
– Have administered
– Have used as a developer
– Have developed plugins for it
– Still using daily but more like a manager
– Good friends with Cloudbees people
3
Thursday, October 10, 13
4. What have I done with Jenkins?
Built-tested-released software
Implemented continuous delivery
Updated websites (docs, changelogs etc.)
Propagating code or binary artifacts
Workflow management
Thursday, October 10, 13
8. Background - 2013
300 600 jobs
8 20 dedicated machines
Amazon ~7000 instance-hour per month
3 4 in house plugins developed, 2
abandoned
Custom dashboard (35 x 215 grid)
Thursday, October 10, 13
9. Jenkins Overlords
• Jenkins Overlord
– Actually his name is Juri
• Each project has a goto guy
– Works with Juri when something
bad happens, also known as an
Overlord :)
9
Thursday, October 10, 13
13. Managing the cluster
• Lots of projects but 1 Jenkins cluster
– Java
– Application server X
– Database server X
– Framework X
– PHP/Python/Groovy/SBT/Maven
– Play Framework
– Android
– Eclipse
– ....
13
Thursday, October 10, 13
19. JRebel Functional JDK Tests
Per JDK
– Per functional test
• Compile couple of classes
• Run some methods and assert
• Recompile couple of classes
• Run some methods and assert
• …
Thursday, October 10, 13
20. JRebel Functional JDK Tests
Which Jenkins feature is the best fit here?
Thursday, October 10, 13
28. API
• Java/JavaScript/Python and others
• Super easy to get started (show demo)
• Retrieve info about Jenkins
• Trigger builds
• Create/copy jobs
28
Thursday, October 10, 13