Thanks for getting in touch! I think the problem here is the expectation. You cannot push packages directly to Tentacles. You need to push them to a feed or repository (like our internal repository) when the release is deployed to a Tentacle we will then move the packages around. You can change the settings in the project to always download the package directly from the Tentacle, but if you are using the Octopus internal repository then we will still stream it from the Octopus server.
To make your nuget.exe push command work you will need to provide the Octopus server /nuget/packages endpoint as the source.
Please let me know if you have any futher questions or I can expand apon anything I have said.
Great to hear. To answer your question is this was now handled by this line: " /p:OctoPackPublishPackageToHttp=http://localhost/nuget/packages" ? Yes that is correct. Octopack itself will also use nuget.exe to send the built packages directly to a NuGet feed or repository, so you do not need another step to push the packages if you are using that.
There are also videos (https://octopus.com/videos). Once you have configured the project and have tested the deployment successfully you can also add a create/deploy release step to Jenkins for after the build succeeds, but you do need to create and configure your project and step/s first.
Please let me know if you have any further questions or run into any more issues.