Uploading artifacts to an existing Github release?

tino's Avatar


15 Feb, 2019 04:17 PM

I'd like to upload artifacts from a tag asynchronously to a previously manually created Github release.

In trying to set that up I encountered the following issue:

1. Since the deployment should be asynchronous, I figured the environment needs to be configured via the Web UI
  a) Problem here is that the Github token can't be given in its encrypted form. Appveyor will complain about access issues to the repo.
  b) Also how can a list of artifacts be defined in the Web UI?
  c) Lastly how can I configure that the name and description and other existing assets of the Github release should not be changed?
2. Or should I configure the deploy environment via the config file?
  a) If so, how can I tell appveyor not to automatically deploy something after a build?


  1. Support Staff 1 Posted by Ilya Finkelshte... on 16 Feb, 2019 12:30 AM

    Ilya Finkelshteyn's Avatar
    • Secure variables are used in YAML file where it is unsafe to keep secrets in clear text. In deployment environment settings they should be set as is. It is safe as no authorized people should be allowed to open deployment environment settings. In AppVeyor database deployment environment configuration is stored in encrypted form.
    • Please check Artifacts to deploy section in the documentation.
    • Existing assets should be preserved if you did not check Update release details if exists checkbox.

    Please let us know if this helps. If you hit some specific issues, please provide a screenshot with deployment environment configurations settings (feel free to delete token from it) and steps to reproduce.

  2. Ilya Finkelshteyn closed this discussion on 18 Apr, 2019 09:00 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac