Skip to content

fix: release builds should upload package after failing integration tests#1587

Open
sachinpro wants to merge 1 commit into
mainfrom
release_pipelines_fix
Open

fix: release builds should upload package after failing integration tests#1587
sachinpro wants to merge 1 commit into
mainfrom
release_pipelines_fix

Conversation

@sachinpro

@sachinpro sachinpro commented Jul 13, 2026

Copy link
Copy Markdown
Collaborator

Integration tests are flaky. Release builds should upload the packages when integration tests are failing.

Successful compilation and unit tests are still a blocker.

@sachinpro
sachinpro marked this pull request as ready for review July 13, 2026 22:14
@sachinpro
sachinpro requested a review from a team as a code owner July 13, 2026 22:14
@sachinpro
sachinpro requested a review from logachev July 13, 2026 22:15
@sachinpro
sachinpro force-pushed the release_pipelines_fix branch from 132bb67 to 7823b39 Compare July 14, 2026 09:40
@sachinpro
sachinpro force-pushed the release_pipelines_fix branch from 7823b39 to 7c7612d Compare July 14, 2026 09:40

@logachev logachev left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I disagree with this PR.

  1. Flaky tests. If there are flaky tests, that is concerning. With JDBC driver, I don't recall flaky tests that were not caused by the issue with the driver.

  2. How can we distinguish flaky test from a regression? I don't want to relax release gates using flakiness as a justification.

  3. It's ok to get a separate pipeline to manually publish a package in case we need a hotfix or any other reason, but it should be exception only.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants