|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Right, there is a chance of an environment variable leaking to others in the build log or similar. An alternative would be a designated file in the slave root containing a secret which the CLI agent would have to be modified to look for and send back to the master; this would not be protected from other builds on the same slave, but then again neither is your workspace. The ideal is to send the secret over a file descriptor inherited only via things started by the Launcher (akin to how ssh-agent works), but this is not portable to Windows that I know of.