Closed alertedsnake closed 9 years ago
Thank you for bringing this to our attention. We were able to reproduce the problem and we are working on a fix.
We added Jenkins Remoting Support in the latest commit 1a9be5e. Closing the issue. If you have any problems, feel free to reopen it.
I got the same error. please could you help me here.
I get this error when building a CodePipeline Jenkins build. The workspace directory exists, but there are no files in it, and nothing anywhere tells me why the file could not be fetched.
I did give the Jenkins server's instance role the "AWSCodePipelineCustomActionAccess" IAM policy, and it also has "AmazonS3FullAccess."
How do I debug this further?