Hi Greg, interesting, but it's not on GitHub. Also same plugin would be available for Bitbucket ... Jenkinsfile is probably not enough. We also would like to have a parametrized build. As an example we would like to run the pipeline for latest as well as for a feature branch. But I will have a look, thanks.
Best Regards, Thomas On Wednesday, November 9, 2016 at 12:13:44 PM UTC+1, Grégory Lureau wrote: > > Hi Thomas, > > If you're using github, maybe that could help you? > https://wiki.jenkins-ci.org/display/JENKINS/GitHub+Organization+Folder+Plugin > It's basically checking all repos in your github organization, and if they > match some requirements (your regexp + have a Jenkinsfile), it will create > all jobs. > I read there is similar tool for Bitbucket but never tried. > > Best Regards, > Greg > > Le mardi 8 novembre 2016 11:07:48 UTC+1, [email protected] a écrit : >> >> Hi, >> >> We have a coded pipeline and using webhooks in our Git system. >> The *existing* Jenkins pipeline job is executed on a change. >> Fine. >> >> As already mentioned this works only when the job does exist. >> *Is there a way to organize that a Jenkins job gets automatically >> created?* >> >> It would be great if we could implement something like: "asking the >> concrete repository what to do" >> I could imagine that I need to store a job.xml in my repository ... >> *Any ideas?* >> >> Regards, >> Thomas >> > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b3aed3e6-e383-4f8a-808b-d5e248211719%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
