| commit | 838dfda8f247ace97ab8927411122b6e85a322bf | [log] [tgz] |
|---|---|---|
| author | Gary Miguel <garymm@google.com> | Wed Aug 14 17:01:53 2019 +0000 |
| committer | Gary Miguel <garymm@google.com> | Wed Aug 14 10:39:19 2019 -0700 |
| tree | f05d67cc056a146bf8d4bf632bb815dc9e1a1042 | |
| parent | 03ee86b0bed66ceef0506fd96d512a1df7290008 [diff] |
[artifacts] Read gcs_bucket from output properties, not input This is a reland of 2e81ae1df391e7b90b9c38f4371330de2ac316c4 Differences: * When retrieving the Build proto from BuildBucket, ask for the Output field instead of the input field. That's what we actually access now. * Remove unused function which accessed the input. Tested by running tool locally with the exact same arguments that we saw failing in CQ. Original change's description: > [artifacts] Read gcs_bucket from output properties, not input > > This is better because: > * It's much more intuitive that something outside a build depends on its > outputs rather than its inputs. > * Our recipe code expects this. It's setting the output property > gcs_bucket already, not the input property. > > Change-Id: Id2ad57c08e4f60a7bd20310afabec9210ca7bffb Change-Id: I03ffe38722f6a65e49dd7e50e6bdc2e3fe1d6ca7
This repo contains tools and config files necessary to run infrastructure related to builds, code review, version control, and continuous integrations.
In order to build the Go code, you must clone this repo into an appropriately named directory. This should do the trick:
REPO=fuchsia.googlesource.com/infra/infra git clone https://${REPO} $(go env GOPATH)/src/${REPO}