step 1 is not necessary, it sounds like online has autoprovisioning enabled now, so you don't need to instantiate jenkins yourself.  Cesar will be replying w/ into about how online needs to be updated to make this work properly.

The cluster configuration needs to be updated to use the template named "jenkins" (or whatever it is called in the online environment) instead of "jenkins-ephemeral". Instructions here: https://docs.openshift.org/latest/install_config/configuring_pipeline_execution.html

Vu is working with Ops to get this addressed in the configuration.

This is now configured in devpreview INT

JenkinsPipeline build can be successfully triggered in INT.

Master config:
...
jenkinsPipelineConfig:
  templateName: jenkins-persistent
...

Create jenkinsPipeLine bc and start build:
$ oc new-app https://raw.githubusercontent.com/openshift/origin/master/examples/jenkins/pipeline/samplepipeline.json

$ oc start-build sample-pipeline
build "sample-pipeline-1" started

$ oc get pod
NAME                             READY     STATUS      RESTARTS   AGE
jenkins-1-m4rlk                  1/1       Running     0          7m
mongodb-1-kmtoj                  1/1       Running     0          7m
nodejs-mongodb-example-1-build   0/1       Completed   0          2m
nodejs-mongodb-example-1-t1k8u   1/1       Running     0          50s

$ oc get build
NAME                       TYPE              FROM          STATUS     STARTED         DURATION
nodejs-mongodb-example-1   Source            Git@fb4415c   Complete   3 minutes ago   1m19s
sample-pipeline-1          JenkinsPipeline                 Complete   6 minutes ago   4m34s

Move to verified. Thanks!