Jenkins Job DSL Configuration as Code
Most developers want to write code, they don’t want to click around in GUIs or do manual work. A lot of development teams uses Jenkins for package building, testing and tons of other automated jobs. All of this, of course, to improve the overall quality and simplicity of a project, but also to remove some of the “pain” from the developers.
Most teams configure everything in Jenkins manually and with limited history, versioning and rollback options.
What can be done to help developers focus on developing while benefitting from their daily work in the Jenkins setup at the same time?
7. November 2016
The leading open source automation server,
Jenkins provides hundreds of plugins to support
building, deploying and automating any project.
- https://jenkins.io/
8. November 2016
• Run Unit tests
• Build docker images
• Build artifacts
• Deploy website/applications
• Publish TER Extensions on Git-tag
• etc.
What can we use Jenkins for
22. November 2016
Pros & Cons
• Version Control
• More readable
• Change shared configurations
• Test locally
• Review
• Not all plugins are supported
• Learning curve
23. November 2016
Best practice
• Start converting few jobs
• All jobs goes to version control
• Trigger seed job on SCM changes
• Don’t commit credentials
• Think about design, refactor, streamline etc.
it’s code treat it like code.