Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Package Acquisition will fail if there is a problem reading packages in the cache #4123

Closed
droyad opened this issue Dec 22, 2017 · 2 comments
Closed

Package Acquisition will fail if there is a problem reading packages in the cache #4123

droyad opened this issue Dec 22, 2017 · 2 comments
Assignees
@droyad
Labels
kind/bug This issue represents a verified problem we are committed to solving
Milestone
2018.1.4

Comments

@droyad
Copy link
Contributor

droyad commented Dec 22, 2017 •
edited

Error reading from the Package Cache should be ignored as it is just an optimisation.

https://help.octopusdeploy.com/discussions/problems/65974
@droyad droyad self-assigned this Dec 22, 2017
@droyad droyad added area/execution kind/bug This issue represents a verified problem we are committed to solving labels Dec 22, 2017
@droyad droyad closed this as completed Dec 22, 2017
@octoreleasebot octoreleasebot added this to the 4.1.6 milestone Dec 22, 2017
@octoreleasebot
Copy link

octoreleasebot commented Dec 22, 2017 •
edited by hnrkndrssn

Release Note: Package Acquisition no longer fails with a Object reference not set error when multiple deployments attempt to access the package cache

@droyad droyad modified the milestones: 4.1.6, 2018.1.4 Feb 1, 2018
@lock
Copy link

lock bot commented Nov 23, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Nov 23, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@droyad droyad

Labels
kind/bug This issue represents a verified problem we are committed to solving
Projects
None yet
Milestone
2018.1.4
Development

No branches or pull requests
2 participants
@droyad @octoreleasebot