Can't Deploy to GitHub Releases or NuGet Environments

splatteredbits's Avatar

splatteredbits

22 Nov, 2021 08:01 PM

I've got a build that generates two artifacts: a .zip file which should get published to GitHub and a .nupkg which should get published to the PowerShell Gallery. Here's my YAML:


skip_tags: true

skip_branch_with_pr: true

image:
- Visual Studio 2022

artifacts:
- path: .output\*.nupkg
  name: PowerShellGallery
- path: .output\*.zip
  name: GitHub
- path: .output\*.xml

build:
  verbosity: minimal

build_script:
- ps: .\build.ps1

Whenever I deploy to GitHub or PowerShell Gallery however, no artifacts are published. I've attached screenshots of my environment settings (API keys removed).

What do I do to get this to work? I'd like to be able to re-use the same environments to deploy multiple projects.

  1. 1 Posted by splatteredbits on 22 Nov, 2021 08:03 PM

    splatteredbits's Avatar

    I've attached a screenshot of the artifacts from a recent build.

  2. Support Staff 2 Posted by Feodor Fitsner on 22 Nov, 2021 08:29 PM

    Feodor Fitsner's Avatar

    The issue I see artifacts were uploaded without "deploymet name" (PowerShellGallery and GitHub). Did you run the build with updated appveyor.yml? Can you drop a link to it?

  3. 3 Posted by splatteredbits on 22 Nov, 2021 08:30 PM

    splatteredbits's Avatar

    Figured it out. Had a global artifacts rule:

    artifacts:
    - path: .output\*
    

    That was grabbing the artifacts before my local YAML was. This is strange behavior. I would have expected each artifact path to upload anything matching, not anything matching except what was uploaded before.

  4. Support Staff 4 Posted by Feodor Fitsner on 22 Nov, 2021 11:14 PM

    Feodor Fitsner's Avatar

    OK, thanks for the update!

  5. Feodor Fitsner closed this discussion on 23 Jan, 2022 09:01 PM.

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

Keyboard shortcuts

Generic

? 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