cr-buildbucket-dev: define luci.chromium.try bucket

cr-buildbucket-dev: define luci.chromium.try bucket

copy luci.chromium.try bucket definition from cr-buildbucket.cfg to
cr-buildbucket-dev.cfg with modifications:
- use luci-milo-dev, not prod
- use chromium-swarm-dev, not prod
- use luci-scheduler-dev, not prod
- use pool Chrome
- remove allow_milo:1 tag, not needed anymore
- allow luci-migration-dev@appspot.gserviceaccount.com to
  schedule builds (for retries)
- exclude buidbot masters from ACLs, we are not going to experiment with them

Bug=719734
NOTRY=true
NOPRESUBMIT=true

Review-Url: https://codereview.chromium.org/2899433002
Committed: https://chromium.googlesource.com/chromium/src/+/93e3be812538b9103dcf749c3f89f8145926fe15

[nodir, 2017-05-19 17:06:39]

Description was changed from

==========
cr-buildbucket-dev: define luci.chromium.try bucket

copy luci.chromium.try bucket definition from cr-buildbucket.cfg to
cr-buildbucket-dev.cfg with modifications:
- use luci-milo-dev, not prod
- use chromium-swarm-dev, not prod
- use luci-scheduler-dev, not prod
- use pool Chrome
- remove allow_milo:1 tag, not needed anymore
- allow luci-migration-dev@appspot.gserviceaccount.com to
  schedule builds (for retries)

Bug: 719734
==========

to

==========
cr-buildbucket-dev: define luci.chromium.try bucket

copy luci.chromium.try bucket definition from cr-buildbucket.cfg to
cr-buildbucket-dev.cfg with modifications:
- use luci-milo-dev, not prod
- use chromium-swarm-dev, not prod
- use luci-scheduler-dev, not prod
- use pool Chrome
- remove allow_milo:1 tag, not needed anymore
- allow luci-migration-dev@appspot.gserviceaccount.com to
  schedule builds (for retries)
- exclude buidbot masters from ACLs, we are not going to experiment with them

Bug: 719734
==========

[nodir, 2017-05-19 17:07:24]

nodir@chromium.org changed reviewers:
+ dnj@chromium.org, estaab@chromium.org

[nodir, 2017-05-19 17:07:25]

PTAL

[estaab, 2017-05-19 17:14:22]

lgtm

https://codereview.chromium.org/2899433002/diff/20001/cr-buildbucket-dev.cfg
File cr-buildbucket-dev.cfg (right):

https://codereview.chromium.org/2899433002/diff/20001/cr-buildbucket-dev.cfg#...
cr-buildbucket-dev.cfg:73: dimensions: "pool:Chrome"
why Chrome? everything else is staging except this one.

[nodir, 2017-05-19 23:59:53]

https://codereview.chromium.org/2899433002/diff/20001/cr-buildbucket-dev.cfg
File cr-buildbucket-dev.cfg (right):

https://codereview.chromium.org/2899433002/diff/20001/cr-buildbucket-dev.cfg#...
cr-buildbucket-dev.cfg:73: dimensions: "pool:Chrome"
On 2017/05/19 17:14:21, estaab wrote:
> why Chrome? everything else is staging except this one.

this is pool "Chrome" on staging server "chromium-swarm-dev.appspot.com". The
alternative is pool "default" on the same server, but I thought Chrome is more
appropriate. It probably does not matter, since both are staging and we are not
going to run many builds here

[nodir, 2017-05-20 00:00:06]

Description was changed from

==========
cr-buildbucket-dev: define luci.chromium.try bucket

copy luci.chromium.try bucket definition from cr-buildbucket.cfg to
cr-buildbucket-dev.cfg with modifications:
- use luci-milo-dev, not prod
- use chromium-swarm-dev, not prod
- use luci-scheduler-dev, not prod
- use pool Chrome
- remove allow_milo:1 tag, not needed anymore
- allow luci-migration-dev@appspot.gserviceaccount.com to
  schedule builds (for retries)
- exclude buidbot masters from ACLs, we are not going to experiment with them

Bug: 719734
==========

to

==========
cr-buildbucket-dev: define luci.chromium.try bucket

copy luci.chromium.try bucket definition from cr-buildbucket.cfg to
cr-buildbucket-dev.cfg with modifications:
- use luci-milo-dev, not prod
- use chromium-swarm-dev, not prod
- use luci-scheduler-dev, not prod
- use pool Chrome
- remove allow_milo:1 tag, not needed anymore
- allow luci-migration-dev@appspot.gserviceaccount.com to
  schedule builds (for retries)
- exclude buidbot masters from ACLs, we are not going to experiment with them

Bug: 719734
NOTRY=true
NOPRESUBMIT=true
==========

[nodir, 2017-05-20 00:00:12]

The CQ bit was checked by nodir@chromium.org

[nodir, 2017-05-20 00:00:20]

Description was changed from

==========
cr-buildbucket-dev: define luci.chromium.try bucket

copy luci.chromium.try bucket definition from cr-buildbucket.cfg to
cr-buildbucket-dev.cfg with modifications:
- use luci-milo-dev, not prod
- use chromium-swarm-dev, not prod
- use luci-scheduler-dev, not prod
- use pool Chrome
- remove allow_milo:1 tag, not needed anymore
- allow luci-migration-dev@appspot.gserviceaccount.com to
  schedule builds (for retries)
- exclude buidbot masters from ACLs, we are not going to experiment with them

Bug: 719734
NOTRY=true
NOPRESUBMIT=true
==========

to

==========
cr-buildbucket-dev: define luci.chromium.try bucket

copy luci.chromium.try bucket definition from cr-buildbucket.cfg to
cr-buildbucket-dev.cfg with modifications:
- use luci-milo-dev, not prod
- use chromium-swarm-dev, not prod
- use luci-scheduler-dev, not prod
- use pool Chrome
- remove allow_milo:1 tag, not needed anymore
- allow luci-migration-dev@appspot.gserviceaccount.com to
  schedule builds (for retries)
- exclude buidbot masters from ACLs, we are not going to experiment with them

Bug=719734
NOTRY=true
NOPRESUBMIT=true
==========

[commit-bot: I haz the power, 2017-05-20 00:00:56]

CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-05-20 00:05:46]

CQ is committing da patch.

Bot data: {"patchset_id": 20001, "attempt_start_ts": 1495238412113050,
"parent_rev": "4870d0f680bf43d9da5eb58c1c5bf87e9f09225c", "commit_rev":
"93e3be812538b9103dcf749c3f89f8145926fe15"}

[commit-bot: I haz the power, 2017-05-20 00:05:52]

Description was changed from

==========
cr-buildbucket-dev: define luci.chromium.try bucket

copy luci.chromium.try bucket definition from cr-buildbucket.cfg to
cr-buildbucket-dev.cfg with modifications:
- use luci-milo-dev, not prod
- use chromium-swarm-dev, not prod
- use luci-scheduler-dev, not prod
- use pool Chrome
- remove allow_milo:1 tag, not needed anymore
- allow luci-migration-dev@appspot.gserviceaccount.com to
  schedule builds (for retries)
- exclude buidbot masters from ACLs, we are not going to experiment with them

Bug=719734
NOTRY=true
NOPRESUBMIT=true
==========

to

==========
cr-buildbucket-dev: define luci.chromium.try bucket

copy luci.chromium.try bucket definition from cr-buildbucket.cfg to
cr-buildbucket-dev.cfg with modifications:
- use luci-milo-dev, not prod
- use chromium-swarm-dev, not prod
- use luci-scheduler-dev, not prod
- use pool Chrome
- remove allow_milo:1 tag, not needed anymore
- allow luci-migration-dev@appspot.gserviceaccount.com to
  schedule builds (for retries)
- exclude buidbot masters from ACLs, we are not going to experiment with them

Bug=719734
NOTRY=true
NOPRESUBMIT=true

Review-Url: https://codereview.chromium.org/2899433002
Committed:
https://chromium.googlesource.com/chromium/src/+/93e3be812538b9103dcf749c3f89...
==========

[commit-bot: I haz the power, 2017-05-20 00:05:53]

Committed patchset #2 (id:20001) as
https://chromium.googlesource.com/chromium/src/+/93e3be812538b9103dcf749c3f89...

[Erik Staab (Google), 2017-05-20 00:23:09]

On 2017/05/19 23:59:53, nodir wrote:
> https://codereview.chromium.org/2899433002/diff/20001/cr-buildbucket-dev.cfg
> File cr-buildbucket-dev.cfg (right):
> 
>
https://codereview.chromium.org/2899433002/diff/20001/cr-buildbucket-dev.cfg#...
> cr-buildbucket-dev.cfg:73: dimensions: "pool:Chrome"
> On 2017/05/19 17:14:21, estaab wrote:
> > why Chrome? everything else is staging except this one.
> 
> this is pool "Chrome" on staging server "chromium-swarm-dev.appspot.com". The
> alternative is pool "default" on the same server, but I thought Chrome is more
> appropriate. It probably does not matter, since both are staging and we are
not
> going to run many builds here

That makes sense, thanks for clarifying.