Hello, If you have some kind of pipeline approach then you could have a look at the Job Generator plugin which is aimed to define job templates. We are using it at work to generate 100+ jobs defined by 20 Job Generators. Maybe it could help you.
Cheers, syl20bnr Le jeudi 31 janvier 2013 08:09:17 UTC-5, jck...@gmail.com a écrit : > > Hi, > > I'm considering Jenkins as continuous integration tool in the company > where I work. I prefer Jenkins than Hudson because I believe it has a > better future and it's widely adopted. > > However, I've seen a drawback in Jenkins which is solved in Hudson: job > inheritance. In other words, the funcionality of defining common > configuration in a parent job and apply to its children. In our case this > is a necesarry feature, because we need to manage 300 projects at least. > > I've seen a presentation of cloudbees about Jenkins and, if I'm not wrong, > they announced that funcionality would be included in the future. Do you > know when? If not, how does the people manage the common data of a huge > amount of projects? > > Thanks in advance. > > > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
