2025-07-29: Cannot create an SSH key in staging/deployments blocked
Cannot create an SSH key in staging/deployments blocked (Severity 3 (Medium))
Problem: Clicking "Add new key" or "Delete" within the SSH key and personal access token management UI in GitLab's staging environment had no effect, blocking deployments due to failing end-to-end tests.
Impact: Deployments were blocked as end-to-end tests related to SSH key and personal access token management failed.
Causes: The issue was caused by non-deterministic webpack builds resulting in differences between local and artifact outputs, exacerbated by cache changes in the pipeline.
Response strategy: A precautionary revert merge request was created to address recent cache-related changes, which mitigated the issue and allowed deployments to resume.
This ticket was created to track INC-2945, by incident.io