Hi,

I have a file defining the parameterized jobDSL script of a job (template).

I have another file defining sets of parameters that should be passed to that script in order to create multiple jobs based on that jobDSL.

I have a pipeline shared library with a class which reads the config file and for each entry passes the parameters to the jobDSL step - such that I have multiple calls to the jobDsl step as the number of configured sets (can be tens).

Motivation: I want the jobDSL script to remain "constant" and allow to add new jobs through configuration such that I don't have to re-approve the script if I did not change the jobDSL itself. Both files are under the resource folder and I read them using libraryResource.

In the build and job summaries, each call to jobDsl is recorded as a separate entity and finding which jobs were created is a mess. I would like to be able to group all jobs created by all jobDsl invocations of the same build to show together as a single entity as if I had a single call to the jobDsl step.

Thanks,

Mor