Similar questions that I(noob) haven't seen an answer for. let's say that i have one sw project, called X, running 50 jobs a night that I want to copy to project Y. the source comes from the same repository but on a different branch. I will need to add tests for Y and do not want the Y test results to interfere with X. do I have to copy all the jobs manually (or via script)? does jenkins have any provisions for copying an entire project? Thanks, Rob
On Friday, August 24, 2012 2:51:29 PM UTC-4, krishna kurnala wrote: > > You can try using Jenkins CLI for updating Jobs in Bulk or even even > scripting interface (your jenkins URL/script > > Recommend the following Links: > https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CLI > https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Script+Console > > Thanks, > > Thanks, > Krishna Chaitanya > > > On Fri, Aug 24, 2012 at 11:29 AM, Les Mikesell > <lesmi...@gmail.com<javascript:> > > wrote: > >> On Fri, Aug 24, 2012 at 10:57 AM, Martin d'Anjou >> <martin....@gmail.com <javascript:>> wrote: >> > What is the plan to scale up Jenkins to handle a very large number of >> > projects? >> > >> > Right now, I have 3 projects in Jenkins. They all have the same build >> flow, >> > so any improvement or plugin I add to one of them, I manually copy it >> to the >> > other two. As we are about to bring more projects to Jenkins, this >> manual >> > copy and paste will quickly become a burden. Reverting a change that was >> > copied by hand to multiple project is also a concern of similar nature. >> > >> > Has there been any thoughts given to how Jenkins can handle these cases? >> > >> > For example, could multiple projects inherit from a common template >> project, >> > such that a change to a template would be reflected into multiple >> projects? >> > I see a Template Project plugin, but there has been no activity for a >> year >> > on it. >> > >> > I have no need to link projects together, so I have stayed away from the >> > Workflow plugins. Should I look into them? >> >> Normally the bulk of the work is done by build scripts/Make/project >> files that are included in the source checkout and once you have one >> or a few jenkins jobs working the way you want, you just tell jenkins >> to copy a similar one when creating a new job, then change the >> url/path to the different source in your VCS. There's not a big need >> for templates, although it can be cumbersome if you want to change >> something in a lot of jobs after they have already been created. >> >> -- >> Les Mikesell >> lesmi...@gmail.com <javascript:> >> > > -- 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.
