-
Notifications
You must be signed in to change notification settings - Fork 38.6k
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
Update build docs to include path for scripts. #31398
Update build docs to include path for scripts. #31398
Conversation
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message will repeat several times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. |
6 similar comments
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message will repeat several times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. |
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message will repeat several times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. |
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message will repeat several times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. |
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message will repeat several times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. |
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message will repeat several times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. |
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message will repeat several times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. |
@@ -23,16 +23,16 @@ There is also early support for building Docker "run" containers | |||
|
|||
The following scripts are found in the `build/` directory: |
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.
maybe add a sentence here noting that these scripts must be run from the Kubernetes root directory?
ok to test |
This fix updates the build docs to include the path of `build/` for shell scripts. The reason is that while trying to follow the `build/README.md`, it is not obvious that all the scripts, e.g., `run.sh make`, `shell.sh`, etc. needs to be executed from the root directory (vs. executed from the `build/` directory). In other words, the executation should be: ``` build/run.sh make build/make-clean.sh ... ``` This fix adds `build/` so that it is easy for user to follow the steps.
Thanks @ixdy. The pull request has been updated with note added. Please let me know if there are any issues. |
LGTM |
GCE e2e build/test passed for commit e939dd3. |
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message will repeat several times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. |
Automatic merge from submit-queue |
What this PR does / why we need it:
This fix updates the build docs (
build/README.md
) to include the path ofbuild/
for shell scripts (likerun.sh
,shell.sh
).The reason is that while trying to follow the
build/README.md
to build the kubernetes, it is not obvious that all the scripts, e.g.,run.sh make
,shell.sh
, etc. needs to be executed from the root directory (vs. executed from thebuild/
directory).In other words, the executation should be:
This fix adds
build/
so that it is easy for user to follow the steps.Which issue this PR fixes (optional, in
fixes #<issue number>(, #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes #Special notes for your reviewer:
Release note:
This change is