|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
Jenkins: 1.580
Parameterized trigger: 2.25
SSH-Agent: 1.5
Authorize project: 1.0.3
If I uncheck "Configure Build Authorization" then it fails with the same output. But of course this time the "Running as Superman" is not printed/run.
I could elaborate on why I'd like it to work.
Every developer has his own public ssh-key on app-servers
Every developer adds his private key to his user
When promoting a build the developer must choose a valid ssh-private-key
This key is sent to a deploy job
Ssh-agent uses the deploy-key and voila.
This works well for Global keys or if the deploy job itself is invoked by a logged in user.
A workaround might be to restrict the number of users authorized to run the deploy job.