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 -- 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/56734179-e037-4d4e-b766-2370aaef6425%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
