diff --git a/bazel.md b/bazel.md index 2c321a905f7..80915f15ee2 100644 --- a/bazel.md +++ b/bazel.md @@ -37,13 +37,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/... +$ bazel build //build-tools/... ``` To run many of the unit tests, run: ``` -$ bazel test //cmd/... //build/... //pkg/... //federation/... //plugin/... +$ bazel test //cmd/... //build-tools/... //pkg/... //federation/... //plugin/... ``` To update automanaged build files, run: diff --git a/cherry-picks.md b/cherry-picks.md index ef2cee70b0a..4283ee3b143 100644 --- a/cherry-picks.md +++ b/cherry-picks.md @@ -79,7 +79,7 @@ tracking the tool to automate the batching procedure. #### Cherrypicking a doc change If you are cherrypicking a change which adds a doc, then you also need to run -`build/versionize-docs.sh` in the release branch to versionize that doc. +`build-tools/versionize-docs.sh` in the release branch to versionize that doc. Ideally, just running `hack/cherry_pick_pull.sh` should be enough, but we are not there yet: [#18861](https://github.com/kubernetes/kubernetes/issues/18861) @@ -89,7 +89,7 @@ running `hack/cherry_pick_pull.sh` and before merging the PR: ``` $ git checkout -b automated-cherry-pick-of-#123456-upstream-release-3.14 origin/automated-cherry-pick-of-#123456-upstream-release-3.14 -$ ./build/versionize-docs.sh release-3.14 +$ ./build-tools/versionize-docs.sh release-3.14 $ git commit -a -m "Running versionize docs" $ git push origin automated-cherry-pick-of-#123456-upstream-release-3.14 ``` diff --git a/development.md b/development.md index 2a0e04104f8..d36f7ec367c 100644 --- a/development.md +++ b/development.md @@ -49,7 +49,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/README.md). +(http://releases.k8s.io/HEAD/build-tools/README.md). ## Building Kubernetes on a local OS/shell environment @@ -142,10 +142,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/build-image/cross/](../../build/build-image/cross/). The `VERSION` file and `Dockerfile`. +- The image for cross compiling in [build-tools/build-image/cross/](../../build-tools/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 [hack/jenkins/gotest-dockerized.sh](../../hack/jenkins/gotest-dockerized.sh). -- The cross tag `KUBE_BUILD_IMAGE_CROSS_TAG` in [build/common.sh](../../build/common.sh) +- The cross tag `KUBE_BUILD_IMAGE_CROSS_TAG` in [build-tools/common.sh](../../build-tools/common.sh) ## Workflow diff --git a/e2e-tests.md b/e2e-tests.md index 4db76f89257..431fa9a26c3 100644 --- a/e2e-tests.md +++ b/e2e-tests.md @@ -305,7 +305,7 @@ Next, specify the docker repository where your ci images will be pushed. * Push the federation container images ```sh - $ build/push-federation-images.sh + $ build-tools/push-federation-images.sh ``` #### Deploy federation control plane diff --git a/running-locally.md b/running-locally.md index 810740fafe3..a6332d71109 100644 --- a/running-locally.md +++ b/running-locally.md @@ -195,7 +195,7 @@ KUBE_DNS_DOMAIN="cluster.local" KUBE_DNS_REPLICAS=1 ``` -To know more on DNS service you can look [here](http://issue.k8s.io/6667). Related documents can be found [here](../../build/kube-dns/#how-do-i-configure-it) +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)