ClickHouse / ClickHouse/clickhouse-java

[repo] Create Pre-release workflow or find point where release verification should happen

Open
#2,961 2 comments 2 reactions 0 assignees View on GitHub
area:general
Dominant language
Java
Stars
1.6k
Forks
636
Avg merge
2d 23h
Merged PRs (30d)
29

Description

## Description

Client is the core library for many connectors. If we release a breaking change unnoticed it may require more effort to fix late. Today we have a release workflow that publishes to Maven. But we should not block this by tests.

What should be done:
- Evaluate idea of creating pre-release wf that can be used to trigger verification tests.
- Find out what to do with long running test WF's in other repos. How they would deliver result to java client maintainers.
- Research what can be done for community users to have similar signal for tests.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the existing release workflow that publishes to Maven and identify where verification currently occurs. Then examine the long-running test workflows in other repositories and how their results could reach Java client maintainers and community users. Done means a decided pre-release verification approach and a clear result-delivery plan.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, java
Domain
ci-cd, release, testing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.