anchor.diff:  
   === Dockerfile Path
   
  -Docker builds normally use a Dockerfile named *_Dockerfile_*, located at the root
  -of the context (identified by the `*BuildConfig.spec.source.contextDir*` field).
  -The `*dockerfilePath*` field allows the build to use a different path to locate your Dockerfile.
  -The path must be relative to the `*BuildConfig.spec.source.contextDir*` field.
  -It could be just a different name for your Dockerfile (*_MyDockerfile_* for example),
  -or a path to a Dockerfile in a subdirectory (*_dockerfiles/app1_* for example):
  +By default, Docker builds use a Dockerfile (named *_Dockerfile_*) located at the
  +root of the context specified in the `*BuildConfig.spec.source.contextDir*`
  +field.
  +
  +The `*dockerfilePath*` field allows the build to use a different path to
  +locate your Dockerfile, relative to the `*BuildConfig.spec.source.contextDir*`
  +field. It can be simply a different file name other than the default
  +*_Dockerfile_* (for example, *_MyDockerfile_*), or a path to a Dockerfile in a
  +subdirectory (for example, *_dockerfiles/app1/_*):
   
   ====
   
  
positive.code: strategy:
    type: Docker
    dockerStrategy:
      dockerfilePath: dockerfiles/app1
  ----
  ====
  
  
negative.code: Additional files can be provided to the build process via images.  Input
  images are referenced in the same way the `From` and `To` image targets
  are defined.  This means both docker images and image stream
  tags can be referenced.  In conjunction with the image, you must provide one or
  more path pairs to indicate the path of the files/directories to copy out of the
  image and the destination to place them in the build context.
  
  