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

Jenkins job "Sanitize database on prod.cms.va.gov" Inconsistent Clean Builds #18203

Closed
5 tasks
Tracked by #18129
7hunderbird opened this issue May 22, 2024 · 2 comments
Closed
5 tasks
Tracked by #18129
Assignees
Labels
CMS Team CMS Product team that manages both editor exp and devops

Comments

@7hunderbird
Copy link

User Story or Problem Statement

We will need to dig into why the "Sanitize database on prod.cms.va.gov" job periodically fails 2/3 times.

CleanShot 2024-05-22 at 16 06 58

Description or Additional Context

Steps for Implementation

Acceptance Criteria

  • Testable_Outcome_X
  • Testable_Outcome_Y
  • Testable_Outcome_Z
  • Requires design review
  • Requires accessibility review
@7hunderbird 7hunderbird added the Needs refining Issue status label May 22, 2024
@7hunderbird
Copy link
Author

While it is annoying to see these alerts in the #cms-notifications channel, this can be a medium to low priority ticket for now because it's a repetative automation task whose purpose is to keep a development copy of the production database up-to-date.

  • It sanitizes the data
  • Publishes a mysqldump file to S3
  • Tugboat uses this to keep in-sync with Prod
  • Local developers also use this "dump file" to setup their development environment

If someone comes to us and says "I have this specific bug and think that my data from prod is off or out of sync". In that case we can increase the priority.

@7hunderbird
Copy link
Author

This was erroring because of a lock issue from the other jenkins server.

With the other jenkins server turned off the lock issue is gone and this is resolved.

@gracekretschmer-metrostar gracekretschmer-metrostar added CMS Team CMS Product team that manages both editor exp and devops and removed Needs refining Issue status labels Jun 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CMS Team CMS Product team that manages both editor exp and devops
Projects
None yet
Development

No branches or pull requests

2 participants