From c48248607fe000a0d6a83e97543d462c3b329e62 Mon Sep 17 00:00:00 2001 From: Bob Summerwill Date: Thu, 11 Aug 2016 13:36:49 -0700 Subject: [PATCH] Added comments about 'auth_token' setup for Appveyor. Switched the white-listed branch to 'develop', so we can dry-run the Windows ZIP generation here. On success, will then delete those artifacts and switch the whitelisting back to 'release', pending creation of a release branch for the solidity repo. --- appveyor.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/appveyor.yml b/appveyor.yml index 6f1836bbd..450239c8d 100644 --- a/appveyor.yml +++ b/appveyor.yml @@ -64,6 +64,15 @@ artifacts: # We are in agreement that generating ZIPs per commit for the develop # branch is probably just noise, so we only run this deployment target # on 'release'. +# +# See https://www.appveyor.com/docs/deployment/github for information +# on GitHub Releases in Appveyor. +# +# You need to generate a GitHub personal access token for Appveyor +# See https://github.com/settings/tokens for more information on that. +# The token you generate there (in an encrypted form) is what is +# passed to this deployment target in the 'auth_token' parameter +# below. deploy: release: solidity-develop-v$(APPVEYOR_BUILD_VERSION) @@ -75,4 +84,4 @@ deploy: secure: yukM9mHUbzuZSS5WSBLKSW0yGJerJEqAXkFhDhSHBBcKJE7GAryjQsdO9Kxh3yRv artifact: solidity-windows-zip on: - branch: release + branch: develop