Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2/23/2024 Build and Deploy Breakdown Postmortem #17339

Closed
4 of 8 tasks
gracekretschmer-metrostar opened this issue Feb 26, 2024 · 1 comment · Fixed by #17386
Closed
4 of 8 tasks

2/23/2024 Build and Deploy Breakdown Postmortem #17339

gracekretschmer-metrostar opened this issue Feb 26, 2024 · 1 comment · Fixed by #17386
Assignees
Labels
CMS Team CMS Product team that manages both editor exp and devops Epic Issue type

Comments

@gracekretschmer-metrostar
Copy link

gracekretschmer-metrostar commented Feb 26, 2024

Background

On 2/23/2024, Christian Burk (Public Facilities Drupal Engineer) notified the CMS team that staging.cms.va.gov did not operate as expected and displayed an error message (see below). Soon after, the #cms-notifications channel began displaying error messages about the deploy process for BRD.

User Story or Problem Statement

The root of the staging.cms.va.gov and deploy errors need to be fully understood to be able to create a solution that will full address the problems and give the CMS team an understanding of more sustainable long term solutions.

Affected users and stakeholders

  • Developers of the public websites product team
  • Developers of the facilities product team
  • Developers of the cms team

Hypothesis

The errors were caused during a failure in the build process due to a missing token from Gitlab. Creating a login and token for Gitlab will resolve the errors from both staging.cms.va.gov and BRD.

Acceptance Criteria

  • The root cause of why staging.cms.va.gov was displaying the error message and BRD was producing errors is fully understood.
  • A solution is implemented that resolves the current errors for both staging.cms.va.gov and BRD.
  • Opportunities to proactively prevent the staging.cms.va.gov and BRD errors from happening in the future are identified.

Team

Please check the team(s) that will do this work.

  • CMS Team
  • Public Websites
  • Facilities
  • User support
  • Accelerated Publishing
@github-actions github-actions bot added the CMS Team CMS Product team that manages both editor exp and devops label Feb 26, 2024
@gracekretschmer-metrostar gracekretschmer-metrostar changed the title 2/23/2024 staging.cms.va.gov 2/23/2024 staging.cms.va.gov Postmortem Feb 26, 2024
@gracekretschmer-metrostar gracekretschmer-metrostar changed the title 2/23/2024 staging.cms.va.gov Postmortem 2/23/2024 Build and Deploy Breakdown Postmortem Feb 27, 2024
@edmund-dunn edmund-dunn linked a pull request Feb 29, 2024 that will close this issue
25 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment