It does not suite my needs, it just allows to organize multiple jobs which are supposed to all be triggered by the same event, am I correct?
My jobs are pretty similar to each other - ex. build jobs have the same configuration except svn url, downstream jobs list and maybe some details (like email notification triggers), all other properties are equal. But they are triggered at different times as they relate to different projects. What I'm looking for is more like configuration inheritance, where I'd need to change job configuration property once, in only one place (in the 'base' job) instead of per each job (plus possibility to override at job level). Maybe there is possibility to use configuration slicing plugin without admin permissions? That would partially work Thanks Marcin On Nov 15, 5:48 pm, Marek Gimza <marekgi...@gmail.com> wrote: > Marcin, > > Do you know about the "MultiJob" plugin? > > https://wiki.jenkins-ci.org/display/JENKINS/Multijob+Plugin > > Regards, > Mgimza > > On Wed, Nov 14, 2012 at 7:39 PM, Marcin Biegan <marcin.bie...@gmail.com>wrote: > > > > > > > > > Hi, > > > I wanted to ask how do you handle configuring multiple jobs. We have > > about 10 maven projects to build in at least 2 versions (trunk/ > > branch), which makes 20 jobs, some more for additional tests, > > releases, maybe deployment, verification, etc. Manually adding > > permissions and adjusting configuration of jobs is cumbersome. Is > > there a working plugin which would allow to set some 'parent' job > > which would define default configuration? (Template Project Plugin is > > not enough, because it 'works' only at job creation). I know also > > about Configuration Slicing Plugin, but this will not work in my case > > as it requires admin permissions. > > > Thanks > > Marcin Biegan
