why do you need to ?
I don't think you can do it. the only way i could think if is if you can pass something from the job that is derived at runtime to show the running user/role but i don't think that's possible either.
You’d have to reach back into the logs at runtime…
Thanks for the answers guys.
"Why do you need to?"
Because I'd like the final script that runs as part of the BLPackage to email the user who ran it with the output logs from all the scripts that ran (BladeLogic logging is atrocious). All our emails are in the format firstname.lastname@example.org, which matches the username when you log into BladeLogic so it would be easy to do.
"You’d have to reach back into the logs at runtime…"
That's not very good for automation
I'm surprised that with all the variables/attributes available that it's not possible to output who ran the job?!
it looks like there's an env var that might work:
shows up in the env in a deploy job's external command.