On 02/14/2014 02:54 AM, Franco Broi wrote: > > > I'm also trying to pass some job dependent information to the trigger > script. Is there somewhere in the job structure for user defined > information to be stored? I could them retrieve this using the jobid.
I was thinking of using an environment variable in the job itself (not the trigger): sbatch --export DATA=[vvv] and retrieve it using the api (if that's possible at all). But depending on the trigger, the job state might be already gone by the time you need it. Encoding it in the comment is also a possibility, since you could later use sacct at any time to fetch it. But at the moment I'm already using the comment to encode other job details (and feels unclean anyway).
