Details
-
Type:
Bug
-
Status: Fixed but Unreleased (View Workflow)
-
Priority:
Major
-
Resolution: Not A Defect
-
Component/s: p4-plugin, windows-slaves-plugin
-
Labels:None
-
Similar Issues:
Description
Two issues:
1) The start of console output for my project always says "Running as SYSTEM", even if I start the windows service as a specific user. "Whoami" returns the user, but it's apparent that the permissions are different.
- My build command works if I run it in a cmd terminal, but if I execute it through Jenkins I see errors like this:
(<type 'exceptions.WindowsError'>, WindowsError(5, 'Access is denied'),
-
- class Spawn, Popen exception.
-
2) I installed another windows machine as a slave and launch it through a user account. At the beginning of the day it was working fine, but after restarting the computer I again see the same access issues.
How do I force Jenkins to run as a specific user, not SYSTEM (besides the approach to "log on as" user in the Services application)?
Thanks!
"Running as SYSTEM" in the build console represents the Jenkins user, not the system user for your agent. If you want to change a Jenkins user for the build, consider using the https://plugins.jenkins.io/authorize-project/ plugin