This article is about Codeship Basic.

Build Artifacts

You will need about one minute to read this article.

For security reasons Codeship does not provide persistent storage of files between builds (aside from the build log). If you wish to retain artifacts for troubleshooting purposes, then you will need to implement steps to transfer them to a remote server during the build run.

Upload artifacts to S3

If you want to upload artifacts to S3 during your test steps, you can use the AWS CLI. First add the following environment variables to your project configuration:

AWS_DEFAULT_REGION
AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY

Then add the following commands to your setup/test steps:

pip install awscli
aws s3 cp your_artifact_file.zip s3://mybucket/your_artifact_file.zip

For Codeship Pro, our Codeship AWS container can be implemented to transfer artifacts to S3 storage.

For more advanced usage of the S3 CLI, please see Amazon’s S3 documentation.

Note that you can simply add another integrated S3 deployment after your actual deployment if you only want to keep artifacts for specific branches.

Upload through SFTP

Each project has its own SSH public key which you’ll find under Project Settings > General. You can use this key to grant access to your storage provider for Codeship or upload files through SFTP.

Need more help?

Contact our support team or post on Stack Overflow using the tag #codeship. Did you check the status page and changelog?

There are also several code examples and sample projects available for you to get started with.

Article not helpful?

Does this article need improvement? If so, please send feedback or submit a pull request!