Hi, I have the problem in the title, I tried your previous solution but it didn’t work, can you provide a new suggestion, thanks！
Hi @jianglili2015,
Thanks for getting in touch!
I’m assuming this is a Push package to Octopus step that is failing?
The error suggests that it is unable to find a package in the location specified:
2021-01-11T09:59:08.7405232Z Package file not found: C:\agent05_work\13\s\CSITest\obj\octopacked\CSITest.1.0.7833.nupkg
Are you able to confirm that a package with that name, version and extension exists in that location?
Regards,
Paul
Thanks for your prompt reply, there is no nupkg package under the specified path, but I don’t know why the creation failed
If you review the logs generated in the earlier step that creates the package, does it indicate any failures? Is it perhaps creating the package in a different location?
2021-01-11T09:59:03.5320137Z ##[section]Starting: Push Packages to Octopus
2021-01-11T09:59:03.5331107Z ==============================================================================
2021-01-11T09:59:03.5331790Z Task : Push Package(s) to Octopus
2021-01-11T09:59:03.5332321Z Description : Push your NuGet or Zip package to your Octopus Deploy Server
2021-01-11T09:59:03.5332776Z Version : 4.1.463
2021-01-11T09:59:03.5333142Z Author : Octopus Deploy
2021-01-11T09:59:03.5333722Z Help : Version: 4.1.463. More Information
2021-01-11T09:59:03.5334405Z ==============================================================================
2021-01-11T09:59:06.2937045Z fd8b6e75-645d-4834-946b-b2170b5b40df exists true
2021-01-11T09:59:06.3100715Z Attempting to contact https://g.octopushq.com to find Octopus CLI tool version latest
2021-01-11T09:59:06.3353124Z (node:24544) Warning: Use Cipheriv for counter mode of aes-256-ctr
2021-01-11T09:59:06.3354427Z (node:24544) Warning: Use Cipheriv for counter mode of aes-256-ctr
2021-01-11T09:59:06.3355177Z (node:24544) Warning: Use Cipheriv for counter mode of aes-256-ctr
2021-01-11T09:59:06.3355744Z (node:24544) Warning: Use Cipheriv for counter mode of aes-256-ctr
2021-01-11T09:59:06.3356315Z (node:24544) Warning: Use Cipheriv for counter mode of aes-256-ctr
2021-01-11T09:59:06.3356868Z (node:24544) Warning: Use Cipheriv for counter mode of aes-256-ctr
2021-01-11T09:59:06.3357431Z (node:24544) Warning: Use Cipheriv for counter mode of aes-256-ctr
2021-01-11T09:59:06.3358056Z (node:24544) Warning: Use Cipheriv for counter mode of aes-256-ctr
2021-01-11T09:59:06.3358627Z (node:24544) Warning: Use Cipheriv for counter mode of aes-256-ctr
2021-01-11T09:59:06.3359203Z (node:24544) Warning: Use Cipheriv for counter mode of aes-256-ctr
2021-01-11T09:59:07.3675592Z Checking local tool cache
2021-01-11T09:59:07.3772755Z Found tool in cache: octo 7.4.4 x64
…
Ok, sorry for not being clear.
The Push Packages to Octopus step does not create a package, it is merely looking in the directory you provide for the package you specify, and will then attempt to upload this to Octopus.
It is failing because the package does not exist in that location.
You should have a step earlier in your build process that creates this package, perhaps a Package Application for Octopus step?
If so, you need to check the log for that step and ensure that it is successful, and that it is placing the packaged application in the same location e.g. C:\agent05_work\13\s\CSITest\obj\octopacked\
Thanks, I actually referenced this link:.
There is no mention of the steps you mentioned here. I’ll check again, thanks!
It looks like that guide uses Octopack to create the package, instead of the standalone package step.
e.g.
If that is what you have configured, then it would be the Build Solution step logs that you should check to see if it successfully creating the package in the correct location.
Thanks, I’m going to check the logs
It’s working now. Thank you very much for your help.
1 Like
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.