Create master.tryserver.libyuv bucket

Create master.tryserver.libyuv bucket

Also README.md, OWNERS and other std files

R=kjellander@chromium.org
BUG=551062
Committed: 1773ecdd764266cfe93521bb5e3a3e6f42dedafd

[nodir, 2016-01-12 17:36:12]

PTAL

[kjellander_chromium, 2016-01-12 17:43:21]

kjellander@chromium.org changed reviewers:
+ fbarchard@chromium.org

[kjellander_chromium, 2016-01-12 17:43:22]

lgtm with comments addressed. 
+fbarchard for question about the project name.

https://codereview.chromium.org/1576093005/diff/1/codereview.settings
File codereview.settings (right):

https://codereview.chromium.org/1576093005/diff/1/codereview.settings#newcode2
codereview.settings:2: # The LibYuv code review is via WebRtc's code review
Remove this line.

https://codereview.chromium.org/1576093005/diff/1/cr-buildbucket.cfg
File cr-buildbucket.cfg (right):

https://codereview.chromium.org/1576093005/diff/1/cr-buildbucket.cfg#newcode10
cr-buildbucket.cfg:10: name: "master.tryserver.libyuv"
No bucket needed for master.client.libyuv? I notice WebRTC has one for each
master.

https://codereview.chromium.org/1576093005/diff/1/project.cfg
File project.cfg (right):

https://codereview.chromium.org/1576093005/diff/1/project.cfg#newcode4
project.cfg:4: name: "LibYUV"
I dunno about this name.
https://chromium.googlesource.com/libyuv/libyuv/+/master/README.chromium says
"libyuv" (all lowercase) and I believe that's the name that is used everywhere.

[nodir, 2016-01-12 17:46:37]

https://codereview.chromium.org/1576093005/diff/1/codereview.settings
File codereview.settings (right):

https://codereview.chromium.org/1576093005/diff/1/codereview.settings#newcode2
codereview.settings:2: # The LibYuv code review is via WebRtc's code review
On 2016/01/12 17:43:22, kjellander (chromium) wrote:
> Remove this line.

Done.

https://codereview.chromium.org/1576093005/diff/1/cr-buildbucket.cfg
File cr-buildbucket.cfg (right):

https://codereview.chromium.org/1576093005/diff/1/cr-buildbucket.cfg#newcode10
cr-buildbucket.cfg:10: name: "master.tryserver.libyuv"
On 2016/01/12 17:43:22, kjellander (chromium) wrote:
> No bucket needed for master.client.libyuv? I notice WebRTC has one for each
> master.

what will trigger builds on client bucket?

https://codereview.chromium.org/1576093005/diff/1/project.cfg
File project.cfg (right):

https://codereview.chromium.org/1576093005/diff/1/project.cfg#newcode4
project.cfg:4: name: "LibYUV"
On 2016/01/12 17:43:22, kjellander (chromium) wrote:
> I dunno about this name.
> https://chromium.googlesource.com/libyuv/libyuv/+/master/README.chromium says
> "libyuv" (all lowercase) and I believe that's the name that is used
everywhere.

Done.

[kjellander_chromium, 2016-01-12 18:07:56]

https://codereview.chromium.org/1576093005/diff/1/cr-buildbucket.cfg
File cr-buildbucket.cfg (right):

https://codereview.chromium.org/1576093005/diff/1/cr-buildbucket.cfg#newcode10
cr-buildbucket.cfg:10: name: "master.tryserver.libyuv"
On 2016/01/12 17:46:37, nodir wrote:
> On 2016/01/12 17:43:22, kjellander (chromium) wrote:
> > No bucket needed for master.client.libyuv? I notice WebRTC has one for each
> > master.
> 
> what will trigger builds on client bucket?

Only the Gitiles poller (but that's the same for WebRTC as well).

[nodir, 2016-01-12 18:16:56]

https://codereview.chromium.org/1576093005/diff/1/cr-buildbucket.cfg
File cr-buildbucket.cfg (right):

https://codereview.chromium.org/1576093005/diff/1/cr-buildbucket.cfg#newcode10
cr-buildbucket.cfg:10: name: "master.tryserver.libyuv"
On 2016/01/12 18:07:56, kjellander (chromium) wrote:
> On 2016/01/12 17:46:37, nodir wrote:
> > On 2016/01/12 17:43:22, kjellander (chromium) wrote:
> > > No bucket needed for master.client.libyuv? I notice WebRTC has one for
each
> > > master.
> > 
> > what will trigger builds on client bucket?
> 
> Only the Gitiles poller (but that's the same for WebRTC as well).

Buildbucket is a transport to buildbot for those running outside master process,
such as git-cl-try, CQ and Rietveld.
GitilesPoller is running inside buildbot process and schedules builds directly
to buildbot.

[kjellander_chromium, 2016-01-12 20:01:17]

still lgtm

https://codereview.chromium.org/1576093005/diff/1/cr-buildbucket.cfg
File cr-buildbucket.cfg (right):

https://codereview.chromium.org/1576093005/diff/1/cr-buildbucket.cfg#newcode10
cr-buildbucket.cfg:10: name: "master.tryserver.libyuv"
On 2016/01/12 18:16:56, nodir wrote:
> On 2016/01/12 18:07:56, kjellander (chromium) wrote:
> > On 2016/01/12 17:46:37, nodir wrote:
> > > On 2016/01/12 17:43:22, kjellander (chromium) wrote:
> > > > No bucket needed for master.client.libyuv? I notice WebRTC has one for
> each
> > > > master.
> > > 
> > > what will trigger builds on client bucket?
> > 
> > Only the Gitiles poller (but that's the same for WebRTC as well).
> 
> Buildbucket is a transport to buildbot for those running outside master
process,
> such as git-cl-try, CQ and Rietveld.
> GitilesPoller is running inside buildbot process and schedules builds directly
> to buildbot. 

Thanks for explaining. That's how I thought it worked yes. So the additional
buckets for WebRTC are unnecessary as long as only GitilesPoller is used?
Anyway, this should be fine for libyuv then.

[nodir, 2016-01-12 20:05:21]

On 2016/01/12 20:01:17, kjellander (chromium) wrote:
> still lgtm
> 
> https://codereview.chromium.org/1576093005/diff/1/cr-buildbucket.cfg
> File cr-buildbucket.cfg (right):
> 
> https://codereview.chromium.org/1576093005/diff/1/cr-buildbucket.cfg#newcode10
> cr-buildbucket.cfg:10: name: "master.tryserver.libyuv"
> On 2016/01/12 18:16:56, nodir wrote:
> > On 2016/01/12 18:07:56, kjellander (chromium) wrote:
> > > On 2016/01/12 17:46:37, nodir wrote:
> > > > On 2016/01/12 17:43:22, kjellander (chromium) wrote:
> > > > > No bucket needed for master.client.libyuv? I notice WebRTC has one for
> > each
> > > > > master.
> > > > 
> > > > what will trigger builds on client bucket?
> > > 
> > > Only the Gitiles poller (but that's the same for WebRTC as well).
> > 
> > Buildbucket is a transport to buildbot for those running outside master
> process,
> > such as git-cl-try, CQ and Rietveld.
> > GitilesPoller is running inside buildbot process and schedules builds
directly
> > to buildbot. 
> 
> Thanks for explaining. That's how I thought it worked yes. So the additional
> buckets for WebRTC are unnecessary as long as only GitilesPoller is used?
> Anyway, this should be fine for libyuv then.

Yes

[nodir, 2016-01-12 20:07:21]

Description was changed from

==========
Create master.tryserver.libyuv bucket

Also README.md, OWNERS and other std files

R=kjellander@chromium.org
BUG=551062
==========

to

==========
Create master.tryserver.libyuv bucket

Also README.md, OWNERS and other std files

R=kjellander@chromium.org
BUG=551062

Committed: 1773ecdd764266cfe93521bb5e3a3e6f42dedafd
==========

[nodir, 2016-01-12 20:07:22]

Committed patchset #2 (id:20001) manually as
1773ecdd764266cfe93521bb5e3a3e6f42dedafd (presubmit successful).