release assets: 404 - Not Found

Mike-E's Avatar

Mike-E

07 Jul, 2020 07:49 AM

Greetings Team AppVeyor!

Everything has been running pretty smoothly for us using your platform. Thank you for all the diligent work over there.

However, I did just now try to build a release and am getting an obscure error that I am not sure what is causing it. It appears to be occurring during the GitHub Release. You can see the build here:

https://ci.appveyor.com/project/ExtendedXmlSerializer/extendedxmlserializer/builds/33949072

Here is the last output:

```
Deploying using GitHub provider
Creating "ExtendedXmlSerializer v3.2.2" release for repository "ExtendedXmlSerializer/home" tag "v3.2.2" commit "4efe913545c1e6200a02d1978e933af6b2617416"...Skipped - release with tag "v3.2.2" already exists
Error creating GitHub release: Error reading repository 'ExtendedXmlSerializer/home' release assets: 404 - Not Found
```
Is this a known issue, perhaps? Thanks again for your work out there and any assistance you can provide.

  1. 1 Posted by Mike-E on 07 Jul, 2020 07:53 AM

    Mike-E's Avatar

    Ah FWIW/BTW all scripts used are found here:
    https://github.com/ExtendedXmlSerializer/home/tree/master/.build

  2. 2 Posted by Mike-E on 07 Jul, 2020 02:15 PM

    Mike-E's Avatar

    So for some further context, what we've been doing is:

    1. Create a release via NextRelease.io, which creates a new Release in our repository: https://github.com/ExtendedXmlSerializer/home/releases/tag/v3.2.2
    2. This, in turn, runs a build from GitHub Actions, which monitors `release.published` event: https://github.com/ExtendedXmlSerializer/home/actions/runs/160303178
    3. The build from GitHub actions calls into AppVeyor to fire off its build: https://github.com/ExtendedXmlSerializer/home/runs/844563567?check_suite_focus=true
    4. In the AppVeyor GitHub release, the nupkg is created and then is attached to the release created in the first step as an attachment. Example of this in the previous release: https://github.com/ExtendedXmlSerializer/home/releases/tag/v3.2.1

    This has been working well without any exceptions until today.

  3. Support Staff 3 Posted by Feodor Fitsner on 07 Jul, 2020 02:27 PM

    Feodor Fitsner's Avatar

    Hi Mike,

    It could be API_GITHUB_TOKEN used to publish GitHub release is not valid anymore. Could you try using a new token to see if that helps?

  4. 4 Posted by Mike-E on 07 Jul, 2020 03:06 PM

    Mike-E's Avatar

    Thank you for your reply, Feodor. Are you referencing this setting here?

    https://github.com/ExtendedXmlSerializer/home/blob/master/.build/appveyor.yml#L145

    I looked in my personal tokens and see that the token was used in the last week, so it appears to be in good standing:
    https://i.imgur.com/cYss6Kn.png

    Are we sure a 404 error message would be the result of an invalid PAT? Part of the reason I ask is that I am under the impression that PATs never go invalid. They are as good for as long as they exist. Please let me know if I have something fundamentally misunderstood here.

  5. 5 Posted by Mike-E on 07 Jul, 2020 03:15 PM

    Mike-E's Avatar

    Well after seeing your reply and that it wasn't anything non-obvious, I decided to delete all 3.2.2 builds and rerun the GitHub Actions workflow above (which kicks off a new build). This one went through. So, who knows what that was all about!

    Anyways, at least it's given me a chance to thank you all again for creating such a cool service. :)

  6. Mike-E closed this discussion on 07 Jul, 2020 03:15 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