tag:help.appveyor.com,2012-11-13:/discussions/problems/23669-wildcards-for-artifacts-work-in-yml-but-not-in-uiAppVeyor: Discussion 2019-07-21T21:01:06Ztag:help.appveyor.com,2012-11-13:Comment/472769012019-05-20T08:07:39Z2019-05-20T08:07:41ZWildcards for artifacts work in YML but not in UI?<div><p>Apologies, a small oversight. The snippet above didn't format as expected. The backspace was swallowed. This is what it should have said:<br></p>
<pre>
<code> artifact: deploy\*.zip</code>
</pre>
<p>Also the workaround to all this, of course, would be to give the artifact a name, and put that name in the UI:<br></p>
<pre>
<code>artifacts:
- path: deploy\*.zip
name: zip</code>
</pre>
Cheers!</div>Dejan Budimirtag:help.appveyor.com,2012-11-13:Comment/472769012019-05-20T17:29:33Z2019-05-20T17:29:33ZWildcards for artifacts work in YML but not in UI?<div><p>I suggest you familiarize yourself with the interplay between UI and yaml config by reading <a href="https://www.appveyor.com/docs/build-configuration/#appveyoryml-and-ui-coexistence">this</a>.<br>
For the most part it is one or the other, i.e. if you have a config file your UI settings are largely ignored.</p></div>Owen McDonnelltag:help.appveyor.com,2012-11-13:Comment/472769012019-05-21T14:47:20Z2019-05-21T14:47:20ZWildcards for artifacts work in YML but not in UI?<div><p>Thanks, Owen!</p>
<blockquote>
<p>It’s worth noticing that both appveyor.yml and UI configuration are mutually exclusive.</p>
</blockquote>
<p>Worth noticing Indeed! It did feel like I was missing something crucial.</p>
<p>I suggest you put this at the top of the "Appveyor.yml reference" section as well. Thank you!</p></div>Dejan Budimirtag:help.appveyor.com,2012-11-13:Comment/472769012019-05-21T15:13:17Z2019-05-21T15:13:19ZWildcards for artifacts work in YML but not in UI?<div><p>I may have been thrown off by the UI's <code>Tag name</code>, <code>Release name</code>, <code>Release description</code>, <code>Github authentication token</code>, etc. not being mentioned in the <a href="https://www.appveyor.com/docs/appveyor-yml/">sample yml</a>.</p>
<pre>
<code> # Deploy to GitHub Releases
- provider: GitHub
artifact: /.*\.nupkg/ # upload all NuGet packages to release assets
draft: false
prerelease: false
on:
branch: master # release from master branch only
APPVEYOR_REPO_TAG: true # deploy on tag push only</code>
</pre>
<p>It's hard to see how to specify them in the file. Possibly as <code>tag_name</code>, <code>release_name</code>, etc.? ( It <a href="https://help.appveyor.com/discussions/problems/6566-cannot-deploy-artifacts-to-github">seems</a> that <code>description</code> is the key and not <code>release_description</code> or <code>message</code>. )</p>
<p>A "workaround" might be to use the <a href="https://www.appveyor.com/docs/build-worker-api/">Build Worker API</a>. For <code>Release message</code> it seems that <code>ps: Update-AppveyorBuild -Message ...</code> should work.</p></div>Dejan Budimirtag:help.appveyor.com,2012-11-13:Comment/472769012019-05-21T16:02:13Z2019-05-21T16:02:13ZWildcards for artifacts work in YML but not in UI?<div><p>Yes, a release description is mandatory for deployment to GitHub releases.<br>
<a href="https://www.appveyor.com/docs/deployment/github/#provider-settings">Here</a> is the relevant section in the docs.</p>
<p>Also, if you make any UI settings changes and are unsure how to put them into a config file, you can always go to <code>Export YAML</code> tab of project settings.</p></div>Owen McDonnell