|
||||||||
|
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.
Another option would be to define a BuildWrapper which sets an environment variable during the build to a random UUID which CommandDuringBuild, and perhaps any CLICommand, would check for; if set, the transport authentication would be set automatically to that of the build, and a flag set so that commands could decide to skip permission checks for the running build.
Such a build wrapper could also ensure that jenkins-cli.jar is available on the slave machine in $JENKINS_CLI_JAR, so that you would not be required to download it manually, which would make running CLI commands from inside a build a lot more convenient. Of course this could be done automatically on any slave without requiring a custom build wrapper, but that would affect performance of everybody.
(Defining a Builder is also an option, though this gives less flexibility for people who want to embed CLI commands in the middle of shell scripts and the like.)