Description of problem:
Testing on ose 3.0.1 with latest oc client, when create new app and build from source code, it failed and error information indicating "'ConfigChange': invalid trigger type"


Version-Release number of selected component (if applicable):
Client version:
oc v1.0.5-134-g01b410a (latest)
kubernetes v1.1.0-alpha.0-1605-g44c91b1

Master version:
ose 3.0.1


How reproducible:
Always

Steps to Reproduce:
1. Create some images 
$ oc create -f  origin/examples/image-streams/image-streams-centos7.json
2. Create application using image and code
$ oc new-app --image=ruby --code=git://github.com/openshift/ruby-hello-world 
3. Create new build
$ oc new-build  openshift/ruby-20-centos7 --code=https://github.com/openshift/ruby-hello-world  --name=myruby2 -l app=testruby2

Actual results:
step2:
I0902 16:01:00.609514   14932 newapp.go:355] Image "library/ruby" is a builder, so a repository will be expected unless you also specify --strategy=docker
I0902 16:01:00.609600   14932 newapp.go:403] Using "git://github.com/openshift/ruby-hello-world" as the source for build
imagestreams/ruby-hello-world
Error: BuildConfig "ruby-hello-world" is invalid: triggers[2].type: invalid value 'ConfigChange': invalid trigger type
deploymentconfigs/ruby-hello-world
services/ruby-hello-world

step3:
$ oc new-build  openshift/ruby-20-centos7 --code=https://github.com/openshift/ruby-hello-world  --name=myruby2 -l app=testruby2
I0902 17:41:28.060157    7345 newapp.go:355] Image "openshift/ruby-20-centos7" is a builder, so a repository will be expected unless you also specify --strategy=docker
I0902 17:41:28.061799    7345 newapp.go:403] Using "https://github.com/openshift/ruby-hello-world" as the source for build
imagestreams/ruby-20-centos7
imagestreams/myruby2
Error: BuildConfig "myruby2" is invalid: triggers[2].type: invalid value 'ConfigChange': invalid trigger type

Expected results:
step2 and step3:
application and build should be created successfully

Additional info: