KAFKA-19686 : release - Trigger docker builds with rc and release#21963
Open
muralibasani wants to merge 2 commits intoapache:trunkfrom
Open
KAFKA-19686 : release - Trigger docker builds with rc and release#21963muralibasani wants to merge 2 commits intoapache:trunkfrom
muralibasani wants to merge 2 commits intoapache:trunkfrom
Conversation
This file contains hidden or 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
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.
https://issues.apache.org/jira/browse/KAFKA-19686
How It Works After the RC tag is
pushed, the script:
Asks the user: "Trigger Docker image build workflows?" - If yes —
collects user's GitHub token, triggers docker_build_and_test.yml for
both JVM and native - Asks: "Also trigger Docker
RC release workflows?"
If yes — triggers docker_rc_release.yml for both JVM and native with
the correct image names (apache/kafka, apache/kafka-native) -
Can be run in dry run mode too
Both steps are optional (behind confirm() prompts), so the existing
flow is unchanged if the user declines. No new dependencies were added —
only Python stdlib urllib is used.
Test runs :