When I needed to run processes as a separate user, I'd configure a slave running as that other user. Jobs which needed that user could then be assigned to execute on that precise slave. The master server continues as the original user, and when a job needs to be a separate user, then that job would be tied to the slave running as the separate user.
Mark Waite On Mon, Aug 4, 2014 at 1:22 PM, johannes.ernst <johannes.er...@gmail.com> wrote: > I'm running Jenkins with Tomcat on Arch Linux. Jenkins executes as Linux > user tomcat7, as expected. > > Build script also execute as tomcat7, but for various reasons, I think > that's not great. For example, some of my build scripts need access to > certain private keys, and I would like to hide those private keys from > other apps running on the same Tomcat instance, and Tomcat itself. > > Question: is there some mechanism in Jenkins, or an extension, or some > best practices, for how to essentially "sudo" build scripts as some kind of > build user? > > I'd rather reuse than reinvent the wheel ... > > Thanks, > > > > Johannes. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Thanks! Mark Waite -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
