ClickHouse / ClickHouse/clickhouse-java
[repo] Smoke tests in CI
Open
enhancement
- Dominant language
- Java
- Stars
- 1.6k
- Forks
- 636
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 29
Description
### Description
Library is delivered in different packages and used in different setups. We should have a CI workflow which verifies that library has no issues.
What should be checked:
- examples are compiled and runnable
- library has all classes in `shaded` and `all` packages.
Contributor guide
Research direction
Start by locating the repository's existing CI workflows, example projects, and package build configuration. Verify how examples can be compiled and run, then inspect how the shaded and all packages are produced; done means CI checks both runnable examples and class coverage in those packages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100