anchor.diff:  Manually cancel a build using the web console, or with the following CLI command:
   
   ----
  -$ oc cancel-build <buildName>
  +$ oc cancel-build <build_name>
   ----
   
   [[viewing-build-details]]
   == Viewing Build Details
  -View build details using the web console, or with the following CLI command:
  -
  -----
  -$ oc describe build <buildName>
  -----
  -
  -The output of the describe command includes information such the build source, strategy and output destination.
  -If the build uses the Docker or Source strategy, it will also include information about the source revision used
  -for the build: commit ID, author, committer, and message.
  +
  +You can view build details using the web console or the following CLI command:
  +
  +----
  +$ oc describe build <build_name>
  +----
  +
  +The output of the `describe` command includes details such as the build source,
  +strategy, and output destination.
   
   [[accessing-build-logs]]
   
   == Accessing Build Logs
  -To allow access to build logs, use one of the following commands:
  -
  -----
  -// Stream the logs using the build directly
  -$ oc logs -f build/<buildName>
  -// Stream the logs of the latest build for build config
  -$ oc logs -f bc/<buildConfigName>
  -// Return the logs of the first build for build config
  -$ oc logs --version=1 bc/<buildConfigName>
  +You can access build logs using the web console or the CLI.
  +
  +To stream the logs using the build directly:
  +
  +----
  +$ oc logs -f build/<build_name>
  +----
  +
  +To stream the logs of the latest build for a build configuration:
  +
  +----
  +$ oc logs -f bc/<buildconfig_name>
  +----
  +
  +To return the logs of a given version build for a build configuration:
  +
  +----
  +$ oc logs --version=<number> bc/<buildconfig_name>
   ----
   
   *Log Verbosity*
  
positive.code: ----
  ====
  
  == Build Output
  
  Docker and source builds will result in a new Docker image getting created. The image is
  then pushed to the registry specified in the `*output*` section of the `*Build*` specification.
  If the output kind is `*ImageStreamTag*` then the image will be pushed to the OpenShift registry
  and tagged in the specified ImageStream. If the output is of type `*DockerImage*` then the
  name of the output reference will be used as a Docker push specification. The specification may contain
  a registry or will default to DockerHub if no registry is specified. If the output section of the
  build specification is empty, then the image will not be pushed at the end of the build.
  
  .Output to an ImageStreamTag
  ====
  
negative.code: ----
  ====
  
  [[output-image-environment-variables]]
  === Output Image Environment Variables
  
  Docker and Source builds set the following environment variables on output
  images:
  
  [options="header"]
  |===
  
  |Variable |Description
  
  |`*OPENSHIFT_BUILD_NAME*`
  |Name of the build
  
  |`*OPENSHIFT_BUILD_NAMESPACE*`
  |Namespace of the build
  
  |`*OPENSHIFT_BUILD_SOURCE*`
  |The source URL of the build
  
  |`*OPENSHIFT_BUILD_REFERENCE*`
  |The Git reference used in the build
  
  |`*OPENSHIFT_BUILD_COMMIT*`
  |Source commit used in the build
  |===
  
  [[output-image-labels]]
  === Output Image Labels
  
  Docker and Source builds set the following labels on output images:
  
  [options="header"]
  |===
  
  |Label |Description
  
  |*io.openshift.build.commit.author*
  |Author of the source commit used in the build
  
  |*io.openshift.build.commit.date*
  |Date of the source commit used in the build
  
  |*io.openshift.build.commit.id*
  |Hash of the source commit used in the build
  
  |*io.openshift.build.commit.message*
  |Message of the source commit used in the build
  
  |*io.openshift.build.commit.ref*
  |Branch or reference specified in the source
  
  |*io.openshift.build.source-location*
  |Source URL for the build
  |===
  