Even though my builds won't start as runners seem to be blocked, it's kinda fascinating to see those in-depth details about the service and how the Gitlab dudes try to find the root cause.
Right? This is EXACTLY what I want to see when there's a service disruption.
A live, in-depth view of who is doing what, any new leads on the issue, multiple teams chiming in with various diagnostic stats, honestly it's really awesome.
I know this can't be expected from most businesses, especially non-open sourced ones, but it's so refreshing to see this instead of the typical "We're working on a potential service disruption" that we normally get.
Comments
Even though my builds won't start as runners seem to be blocked, it's kinda fascinating to see those in-depth details about the service and how the Gitlab dudes try to find the root cause.
Right? This is EXACTLY what I want to see when there's a service disruption.
A live, in-depth view of who is doing what, any new leads on the issue, multiple teams chiming in with various diagnostic stats, honestly it's really awesome.
I know this can't be expected from most businesses, especially non-open sourced ones, but it's so refreshing to see this instead of the typical "We're working on a potential service disruption" that we normally get.
I think it's cool but I'd be totally self-aware and fearful or making the idiot post in the thread for HN to judge :p
It's certainly something I'd be scared of too. It's honestly really brave of them to approach it this way, but I do enjoy watching them work :D