This allows us to think about how we want to run pipelines in a way that's more common across repos/projects/teams, and to enforce teams to work in a similar way, with the aim not to remove any flexibility or room to experiment we want, but to simplify the build/test/deploy lifecycle for applications, and to make it much more effective to get work shipped to customers. The best application I've found for Job DSL is to make your Jenkins pipelines standardised. The perk of Job DSL is that it allows us to go one step further than that, as we can populate folders, jobs, and more, all through one manually created Jenkins job and a (git) repo.īy using a source controlled configuration, we can ensure that we always have a source of truth in-tree that we enforce code review on, and are able to use things like git revert if things go wrong. Now, I hear some of you readers say "I can do that already, I've got a Jenkinsfile I store in my project" - the issue is that you still need to configure a job in the Jenkins UI to read that Jenkinsfile. The Jenkins Job DSL plugin, commonly referred to as "Job DSL", is a plugin that allows you to manage all your Jenkins jobs' configuration as code.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |