|
||||||||
|
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.
Tried pulling 131 and patching current master - it fails to connect to aws.
Pulled current master - built and depoyed - connects okay (but has normal bug in it)
Pulled 131 and split the patch in two - first half (ie prior 131) works - can connect to aws
Apply second patch as a straight merge - and it builds - but cannot connect
Next tried pull master, apply firt half - and then apply my patch alone - this works.
Looks like something in the second patch causes aws to fail.
Let me know if you need a stack trace or anything if you cannot reproduce - but happens every time for me.
Try executing 'Test Connection' from jenkins config page for ec2 - fails immediately for both profile and real keys.