Yes, I think that's how it should be. But the Job DSL document only shows how to use freestyle job as a seed job. I am wondering is their any example showing how to use a pipeline job as a seed job. Meanwhile Jenkins Job Builder can do the similar thing via command line. That's why I feel difficult to choose betweeen them.
On Friday, September 9, 2022 at 2:43:39 PM UTC+8 dheinric wrote: > Am Donnerstag, dem 08.09.2022 um 23:15 -0700 schrieb Weihong Xu: > > Not exactly. I have already used Jenkins pipeline to define the CI/CD > workflow. The problem is I still need to create Jenkins job manually in the > web UI to run those pipeline scripts. I hope this could also be automated. > In the end users just need to tell the meta job where their repos are, and > the meta job will created the pipeline Job automatically by reading some > .yml file in the repos they provided. > > > Ah, OK. Got it now. > > I guess then it's best to use Job-DSL. You can create a seed job which > reads some Job-DSL code along with a configuration file from a repository > (or even separate ones). The DSL code then just iterates over the entries > in the configuration file and creates a job for each one, maybe like (in > YAML): > > --- > jobs: > > - name: job_1 > > repository: > > credentials: <credentials id> > > url: <ssh or https repo url> > > type: <either pipeline or multibranch pipeline> > > - name: folder/job2 > > repository: > > ... > > > This way users can update the file, issue a merge request, which triggers > your seed job after merge... > > HTH... > > Dirk > > -- > > *Dirk Heinrichs* > Senior Systems Engineer, Delivery Pipeline > OpenText ™ Discovery | Recommind > *Phone*: +49 2226 15966 18 <+49%202226%201596618> > *Email*: dhei...@opentext.com > *Website*: www.recommind.de > Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach > Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, > Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646 > This e-mail may contain confidential and/or privileged information. If you > are not the intended recipient (or have received this e-mail in error) > please notify the sender immediately and destroy this e-mail. Any > unauthorized copying, disclosure or distribution of the material in this > e-mail is strictly forbidden > Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte > Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail > irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und > vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte > Weitergabe dieser Mail sind nicht gestattet. > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/179b8cb9-86f7-490b-8464-71bb52944014n%40googlegroups.com.
