Parametrized seed job question

[Misty Stanley-Jones]

Hi all, sorry for the multiple questions over the last little bit. I've got a top-level job set up to run one or more seed jobs depending on its parameters. These seed jobs each run a DSL using parameters passed down to them from the top-level job. The DSLs are stored in Git. The parameters are details like repository, branch, build target and parameters that are not the same or always even similar, but the build process itself is, hence the DSL approach so I don't have to manage 60+ jobs manually.

I'm trying to wrap my head around how to update the generated jobs and what happens to the old jobs that already exist if I create new jobs. The generated jobs' names are determined by their parameters, among other things. So if I have job foo, and I re-run the seed but change that parameter to bar, does my existing job change to bar or do I now have two jobs, foo and bar? Now what happens if I update the DSL in git and the seed job is set to run on GitHub push? Will it update both foo and bar jobs or will it create new jobs with the parameter defaults? I guess this last question is more about how to update existing jobs without creating a new one?

I also realized that it might be better to use a super-seed job that reads sets of parameters from somewhere (csv or json maybe?) and creates jobs based on those. Then if we want a new job we just add some parameters at that location. In that case, how would we delete or disable jobs we no longer need, say after a branch is retired. Does anyone have an example of this kind of approach they can point me to?

The jobs are not all exactly the same per branch or per anything else, and we may want to create new ones on the fly to build feature branches or tags or individual hashes from git

I did read the docs but I think I'm just not understanding something fundamental.

Thanks again,
Misty