News for hackers. Stuff that matters.

A comment on Introducing Google Cloud Container Builder. Parent comment

Re:Introducing Google Cloud Container Builder by puzzle on Monday March 06, 2017 @05:20PM (#13806584)
Is there any caching involved?

In other words, what happens if I build the same source tree twice or if one line changes between one run and the next?

[ Parent | on HN ]
Re:Introducing Google Cloud Container Builder by skj on Monday March 06, 2017 @05:21PM (#13806595)
We don't currently cache anything from one build to the next. We are open to optimizations here, in the future.
[ Parent | on HN ]
Re:Introducing Google Cloud Container Builder by bendavis381 on Sunday March 19, 2017 @01:35PM (#13908478)
Our Python dependencies include gensim and numpy which puts the build > 10min. Without layer caching, what can I do to get the build time down?
[ Parent | on HN ]
Re:Introducing Google Cloud Container Builder by derefr on Friday March 10, 2017 @06:59PM (#13843204)
In my mind, at least for custom builds, the most widely-applicable optimization would be providing the build environment with a FUSE-mounted build-cache GCS bucket. Such a mount could then be used in ways similar to the way Heroku's buildpacks use their build artifact cache directory.
[ Parent | on HN ]