Merge pull request #24813 from duglin/AddBuildPath

Automatic merge from submit-queue

Make it clear where the `build` scripts are located


Signed-off-by: Doug Davis <dug@us.ibm.com>
This commit is contained in:
k8s-merge-robot 2016-05-09 15:03:12 -07:00
commit 90c02c6d96

View File

@ -21,6 +21,8 @@ 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 hack/build-go.sh`: Build just linux binaries in the container. Pass options and packages as necessary.
* `run.sh hack/build-cross.sh`: Build all binaries for all platforms
@ -33,7 +35,7 @@ There is also early support for building Docker "run" containers
## Releasing
The `release.sh` script will build a release. It will build binaries, run tests, (optionally) build runtime Docker images and then (optionally) upload all build artifacts to a GCS bucket.
The `build/release.sh` script will build a release. It will build binaries, run tests, (optionally) build runtime Docker images and then (optionally) upload all build artifacts to a GCS bucket.
The main output is a tar file: `kubernetes.tar.gz`. This includes:
* Cross compiled client utilities.