You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
-p ${PRIORITY_PARAM}
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: