Be the first to like this
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?