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

Improve the error handling for database schema upgrades #4812

Closed
michaelnoonan opened this issue Aug 15, 2018 · 2 comments
Closed

Improve the error handling for database schema upgrades #4812

michaelnoonan opened this issue Aug 15, 2018 · 2 comments
Assignees
Labels
area/hosted kind/enhancement This issue represents an enhancement we are committed to adding to Octopus as some time
Milestone

Comments

@michaelnoonan
Copy link
Contributor

When supporting some customers, including those hosted by Octopus Cloud, it became evident some additional comfort could be offered when we have problems upgrading the database schema. This can be quite discomforting for customers, and we should be very clear about:

  1. The state of their database
  2. What they can do to get back up and running
  3. How to get help if they need it
@michaelnoonan michaelnoonan added kind/enhancement This issue represents an enhancement we are committed to adding to Octopus as some time area/hosted labels Aug 15, 2018
@michaelnoonan michaelnoonan self-assigned this Aug 15, 2018
@octoreleasebot octoreleasebot added this to the 2018.8.3 milestone Sep 5, 2018
@octoreleasebot
Copy link

Release Note: Improved messaging for different failure scenarios when running the database schema upgrades to be clearer about the state of their database, what they can do to get back up and running, and how to get help if they need it

@lock
Copy link

lock bot commented Dec 5, 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 Dec 5, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/hosted kind/enhancement This issue represents an enhancement we are committed to adding to Octopus as some time
Projects
None yet
Development

No branches or pull requests

2 participants