Skip to content

Conversation

@jschaul
Copy link
Member

@jschaul jschaul commented Jul 18, 2023

We wish to avoid needing persistence during CI runs, as we run into limits of volume creation, which causes integration test setup failures.

This PR can be reverted at some point in the future when:

  • hedis code is both compatible with current redis version AND redis version 7 and its tests pass, and it is released to hackage / nixpkgs.
  • (or temporarily if you make changes to redis and/or redis code in gundeck and wish to test these changes on CI)

Then:

  • Step 1. We can use latest hedis code (and merge this to develop, ensuring this works on staging)
  • Step 2: Subsequently this PR can be reverted, and the redis-cluster helm chart bumped, and persistence disabled. See also Wpb 2824 disable redis persistence (upgrade hedis) #3444
  • ensure to do steps 1 and 2 on separate PRs, to avoid requiring a redis helm chart update concurrently with a code update - that would not work well in production and cause downtime.

Context:

Checklist

  • Add a new entry in an appropriate subdirectory of changelog.d
  • Read and follow the PR guidelines

@zebot zebot added the ok-to-test Approved for running tests in CI, overrides not-ok-to-test if both labels exist label Jul 18, 2023
@jschaul jschaul force-pushed the redis-ephemeral-on-ci branch 3 times, most recently from 18f0a28 to fcea87a Compare July 18, 2023 12:00
@jschaul jschaul requested a review from akshaymankar July 18, 2023 15:05
@jschaul
Copy link
Member Author

jschaul commented Jul 18, 2023

unrelated integration test failures...

We wish to avoid needing persistence during CI runs, as we run into
limits of volume creation, which causes integration test setup failures.

This PR can be reverted at some point in the future when:

- hedis code is both compatible with current redis version AND redis version 7 and its tests pass, and it is released to hackage / nixpkgs.

Then:

- Step 1. We can use latest hedis code (and merge this to develop, ensuring this
  works on staging)
- Step 2: Subsequently this PR can be reverted, and the redis-cluster helm chart
  bumped, and persistence disabled. See also #3444
- ensure to do steps 1 and 2 on *separate* PRs, to avoid requiring a
  redis helm chart update concurrently with a code update - that would
  not work well in production and cause downtime.

Context:

- https://wearezeta.atlassian.net/browse/WPB-2824
- https://wearezeta.atlassian.net/browse/WPB-2783
- #3427
- #3444
- #3445
@jschaul jschaul force-pushed the redis-ephemeral-on-ci branch from fcea87a to 68040eb Compare July 19, 2023 09:26
@jschaul jschaul merged commit 3020095 into develop Jul 19, 2023
@jschaul jschaul deleted the redis-ephemeral-on-ci branch July 19, 2023 12:32
@echoes-hq echoes-hq bot added the echoes: technical-roadmap/throughput More specific category, to highlight task aiming at improving the development velocity and effici... label Jan 13, 2025
@smatting smatting mentioned this pull request Nov 7, 2025
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

echoes: technical-roadmap/throughput More specific category, to highlight task aiming at improving the development velocity and effici... ok-to-test Approved for running tests in CI, overrides not-ok-to-test if both labels exist

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants