You could leverage Jenkins' plethora of plugins. Perhaps use the matrix plugin, that way you only need to detail the array of module names under test - not duplicate the jobs
On Thu, Oct 23, 2014 at 10:31 AM, Sandro Roth <sandro.r...@gmail.com> wrote: > Thank you guys for your replies. > > Yes Javier, we are in fact using gitlab ;) So let me know if we can help > you with the hook scripts in any way, I'd be very interested. > > In the meantime I'll look into automating the jenkins job creation with > the cli and or api. > I have read about job builder which uses templates and stuff like Atom > Powers mentioned. > > Wildcards in git repo names is actually not possible within a jenkins job, > tried that. > > > Cheers > Sandro > > On Wednesday, October 22, 2014 9:14:12 PM UTC+2, Javier Palacios wrote: >> >> >> >> On Wed, Oct 22, 2014 at 3:18 PM, Sandro Roth <sandr...@gmail.com> wrote: >> >>> >>> It works great when I create a Jenkins job which tracks changes in a git >>> repo, runs the tests and if succeeded pushes the puppet module to the >>> master. >>> But we have about 30 modules and creating a job for each module seems >>> inefficient? >>> >>> Maybe there is a way doing this dynamically that someone could point me >>> to? >>> Or perhaps jenkins is not the right solution here for us? >>> >>> >> More than 'recommended', you will a jenkins job for each repo. Maybe you >> could circumvent it in some manner, but as far as I know, wildcards are not >> allowed on repository names, so you will need at least to explicitly list >> each of your individual repos. >> >> Altough creating many jenkins jobs is not that hard. If by chance you are >> using gitlab, I'm working on the gitlab-hook plugin to allow template based >> automatic job creation. >> >> But in any case, you can use the command line jenkins client (point your >> browser to /cli on your jenkins server). In particular, you can get the >> configuration of an existing job in xml format, and create/modify a job by >> uploading an xml file. So you have a poor man templating engine. Basically, >> you only need to modify the cloning url on the xml, as the job name is not >> written there. >> >> Javier Palacios >> > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/c355f4a0-62eb-42f8-81ab-e06bc6e84ee1%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/c355f4a0-62eb-42f8-81ab-e06bc6e84ee1%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- $ echo "kpfmAdpoofdufevq/dp/vl" | perl -pe 's/(.)/chr(ord($1)-1)/ge' -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CA%2Bwb_2tsvn%2Bxd67nfL2rdb97r0HcL%2B%2BMMKUkabR4miabdRf-xQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
