3 ms·
I haven't used Jenkins in 2 years, but before that I used the Groovy DSL plugin. A job that would run that and create the other jobs. Incidentally, a similar
by paulddraper 7y ago
I haven't used Jenkins in 2 years, but before that I used the Groovy DSL plugin.
A job that would run that and create the other jobs.
Incidentally, a similar (but native and more streamlined) approach is taken by Buildkite: job that processes a DSL that then generates other jobs (could even be recursive if you like that sort of thing) [1]
[1] https://buildkite.com https://buildkite.com
- peterwwillis 7y agoI know that in some cases that's the best solution to a problem, but I try hard to stay away from generative processes. There's a raft of complexity issues that arises from the need to reproduce exactly the same behavior and results, and usually you're introducing several new layers of complexity (a DSL, a job to process it, jobs generated from it, actions taken by those jobs, the input and output of each process... versus one giant static job with minimal variability).
- paulddraper 7y agoIt was certainly unpleasantly complicated.