tag:help.appveyor.com,2012-11-13:/discussions/questions/3823-deploying-to-github-releasesAppVeyor: Discussion 2018-08-25T02:17:05Ztag:help.appveyor.com,2012-11-13:Comment/425139172017-05-08T20:21:23Z2017-05-08T20:21:23ZDeploying to GitHub releases<div><p>Cold you please send us <code>artifacts:</code> part of your configuration (or better the whole configuration in YAML)?</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/425139172017-05-09T08:53:38Z2017-05-09T08:53:38ZDeploying to GitHub releases<div><p>Here’s the yaml:</p>
<p>version: 0.1.{build}<br>
pull_requests:<br>
do_not_increment_build_number: true branches:<br>
only: - master image: Visual Studio 2017<br>
configuration: Debug<br>
clone_depth: 1<br>
install:<br>
- cmd: git submodule update --init --recursive build_script:<br>
- ps: >- msbuild source\Tools.MetaDataProcessor\nanoFramework.Tools.MetaDataProcessor.sln /p:Configuration=Release /logger:"C:\Program Files\AppVeyor\BuildAgent\Appveyor.MSBuildLogger.dll"</p>
<pre>
<code>nuget restore source\Tools.BuildTasks\Tools.MSBuildSystem.sln</code>
</pre>
<p>msbuild source\Tools.BuildTasks\Tools.MSBuildSystem.sln /p:Configuration=Release /logger:"C:\Program Files\AppVeyor\BuildAgent\Appveyor.MSBuildLogger.dll"</p>
<pre>
<code>nuget restore source\nanoFramework.Tools.VisualStudio.AppVeyorBuild.sln
msbuild source\nanoFramework.Tools.VisualStudio.AppVeyorBuild.sln /p:Configuration=Release /logger:"C:\Program Files\AppVeyor\BuildAgent\Appveyor.MSBuildLogger.dll"</code>
</pre>
<p>artifacts:<br>
- path: '<strong>\bin\Release*MSBuildSystem*.nupkg' name: MSBuild System Nuget Package - path: '</strong>*.vsix' name: VS extension deploy:<br>
- provider: NuGet api_key: secure: NSRDXbS8tmzOy4wStGuO3yQMKI8Sk10vF8iQtz9ZDXEnHfwnuDdnXbr/Kno3MMvY skip_symbols: true - provider: GitHub tag: v$(appveyor_build_version) release: nanoFramework VS2017 Extension v$(appveyor_build_version) description: add description here auth_token: secure: DNixoFFE+pGlwyhj7McfZoln42vOmj0iY1iNV9zXEr3y0NpXlOIgL8k5ehzlFM1S artifact: /.*.visx/ draft: true prerelease: true force_update: false</p></div>José Simõestag:help.appveyor.com,2012-11-13:Comment/425139172017-05-10T17:40:53Z2017-05-10T17:40:53ZDeploying to GitHub releases<div><p>Sorry late reply and for back and forth, but I see that <a href="https://ci.appveyor.com/api/buildjobs/a61sdxgxxtvebdhl/artifacts/source%2FVisualStudio.Extension%2Fbin%2FRelease%2FnanoFramework.Tools.VS2017.Extension.vsix">your artifact has vsix extension</a>, not zip...<br>
Also I see that artifact <a href="https://github.com/nanoframework/nf-Visual-Studio-extension/releases/download/v0.1.15/nanoFramework.Tools.VS2017.Extension.vsix">is added to GitHub release</a>, also see attached picture.</p>
<p>I probably misunderstand the problem, if yes, please elaborate...</p>
<p>Ilya.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/425139172017-05-10T18:08:06Z2017-05-10T18:08:06ZDeploying to GitHub releases<div><p>I know that it has a vsix extension, the fact is that when I try to download it (by clicking on the URL) it’s downloaded as a ZIP file.<br>
(have you tried that yourself?)</p>
<p>As for the release that you are seeing there on the image, I edited it manually to include the artefact there….. no surprise it’s there.<br>
I have a few others in draft that have no artefact attached.</p></div>José Simõestag:help.appveyor.com,2012-11-13:Comment/425139172017-05-10T19:24:15Z2017-05-10T19:24:15ZDeploying to GitHub releases<div><p>Yes I tried that, see pic. Please try to use artifact deployment name in GitHub deployment provider settings, e.g. <code>artifact: VS extension</code>.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/425139172017-05-11T16:00:37Z2017-05-11T16:00:37ZDeploying to GitHub releases<div><p>To let you know that after:</p>
<p>1) Renaming the artifact so it doesn’t have spaces</p>
<p>2) Using the artefact name instead of the expression (as you suggested)</p>
<p>I now have a draft deployment on GitHub that includes the artefact file.</p>
<p>So I would say that there should be an underlying issue with the artifact naming handling. Or it can’t allow names with spaces or, if those are allowed, then something seems to be broken about that…</p>
<p>De: Ilya Finkelshteyn [mailto:<a href="mailto:tender2+d799f3702a@tenderapp.com">tender2+d799f3702a@tenderapp.com</a>]<br>
Enviada: 10 de maio de 2017 20:24<br>
Para: José Simões <a href="mailto:jose.simoes@eclo.solutions">jose.simoes@eclo.solutions</a><br>
Assunto: Re: Deploying to GitHub releases [Questions #3823]</p></div>José Simõestag:help.appveyor.com,2012-11-13:Comment/425139172017-05-11T17:35:04Z2017-05-11T17:35:04ZDeploying to GitHub releases<div><p>Right, thank you for catching this! Filed <a href="https://github.com/appveyor/ci/issues/1550">this issue</a></p></div>Ilya Finkelshteyn