Allow Octopack to not publish packages as artifacts to keep them out of TC feed

[vanessalove]

Octopack currently when embedded in TC publishes the packages as artifacts so they show in the TeamCity feed. We need a variable to stop this behaviour.

Source: http://help.octopusdeploy.com/discussions/problems/25199

[bettiolo]

We really need this, otherwise our Internal TeamCity NuGet feed gets polluted with build packages.

[stevenkuhn]

I posted a reply to the help thread regarding some potential workarounds until it's possible to configure the location of the output directory used by OctoPack.

1. Remove the output directory from the artifact path. Simplest solution, but may not be feasible. By removing the output directory not only do you prevent the NuGet package from showing up as an artifact, but you also prevent any other files from being an artifact. If you need other files to be included as artifacts, this workaround will not work.
2. Create a new Command Line or Powershell build step to move the NuGet package out of the original output directory. It would run after the original build step and would prevent the package from showing up as an artifact.
3. Change the artifact path to zip up the output directory. TeamCity will not add any NuGet packages to its internal feed if the package is in a zip file artifact. If your Artifact path specification is bin\Release\ => then change it to bin\Release => artifacts.zip where artifacts.zip is any filename with a .zip extension. TeamCity will automatically take all of the files in bin\Release and add them to a new file called artifacts.zip. If you need those artifacts in another build configuration (as an artifact dependency), your artifact rule for that dependency would be artifacts.zip!** => artifacts. That would extract all the files from the zip file and place them into an artifacts folder readily available for your new build configuration.

I've had success with the third workaround. In cases where I only needed the Octopus Deploy NuGet packages from several projects in one build, I've just set the Artifact path in TeamCity to something like this:

MyProject\bin\Release\MyProject.%build.number%.nupkg => nuget.zip
MyOtherProject\bin\Release\MyOtherProject.%build.number%.nupkg => nuget.zip

That adds all of my Octopus Deploy NuGet packages to a single nuget.zip file without TeamCity adding them to its internal feed.

Hope that helps!
Steven