Error handling for "What's New"
Problem to solve
We added a first try at a "what's new" feature showcasing content in the current version of GitLab. We should account for airgapped/offline instances and cases where about.gitlab.com
is down or otherwise unreachable.
See https://gitlab.slack.com/archives/C0NFPSFA8/p1548366492560200 for additional context.
Target audience
Anyone using GitLab.
Proposal
- Add error handling to the call to
about.gitlab.com
. Prevent 500s whenabout.gitlab.com
is not reachable. Hide theWhat's new
link in this case.
What does success look like, and how can we measure that?
- Accessing "what's new" should be possible for an offline instance.
- Reachability of
about.gitlab.com
should have no functional impact on the instance.
Links / references
Edited by Jeremy Watson (ex-GitLab)