[JIRA] (JENKINS-38898) Managed artifacts fails to upload to S3 - no errors logged

2016-10-11 Thread bret.han...@ellucian.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bret Hansen commented on  JENKINS-38898  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Managed artifacts fails to upload to S3 - no errors logged   
 

  
 
 
 
 

 
 the buildnumber folder doesn't get created in S3, is the outcome  I found it because a later job that deploys to AWS fails because the artifacts are missing. Things that may be relevant but not sensitive include: job settings: Storage class - Standard Bucket Region - us-east-1 No upload on build failure is checked Manage artifacts is checked no other options are checked  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-38898) Managed artifacts fails to upload to S3 - no errors logged

2016-10-11 Thread bret.han...@ellucian.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bret Hansen created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38898  
 
 
  Managed artifacts fails to upload to S3 - no errors logged   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Alexander A  
 
 
Components: 
 s3-plugin  
 
 
Created: 
 2016/Oct/11 1:10 PM  
 
 
Environment: 
 Jenkins version 1.625.18.3 (CloudBees Jenkins Enterprise 15.11)  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Bret Hansen  
 

  
 
 
 
 

 
 Our devops core team updated to version 0.10.10 of the S3 Plugin. Build jobs that used the "Manage artifacts" check box for the post-build Publish artifacts to S3 Bucket then failed to upload the artifacts. Not even the directories were created in S3.  However, as old builds where discarded the old artifacts are removed from S3. No errors are given. It looks successful but it fails to upload. Output looks like this: Publish artifacts to S3 Bucket Build is still running Publish artifacts to S3 Bucket Using S3 profile: jenkins Publish artifacts to S3 Bucket bucket=ellucian-mobilecloud, file=mobilecloud.war region=us-east-1, will be uploaded from slave=false managed=true , server encryption false Archiving artifacts After reverting back to 0.8 version of the S3 plugin that we were using output looks like this: Publish artifacts to S3 Bucket Using S3 profile: jenkins Publish artifacts to S3 Bucket bucket=ellucian-mobilecloud, file=mobilecloud.war region=us-east-1, upload from slave=false managed=true , server encryption false Archiving artifacts