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!
Attachments
Activity
hi Oleg Nenashev,
This functionality is required, the agent should run with the account the service is configured with and if no account is configured then it should run with SYSTEM account.
https://plugins.jenkins.io/authorize-project/ , this plugin does not satisfy this requirement.
Their are scenario when we cannot configure credentials in the job or build, but the agent can be run with specified account.
Please advise when this functionality would be available.
Vishwadeep Bansal
added a comment - - edited hi Oleg Nenashev ,
This functionality is required, the agent should run with the account the service is configured with and if no account is configured then it should run with SYSTEM account.
https://plugins.jenkins.io/authorize-project/ , this plugin does not satisfy this requirement.
Their are scenario when we cannot configure credentials in the job or build, but the agent can be run with specified account.
Please advise when this functionality would be available. Vishwadeep Bansal you are mixing Jenkins-internal users (e.g. system, oleg-nenashev mentioned in the log) and operating system users. Currently they are not aligned, and it is up to Jenkins admins to configure their system. I highly advice automation accounts for operating system users
"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