Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
If a database upgrade script is long running and silent we should log a "still working" message every so often #5094
We have had reports over the years where customers would upgrade their Octopus Server, and a database upgrade script would take a long time to run. This is OK if the script reports progress in a way the user knows something is happening.
However there are cases where TSQL is the best fit, and not all of those can report progress easily.
From a user's point of view it would be really nice if:
Here's a mockup using a 1s interval. Perhaps 1m is a better default? :)