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
When a non-Analysis role is given, make sure we set BEARER_TOKEN_FILE (and thus BEARER_TOKEN) correctly in wrapper scripts. For example, for role production, experiment dune, the jobsub_submit line will be something like:
jobsub_submit -G dune --role production <args> file:///<path>/<to>/<executable>
In this case, in the wrapper scripts, (like https://github.com/marcmengel/jobsub_lite/blob/master/templates/simple/simple.sh#L10), we need to make sure that not only is the group templated, but the role. The convention is that the bearer token file for a production token will be named something like dune_production.use. So in general, _.use.
This should be pretty similar to the changes that had to be made for #13 .
The text was updated successfully, but these errors were encountered:
When a non-Analysis role is given, make sure we set BEARER_TOKEN_FILE (and thus BEARER_TOKEN) correctly in wrapper scripts. For example, for role production, experiment dune, the jobsub_submit line will be something like:
In this case, in the wrapper scripts, (like https://github.com/marcmengel/jobsub_lite/blob/master/templates/simple/simple.sh#L10), we need to make sure that not only is the group templated, but the role. The convention is that the bearer token file for a production token will be named something like dune_production.use. So in general, _.use.
This should be pretty similar to the changes that had to be made for #13 .
The text was updated successfully, but these errors were encountered: