tag:help.appveyor.com,2012-11-13:/discussions/problems/1753-upload-artifact-to-existing-github-releaseAppVeyor: Discussion 2018-10-19T08:17:04Ztag:help.appveyor.com,2012-11-13:Comment/362517762015-03-11T06:49:52Z2015-03-11T06:49:53ZUpload artifact to existing github release<div><p>I work with another CIs for on of my projects so whenever a tag
is pushed, it might happen that the other CI is done building and
uploading its artifact first and as a result appveyor does not
upload anything.</p>
<p>It complains that "Release "" already exists.", which is
correct, but on the other hand should not be a problem. User that
use the github interface to publish new releases and expect
appveyor to build their release for them will also run into this
problem, by the way. Github releases always trigger a tag creation,
but appveyor will be unable to upload its artifacts because of the
same error.</p>
<p>Is there any way around this limitation. I would like to avoid
writing my own deployment script. Thank you in advance for your
support.</p></div>Florian Franzentag:help.appveyor.com,2012-11-13:Comment/362517762015-03-11T20:10:16Z2015-03-11T20:10:16ZUpload artifact to existing github release<div><p>Hi Florian,</p>
<p>Actually, that is not a complaint but a warning and AppVeyor
goes ahead and upload artifacts to the existing release. The
process is not terminated if release already exists.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/362517762015-03-12T15:53:37Z2015-03-12T15:53:38ZUpload artifact to existing github release<div><p>Hi Feodor.</p>
<p>Ok, I understand. I thought the "No artifacts were published.
Make sure you have specified correct artifacts filter." was related
to the message.</p>
<p>I checked the config again and thought the problem was that I
should have used "artifact: neuroscope-.*-win64.exe" instead of
"artifact: neuroscope-*-win64.exe", but still no luck. The
documentation states after all that I have to use a proper regular
expression.</p>
<p>It still misses to upload the generated file
"C:/projects/neuroscope/neuroscope-2.0.0-win64.exe".</p>
<p>Any ideas on how to get the deployment working? Do I have to
specify the absolute path?</p>
<p>Thanks a lot,<br>
Florian</p></div>Florian Franzentag:help.appveyor.com,2012-11-13:Comment/362517762015-03-12T16:52:08Z2015-03-12T16:52:08ZUpload artifact to existing github release<div><p>Surround regex with <code>//</code>:</p>
<pre>
<code>artifact: /neuroscope-.*-win64\.exe/</code>
</pre></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/362517762015-03-16T12:20:05Z2015-03-16T12:20:06ZUpload artifact to existing github release<div><p>I did that....<br>
<a href=
"https://github.com/neurosuite/neuroscope/blob/master/.appveyor.yml">
https://github.com/neurosuite/neuroscope/blob/master/.appveyor.yml</a></p>
<p>... but it still does not upload anything: <a href=
"https://ci.appveyor.com/project/FloFra/neuroscope/build/v2.0.0-master-9">
https://ci.appveyor.com/project/FloFra/neuroscope/build/v2.0.0-mast...</a></p>
<p>I ran the exact same code on my Windows build machine and the
file I filter for is there, so I can only assume the deployment
script is to blame. I am out of ideas. Any hints what I might be
doing wrong?</p>
<p>Thank you in advance,<br>
Florian</p></div>Florian Franzentag:help.appveyor.com,2012-11-13:Comment/362517762015-03-16T12:23:12Z2015-03-16T12:23:12ZUpload artifact to existing github release<div><p>The build has no artifacts: <a href=
"https://ci.appveyor.com/project/FloFra/neuroscope/build/v2.0.0-master-9/artifacts">
https://ci.appveyor.com/project/FloFra/neuroscope/build/v2.0.0-mast...</a></p>
<p>You should package/push artifacts and then deploy them: <a href=
"http://www.appveyor.com/docs/packaging-artifacts">http://www.appveyor.com/docs/packaging-artifacts</a></p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/362517762015-03-18T13:44:18Z2015-03-18T13:44:21ZUpload artifact to existing github release<div><p>Oh, I see. Should have read the documentation more carefully. I
feel kind of dumb now. ;-)</p>
<p>Thanks a lot for the great support. Everything works as expected
now.</p></div>Florian Franzen