Jason Hall

We can get information about refs without invoking the git CLI, using a package like [`go-git`](https://godoc.org/gopkg.in/src-d/go-git.v4), for instance: ``` func main() { repo, _ := git.Init(memory.NewStorage(), nil) remo, _ :=...

That's a good question. I think when we talk about "outputs" what we're actually talking about is two types of things (at least) that it's useful to know your build...

I like the idea of builder writing images to volumes for us to push ourselves later, I'm just not sure why they would if they can push directly themselves already...

I don't think we should trust the builders to report what they pushed. An earlier alternative which was discussed was to scrape step status text and just report that, but...

/cc @jchesterpivotal @sixolet @julz

Another option would be to integrate with the new proposed [`knctl`](https://github.com/cppforlife/knctl) to upload source (where + how TBD), then create a build that points to it, and even a configuration...

I think the bigger issue might be how to set those configurations for the step we prepend that fetches the specified source. If `HTTP_PROXY` is needed to fetch from the...

@adamglt That's not something we've considered so far, but we could if using init containers blocks some important functionality.

We're definitely interested in making Build suitable in a multi-tenant environment, and it should definitely be possible to limit what a build can reach, and what can reach the build....

Indeed there is a lack of documentation for real-world build use cases. Until such docs exist, you might find it easier to use the [`go` builder](https://github.com/GoogleCloudPlatform/cloud-builders/tree/master/go) we recommend for GCB,...