|
||||||||
|
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/groups/opt_out.
First of all, in a secure environment you should configure the master computer to have no executors, so all builds are run on slaves, which may have their own user ID. Then you can configure which jobs can use certain slaves, e.g. http://jenkins-enterprise.cloudbees.com/docs/user-guide-bundle/foldersplus-sect-controlledslaves.html in Jenkins Enterprise (not sure if there is an open-source plugin with comparable functionality).
That said, it would indeed be useful to have a plugin using LauncherDecorator to run builds of certain jobs using sudo or the Windows equivalent. The tricky part would be integrating smoothly with the Credentials plugin.