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.

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

Show a better error in UI when package release notes can't be found on release page #5487

Closed
hnrkndrssn opened this issue Apr 17, 2019 · 2 comments

Comments

@hnrkndrssn
Copy link

commented Apr 17, 2019

Prerequisites

  • I have verified the problem exists in the latest version
  • I have searched open and closed issues to make sure it isn't already reported
  • I have written a descriptive issue title
  • I have linked the original source of this report
  • I have tagged the issue appropriately (area/*, kind/bug, tag/regression?)

The bug

If we are unable to retrieve release notes for a package, because that package doesn't exist in the package feed, we return a less than helpful Object reference not set to an instance of an object. error.

What I expected to happen

I should see an error letting me know that the package could not be found in the feed.

Steps to reproduce

  1. Create a project with a Deploy package step that references a package that doesn't exist in the built-in repository.
  2. Create a release, manually specify a package version and save the release
  3. See error

Screen capture

image

Log exerpt

Affected versions

Octopus Server: Confirmed on latest build

Workarounds

N/A

Links

Release showing the issue (Octopus staff access only): https://master.octopushq.com/app#/Spaces-1/projects/jess/releases/0.123.397

@octoreleasebot

This comment has been minimized.

Copy link

commented Apr 17, 2019

Release Note: Return a more helpful error message on the release page if a package / version combination cannot be found in the built-in repository

@lock

This comment has been minimized.

Copy link

commented Jul 16, 2019

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 Jul 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
2 participants
You can’t perform that action at this time.