anchor.diff:  |Variable name |Description
   
   |`*JENKINS_PASSWORD*`
  -|Password for the `*admin*` user when using standard Jenkins authentication.  Not applicable when using {product-title} OAuth authentication.
  +|The password for the `*admin*` user when using standard Jenkins authentication.  Not applicable when using {product-title} OAuth authentication.
   
   |`*OPENSHIFT_ENABLE_OAUTH*`
  -|Determines whether the OpenShift Login plugin manages authentication when logging into Jenkins.  Enabled when set to any non-empty value other than "false".
  +|Determines whether the OpenShift Login plug-in manages authentication when logging into Jenkins. Enabled when set to any non-empty value other than "false".
   
   |`*OPENSHIFT_PERMISSIONS_POLL_INTERVAL*`
  -|Specifies in seconds how often the OpenShift Login plugin polls {product-title} for the permissions associated with each user defined in Jenkins.
  +|Specifies in seconds how often the OpenShift Login plug-in polls {product-title} for the permissions associated with each user defined in Jenkins.
   
   |===
   
  +[[jenkins-cross-project-access]]
   === Cross Project Access
   
  -If you are going to run Jenkins somewhere other than as a deployment within your same project you will need to provide an access token to Jenkins to access your project.
  -
  -    1. Identify the service account token secret associated with a service account that has appropriate permissions to access the project Jenkins will need to access::
  -
  -            $ oc describe serviceaccount default
  -
  -        Example output:
  -
  -            Name:       default
  -            Labels:     <none>
  -            Secrets:    {  default-token-uyswp    }
  -                        {  default-dockercfg-xcr3d    }
  -            Tokens:     default-token-izv1u
  -                        default-token-uyswp
  -
  -        In this case the secret name is `default-token-uyswp`
  -
  -    2. Retrieve the token from the secret:
  -
  -            $ oc describe secret <secret name from above> # e.g. default-token-izv1u
  -
  -        Example output:
  -
  -            Name:       default-token-izv1u
  -            Labels:     <none>
  -            Annotations:    kubernetes.io/service-account.name=default,kubernetes.io/service-account.uid=32f5b661-2a8f-11e5-9528-3c970e3bf0b7
  -            Type:   kubernetes.io/service-account-token
  -            Data
  -            ====
  -            ca.crt: 1066 bytes
  -            token:  eyJhbGc..<content cut>....wRA
  -
  -The token field contains the token value Jenkins will need to access the project.
  -
  +If you are going to run Jenkins somewhere other than as a deployment within your same project, you will need to provide an access token to Jenkins to access your project.
  +
  +. Identify the secret for the service account that has appropriate permissions
  +to access the project Jenkins needs to access:
  ++
  +----
  +$ oc describe serviceaccount default
  +Name:       default
  +Labels:     <none>
  +Secrets:    {  default-token-uyswp    }
  +            {  default-dockercfg-xcr3d    }
  +Tokens:     default-token-izv1u
  +            default-token-uyswp
  +----
  ++
  +In this case the secret is named `default-token-uyswp`
  +
  +. Retrieve the token from the secret:
  ++
  +----
  +$ oc describe secret <secret name from above> # e.g. default-token-izv1u
  +Name:       default-token-izv1u
  +Labels:     <none>
  +Annotations:    kubernetes.io/service-account.name=default,kubernetes.io/service-account.uid=32f5b661-2a8f-11e5-9528-3c970e3bf0b7
  +Type:   kubernetes.io/service-account-token
  +Data
  +====
  +ca.crt: 1066 bytes
  +token:  eyJhbGc..<content cut>....wRA
  +----
  +
  +The token field contains the token value Jenkins needs to access the project.
  +
  +[[jenkins-volume-mount-points]]
   === Volume Mount Points
   The Jenkins image can be run with mounted volumes to enable persistent storage for the configuration:
   
   * *_/var/lib/jenkins_* - This is the data directory where Jenkins stores configuration files including job definitions.
   
  +[[jenkins-creating-jenkins-service-from-template]]
   == Creating a Jenkins Service from a Template
   
   xref:../../dev_guide/templates.adoc#dev-guide-templates[Templates] provide parameter fields to
  
positive.code: toc::[]
  
  == Overview
  {product-title} provides a container image for running Jenkins.  This image provides a Jenkins server instance which can be used to set up a basic flow for continuous testing, integration, and delivery.
  
  This image also includes a sample Jenkins job which triggers a new build of a `*BuildConfig*` defined in {product-title}, tests the output of that build, and then on successful build, retags the output to indicate the build is ready for production.
  
  == Versions
  
  {product-title} follows the https://jenkins.io/changelog-stable/[LTS] releases of Jenkins.
  
  == Images
  
  This image comes in two flavors, depending on your needs:
  
negative.code: * hudson.model.View.Delete
  * hudson.scm.SCM.Tag
  
  Users with the `edit` or `view` roles for the {product-title} project have progressively reduced permissions within Jenkins.
  
  For the `view` role:
  
  * hudson.model.Hudson.Read
  * hudson.model.Item.Read
  
  For the `edit` role, in addition to the permissions available to `*view*`:
  
  * hudson.model.Item.Build
  * hudson.model.Item.Configure
  