Just to be clear the job-dsl plugin can generate ANY xml seen in the config.xml. There just happens to be some dsl method which make it easier to generate the xml for common plugins, we're adding new dsl methods all the time. Likewise we can use another job config as a base for the new job, so if you already have a job that does 90% of what you want, you only need make your tweaks using the job dsl. The Domain Specific Language (DSL) we're talking about here is Jenkins jobs, so if you're in the business of making jobs, the plugin should help. Generating hundreds of similar jobs is * trivial *with the job-dsl plugin. Ask some questions in the mailing list and I think you'll be surprised how we can come up a solution, as a long as you're willing to programmatically create the jobs.
https://groups.google.com/d/forum/job-dsl-plugin The plugin uses internal Jenkins calls to update and create jobs, so there's no reloading of the server. On Sun, Nov 18, 2012 at 4:26 AM, blalor <[email protected]> wrote: > I think lots of us are trying to solve this problem. I haven't played > with the job-dsl plugin, yet; it sounds like it's on the right path, but as > I understand it needs to be extended to support specific plugins. > > I've got a pretty simple set of Python scripts that I use to build jobs. > We've got about a dozen projects, each with one or more downstream deploy > jobs, and another set of parallel regression and automation test jobs. So > we're deep into the tens of jobs that need to be maintained. My script has > a templatized XML file for each type of job and a config file for each > project (which could probably be done away with if the projects were named > consistently). It uses Jinja to generate the concrete job config.xml from > the template and per-project config. It can both generate new jobs and > update existing jobs with the new config. All I'm missing now is the > ability to keep people from modifying these templatized jobs! >
