Error packaging artifacts - The remote server returned an error: (500) Internal Server Error
I am receiving a (500) Internal Server Error when packaging the artifacts of an otherwise successful build. There are four artifacts to be uploaded and it is always the last artifact (a symbols package) that fails to upload.
[00:06:58] Packaging artifacts...
[00:06:58] OK
[00:06:59] Uploading artifact artifacts\packages\Release\Autofac.4.0.0-alpha2-37.nupkg (361.9 KB)...
[00:07:00] OK
[00:07:00] Uploading artifact artifacts\packages\Release\Autofac.4.0.0-alpha2-37.symbols.nupkg (1010.2 KB)...
[00:07:01] OK
[00:07:01] Uploading artifact artifacts\packages\Release\Autofac.Dnx.4.0.0-alpha2-37.nupkg (247.8 KB)...
[00:07:01] The remote server returned an error: (500) Internal Server Error.
You can see at the link below the first three packages uploaded correctly. The missing symbol package is Autofac.Dnx.4.0.0-alpha2-37.symbols.nupkg and was built successfully above.
https://ci.appveyor.com/project/Autofac/autofac/build/4.0.0.37/arti...
I would appreciate any suggestions on how to debug this error.
- log.txt 134 KB
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
Support Staff 1 Posted by Feodor Fitsner on May 03, 2015 @ 05:10 PM
Thanks for reporting that! Working on that right now.
- Feodor
Support Staff 2 Posted by Feodor Fitsner on May 03, 2015 @ 07:43 PM
It's been fixed. Give it another try.
3 Posted by alexmg on May 04, 2015 @ 01:11 PM
Thank you very much for the quick response! I gave the build another go and the artifacts were uploaded correctly. What ended up being the problem? I ask only out of general interest.
The final step to push the symbol packages did fail though. I suspect this might be a problem with symbolsource.org from what is present in the logs.
Is this an error you have seen before with DNX packages?
Support Staff 4 Posted by Feodor Fitsner on May 04, 2015 @ 04:47 PM
Internally AppVeyor uses
NuGet.Core
library to work with NuGet packages and it wasn't the latest version which is currently 2.8.5 with "frameworks" enum having DNX.Now, when it's fixed on our side seems like SymbolSource still has this issue. I've dropped them a message.
5 Posted by alexmg on May 05, 2015 @ 01:55 PM
You guys are awesome! Thanks for the great support. It is appreciated.
Ilya Finkelshteyn closed this discussion on Aug 25, 2018 @ 01:56 AM.