github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-07-30 23:15:14 +00:00
Code Issues Projects Releases Wiki Activity

Skip cleaning docker cache prior to build

Browse Source 
This seems to be more trouble than its worth, and much of
the remaining build time (except the push itself). We can
cache the cross-build/golang images between builds - it's
not going to kill us, and it'll save the occasional weird
flake of not finding an image when it tries to rm one of
these.
This commit is contained in:
Zach Loafman 2015-04-01 19:20:44 -07:00
parent 9949936b5c
commit 6ba14f1c28
1 changed files with 8 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
hack/jenkins/build.sh
View File

@ -34,15 +34,17 @@ export PATH=$PATH:/usr/local/go/bin
export KUBE_RELEASE_RUN_TESTS=n
export KUBE_SKIP_CONFIRMATIONS=y
# Clean stuff out. Assume the worst - the last build may have left the
# tree in an odd state. There's a Jenkins git clean plugin, but we
# have the docker images to worry about as well, so be really pedantic
# about cleaning.
# Clean stuff out. Assume the last build left the tree in an odd
# state.
rm -rf ~/.kube*
make clean
git clean -fdx
docker ps -aq | xargs -r docker rm
docker images -q | xargs -r docker rmi
# Uncomment if you want to purge the Docker cache completely each
# build. It costs about 150s each build to pull the golang image and
# rebuild the kube-build:cross image, but these rarely change.
# docker ps -aq | xargs -r docker rm
# docker images -q | xargs -r docker rmi
# Build
go run ./hack/e2e.go -v --build