anchor.diff:  ====
   
   [[other-authentication]]
  -==== Other
  +===== Other
   
   In case the cloning of your application is dependent on a `CA certificate`, `.gitconfig`
   file or both, you can create a secret that contains them, add it to the builder service
  
positive.code: 
  [[image-source]]
  
  == Image Source
  
  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
  
negative.code: ----
  ====
  
  [[build-inputs]]
  == Build Inputs
  
  There are several ways to provide content for builds to operate on. In order of precedence:
  
  * Inline Dockerfile definitions
  * Content extracted from existing images
  * Git repositories
  * Binary inputs
  
  These can be combined into a single build. As the inline Dockerfile takes precedence, it can overwrite any other file named Dockerfile provided by another input. Binary input and Git repository are mutually exclusive inputs.
  
  When the build is run, a working directory is constructed and all input content is placed in the working directory (e.g. the input git repository is cloned into the working directory, files specified from input images are copied into the working directory using the target path).  Next the build process will `*cd*` into the `*contextDir*` if one is defined.  Then the inline `*Dockerfile*` (if any) is written to the current directory.  Last, the content from the current directory will be provided to the build process for reference by the `*Dockerfile*`, `*assemble*` script, or custom builder logic.  This means any input content that resides outside the `*contextDir*` will be ignored by the build.
  
  Here is an example of a source definition that includes multiple input types and an explanation of how they are combined.  For more details
  on how each input type is defined, see the specific sections for each input type.
  
  ====
  [source,yaml]
  ----
  source:
    git:
      uri: https://github.com/openshift/ruby-hello-world.git <1>
    images: 
    - from: 
        kind: ImageStreamTag
        name: myinputimage:latest
        namespace: mynamespace
      paths: 
      - destinationDir: app/dir/injected/dir <2>
        sourcePath: /usr/lib/somefile.jar
    contextDir: "app/dir" <3>
    dockerfile: "FROM centos:7\nRUN yum install -y httpd" <4>
  
  ----
  
  <1> The repository to be cloned into the working directory for the build
  <2> `*/usr/lib/somefile.jar*` from `*myinputimage*` will be stored in `*<workingdir>/app/dir/injected/dir*`
  <3> The working dir for the build will become `*<original_workingdir>/app/dir*`
  <4> A `*Dockerfile*` with this content will be created in `*<original_workingdir>/app/dir*`, overwriting any existing file with that name
  ====
  
  
  [[source-code]]
  
  === Git Repository Source Options
  
  When the `*BuildConfig.spec.source.type*` is `*Git*`, a Git repository is
  required, and an inline Dockerfile is optional.
  