Description of problem: > $ oc new-app --docker-image='openshift/mysql-55-centos7' --code='https://github.com/openshift/ruby-hello-world' -l 'app=hi' --env='MYSQL_USER=root,MYSQL_PASSWORD=test,MYSQL_DATABASE=test' > ... > A build was created - you can run `oc start-build ruby-hello-world` to start it. > ... The build starts automatically and user does not have to run the suggested command. If user runs the suggested command, a second build is started. I think this advice needs to be removed. Version-Release number of selected component (if applicable): 1.0.2
*** Bug 1252647 has been marked as a duplicate of this bug. ***
Fixed in https://github.com/openshift/origin/pull/4218
Commit pushed to master at https://github.com/openshift/origin https://github.com/openshift/origin/commit/3319f9f74b4ca46d65fcdd0ea30c7aa4b7dac12d Bug 1248464 - fixes message about builds created by new-app
may we have a test build?
Test on latest origin env, got message (Build "ruby-hello-world" created and started - you can run `oc status` to check the progress.) when create the app. oc v1.0.4-330-gcca4a42 kubernetes v1.1.0-alpha.0-1605-g44c91b1 # oc new-app --docker-image='openshift/mysql-55-centos7' --code='https://github.com/openshift/ruby-hello-world' -l 'app=hi' --env='MYSQL_USER=root,MYSQL_PASSWORD=test,MYSQL_DATABASE=test' imagestreams/mysql-55-centos7 deploymentconfigs/mysql-55-centos7 imagestreams/ruby-20-centos7 imagestreams/ruby-hello-world buildconfigs/ruby-hello-world deploymentconfigs/ruby-hello-world services/mysql-55-centos7 services/ruby-hello-world Build "ruby-hello-world" created and started - you can run `oc status` to check the progress. Service "mysql-55-centos7" created at 172.30.70.83 with port mappings 3306. Service "ruby-hello-world" created at 172.30.39.72 with port mappings 8080. Run 'oc status' to view your app. Issue have been fixed, Move bug to verified.