[JIRA] (JENKINS-58096) Authorize Project plugin not working for pipeline
Title: Message Title Daniel Beck commented on JENKINS-58096 Re: Authorize Project plugin not working for pipeline The same way you could complain (even without the plugin) that the user name in the shell is svcbuildadmin and not Michael Marcucilli. Note that Jenkins's SYSTEM user has nothing to do with Windows's SYSTEM (or LocalSystem now?) user. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200138.1560954019000.6192.1564739160202%40Atlassian.JIRA.
[JIRA] (JENKINS-58096) Authorize Project plugin not working for pipeline
Title: Message Title Daniel Beck closed an issue as Not A Defect This isn't how this works. Authorize Project changes the virtual user identity of the build running inside Jenkins, which controls the actions the build can take inside Jenkins (such as triggering other builds). It does not magically cause processes to su to a different user that may not even exist in the OS. Jenkins / JENKINS-58096 Authorize Project plugin not working for pipeline Change By: Daniel Beck Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit
[JIRA] (JENKINS-58096) Authorize Project plugin not working for pipeline
Title: Message Title
Mike Marcucilli created an issue
Jenkins / JENKINS-58096
Authorize Project plugin not working for pipeline
Issue Type:
Bug
Assignee:
Unassigned
Components:
authorize-project-plugin
Created:
2019-06-19 14:20
Environment:
Windows Server 2012 R2
Priority:
Major
Reporter:
Mike Marcucilli
When I run a pipeline build with the Authorization set to either "Run as User who Triggered Build" or "Run as Specific User", the commands still execute as the account my Jenkins service is running as (hps\svcBuildAdmin). The below script demonstrates the problem
pipeline {
agent any
stages {
stage ('Check User') {
steps {
bat "whoami"
}
}
}
}
Output:
Started by user Michael Marcucilli
Running as Michael Marcucilli
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] Start of Pipeline
[Pipeline] node
Running on Jenkins in C:\Program Files (x86)\Jenkins\workspace\ApplicationADSyncer-Deploy
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Check User)
[Pipeline] bat
C:\Program Files (x86)\Jenkins\workspace\ApplicationADSyncer-Deploy>whoami
hps\svcbuildadmin
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Finished: SUCCESS
