anchor.diff:  ----
   ====
   
  -Once you have the `*Secret*` created, you can add a `PushSecretName` field into
  +Once you have the `*Secret*` created, you can add a `PushSecret` field into
   `Output` section inside the `BuildConfig` and set it to the name of the
   `*Secret*` that you created, in this case `*dockerhub*`.
  +
  +```
  +"parameters": {
  +  "output": {
  +    "to": {
  +      "name": "private-image"
  +    },
  +    "pushSecret":{
  +      "name":"dockerhub"
  +    }
  +  }
  +}
  +```
  +
  +For pulling the builder Docker image from a private Docker registry, you have to specify
  +the `PullSecret` field, which is part of the build strategy definition:
  +
  +```
  +{
  +  "strategy": {
  +    "stiStrategy": {
  +      "from": {
  +        "kind": "DockerImage",
  +        "name": "docker.io/user/private_repository"
  +       },
  +       "pullSecret": {
  +        "name": "dockerhub"
  +       },
  +    },
  +    "type": "STI"
  +  }
  +}
  +```
   
   [#using-private-repositories-for-builds]
   == Using private repositories for builds
  
positive.code: Custom builds are the most sophisticated version of builds, allowing developers to define a builder image which is responsible for the entire process of the build. The custom builder image is a plain Docker image within which the author embeds the logic of the desired build process, such as building RPMs or building
  base Docker images.
  
  [#using-docker-credentials-for-pushing-images]
  == Using Docker Credentials for Pushing Images
  
  In case you want to push the output image into private Docker registry that
  requires authentication or Docker Hub, you must supply a `.dockercfg` file
  with valid Docker registry credentials.
  
  The *_.dockercfg_* JSON file usually exists in your home directory and has
  following format:
  
negative.code:       "git": {
          "uri": "git@repository.com:user/app.git"
        },
        "sourceSecret": {
          "name": "scmsecret"
        },
        "type": "Git"
      },
      "strategy": {
  