tag:help.appveyor.com,2012-11-13:/discussions/problems/23134-push-built-file-to-opensource-public-github-releaseAppVeyor: Discussion 2019-06-24T21:01:09Ztag:help.appveyor.com,2012-11-13:Comment/471925922019-04-21T12:55:24Z2019-04-21T14:08:35ZPush built Artifact *.exe to Github "Release" (opensource, public repos, dev account)<div><p>I am getting this result now:</p>
<p>Collecting artifacts...<br>
Found artifact 'build\weatherfax_pi-1.9.002-ov42-win32.exe' matching 'build*.exe' path<br>
Uploading artifacts...<br>
[1/1] build\weatherfax_pi-1.9.002-ov42-win32.exe (721,826 bytes)...100% Deploying using GitHub provider<br>
Creating "weatherfax_pi-v $(APPVEYOR_REPO_TAG_NAME) -win32" release for repository "rgleason/weatherfax_pi" tag "$(APPVEYOR_REPO_TAG_NAME)" commit "fa47cfbf64a54ab84b8554d6d9f2399c20969273"...Error creating GitHub release: Provider setting not found or it's value is empty. If secure setting is used please check that value was encrypted (or YAML was exported) while being logged under correct account.<br>
Parameter name: auth_token</p>
<p>I have made a Personal Token, selecting "Repro" in the check box for both public and personal read/write, entered a description of "appveyor_auth_token" hit "update", and then encrypted the access token on: <a href="https://ci.appveyor.com/tools/encrypt">https://ci.appveyor.com/tools/encrypt</a></p>
<p>Then used the result at the environment head of the appveyor.yml file<br></p>
<pre>
<code>environment:
auth_token:
secure: xxxxxx (not shown, but it was encryted.)</code>
</pre>
Am I doing this correctly? I thought it had to be associated with each repository to work. How is this done? Or have I taken the wrong steps?</div>fcgleasontag:help.appveyor.com,2012-11-13:Comment/471925922019-04-21T12:57:31Z2019-04-21T14:09:31ZPush built Artifact *.exe to Github "Release" (opensource, public repos, dev account)<div><p>Appveyor.yml</p>
<p>HEAD</p>
<pre>
<code># General Configuration #
# Environment Configuration #
environment:
auth_token:
secure:'mbgPeg6VB7oIYlnLQNd4XDi5/i46y+O/xXNKsnfdFFusOJjfxS5F1U1yZISa3aGg=='
# Appveyor auth token encrypted
# Build worker image (VM template)
image:
- Visual Studio 2015
# scripts that are called at very beginning, before repo cloning
# init:
version: 1.9.{build}
# clone directory
clone_folder: c:\project\weatherfax_pi
# fetch repository as zip archive
shallow_clone: true # default is "false"
# set clone depth, clone entire repository history if not defined
# clone_depth:5</code>
</pre>
<p>BOTTOM</p>
<pre>
<code>build_script:
# - cmake --build . --config debug
- cmake --build . --target package --config release
# Artifacts Configuration #
artifacts: # push all files in directory
path: build\*.exe
name: installer
# Deploy to GitHub Releases
deploy:
release: weatherfax_pi-v $(APPVEYOR_REPO_TAG_NAME) -win32
description: 'Release of weatherfax_pi $(APPVEYOR_REPO_TAG_NAME) tag created by AppVeyor build $(appveyor_build_version)'
provider: GitHub
artifact: installer, portable
draft: true
prerelease: true
tag: $(APPVEYOR_REPO_TAG_NAME) # will not work until tag is pushed
on:
# APPVEYOR_REPO_TAG: true # deploy on tag push only
configuration: Release # Debug contains non-redist MS DLLs
# branch: master # release from master branch only</code>
</pre></div>fcgleasontag:help.appveyor.com,2012-11-13:Comment/471925922019-04-21T13:37:49Z2019-04-21T13:37:51ZPush built Artifact *.exe to Github "Release" (opensource, public repos, dev account)<div><p>For GitHub Deployment to work shallow_clone must be set to false.<br>
I have it set to true. <a href="https://help.appveyor.com/discussions/problems/8009-github-release-deployment-issue">https://help.appveyor.com/discussions/problems/8009-github-release-...</a></p></div>fcgleasontag:help.appveyor.com,2012-11-13:Comment/471925922019-04-21T13:43:00Z2019-04-21T14:23:35ZPush built Artifact *.exe to Github "Release" (opensource, public repos, dev account)<div><p>Could try creating a release like this<br>
<a href="https://help.appveyor.com/discussions/problems/2971-github-deployment#comment_37865264">https://help.appveyor.com/discussions/problems/2971-github-deployme...</a></p>
<p>Read for formatting:<br>
<a href="https://help.appveyor.com/discussions/problems/2975-github-deployment#comment_37876490">https://help.appveyor.com/discussions/problems/2975-github-deployme...</a></p>
<p>Issues pushing Tags, Rolling builds:<br>
<a href="https://help.appveyor.com/discussions/problems/3362-deployment-to-github">https://help.appveyor.com/discussions/problems/3362-deployment-to-g...</a></p>
<p>Example, making the tag in appveyor from variables?<br>
<a href="https://github.com/tgjones/dryrunner/blob/master/appveyor.yml">https://github.com/tgjones/dryrunner/blob/master/appveyor.yml</a></p>
<p>================= So in summary: I have a workflow formula that should trigger a simultaneous release<br>
of both Linux and Windows binaries. Which is good. Thanks!!<br>
<a href="https://help.appveyor.com/discussions/problems/3362-deployment-to-github">https://help.appveyor.com/discussions/problems/3362-deployment-to-g...</a></p>
<p>At present if a commit message contains [ci skip] Appveyor will skip<br>
building.</p>
<p>It would be useful if Travis did the same, then I would have a unified per<br>
commit way to skip building when I’m, say, changing documentation.</p>
<p>It would also be useful if Appveyor recognised</p>
<p>[appveyor skip]</p>
<p>and Travis</p>
<p>[travis skip]</p>
<p>so if I am working on a platform dependent part of the code<br>
I can trigger one CI builder but not the other.</p>
<p>Of course I can control builds by rewriting appveyor.yml and .travis.yml<br>
every commit (eg renaming them to something else will prevent building).</p>
<h1><a name="but-that-s-a-pretty-heavyweight-way-to-do-a-commit-" class="anchor" href="#but-that-s-a-pretty-heavyweight-way-to-do-a-commit-"></a>But that’s a pretty heavyweight way to do a commit :)</h1>
<p>Use of isgithubrelease<br>
<a href="https://github.com/tgjones/dryrunner/blob/master/appveyor.yml">https://github.com/tgjones/dryrunner/blob/master/appveyor.yml</a></p>
<p>Trouble shoot using powerscript from local machine<br>
<a href="https://help.appveyor.com/discussions/questions/18741-publishing-to-github-releases-fails-sending-the-request">https://help.appveyor.com/discussions/questions/18741-publishing-to...</a></p>
<p>Workflows to Publish<br>
<a href="https://help.appveyor.com/discussions/questions/1106-github-release-deployment-hows-this-supposed-to-work">https://help.appveyor.com/discussions/questions/1106-github-release...</a></p>
<p>Trying to do a simple build and push.<br>
<a href="https://help.appveyor.com/discussions/problems/21897-trying-to-do-a-simple-github-deploy">https://help.appveyor.com/discussions/problems/21897-trying-to-do-a...</a></p></div>fcgleasontag:help.appveyor.com,2012-11-13:Comment/471925922019-04-21T14:12:21Z2019-04-21T14:12:49ZPush built Artifact *.exe to Github "Release" (opensource, public repos, dev account)<div><p>Making shallow_clone: false was not the problem</p>
<pre>
<code>Deploying using GitHub provider
Creating "weatherfax_pi-v $(APPVEYOR_REPO_TAG_NAME) -win32" release for repository "rgleason/weatherfax_pi" tag "$(APPVEYOR_REPO_TAG_NAME)" commit "1e2f6651cb14fa996198b915e6ff315d5c73fb6a"...Error creating GitHub release: Provider setting not found or it's value is empty. If secure setting is used please check that value was encrypted (or YAML was exported) while being logged under correct account.
Parameter name: auth_token</code>
</pre></div>fcgleasontag:help.appveyor.com,2012-11-13:Comment/471925922019-04-22T15:39:35Z2019-04-22T15:39:35ZPush built Artifact *.exe to Github "Release" (opensource, public repos, dev account)<div><p>Can you clarify what your current issue is? Is it simply that you are unable to deploy to GitHub release?<br>
Can you try putting the auth token in the <code>deploy:</code> settings as per the documentation.<br>
i.e.<br></p>
<pre>
<code>deploy:
auth_token:
secure: <your encrypted token> # your encrypted token from GitHub
release: weatherfax_pi-v $(APPVEYOR_REPO_TAG_NAME) -win32
description: 'Release of weatherfax_pi $(APPVEYOR_REPO_TAG_NAME) tag created by AppVeyor build $(appveyor_build_version)'
provider: GitHub
artifact: installer, portable
draft: true
prerelease: true
tag: $(APPVEYOR_REPO_TAG_NAME) # will not work until tag is pushed
on:
configuration: Release # Debug contains non-redist MS DLLs</code>
</pre></div>Owen McDonnelltag:help.appveyor.com,2012-11-13:Comment/471925922019-04-23T03:56:21Z2019-04-23T03:56:21ZPush built Artifact *.exe to Github "Release" (opensource, public repos, dev account)<div><p>Thanks Owen, for looking at this. I tried moving the auth_token down to deploy as you suggested:</p>
<p>I still seem to be getting this:<br></p>
<pre>
<code>Collecting artifacts...
Found artifact 'build\weatherfax_pi-1.9.002-ov42-win32.exe' matching 'build*.exe' path
Uploading artifacts...
[1/1] build\weatherfax_pi-1.9.002-ov42-win32.exe (721,838 bytes)...100%
Deploying using GitHub provider
Creating "$(APPVEYOR_REPO_TAG_NAME)" release for repository "rgleason/weatherfax_pi" tag "$(APPVEYOR_REPO_TAG_NAME)" commit "c24ab24f3b53bb7b016da6720eebd3233514aae3"...Error creating GitHub release: Error reading repository 'rgleason/weatherfax_pi' releases: 401 - Unauthorized</code>
</pre>
<p>This is an unauthorized reading error of the rgleason/weatherfax_pi<br>
I am not sure why it is trying to read that.</p>
<p>I would like to push the <a href="https://ci.appveyor.com/project/rgleason/weatherfax-pi/builds/24030333/artifacts">artifact file here</a></p>
<p>to my <a href="https://github.com/rgleason/weatherfax_pi/releases">github release location here</a></p>
<p>when I have push a new tag to the github repository. Right now I have that disabled, because I think it works, but I am getting this auth error, so I am just trying to deploy the file with every commit.</p>
<p>It looks to me like it might have happened once, when I pushed a new tag but did not see it <a href="https://github.com/rgleason/weatherfax_pi/releases/tag/v1.9.2-ov42">v1.9.2-ov42</a> when I "changed to "appveyor_auth_token" but it resulted in an error, <a href="https://ci.appveyor.com/project/rgleason/weatherfax-pi/builds/23999698">see this</a> which does have a file that was uploaded.</p>
<p>Do you have any other suggestions?</p>
<p>could I try git push or something as a way to test the authorization?</p></div>fcgleasontag:help.appveyor.com,2012-11-13:Comment/471925922019-04-23T10:52:27Z2019-04-23T10:52:27ZPush built Artifact *.exe to Github "Release" (opensource, public repos, dev account)<div><p>When I encrypted the public key using the <a href="https://ci.appveyor.com/tools/encrypt">appveyor encryption page here</a> I gave it a description of "appveyor_auth_token" and using that as the designator seems to work to create a "release". So I will use that instead of "auth_token" in hopes that future releases are more successful.</p>
<p>The second part of this this problem is that the file is not being copied. Perhaps the reason is that source is not being "found" and thus can't be "read".</p>
<p>I have to check pathnames and verify what all the deploy settings do.</p></div>fcgleasontag:help.appveyor.com,2012-11-13:Comment/471925922019-04-23T10:57:33Z2019-04-23T12:20:18ZPush built Artifact *.exe to Github "Release" (opensource, public repos, dev account)<div><p>Under "Account Details" "Authorizations" I find</p>
<blockquote>
<p>AppVeyor is authorized to act on behalf of rgleason GitHub account with admin:repo_hook, read:org, repo:status scope.<br>
Don't see org resources? Ensure organization access is granted to AppVeyor CI application.</p>
</blockquote>
<p>I am not sure that this covers write to the github "release" directory.</p>
<p>Under my Github overall "Settings" (not for a certain repository) The OAuth Apps listed are:</p>
<p>Appveyor<br>
- Read org and team membership, read org projects - Access user email addresses (read-only)</p>
<p>Appveyor CI<br>
- Full control of repository hooks - Read org and team membership, read org projects - Access commit status</p>
<p>Under a note "Read about Third Party Access"<br>
I wonder if I need to become a git "organization" in order to be able to copy a file to a particular github "Release" directory?<br>
<a href="https://help.github.com/en/articles/enabling-oauth-app-access-restrictions-for-your-organization">https://help.github.com/en/articles/enabling-oauth-app-access-restr...</a></p>
<p>This github page is about <a href="https://help.github.com/en/articles/enabling-oauth-app-access-restrictions-for-your-organization">Enabling OAuth Apps restrictions for your Organization</a></p>
<p>This github page is about <a href="https://help.github.com/en/articles/authorizing-oauth-apps">Authorizing OAuth Apps</a></p>
<blockquote>
<p>OAuth App access OAuth Apps can have read or write access to your GitHub data. Read access only allows an app to look at your data. Write access allows an app to change your data.</p>
</blockquote>
<p>So it looks like my permissions might not be configured properly, or need to be checked.</p>
<p>Earlier, under Github, > Setttings > Developer Settings<br>
I created a "Personal Access Token" with the description appveyor_auth_token"<br>
When this was done the scope checked was "Repo -Full control of Private Repositories" which gives repo-status, repo-deployment, public-repo, repo-invite.</p>
<p>Perhaps this is not enough, I need to be able to write to the Release directory.<br>
Should I also check ADMIN: REPO-HOOK?</p>
<p>The public key was then encryped</p></div>fcgleasontag:help.appveyor.com,2012-11-13:Comment/471925922019-04-23T12:10:31Z2019-04-23T12:32:46ZPush built Artifact *.exe to Github "Release" (opensource, public repos, dev account)<div><p>Progress: After un-commenting the</p>
<p>APPVEYOR_REPO_TAG: true # deploy on tag push only</p>
<p>and making a commit and then pushing it up to origin, then making another commit to change the tag "git tag v1.9.3-0v42" and "git push origin v1.9.3-ov42"</p>
<p>I find that the new "Release" folder exists, however the *.exe file is not there.</p>
<p>Now I realize that this Release folder is being created from my local repos, by my git push of the tag to origin. So appveyor has nothing to do with this. Also appveyor finished with</p>
<p>Collecting artifacts...<br>
Found artifact 'build\weatherfax_pi-1.9.002-ov42-win32.exe' matching 'build*.exe' path<br>
Uploading artifacts...</p>
<blockquote>
<p>[1/1] build\weatherfax_pi-1.9.002-ov42-win32.exe (721,835 bytes)...100% Deploying using GitHub provider Creating "v1.9.3-ov42" release for repository "rgleason/weatherfax_pi" tag "v1.9.3-ov42" commit > "cd57cabe32ce5347f6f89ce1488f171233fbf0d0"...Error creating GitHub release: Provider setting not found or it's value is empty. If secure setting is used please check that value was encrypted (or YAML was exported) while being logged under correct account. Parameter name: auth_token</p>
</blockquote>
<p>As stated before, I have created a Github Personal Auth and encryted the public key using the Yaml encryption and have used that in the appveyor.yml file.</p></div>fcgleasontag:help.appveyor.com,2012-11-13:Comment/471925922019-04-23T23:45:18Z2019-04-24T00:34:04ZPush built Artifact *.exe to Github "Release" (opensource, public repos, dev account)<div><p>Some links that might be useful:</p>
<p><a href="https://help.appveyor.com/discussions/problems/14881-build-hanging-in-on_success-during-git-push">Build hanging in 'on_success' during git push</a></p>
<blockquote>
<p>If it has been encrypted make sure you're doing so from the same account your building on and syntax should be, environment: access_token: secure:</p>
</blockquote>
<ul>
<li>The token i use only has "repo" permissions.I can't imagine granting all permissions could possibly do anything to interrupt this process...</li>
<li>Created a new token only with the "repo" permission, same behavior. On the agent it stucks in the git push, but in the RDP session, it works. May it be a different version of git.exe?</li>
<li>The end result of this discussion was unsuccessful. The push to release did not work.</li>
</ul>
<p><a href="https://www.appveyor.com/docs/how-to/rdp-to-build-worker/">RDP Remote Desktop</a></p>
<p><a href="https://help.appveyor.com/discussions/problems/2971-github-deployment">GitHub deployment</a></p>
<p><a href="https://help.appveyor.com/discussions/questions/3823-deploying-to-github-releases">Deploying to GitHub releases</a></p>
<p><a href="https://help.appveyor.com/discussions/kb/2-guide-how-to-release-automatically-your-artifact-to-github">How to release automatically your artifact to GitHub</a> dated 2014, since then I think appveyor has more automation.</p>
<p><a href="https://help.appveyor.com/discussions/problems/2393-push-tags-to-git">Push tags to git</a></p>
<p>Posted in 2015, have things changed?</p>
<ul>
<li>But since you are currently on GitHub</li>
<li>I'd like recommend using Personal Access Tokens instead of username:password:</li>
<li>1. Generate token: <a href="https://help.github.com/en/articles/creating-a-personal-access-token-for-the-command-line">https://help.github.com/en/articles/creating-a-personal-access-toke...</a></li>
<li>2. Use token in repo URL as token: (password is empty): <a href="https://help.github.com/articles/git-over-https-using-oauth-token">https://help.github.com/articles/git-over-https-using-oauth-token</a></li>
<li>Repo URL will look like: https://token:@github.com/jwChung/Funz.git</li>
</ul>
<p><a href="https://help.appveyor.com/discussions/questions/35480-build-from-release-tarball-or-cvs-checkout">build from release tarball or CVS checkout</a> Not something I am doing now, but might be needed.</p>
<p><a href="https://help.appveyor.com/discussions/questions/2375-how-do-you-specify-artifacts-for-a-github-release">How do you specify artifacts for a GitHub release?</a> Useful for path names etc.</p></div>fcgleasontag:help.appveyor.com,2012-11-13:Comment/471925922019-04-24T00:39:34Z2019-04-24T00:40:02ZPush built Artifact *.exe to Github "Release" (opensource, public repos, dev account)<div><p>Just found another page with more info about webhooks on the repository webpage.</p>
<p><a href="https://github.com/rgleason/weatherfax_pi/settings/hooks">https://github.com/rgleason/weatherfax_pi/settings/hooks</a></p>
<ul>
<li><a href="https://ci.appveyor.com/api/github/webhook">https://ci.appveyor.com/api/github/webhook</a> (pull_request and push)</li>
<li><a href="https://notify.travis-ci.org/">https://notify.travis-ci.org/</a> (create, delete, issue_comment, member, public, pull_request, push, and repository)</li>
</ul>
<p>So webhooks will permit push. Just get the auth_token working!</p></div>fcgleasontag:help.appveyor.com,2012-11-13:Comment/471925922019-04-24T01:31:57Z2019-04-24T01:47:55ZPush built Artifact *.exe to Github "Release" (opensource, public repos, dev account)<div><p>Creating a new Personal Access Token, encrypting and adding the result to appveyor.yml</p>
<p><strong>New Github Personal Access Token</strong></p>
<p>Log into Github Account and create a Git Personal Access Token<br>
Go to Account > Settings (from upper right dropdown) > Developer Settings at bottom > Personnal Access Tokens<br>
<a href="https://github.com/settings/tokens">https://github.com/settings/tokens</a></p>
<p>Generate a new token, add description "appveyor_auth_token"<br>
When it is created, copy it immediately to your clipboard as it will disappear. Also Edit the Personnel Token to set the scope to "repo" with a check in the checkbox.</p>
<p><strong>Appveyor Yaml Encryption</strong></p>
<p>Go to Yaml Encryption <a href="https://ci.appveyor.com/tools/encrypt">https://ci.appveyor.com/tools/encrypt</a> and paste the Personnel Token into the encrypt-er. Then copy the result, which is then used in the appveyor.yml file.</p>
<blockquote>
<p>environment: auth_token: secure: VVAVg9a8n+XgesI85/cXrXyNeStivq8FynlajE94lGUtzDGeu5PMWI5f1OSYg0tS</p>
</blockquote>
<p>or under deploy:</p>
<blockquote>
<p>appveyor_auth_token: secure: VVAVg9a8n+XgesI85/cXrXyNeStivq8FynlajE94lGUtzDGeu5PMWI5f1OSYg0tS <a href="https://ci.appveyor.com/tools/encrypt">https://ci.appveyor.com/tools/encrypt</a></p>
</blockquote>
<p><strong>Verify the appveyor.yml file (it passed)</strong></p>
<p><a href="https://ci.appveyor.com/tools/validate-yaml">https://ci.appveyor.com/tools/validate-yaml</a></p></div>fcgleasontag:help.appveyor.com,2012-11-13:Comment/471925922019-04-24T02:04:30Z2019-04-24T03:04:32ZPush built Artifact *.exe to Github "Release" (opensource, public repos, dev account)<div><p>Once again this was the error<br>
<a href="https://ci.appveyor.com/project/rgleason/weatherfax-pi">https://ci.appveyor.com/project/rgleason/weatherfax-pi</a></p>
<pre>
<code>Collecting artifacts...
Found artifact 'build\weatherfax_pi-1.9.3-ov42-win32.exe' matching 'build\*.exe' path
Uploading artifacts...
[1/1] build\weatherfax_pi-1.9.3-ov42-win32.exe (721,813 bytes)...100%
Deploying using GitHub provider
Creating "$(APPVEYOR_REPO_TAG_NAME)" release for repository "rgleason/weatherfax_pi" tag "$(APPVEYOR_REPO_TAG_NAME)" commit "358efcbda183e48f52e47dc35495a277dc95c60b"...
Error creating GitHub release: Provider setting not found or it's value is empty.
If secure setting is used please check that value was encrypted
(or YAML was exported) while being logged under correct account.
Parameter name: auth_token</code>
</pre>
<p>Something has been done wrong. The real question is what is it?</p>
<p>Appveyor validation passed, but the security: is not working.</p>
<p><a href="https://github.com/settings/security">https://github.com/settings/security</a> shows</p>
<p>Security history</p>
<p>This is a security log of important events involving your account. an hour ago<br>
oauth_authorization.create – Personal access token (appveyor_auth_token) an hour ago oauth_authorization.destroy – Personal access token (appveyor_auth_token) deleted on github.com 4 days ago user.login – Originated from 73.60.236.200 4 days ago public_key.verification_failure 4 days ago public_key.delete – appveyor_deploy_key - 77:79:94:c3:21:03:5b:4f:37:c0:05:b2:61:4f:b1:92</p>
<p>Under Github Account > Developer Settings > Personal Access<br>
<a href="https://github.com/settings/tokens">https://github.com/settings/tokens</a></p>
<p>shows appveyor_auth_token as never being used again!</p>
<p><a href="https://github.com/rgleason/weatherfax_pi/commits/deploy-win2">https://github.com/rgleason/weatherfax_pi/commits/deploy-win2</a></p></div>fcgleasontag:help.appveyor.com,2012-11-13:Comment/471925922019-04-24T03:10:08Z2019-04-24T03:13:00ZPush built Artifact *.exe to Github "Release" (opensource, public repos, dev account)<div><pre>
<code>Error creating GitHub release: Provider setting not found or it's value is empty.
If secure setting is used please check that value was encrypted
(or YAML was exported) while being logged under correct account.</code>
</pre>
<ul>
<li>What provider setting is not found or is empty?</li>
<li>The Github Personal Access Token was encrypted using Appveyor Yaml encryption</li>
<li>The result is used with security: xxxxxx</li>
</ul></div>fcgleasontag:help.appveyor.com,2012-11-13:Comment/471925922019-04-24T03:14:35Z2019-04-24T03:14:35ZPush built Artifact *.exe to Github "Release" (opensource, public repos, dev account)<div><p>I am beginning to think that there is not a good answer as to how to accomplish this task and am ready to quit this insanity.</p></div>fcgleasontag:help.appveyor.com,2012-11-13:Comment/471925922019-04-24T03:40:13Z2019-06-22T16:17:58ZPush built Artifact *.exe to Github "Release" (opensource, public repos, dev account)<div><p>Simplifying and eliminating the Tag operations have allowed the Artifact *.exe file to be pushed to Git Release. See Release 1.9.149 <a href="https://github.com/rgleason/weatherfax_pi/releases/tag/untagged-87f9031bebca058d73c0">https://github.com/rgleason/weatherfax_pi/releases/tag/untagged-87f...</a></p>
<p>The deploy settings are now:</p>
<pre>
<code>build_script:
# - cmake --build . --config debug
- cmake --build . --target package --config release
# Artifacts Configuration #
artifacts: # push all files in directory
path: build\*.exe
name: installer
# Deploy to GitHub Releases
deploy:
provider: GitHub
auth_token:
secure: VVAVg9a8n+XgesI85/cXrXyNeStivq8FynlajE94lGUtzDGeu5PMWI5f1OSYg0tS
artifact: installer, portable
draft: true
prerelease: true
description: "describe the plugin here" (mandatory - added later)
# tag: $(APPVEYOR_REPO_TAG_NAME) # will not work until tag is pushed
on:
configuration: Release # Debug contains non-redist MS DLLs
# APPVEYOR_REPO_TAG: true # deploy on tag push only
# branch: master # release from master branch only</code>
</pre>
<p>Now I have to figure out how to<br>
1. Push artifacts to release when I push a new Tag and show a green check.<br>
2. When a new Tag is not pushed, just create the artifact and show a green check.</p></div>fcgleasontag:help.appveyor.com,2012-11-13:Comment/471925922019-04-24T13:22:10Z2019-04-24T13:22:10ZPush built Artifact *.exe to Github "Release" (opensource, public repos, dev account)<div><p>As per the docs on <a href="https://www.appveyor.com/docs/deployment/github/#provider-settings">GitHub deployment</a>, a <code>description:</code> key for <em>release description</em> is mandatory.</p></div>Owen McDonnell