Hi
we have a scenario where the build system has created a release with the artifacts on an external Nuget repository. Between the point of the release being created and deployment initiated, some (not all) of the packages in the release have been cleaned up (deleted) from the Nuget repo.
Octopus deploy knows that these packages are missing as it shows ‘The Resource xxxx version xxxx was not found’.
However, Octopus does not stop or warn the user on deployment that the packages are missing. Is there an option to enable this warning ?
Regards
Owen
Hi Owen,
Thanks for reaching out!
However, Octopus does not stop or warn the user on deployment that the packages are missing. Is there an option to enable this warning ?
There’s no warning or such thing for that. Octopus will attempt to fetch the packages during the deployment, so only at that time you can find out if they are missing or not.
Between the point of the release being created and deployment initiated, some (not all) of the packages in the release have been cleaned up (deleted) from the Nuget repo.
Why are the packages being deleted from your repo between the release creation and the deployment? Is this a normal thing in your deployment process?
Thanks,
Daniel
Notice:
This issue has been closed due to inactivity. If you encounter the same or a similar issue and require help, please open a new discussion (if we asked for logs or extra details in this thread, consider including them in the new thread). If you are the creator of this thread and believe it should not be closed let us know via our support email.