anchor.diff:  
   [[override-builder-image-scripts]]
   
  -=== Override Builder Image Scripts
  +=== Overriding Builder Image Scripts
   
   You can override the *_assemble_*, *_run_*, and *_save-artifacts_*
   link:../creating_images/s2i.html#s2i-scripts[S2I scripts] provided by the
  
positive.code: ----
  ====
  
  In practice you may want to use an environment variable for the file location
  so that the specific file to be downloaded can be customized via an environment
  variable defined on the `BuildConfig` rather than updating the assemble script or
  `Dockerfile`.
  
  You could choose between a different ways of defining environment variables:
  
  - link:#environment-files[put into the `.sti/environment` file] (only for a `*Source*` build strategy)
  - link:#buildconfig-environment[set in `*BuildConfig*`]
  - link:../cli_reference/basic_cli_operations.html#build-and-deployment-cli-operations[provide explicitly with `*oc start-build --env*`]
    (only for builds that are triggered manually)
  
negative.code: |Source URL for the build
  |===
  
  [[using-external-artifacts]]
  == Using External Artifacts During a Build
  
  It is not recommended to store binary files in a source repository. Therefore,
  you may find it necessary to define a build which pulls additional files (such
  as Java *_.jar_* dependencies) during the build process. How this is done
  depends on the build strategy you are using.
  
  For a `*Source*` build strategy, you must put appropriate shell commands into
  the *_assemble_* script:
  
  .*_.sti/bin/assemble_* File
  ====
  
  [source,bash]
  