| commit | 2e81ae1df391e7b90b9c38f4371330de2ac316c4 | [log] [tgz] |
|---|---|---|
| author | Gary Miguel <garymm@google.com> | Tue Aug 13 15:07:49 2019 -0700 |
| committer | Gary Miguel <garymm@google.com> | Tue Aug 13 15:30:45 2019 -0700 |
| tree | 9574d591b3a7b013626698a92ffb354b91da6d90 | |
| parent | 824474aef03ad7c27e18c40fe8a5187a742bda1d [diff] |
[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
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}