Impact
An unknown number of groups encountered issues while cloning repositories via SSH. The issue started on UTC-5 24-07-16 14:43 and was proactively discovered 1.9 hours (TTD) later by a staff member who reported through our help desk [1] that cloning errors were occurring. The problem was resolved in 1.2 hours (TTF), resulting in a total window of exposure of 3.1 hours (WOE) [2].
Cause
Discontinuing the use of a function that parsed SSH URLs and removed the ssh:// prefix led to the inability to clone repositories properly [3].
Solution
Reverting the merge request that caused the problem was necessary to restore the functionality of repository cloning via SSH [4].
Conclusion
The lack of testing and failure to test changes locally led to the problem. The team will implement the necessary tests to prevent similar issues before making changes. INCOMPLETE_PERSPECTIVE < MISSING_TEST