Can you guys please fix the following UI glitch. It’s been there for months and multiple times it has caused MASSIVE production issues:
Summary of issue:
- click deploy from latest commit on Service A.
- kicks off some background process that takes seconds before service A actually marked as deploying.
- Immediately back to overview page, click another service (Service B).
- Click into Service B. Service B page loads
- Then, once deploy from service A starts (which 100% of the time is after clicking into service B unless you wait an annoying amount of time on Service Page A), page just re-renders (lol render) and Service B page transforms into Service A page
- This is the “glitch”
Consequences:
- (less important) Annoying. Workarounds are all kind of frustrating:
- I need to go back to overview page again and re-click into Service B after the re-render
- Wait for what can be like 5-8s for Service A to begin deploying which I always forget to do because the deploy button just works so I feel no need to wait..
- (more important) Massive Potential for Deployment Failures:
- I’ll not notice the page re-render because my services have similar names and think I’m deploying Service B when in fact I’m just re-clicking deploy on Service A
- If I don’t remember to double check in the overview page, Service B will have never been deployed.
- NUMEROUS TIMES (probably > 50) this has caused an issue where an engineer thought service B was deployed when in fact it wasn’t. Sometimes this is caught in seconds / minutes, sometimes it takes days to notice if the dev doesn’t double check