Reputation: 579
I just updated my Jenkins from 2.79 to 2.86
It seems to add new security fixes but it broke the EC2-Plugin
Indeed, now everytime the plugin is trying to launch a slave agent, I got an error:
"Launching agent" "ERROR: script not yet approved for use"
But the script to be approve via the Script Approval page is dynamic, containing temporary information
Did someone find how to solve the issue?
Thank you
EDIT:
I partially found a fix by unchecking the Connect by SSH Process
in the EC2 configuration
Upvotes: 0
Views: 578
Reputation: 11
Upvotes: 0
Reputation: 1
We were having the same issue while launching the slave agent via the SSH client process. As we were not able to quickly solve this, we've decided to downgrade Jenkins to version 2.84.
Upvotes: 0
Reputation: 60
I also downgraded to 2.84 as I could not figure out how to enable sandbox mode. Created new JIRA with Jenkins team.
https://issues.jenkins-ci.org/browse/JENKINS-47979
Upvotes: 0