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

refactor(workflows): avoid using cached states for release instances #9137

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

gustavovalverde
Copy link
Member

Motivation

We don't need the complexity of cached states in our long-lived instances, as we'll be using the same state across releases (this will also test the upgrades will work as expected).

This will also fix an regression in our main branch, caused by #9003

Solution

  • Renamed no_cached_disk input to need_cached_disk in cd-deploy-nodes-gcp.yml to clarify its purpose.
  • Adjusted conditional logic for cached disk usage based on event types (release vs. non-release) in cd-deploy-nodes-gcp.yml.
  • Removed the environment strategy matrix from sub-deploy-integration-tests-gcp.yml to avoid creating cached states in another environments

Follow-up Work

  • Do frequent backups to our release nodes states (bi-daily, weekly, etc) as decided.

PR Author's Checklist

  • The PR name will make sense to users.
  • The PR provides a CHANGELOG summary.
  • The solution is tested.
  • The documentation is up to date.
  • The PR has a priority label.

PR Reviewer's Checklist

  • The PR Author's checklist is complete.
  • The PR resolves the issue.

- Renamed `no_cached_disk` input to `need_cached_disk` in `cd-deploy-nodes-gcp.yml` to clarify its purpose.
- Adjusted conditional logic for cached disk usage based on event types (release vs. non-release) in `cd-deploy-nodes-gcp.yml`.
- Removed the environment strategy matrix from `sub-deploy-integration-tests-gcp.yml` to simplify the workflow configuration.
- Enhanced comments for better clarity on caching and environment handling across workflows.
@gustavovalverde gustavovalverde added C-bug Category: This is a bug C-design Category: Software design work A-devops Area: Pipelines, CI/CD and Dockerfiles I-integration-fail Continuous integration fails, including build and test failures P-Critical 🚑 labels Jan 17, 2025
@gustavovalverde gustavovalverde self-assigned this Jan 17, 2025
@gustavovalverde gustavovalverde requested a review from a team as a code owner January 17, 2025 14:54
@gustavovalverde gustavovalverde requested review from oxarbitrage and removed request for a team January 17, 2025 14:54
@github-actions github-actions bot added the C-trivial Category: A trivial change that is not worth mentioning in the CHANGELOG label Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-devops Area: Pipelines, CI/CD and Dockerfiles C-bug Category: This is a bug C-design Category: Software design work C-trivial Category: A trivial change that is not worth mentioning in the CHANGELOG I-integration-fail Continuous integration fails, including build and test failures P-Critical 🚑
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant