I am pushing a package from Jenkins using Nuget.exe to Octopus. Even though package has been successfully pushed but still Octopus is not able to find the package during the release. Where can see the uploaded package? It’s not in Library->Package
“C:\ProgramData\chocolatey\bin\NuGet.exe” push “c:\data\Habitat.2.0.0.nupkg” -ApiKey API-DXXXXXXXXXXXXXXXXX -Source http://octopus.demos.hclets.com/nuget/packages?replace=true -Timeout 600
“C:\ProgramData\chocolatey\bin\Octo.exe” create-release --project Habitat --version 1.2.%BUILD_NUMBER% --packageversion 2.0.0 --server http://octopusdeploy.demos.hclets.com --apiKey API-DXXXXXXXXXXXXXX --deployto DEV --releaseNotes “Jenkins build [%BUILD_NUMBER%](http://localhost:8080/job/test/”
The step failed: Activity failed with error ‘The package Habitat.2.0.0 could not be downloaded to the package cache from Octopus Server (built-in) after making 5 attempts over a total of 0s. Make sure the package is pushed to the feed and try the deployment again. For a detailed troubleshooting guide go to http://g.octopushq.com/TroubleshootMissingPackages’.
Thanks for getting in touch.
We notice that in your Jenkins
nuget.exe push command, it’s referencing an
octopus.demos.hclets.com server, whereas in your
create-release step it’s referencing a different server
octopusdeploy.demos.hclets.com. Can you confirm if these are actually resolving to the same server? Is there a reason these are different urls?
nuget.exe push command has executed successfully, you would expect to see it listed in
Library > Packages as you expected. If you click the “Habitat” link on that packages page, you will then be able to see all the versions of that package that have been uploaded.
Let me know how you go.
Thanks fir the prompt response.
Just for the security purpose for this post, i changed the actual server name but in real they both are same. Refer my screenshot.
Package is successfully pushed to octopus but the release can’t find the artifact.
Thanks for clarifying.
If you go to your audit log in Octopus (right after you’ve pushed the package), can you confirm if an audit entry shows up for that action? You should see something like: “Package Habitat version 2.0.0 was pushed to the builtin feed”.
If not, what audit entry does show up when you successfully push the package?
Some possible things to look for…
Does the audit trail show any evidence of your 2.0.0 package being deleted after it’s been uploaded?
Does your package contain a nuspec file, and if so, can you confirm whether the version within this nuspec file could be conflicting here?
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.