Open tfnico opened 9 years ago
Hi @tfnico!
I like the idea of having this option. I think for Maven jobs, or Maven build steps, you can do the same thing in Jenkins.
Right now I'm almost done understanding the current state of pbs-java-api, drmaa-pbs, and external API's.
The plan is to choose one, that is easy to be extended. Then, build a generic API replacing or enhancing the existing pbs-java-api.
This way the pbs-plugin will be able to support others server, like SGE (and we may probably vote a rename).
If I realize it will take too long, I will simply fix the issues in pbs-plugin, cut a release, and work on this in parallel.
Feel free to bump this issue if I take too long to reply here.
Cheers Bruno
Currently, running a PBS job will have no arguments, hence being limited to the #PBS comments we hardcode into the top of the script.
In order to allow dynamic arguments, say for example from a parameterized Jenkins job, there could be a text field below the PBS script where one could type stuff like:
then it would be passed on to qsub. This is pretty similar to how one can provide dynamic arguments to other builders in Jenkins (Maven, etc).
Sound like a good idea?