diff options
| author | Jeff Grafton <jgrafton@google.com> | 2016-12-19 15:42:31 -0800 |
|---|---|---|
| committer | Jeff Grafton <ixdy@users.noreply.github.com> | 2016-12-19 16:22:07 -0800 |
| commit | 6e00f5a70d395c17a143488ed5382163dfd1d723 (patch) | |
| tree | c755fa0d563d6704b7adee15187b995d8b70aea4 | |
| parent | 1711e75d348925990abb4f4b710fa6134e90ab90 (diff) | |
build-tools/ has been renamed build/
| -rw-r--r-- | contributors/design-proposals/multi-platform.md | 6 | ||||
| -rw-r--r-- | contributors/devel/bazel.md | 4 | ||||
| -rw-r--r-- | contributors/devel/development.md | 8 | ||||
| -rw-r--r-- | contributors/devel/e2e-tests.md | 2 | ||||
| -rw-r--r-- | contributors/devel/running-locally.md | 3 |
5 files changed, 11 insertions, 12 deletions
diff --git a/contributors/design-proposals/multi-platform.md b/contributors/design-proposals/multi-platform.md index 36eacefa..145c0ab9 100644 --- a/contributors/design-proposals/multi-platform.md +++ b/contributors/design-proposals/multi-platform.md @@ -277,7 +277,7 @@ A great blog post [that is describing this](https://medium.com/@rakyll/go-1-5-cr Before Go 1.5, the whole Go project had to be cross-compiled from source for **all** platforms that _might_ be used, and that was quite a slow process: ```console -# From build-tools/build-image/cross/Dockerfile when we used Go 1.4 +# From build/build-image/cross/Dockerfile when we used Go 1.4 $ cd /usr/src/go/src $ for platform in ${PLATFORMS}; do GOOS=${platform%/*} GOARCH=${platform##*/} ./make.bash --no-clean; done ``` @@ -288,7 +288,7 @@ If you cross-compile multiple times, Go will build parts of `std`, throw it away However, there is an easy way of cross-compiling all `std` packages in advance with Go 1.5+: ```console -# From build-tools/build-image/cross/Dockerfile when we're using Go 1.5+ +# From build/build-image/cross/Dockerfile when we're using Go 1.5+ $ for platform in ${PLATFORMS}; do GOOS=${platform%/*} GOARCH=${platform##*/} go install std; done ``` @@ -377,7 +377,7 @@ In order to dynamically compile a go binary with `cgo`, we need `gcc` installed The only Kubernetes binary that is using C code is the `kubelet`, or in fact `cAdvisor` on which `kubelet` depends. `hyperkube` is also dynamically linked as long as `kubelet` is. We should aim to make `kubelet` statically linked. -The normal `x86_64-linux-gnu` can't cross-compile binaries, so we have to install gcc cross-compilers for every platform. We do this in the [`kube-cross`](../../build-tools/build-image/cross/Dockerfile) image, +The normal `x86_64-linux-gnu` can't cross-compile binaries, so we have to install gcc cross-compilers for every platform. We do this in the [`kube-cross`](https://github.com/kubernetes/kubernetes/blob/master/build/build-image/cross/Dockerfile) image, and depend on the [`emdebian.org` repository](https://wiki.debian.org/CrossToolchains). Depending on `emdebian` isn't ideal, so we should consider using the latest `gcc` cross-compiler packages from the `ubuntu` main repositories in the future. Here's an example when cross-compiling plain C code: diff --git a/contributors/devel/bazel.md b/contributors/devel/bazel.md index e6a4e9c5..5c18ec41 100644 --- a/contributors/devel/bazel.md +++ b/contributors/devel/bazel.md @@ -8,13 +8,13 @@ can be found [here](https://www.bazel.io/versions/master/docs/install.html). To build docker images for the components, run: ``` -$ bazel build //build-tools/... +$ bazel build //build/... ``` To run many of the unit tests, run: ``` -$ bazel test //cmd/... //build-tools/... //pkg/... //federation/... //plugin/... +$ bazel test //cmd/... //build/... //pkg/... //federation/... //plugin/... ``` To update automanaged build files, run: diff --git a/contributors/devel/development.md b/contributors/devel/development.md index 8248839e..cb999f9d 100644 --- a/contributors/devel/development.md +++ b/contributors/devel/development.md @@ -15,7 +15,7 @@ branch, but release branches of Kubernetes should not change. Official releases are built using Docker containers. To build Kubernetes using Docker please follow [these instructions] -(http://releases.k8s.io/HEAD/build-tools/README.md). +(http://releases.k8s.io/HEAD/build/README.md). ## Building Kubernetes on a local OS/shell environment @@ -107,10 +107,10 @@ bump to a minor release version for security updates. Since kubernetes is mostly built and tested in containers, there are a few unique places you need to update the go version. -- The image for cross compiling in [build-tools/build-image/cross/](../../build-tools/build-image/cross/). The `VERSION` file and `Dockerfile`. +- The image for cross compiling in [build/build-image/cross/](https://github.com/kubernetes/kubernetes/blob/master/build/build-image/cross/). The `VERSION` file and `Dockerfile`. - Update [dockerized-e2e-runner.sh](https://github.com/kubernetes/test-infra/blob/master/jenkins/dockerized-e2e-runner.sh) to run a kubekins-e2e with the desired go version, which requires pushing [e2e-image](https://github.com/kubernetes/test-infra/tree/master/jenkins/e2e-image) and [test-image](https://github.com/kubernetes/test-infra/tree/master/jenkins/test-image) images that are `FROM` the desired go version. -- The docker image being run in [gotest-dockerized.sh](https://github.com/kubernetes/test-infra/tree/master/jenkins/gotest-dockerized.sh). -- The cross tag `KUBE_BUILD_IMAGE_CROSS_TAG` in [build-tools/common.sh](../../build-tools/common.sh) +- The docker image being run in [gotest-dockerized.sh](https://github.com/kubernetes/test-infra/blob/master/jenkins/gotest-dockerized.sh). +- The cross tag `KUBE_BUILD_IMAGE_CROSS_TAG` in [build/common.sh](https://github.com/kubernetes/kubernetes/blob/master/build/common.sh) ## Workflow diff --git a/contributors/devel/e2e-tests.md b/contributors/devel/e2e-tests.md index fc8f1995..6fc995cd 100644 --- a/contributors/devel/e2e-tests.md +++ b/contributors/devel/e2e-tests.md @@ -271,7 +271,7 @@ Next, specify the docker repository where your ci images will be pushed. * Push the federation container images ```sh - $ build-tools/push-federation-images.sh + $ build/push-federation-images.sh ``` #### Deploy federation control plane diff --git a/contributors/devel/running-locally.md b/contributors/devel/running-locally.md index 60fb3c74..64714ce9 100644 --- a/contributors/devel/running-locally.md +++ b/contributors/devel/running-locally.md @@ -169,8 +169,7 @@ KUBE_DNS_SERVER_IP="10.0.0.10" KUBE_DNS_DOMAIN="cluster.local" ``` -To know more on DNS service you can look [here](http://issue.k8s.io/6667). Related documents can be found [here](../../build-tools/kube-dns/#how-do-i-configure-it) - +To know more on DNS service you can check out the [docs](http://kubernetes.io/docs/admin/dns/). <!-- BEGIN MUNGE: GENERATED_ANALYTICS --> []() |
