-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make use staged sdk harness effective whenever experiment flag added #33954
Conversation
db4770d
to
b53ea9e
Compare
Checks are failing. Will not request review until checks are succeeding. If you'd like to override that behavior, comment |
R: @tvalentyn internal context - b/394923242#comment3 |
Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control. If you'd like to restart, comment |
R: @shunping |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Thanks!
if !hasWorkerExperiment { | ||
cp = append(cp, filepath.Join(jarsDir, javaHarnessJar)) | ||
} else { | ||
// Skip adding system "beam-sdks-java-harness.jar". User-provided jar will |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for my education, is this internal-only flow?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
external user could also use it. The purpose is detailed in the description of #33508users without docker access could test/run custom build beam-sdk-harness now
#33508 supported use staged sdk harness, however, it is only effective when a staged jar named after beam-sdks-java-harness*.jar. In. the case a uber jar is used, the flag isn't effective.
This change will make the flag effective regardless the staged jar file names.
Please add a meaningful description for your change here
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
addresses #123
), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, commentfixes #<ISSUE NUMBER>
instead.CHANGES.md
with noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.