1. Open Source Continuous Integration Server

2. WHO AM I? Matt Anderson Moved to Dayton from Detroit eight years ago
Software Engineer at Northrop Grumman

3. Open Source Continuous Integration Server

4. WHAT IS JENKINS? Monitors executions of repeated jobs
Used primarily for continuously building and testing software projects, i.e. “Continuous Integration” or “CI”
Previously known as “Hudson”

5. WHO USES JENKINS? 5

6. WHY USE JENKINS? Immediate feedback on broken builds
No building from dev machines and manually copying files
Automated deployment
Automated test execution and feedback

7. WHY USE JENKINS?

8. DASHBOARD
This is the Jenkins Dashboard. 8

9. DASHBOARD
Projects/Items can be organized into views. 9

10. DASHBOARD
The build queue (pending builds) and currently executing builds are shown on the dashboard. 10

11. DASHBOARD
The “S” column indicates the project’s last build status. Blue indicates success, red indicates failure, and grey means it is disabled. 11

12. DASHBOARD
The “W” column shows build trends based on the last five builds. Sunny weather is better! 12

13. DASHBOARD
The “W” column shows build trends based on the last five builds. Sunny weather is better! 13

14. PROJECT VIEW

15. PROJECT VIEW
Click on a build to view that build’s history. 15

16. PROJECT VIEW
Click on a build to view that build’s history. 16

17. PROJECT VIEW 17

18. WORKSPACE
Zipping up the project workspace and copying to another PC to execute a manual build in your IDE can be useful for diagnosing build errors. 18

19. PROJECT VIEW

20. CONFIGURE

21. CONFIGURE
The number of builds to keep can be specified to limit the amount of space used on the build server. 21

22. CONFIGURE

23. ADVANCED PROJECT OPTIONS

24. ADVANCED PROJECT OPTIONS
Customizing the workspace can be useful if projects or dependencies expect a particular directory structure. 24

25. SOURCE CODE MANAGEMENT

26. SOURCE CODE MANAGEMENT
Enter your SCM URL and credentials. A separate SCM account is preferable to using an individual’s credentials. 26

27. SOURCE CODE MANAGEMENT
If a project has SVN externals, additional credentials are required. 27

28. BUILD TRIGGERS

29. BUILD TRIGGERS 29

30. BUILD

31. BUILD

32. BUILD
Scripts can be used to deploy code as part of the build process. Since this is part of the build, Jenkins will mark the build as failed if the script returns/exits with a value that represents an error. 32

33. BUILD
Scripts can be used to deploy code as part of the build process. Since this is part of the build, Jenkins will mark the build as failed if the script returns/exits with a value that represents an error. 33

34. POST BUILD ACTIONS

35. POST BUILD ACTIONS
It is preferable to only send s to individuals who broke the build; however, Jenkins is not currently configured with addresses. Thus, individual recipients must be specified and every receives an . 35

36. POST BUILD ACTIONS Customized email notifications Build other projects
Create/update JIRA issues
Publish Javadocs

37. PLUG-INS Over 600 plug-ins available for customization Examples: JIRA
Ant
Maven
JUnit
Javadoc
SSH
MSBuild
NUnit
PowerShell
Notifications

38. LET’S DO THIS A final word of encouragement

39. QUESTIONS?