Home → Problems →

GitHub Releases force_update doesn't work: it says "already exists"

• Edit

acme_pjz

18 Jul, 2019 09:03 AM

I have setup an AppVeyor CI build script for automatic nightly builds and uploads to GitHub release. I'd like to upload the untagged nightly builds to "nightly_build" tag, and overwrite existing files each time. The appveyor.yml is at:

https://github.com/acmepjz/meandmyshadow/blob/master/appveyor.yml

and the relevant part is

deploy:  
  # for nightly build
  - provider: GitHub
    tag: nightly_build
    release: 'Nightly build'
    description: 'Latest nightly build binary. NOTE: The source package is not up-to-date.'
    draft: false
    prerelease: true
    force_update: true
    auth_token:
      secure: 2Tnff9RUodlw+zHXbliNNUg1+HyRMkmABSWsjMfo1NeNJ04fwYUY9BdxRMi2EZZh
    on:
      branch: master
  # for tag build
  - provider: GitHub
    description: 'Release description'
    draft: true
    prerelease: true
    force_update: true
    auth_token:
      secure: 2Tnff9RUodlw+zHXbliNNUg1+HyRMkmABSWsjMfo1NeNJ04fwYUY9BdxRMi2EZZh
    on:
      branch: master
      APPVEYOR_REPO_TAG: true

However, this doesn't work: the log is at:

https://ci.appveyor.com/project/acmepjz/meandmyshadow/builds/260625...

and the last few lines reads:

Deploying using GitHub provider  
Creating "Nightly build" release for repository "acmepjz/meandmyshadow" tag "nightly_build" commit "0d0ae1f3eeb542e43739dcf203a35499776bcb44"...  
Skipped - release with tag "nightly_build" already exists  
Uploading "bin+data-Win32-VS2013-Debug.7z" to release assets...  
Error uploading release asset. Validation Failed: (resource=ReleaseAsset, code=already_exists, field=name)

By the way, the Travis CI can overwrite existing files successfully, see https://github.com/acmepjz/meandmyshadow/blob/master/.travis.yml and the log https://travis-ci.org/acmepjz/meandmyshadow/jobs/559990008.

How do I fix this problem?

1. Support Staff 1 Posted by Owen McDonnell on 18 Jul, 2019 03:00 PM

   

   As an experiment can you try to run a build with the + in the artifact name replaced with a ., i.e. bin.data not bin+data, and let us know the results.

   • Edit

2. 2 Posted by acme_pjz on 18 Jul, 2019 05:13 PM

   

   Thanks! It works after I removed + in the artifact name.

   • Edit

3. Support Staff 3 Posted by Owen McDonnell on 18 Jul, 2019 06:29 PM

   

   Thanks for the update!

   • Edit

4. Owen McDonnell closed this discussion on 18 Jul, 2019 06:29 PM.