anchor.diff:  [[using-the-jenkins-kubernetes-plug-in-to-run-jobs]]
   == Using the Jenkins Kubernetes Plug-in to Run Jobs
   
  -The official OpenShift Jenkins image includes the pre-installed
  +The official {product-title} Jenkins image includes the pre-installed
   https://wiki.jenkins-ci.org/display/JENKINS/Kubernetes+Plugin[Kubernetes
   plug-in] that allows Jenkins slaves to be dynamically provisioned on multiple
  -Docker hosts using Kubernetes and OpenShift.
  +Docker hosts using Kubernetes and {product-title}.
   
   The Jenkins image entrypoint also provides auto-discovery and auto-configuration
   of the Kubernetes plug-ins by scanning the project Jenkins is deployed in for
  
positive.code: 
  * `jenkins-persistent` uses a persistent volume store. Data survives a pod
  restart. To use a persistent volume store, the cluster administrator must
  define a persistent volume pool in the OpenShift deployment.
  
  Once selected, you must link:../../dev_guide/templates.html#creating-resources-from-a-template[instantiate] the template to be able to use Jenkins.
  
  [[jenkins-as-s2i-builder]]
  == Using Jenkins as a Source-To-Image builder
  
  To customize the official OpenShift Jenkins image, you have two options:
  
  * Use Docker layering.
  * Use the image as a Source-To-Image builder, described here.
  
negative.code: 
  Alternatively, you can use
  https://github.com/openshift/origin/blob/master/examples/jenkins-master/jenkins-slave-template.json[a
  provided {product-title} template] to convert an existing image stream to a Jenkins
  slave.
  
  == Tutorial
  