Home → Questions →

Artifacts

• Edit

Steven Thuriot

16 Oct, 2013 07:39 AM

Hi Feodor,

A few of the projects I have building on AppVeyor have reached the maturity where I can start distributing them via NuGet. I've edited my builds so nupkg's are created automatically. I've read through the build log and verified that this is working properly. (As a side note, the "BuildPackages" parameter nuget's package restore feature accepts seems to work just fine when using msbuild, but not when "visual studio sln file" is selected).

The issue I'm having, however, is that I can't find an easy way to mark them as artifacts. For now, rather than automatically push them to nuget.org, I'd rather have appveyor build and create my packages and attach them as artifacts. When the actual packages pass some of my tests, I would like to manually push them to nuget.org. Eventually, I would like to start pushing them automatically, but having them as artifacts are still a nice thing to have.

Since the nuget packages have the version number in their file name, there doesn't seem to be an easy way to include them as artifacts. When i try to use an asterisk as wildcard, I receive the message that there are illegal characters in the path. Are wildcards indeed not supported, or am I doing something wrong? It would be nice to just add a wildcard, e.g. "**/*.nupkg" to just include all nupkg's as artifacts.

Is there any way I can get arround this issue?

Thanks in advance,
-Steven Thuriot

1. Support Staff 1 Posted by Feodor Fitsner on 16 Oct, 2013 04:33 PM

   

   Hi Steven,

   It seems I have an answer to your question! :)

   Take a look at "Pushing artifacts to build storage" section in this guide: http://www.appveyor.com/docs/custom-build-scripts.

   In two words, you should copy NuGet packages to %OutFolder% folder for AppVeyor to pickup them.

   Let me know if it works for you. I should probably have published that as a separate article.

   -Feodor

   • Edit

2. 2 Posted by Steven Thuriot on 17 Oct, 2013 06:51 AM

   

   Hey Feodor,

   That is indeed exactly what I need! I had read through the documentation, so I can't believe I missed that part.

   One more question, though. Is there any way for me to use these variables when using appveyor's msbuild/vs sln setting?

   If so, this specific issue could easily be solved by adding "PackageOutputDir" with $(OutFolder) as a replacement in the build settings tab. If not, I'll create a custom build script later today and post the results!

   Thanks,
   -Steven

   • Edit

3. Support Staff 3 Posted by Feodor Fitsner on 17 Oct, 2013 05:34 PM

   

   %OutFolder% is not set for MSBuild scenarios, but I will add that into the next update. Though out folder is always created and checked during the packaging process. MSBuild runs in src folder, so out could be defined like ..\out. Give it a try.

   • Edit

4. 4 Posted by Steven Thuriot on 17 Oct, 2013 05:56 PM

   

   That worked perfectly! All my packages are built and added as artifacts!
   Couldn't be happier :) Thanks!

   • Edit

5. Steven Thuriot closed this discussion on 17 Oct, 2013 05:56 PM.