Add Build watch support

They're all wrong.  No one should be doing any filtering logic in REST on watches.  The label and field selectors should be passed directly into the etcd registry.  Only the etcd registry should know about how to filter watches.

@derekwaynecarr since we were talking about this the other day.


> On Oct 30, 2014, at 9:30 AM, Dan Mace <notifications@github.com> wrote:
> 
> In pkg/build/registry/build/rest.go:
> 
> > @@ -98,3 +99,15 @@ func (r *REST) Update(ctx kubeapi.Context, obj runtime.Object) (<-chan runtime.O
> >  		return build, nil
> >  	}), nil
> >  }
> > +
> > +// Watch begins watching for new, changed, or deleted Builds.
> > +func (s *REST) Watch(ctx kubeapi.Context, label, field labels.Selector, resourceVersion string) (watch.Interface, error) {
> > +	return s.registry.WatchBuilds(resourceVersion, func(build *api.Build) bool {
> I'm not sure what you're referring to here. This is following the exact same pattern used for all the other watch implementations we have. Clarify?
> 
> —
> Reply to this email directly or view it on GitHub.