Cherry pick #55717 to 23.9: Improve Dockerfiles for keeper and server images #57252
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Improve Dockerfiles for keeper and server images
robot-clickhouse-ci-2
added
pr-cherrypick
…3351409a20554948a7f86a06f1a
|
This is an automated comment for commit 44c3050 with description of existing statuses. It's updated for the latest CI running ❌ Click here to open a full report in a separate page
|
robot-ch-test-poll4
deleted the
cherrypick/23.9/8935c6ce5dc283351409a20554948a7f86a06f1a
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Original pull-request #55717
This pull-request is a first step of an automated backporting.
It contains changes like after calling a local command
git cherry-pick.If you intend to continue backporting this changes, then resolve all conflicts if any.
Otherwise, if you do not want to backport them, then just close this pull-request.
The check results does not matter at this step - you can safely ignore them.
Note
This pull-request will be merged automatically as it reaches the mergeable state, do not merge it manually. It's 100% safe, but completely meaningless.
If the PR was closed and then reopened
If it stuck (e.g. for a day), check #55717 for
pr-backports-createdlabel and delete it if necessary. Manually merging will do nothing, sincepr-backports-createdlabel prevents the original PR #55717 from being processed.If the cherry-pick PR is completely screwed, and you want to recreate it: delete the
pr-cherrypicklabel and delete this branch.You may also need to delete the
pr-backports-createdlabel from the original PR.