Home → Problems →

Issue with deploying artifacts

• Edit

Eric J. Smith

03 Mar, 2015 03:25 AM

I have a project that builds a bunch of nuget packages and I'm trying to get them publishing to myget, but I am getting this error:

No artifacts were uploaded. Make sure you have specified correct artifacts filter.

I see all my artifacts on the build. What am I missing?

1. Support Staff 1 Posted by Feodor Fitsner on 03 Mar, 2015 03:31 AM

   

   Do you have artifact setting set for NuGet deployment provider?

   • Edit

2. 2 Posted by Eric J. Smith on 03 Mar, 2015 03:40 AM

   

   I am using the Environment provider.

   • Edit

3. 3 Posted by Eric J. Smith on 03 Mar, 2015 03:44 AM

   

   artifacts:
     - path: Build\Deploy\packages\*.nupkg
       name: packages

   deploy:
     - provider: Environment
       name: MyGet
       artifact: packages

   • Edit

4. Support Staff 4 Posted by Feodor Fitsner on 03 Mar, 2015 03:49 AM

   

   artifact defined in appveyor.yml is not applied to "Environment" provider. Do you have "Artifact" defined on "MyGet" environment settings?

   • Edit

5. 5 Posted by Eric J. Smith on 03 Mar, 2015 04:18 AM

   

   Ugh. So the problem was that I didn't read the environment settings very well and pasted my api key into the artifacts field. But now the problem seems to be that you aren't using my api key when publishing symbols. Getting this message:

   nuget push "C:\Resources\directory\414464e4bda24612b1f57a8e0b52a7f6.Appveyor.Worker.Temp\mdiutpno\Build\Deploy\packages\Exceptionless.2.0.1229.symbols.nupkg" -Source https://nuget.symbolsource.org/MyGet/exceptionless
   Pushing Exceptionless 2.0.1229 to 'https://nuget.symbolsource.org/MyGet/exceptionless'...
   ERROR: Failed to process request. 'User authentication failure: The request failed with HTTP status 503: Service Unavailable.. See http://www.symbolsource.org/Public/Home/Help for possible reasons. Fiddler may help diagnosing this error if your client discards attached detailed information.'.
   ERROR: The remote server returned an error: (418) User authentication failure: The request failed with HTTP status 503: Service Unavailable.. See http://www.symbolsource.org/Public/Home/Help for possible reasons. Fiddler may help diagnosing this error if your client discards attached detailed information...

   • Edit

6. Support Staff 6 Posted by Feodor Fitsner on 03 Mar, 2015 04:26 AM

   

   -ApiKey parameter is always added to push command - it's just not echoed to the log.

   To my mind 503 (service unavailable) means something bad, but not like auth problem.

   • Edit

7. Support Staff 7 Posted by Feodor Fitsner on 03 Mar, 2015 04:27 AM

   

   Change build deployment to a script and try using the same nuget push command from there to see if that works. Do not forget to put your API key to environment variable to avoid printing it to the build log.

   • Edit

8. Support Staff 8 Posted by Feodor Fitsner on 03 Mar, 2015 04:32 AM

   

   ...or download that NuGet package and try running the same command locally but with -ApiKey added.

   • Edit

9. 9 Posted by Eric J. Smith on 03 Mar, 2015 04:53 AM

   

   Looks like they are down. Sorry for the confusion.

   https://www.symbolsource.org/Public/Status

   • Edit

10. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:54 AM.