Unfortunately gonna be missing this (due to speaking at Digital Lincoln) but I'm sure this will be interesting. #Jenkins is a great piece of software, the problems that many folks see with it are how their organisation uses it not the underlying software that's built by awesome people
Thanks to @JamieTanna for stepping up up as a @jenkinsci JobDSL plugin maintainer! And kudos to @daspilker for leading it for almost ten years π
JobDSL is one of the well documented and stable plugins and it is also essential for the configuration as code ecosystem in Jenkins
Just to update on this - I'm a maintainer now, it's been released as 1.78 this morning, and I'll see over the coming weeks if there's anything other high-priority to ship π (jvt.me/mf2/2021/10/jyβ¦)
Thanks to @JamieTanna for stepping up up as a @jenkinsci JobDSL plugin maintainer! And kudos to @daspilker for leading it for almost ten years π
JobDSL is one of the well documented and stable plugins and it is also essential for the configuration as code ecosystem in Jenkins
Just to update on this - I'm a maintainer now, it's been released as 1.78 this morning, and I'll see over the coming weeks if there's anything other high-priority to ship π (jvt.me/mf2/2021/10/jyβ¦)
I am not sure whether Daniel has any bandwidth these days. Last 1.5 have been pretty complicated to anyone, and we need more maintainers in @jenkinsci . Any contributions like reviews and testing would be appreciated, and maybe even adopting the plugin.
jenkins.io/doc/developer/β¦
Folks using #Jenkins, how do you manage your jobs? Only through the UI? Or using #JobDsl? If not the latter, would you like a talk on being able to track all your jobs in repo and peer-review changes? While being able to quickly spit out duplicate jobs