switch e2e to use sti type builds

Another option is we could allow service substitution for registry in the pod inputs, or allow it to be inferred per project or globally.  We may want the e2e to define the service up it uses when we rebase as well.


> On Nov 2, 2014, at 6:20 PM, Ben Parees <notifications@github.com> wrote:
> 
> In examples/sample-app/application-template.json:
> 
> >          "sourceURI": "git://github.com/openshift/ruby-hello-world.git",
> >          "imageTag": "openshift/origin-ruby-sample:latest",
> > -        "registry": "172.121.17.1:5001"
> > +        "registry": "172.121.17.1:5001",
> not yet, no. but if you want to go down that path, then the registry used in the image name is also fragile (in the pod template). and the IP used in the docker-registry definition (the one that points back the openshift api server) is also fragile.
> 
> We do have plans to allow parameter substitution of more than just ENV which would be one way to make this slightly less fragile.
> 
> —
> Reply to this email directly or view it on GitHub.