ClickHouse / ClickHouse/clickhouse-go
Reduce number of running containers in CI to one per run
Open
enhancement
tests
- Dominant language
- Go
- Stars
- 3.3k
- Forks
- 680
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 14
Description
## Observed
Each CI tests run creates a few ClickHouse containers per test directory. This is an unnecessary overhead that could be reduced to a single container per run.
## Expected behaviour
Run a single ClickHouse container per tests run.
Contributor guide
Research direction
Start by locating the CI test setup that creates ClickHouse containers for each test directory. Trace how containers are created and scoped during a test run, then verify that a CI run uses one ClickHouse container while all test directories still execute successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- ci-cd, testing
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100