[JIRA] [s3-plugin] (JENKINS-16025) Allow full path when uploading a file
Joshua K commented on JENKINS-16025 Allow full path when uploading a file Hey Justin, I found that if I use 'flatten directories' option in 0.7, this piece of code is skipped and it just uses the basename of the file, which is what i wanted anyway. You can add multiple upload configuration blocks if you need to put stuff in S3 sub-buckets. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [s3-plugin] (JENKINS-16025) Allow full path when uploading a file
Joshua K commented on JENKINS-16025 Allow full path when uploading a file ...Not to say that this shouldn't be fixed anyway, but i find this an effective workaround. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [s3] (JENKINS-16025) Allow full path when uploading a file
Joshua K edited a comment on JENKINS-16025 Allow full path when uploading a file Yeah, I think this patch is buggy. Not only should there be a "don't flatten" option and the default restored to the original behavior, but as-is, it doesn't appear to work. Here's my matcher: src/failed-gui-tests/*,src/build/logs/*.log,src/**/vncserver-*.out Here's what the UI says I uploaded: Publish artifacts to S3 Bucket bucket=my-bucket/my-project-3159_2014-06-12_01-55-55, file=test.all._javascript_.log region=US_EAST_1, upload from slave=false managed=false Publish artifacts to S3 Bucket bucket=my-bucket/my-project-3159_2014-06-12_01-55-55, file=test.all.python.log region=US_EAST_1, upload from slave=false managed=false Publish artifacts to S3 Bucket bucket=my-bucket/my-project-3159_2014-06-12_01-55-55, file=test.report.log region=US_EAST_1, upload from slave=false managed=false Publish artifacts to S3 Bucket bucket=my-bucket/my-project-3159_2014-06-12_01-55-55, file=test.system.run.log region=US_EAST_1, upload from slave=false managed=false Publish artifacts to S3 Bucket bucket=my-bucket/my-project-3159_2014-06-12_01-55-55, file=test.unit.run.log region=US_EAST_1, upload from slave=false managed=false Publish artifacts to S3 Bucket bucket=my-bucket/my-project-3159_2014-06-12_01-55-55, file=unpack-and-run.log region=US_EAST_1, upload from slave=false managed=false Publish artifacts to S3 Bucket bucket=my-bucket/my-project-3159_2014-06-12_01-55-55, file=update.all.log region=US_EAST_1, upload from slave=false managed=falsePublish artifacts to S3 Bucket bucket=my-bucket/my-project-3159_2014-06-12_01-55-55, file=vncserver-:1.out region=US_EAST_1, upload from slave=false managed=false Here's what I end up with in the S3 bucket: 2014-06-11 22:44:11 86740 -and-run.log 2014-06-11 22:44:12 2946 .all.log 2014-06-11 22:44:10102 .start.log 2014-06-11 22:44:11 38 .stop.log 2014-06-11 22:44:10 35601 e.tests.log 2014-06-11 22:44:10 2726 e.windows.all.log 2014-06-11 22:44:11 1029 eport.log 2014-06-11 22:44:10279 junit.report.dirs.log 2014-06-11 22:44:10 20 lease.files.log 2014-06-11 22:44:11 59899 ll._javascript_.log 2014-06-11 22:44:11 12879 ll.python.log 2014-06-11 22:44:11 208326 nit.run.log 2014-06-11 22:44:10 37 stop.log 2014-06-11 22:44:09 26294 upload.log 2014-06-11 22:44:11 4448 ystem.run.log 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [s3] (JENKINS-16025) Allow full path when uploading a file
Joshua K reopened JENKINS-16025 Allow full path when uploading a file Yeah, I think this patch is buggy. Not only should there be a "don't flatten" option and the default restored to the original behavior, but as-is, it doesn't appear to work. Here's my matcher: src/failed-gui-tests/,src/build/logs/.log,src/*/vncserver-.out Here's what the UI says I uploaded: Publish artifacts to S3 Bucket bucket=my-bucket/my-project-3159_2014-06-12_01-55-55, file=test.all._javascript_.log region=US_EAST_1, upload from slave=false managed=false Publish artifacts to S3 Bucket bucket=my-bucket/my-project-3159_2014-06-12_01-55-55, file=test.all.python.log region=US_EAST_1, upload from slave=false managed=false Publish artifacts to S3 Bucket bucket=my-bucket/my-project-3159_2014-06-12_01-55-55, file=test.report.log region=US_EAST_1, upload from slave=false managed=false Publish artifacts to S3 Bucket bucket=my-bucket/my-project-3159_2014-06-12_01-55-55, file=test.system.run.log region=US_EAST_1, upload from slave=false managed=false Publish artifacts to S3 Bucket bucket=my-bucket/my-project-3159_2014-06-12_01-55-55, file=test.unit.run.log region=US_EAST_1, upload from slave=false managed=false Publish artifacts to S3 Bucket bucket=my-bucket/my-project-3159_2014-06-12_01-55-55, file=unpack-and-run.log region=US_EAST_1, upload from slave=false managed=false Publish artifacts to S3 Bucket bucket=my-bucket/my-project-3159_2014-06-12_01-55-55, file=update.all.log region=US_EAST_1, upload from slave=false managed=falsePublish artifacts to S3 Bucket bucket=my-bucket/my-project-3159_2014-06-12_01-55-55, file=vncserver-:1.out region=US_EAST_1, upload from slave=false managed=false Here's what I end up with in the S3 bucket: 2014-06-11 22:44:11 86740 -and-run.log 2014-06-11 22:44:12 2946 .all.log 2014-06-11 22:44:10102 .start.log 2014-06-11 22:44:11 38 .stop.log 2014-06-11 22:44:10 35601 e.tests.log 2014-06-11 22:44:10 2726 e.windows.all.log 2014-06-11 22:44:11 1029 eport.log 2014-06-11 22:44:10279 junit.report.dirs.log 2014-06-11 22:44:10 20 lease.files.log 2014-06-11 22:44:11 59899 ll._javascript_.log 2014-06-11 22:44:11 12879 ll.python.log 2014-06-11 22:44:11 208326 nit.run.log 2014-06-11 22:44:10 37 stop.log 2014-06-11 22:44:09 26294 upload.log 2014-06-11 22:44:11 4448 ystem.run.log Change By: Joshua K (12/Jun/14 4:24 AM) Resolution: Fixed Status: Resolved Reopened 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [s3] (JENKINS-23338) Retry S3 uploads a couple times before giving up?
Joshua K created JENKINS-23338 Retry S3 uploads a couple times before giving up? Issue Type: Bug Assignee: Michael Watt Components: s3 Created: 05/Jun/14 6:04 PM Description: We often see this in our builds, usually a rebuild fixes it. Could the S3 plugin retry a couple times if it receives an error? 00:04:27.998 Publish artifacts to S3 Bucket Using S3 profile: 00:04:28.070 Publish artifacts to S3 Bucket bucket=x/y_master-471_2014-06-05_17-45-08, file=y_dist-Linux-x86_64.tgz region = US_EAST_1 00:05:40.909 ERROR: Failed to upload files 00:05:40.910 java.io.IOException: put Destination [bucketName=, objectName=_master-471_2014-06-05_17-45-08/_dist-Linux-x86_64.tgz]: com.amazonaws.AmazonClientException: Encountered an exception and couldn't reset the stream to retry 00:05:40.910 at hudson.plugins.s3.S3Profile.upload(S3Profile.java:90) 00:05:40.910 at hudson.plugins.s3.S3BucketPublisher.perform(S3BucketPublisher.java:144) 00:05:40.910 at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) 00:05:40.910 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) 00:05:40.910 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) 00:05:40.910 at hudson.model.Build$BuildExecution.post2(Build.java:183) 00:05:40.910 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:725) 00:05:40.910 at hudson.model.Run.execute(Run.java:1701) 00:05:40.910 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 00:05:40.910 at hudson.model.ResourceController.execute(ResourceController.java:88) 00:05:40.910 at hudson.model.Executor.run(Executor.java:231) 00:05:40.910 Build step 'Publish artifacts to S3 Bucket' changed build result to UNSTABLE Project: Jenkins Priority: Major Reporter: Joshua K 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-slaves] (JENKINS-22320) High CPU consumption because of SSH communication
Joshua K commented on JENKINS-22320 High CPU consumption because of SSH communication I strace'd and it looks like a lot of the traffic is due to repeatedly sending exceptions over the remoting channel: write(8, "q\0~\0\5\0\2\16`\0\0\0\0sr\0 java.lang.ClassNotFoundException\177Z\315f\324 \216\2\0\1L\0\2exq\0~\0\1xq\0~\0\10pt\0\23java.nio.file.Filesuq\0~\0\r\0\0\0\21sq\0~\0\17\0\0\5_t\0\33jenkins.util.AntClassLoadert\0\23AntClassLoader.javat\0\25findClassInComponentssq\0~\0\17\0\0\5-q\0~\0004q\0~\0005t\0\tfindClasssq\0~\0\17", 233) = 233 This is plausible, as our slaves/master run on Java 1.6 and java.nio.file.Files is new in 1.7. I will try to bump our slaves to use JDK 1.7 and see if that helps. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [s3] (JENKINS-21577) S3 Plugin: Publish Mulitple Artifacts
Joshua K commented on JENKINS-21577 S3 Plugin: Publish Mulitple Artifacts FYI, if you need to add more than one file all going to the same bucket, just add all the patterns in the first artifact description separated by commas as a workaround. If you have to use multiple buckets you have to go in and hack the config.xml. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
