PipelineFX Forum
Qube! => General => Topic started by: bijuramavfx on August 10, 2012, 06:51:01 PM
-
Hi there:
Is it possible to print the environment variables in the stdout tab in Qube GUI before running a job ..?
Thanks
/Biju
-
Hi there:
How do I specify to run env command(Linux) to output the env. variables to output tab before executing a job ..?
Thanks
-
Before running the job? hmmm... You could modify the command template so that it looks something like:
set && <original command template>
That will print out the environment and then immediately run the job. Printing out the env will have 0 effect on the job & will only change things by bloating the logs with the env prior to job starting.
If you're trying to take action based on the env, you could potentially run a script prior to the job by doing something similar:
my_script && <original command template>
if my_script returns non-zero, the original command template will not run & the frame/agenda will be considered a failure. For example, if my_script looked like this:
#!/bin/sh
exit 1
no frame/agenda wil ever run. You could, then, put some logic in the script to control how it exits & therefore control if/when the frame/agenda starts running.