-
Notifications
You must be signed in to change notification settings - Fork 294
Conversation
6c68dcf
to
9bb6611
Compare
Store snap travici linux builds in a s3 repository. * Upload build directory to AWS s3. * Update DNS build.ci.snap-telemtry.io -> s3 repo.
@IzabellaRaulin this is ready for review now. Because of the following condition restriction, you won't see anything interesting in the travis.ci run for the pull request, only when the code is merged to master:
Due to this reason, I have a temporary build branch to demonstrate this change here. The interesting section are summarized below:
When a PR is merged on master, the last test (medium on Go 1.6.2) will:
The will ensure the latest snap binary is available at:
Older versions will be available at: NOTE: This is strictly used for internal testing, and there is neither guarantees on url nor file availability, and we have not decided how long to store old binaries. |
cedc360
to
81c83db
Compare
* add a s3 build matrix for travis.ci * use full git log sha %H instead of %h for folder name
Updated to use full sha and a separate build branch. Latest build example: https://travis-ci.org/intelsdi-x/snap/jobs/146729271#L203-L237 |
LGTM |
Store snap travici linux builds in a s3 repository.
Testing done:
@intelsdi-x/snap-maintainers