array of identical Jenkins jobs, redundant code – how to replace using a "super-feature"?

[Jochen Hayek]

We do have like 10 Jenkins jobs here,

and they all call the same batch script,

always with the Jenkins job name as parameter

in order to give the batch script an opportunity to decide who is who.

I knew that kind of redundancy is bad,

but I don't know a better approach yet.

I don't think a usual parameterized Jenkins jobs solves it,

but maybe I am missing the magic trick.

Do you what I mean resp. what I need?

I need your advice.

~j