OctoPack vs nuget.exe - Which one is faster? [closed]

Question

I'm currently trying to speed up our Team City builds.

After a successful msbuild step, we package up our solution using nuget.exe and then publish to a nuget feed in order to allow Octopus Deploy to do it's thing.

I'm at the stage now where the nuget package step takes ~4 minutes (we have a large amount of assets) and the nuget publish step takes ~30 seconds. This takes up about 75% of our overall build time, so any time I can shave off this would be good progress.

I was wondering if anyone has any experience with both OctoPack and nuget.exe, and are in a position to tell me if either of the two methods are quicker than the other? No hard numbers needed, just anecdotal evidence is enough.

Answer 1

The Octopack uses NuGet.exe so you can't really contrast them. You can view the OctoPack source code on GitHub to see how it works. I would point out that using a different version of NuGet.exe might make a difference. I have no evidence to support this but it's a shot in the dark.

Within the OctoPack, you can pass a parameter (NuGetExePath) to specify the specifc NuGet.exe you want to use. See this targets file within the Octopack for more information on parameters you can pass to OctoPack.