The most efficient way to accomplish your goal is to:
Parameterize your batch dataflow.
Download it, and re-upload one time for every set of parameter values you wish to trigger via Jenkins.
Configure the parameter values and create an individual trigger for each batch dataflow.
Then configure Jenkins to trigger the dataflow parameter sets via the individual trigger name.
The advantage of this technique is that it will result in a separate logging for each set of parameters to help with any troubleshooting.
Do you want me to submit a feature request for a technique to submit parameters when you trigger a Batch Dataflow using Jenkins?
Does this answer your question?