This documentation relates to QuickBuild 10.0.x
Select here if you are using a different version

Amazon S3 Integration

Version 2 by Steve Luo
on Feb 19, 2020 07:46.


compared with
Current by Steve Luo
on Feb 19, 2020 07:48.


 
Key
These lines were removed. This word was removed.
These lines were added. This word was added.

View page history


There are 1 changes. View first change.

  Since QuickBuild 10, artifacts can be published to Amazon S3 ([Amazon Simple Storage Service|https://aws.amazon.com/s3/] and also, artifacts can be checked out from Amazon S3.
  Since QuickBuild 10, artifacts can be published to Amazon S3 ([Amazon Simple Storage Service|https://aws.amazon.com/s3/]), artifacts can also be checked out from Amazon S3.
  
 h2. Publish Artifacts
  
 To publish artifacts to Amazon S3, you can add Publish S3 Artifacts step to your build workflow:
  
 !s3-menu.png!
  
 In step definitions, specify the source directory and files to publish pattern, and S3 bucket and region fields are required.
  
 !s3-step.png!
  
 if artifacts have been published to S3 successfully, QuickBuild will show you the artifacts report in build overview page like below:
  
 !s3-report.png!
  
  
 h3. Authentication
  
 In QuickBuild, credential provider chain looks for credentials in below order to communicate with S3 service:
  
 * *Step level*: access key id and access secret specified in the step.
 * *Credential File* specified in EC2 plugin setting.
 * *Environment variables*: AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY
 * *Java system properties*: aws.accessKeyId and aws.secretKey.
 * *The default credential profiles file*: typically located at ~/.aws/credentials (location can vary per platform).
 * *Amazon ECS container credentials*: loaded from the Amazon ECS if the environment variable AWS_CONTAINER_CREDENTIALS_RELATIVE_URI is set.
  
  
 h2. S3 Repository
  
 You can also use S3 as a repository and then later use checkout step to checkout the artifacts from Amazon S3.
  
 !s3-repo.png!