Add S3 deployment to appveyor setup #3441
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tests off, always do s3 upload, collect artifacts at right time
Add region, ls artifacts folder, echo an env var
mossheim
added
the
comp: appveyor
|
Thank you! |
|
A tagged release is now building: https://ci.appveyor.com/project/brianlheim/supercollider-mu8dk/build/146 |
|
This is ready for merge! |
patrickdupuis
approved these changes
Jan 20, 2018
nhthn
approved these changes
Jan 21, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds S3 deployment to our Appveyor setup so that "bleeding-edge" builds can be downloaded and tested by interested users and developers. Most of this was copied/adapted from
.travis.yml. Thanks to @scztt for helping with S3 access and general usage.This should be accompanied by an appropriate PR to the website making these builds available.
With the current config, builds are uploaded both for 32-bit and 64-bit builds.
I haven't tackled the automatic release asset uploading part of the script. If it isn't too hard to add that in, we can merge both at once. Might take some testing with temp tags created on this branch, if you're ok with that @snappizz.