Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid travis build collision on S3 storage #432

Closed
soffokl opened this issue Oct 9, 2018 · 0 comments
Closed

Avoid travis build collision on S3 storage #432

soffokl opened this issue Oct 9, 2018 · 0 comments
Assignees
Labels

Comments

@soffokl
Copy link
Member

soffokl commented Oct 9, 2018

We are using S3 storage for sharing artifacts between build stages.
There could be collisions in Travis builds, since we are using the same bucket and location for all builds. Several parallel builds can affect each other.

We need to use $TRAVIS_BUILD_NUMBER to make our storage path independent.
And don't forget to clean S3 storage after build finished or failed. Travis support after_success and after_failure blocks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant