On Monday, February 13, 2017 at 8:11:27 AM UTC-8, Richard Ginga wrote: > > Francesco, there are actually many ways to do this. > > 1. use Pipeline script or System groovy build step or post build - > "trigger parameterized builds on other projects" to pass in parameter x > > 2. with system groovy script, you can create/update a global variable that > all builds will see > > On Sat, Feb 11, 2017 at 5:43 AM, francesco desposito < > francesco.d...@gmail.com <javascript:>> wrote: > >> Hello, >> I want to group the jobs referring to a single project together. >> Then I would like to define some parameters at group level and I want >> that those parameters are automatically passed to the jobs belonging to >> that group. >> For example I want to create a group P1 with jobs a1, b1, c1. Then I >> define a parameter x for P1. I would like that x is automatically defined >> for the jobs a1, b1, c1. >> >> Is that possible? >> >> Thanks >> > > I understood the OP's request, which I've often wanted myself, and I don't see how either of those strategies would do what he wants. I think you misunderstood what he's asking.
Let's say you have ten related jobs in a "project", all of which are parameterized, and all of which take a "Foo" parameter, a "Bar" parameter, and a "Something" parameter. He wants the ability to define in a single place that all of these jobs should expect the "Foo", "Bar", and "Something" parameters, instead of creating each one manually in each of the ten projects, copying the default value (if any) and description from the first one. -- 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/c1f1b5f4-a24f-44f6-a93d-4562d5a56e53%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
