Update build docs to include path for scripts.

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.

Update build docs to include path for scripts.
e939dd37 · Yong Tang · b551bf1e · e939dd37
Commit e939dd37 authored Aug 24, 2016 by Yong Tang
Hide whitespace changes
Inline Side-by-side

Showing with 12 additions and 12 deletions

README.md build/README.md +12 -12

No files found.
--- a/build/README.md
+++ b/build/README.md
@@ -21,18 +21,18 @@ There is also early support for building Docker "run" containers

 ## Key scripts

-The following scripts are found in the `build/` directory:
-
-* `run.sh`: Run a command in a build docker container.  Common invocations:
-  *  `run.sh make`: Build just linux binaries in the container.  Pass options and packages as necessary.
-  *  `run.sh make cross`: Build all binaries for all platforms
-  *  `run.sh make test`: Run all unit tests
-  *  `run.sh make test-integration`: Run integration test
-  *  `run.sh make test-cmd`: Run CLI tests
-* `copy-output.sh`: This will copy the contents of `_output/dockerized/bin` from any remote Docker container to the local `_output/dockerized/bin`.  Right now this is only necessary on Mac OS X with `boot2docker` when your git repo isn't under `/Users`.
-* `make-clean.sh`: Clean out the contents of `_output/dockerized` and remove any local built container images.
-* `shell.sh`: Drop into a `bash` shell in a build container with a snapshot of the current repo code.
-* `release.sh`: Build everything, test it, and (optionally) upload the results to a GCS bucket.
+The following scripts are found in the `build/` directory. Note that all scripts must be run from the Kubernetes root directory.
+
+* `build/run.sh`: Run a command in a build docker container.  Common invocations:
+  *  `build/run.sh make`: Build just linux binaries in the container.  Pass options and packages as necessary.
+  *  `build/run.sh make cross`: Build all binaries for all platforms
+  *  `build/run.sh make test`: Run all unit tests
+  *  `build/run.sh make test-integration`: Run integration test
+  *  `build/run.sh make test-cmd`: Run CLI tests
+* `build/copy-output.sh`: This will copy the contents of `_output/dockerized/bin` from any remote Docker container to the local `_output/dockerized/bin`.  Right now this is only necessary on Mac OS X with `boot2docker` when your git repo isn't under `/Users`.
+* `build/make-clean.sh`: Clean out the contents of `_output/dockerized` and remove any local built container images.
+* `build/shell.sh`: Drop into a `bash` shell in a build container with a snapshot of the current repo code.
+* `build/release.sh`: Build everything, test it, and (optionally) upload the results to a GCS bucket.

 ## Releasing