-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test Connection button on configure screen does not test with newly supplied credentials #15
Comments
I ran into this as well. When I first added the credentials it worked, but after I created a different spot fleet and reconfigured the plugin to use that instead, it stopped working. Temporarily adding full administrator access to the jenkins user did not help - the credentials are definitely not being used. I think attaching the Spot instance management policies to the Instance profile role is the better way to go. That way there's no need to manage a jenkins user and credentials separately. |
probably duplicate #71 |
Looks like two different issues: @jarrodspiga I don't think this is an issue with the plugin, it cannot work without permission, so first failed to try looks ok for me. Do you expect different behavior? @Cyphus in your case did you just change one fleet on another? |
@terma yes, the only change I made was to update the spot fleet instance to connect to a different spot fleet. |
#15 Fix test connections (avoid conflict credentialsId with ssh creds)
going to close issues, feel free to open if you still have problem or questions, thx |
Steps to re-produce:
The text was updated successfully, but these errors were encountered: