Build skaffold-builder image from a pre-pushed base#3433
Build skaffold-builder image from a pre-pushed base#3433nkubala merged 1 commit intoGoogleContainerTools:masterfrom
Conversation
87e2eb6 to
e169c38
Compare
Codecov Report
|
How about using artifact caching and use skaffold itself to build & push the build_deps? That will lose a couple of seconds on each build but not full rebuilds of the deps. |
e169c38 to
8800bb0
Compare
|
how will we know when we need to rebuild the base image here? I guess it's not really a huge deal cause we're probably not updating build tools very often. |
d790bff to
4b03792
Compare
|
@nkubala I added a script that updates |
c2676ca to
55ec3e4
Compare
|
Hey @nkubala can you TAL at this one? |
Signed-off-by: David Gageot <david@gageot.net>
55ec3e4 to
79f3fa8
Compare
Revert "Merge pull request #3433 from dgageot/faster-skaffold-builder"
…affold-builder Signed-off-by: David Gageot <david@gageot.net>
…affold-builder Signed-off-by: David Gageot <david@gageot.net>
…affold-builder Signed-off-by: David Gageot <david@gageot.net>
…affold-builder Signed-off-by: David Gageot <david@gageot.net>
…affold-builder Signed-off-by: David Gageot <david@gageot.net>
This is meant to accelerate the integration tests: instead of installing all the cli tools on each build, we have a pre-pushed base image that contains all those tools.
What I've done is pre-built the
gcr.io/k8s-skaffold/build_depsimage and referenced it by digest.Question: How can we do that in a more automatized way?
Signed-off-by: David Gageot david@gageot.net