![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Michael Watt
|
|
Components:
|
s3 |
|
Created:
|
31/Oct/12 8:36 AM
|
|
Description:
|
Upload broke with this error:
Publish artifacts to S3 Bucket Using S3 profile: jenkins
Publish artifacts to S3 Bucket bucket=deploy.***.com, file=www-site.tar.gz
ERROR: Failed to upload files
java.io.IOException: put Destination [bucketName=deploy.***.com, objectName=www-site.tar.gz]: com.amazonaws.AmazonClientException: Unable to execute HTTP request: Input stream cannot be reset as 5365760 bytes have been written, exceeding the available buffer size of 131072
at hudson.plugins.s3.S3Profile.upload(S3Profile.java:82)
at hudson.plugins.s3.S3BucketPublisher.perform(S3BucketPublisher.java:119)
at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:27)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:807)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:782)
at hudson.model.Build$BuildExecution.post2(Build.java:183)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:729)
at hudson.model.Run.execute(Run.java:1541)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:236)
Build step 'Publish artifacts to S3 Bucket' changed build result to UNSTABLE
Artifact size hasn't changed so I don't think could be client related. Here a related discussion on AWS forum: https://forums.aws.amazon.com/thread.jspa?threadID=66753
It would be nice to be able to tweak the retry number, or at least have a fixed value for that and not fail at the first try.
|
|
Environment:
|
Ubuntu 11.10, Linux 3.0.0-24-virtual #40-Ubuntu SMP Tue Jul 24 16:16:08 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux (Ec2)
|
|
Project:
|
Jenkins
|
|
Labels:
|
plugin
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Alexander Fortin
|
|
|
|
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
|
