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: ----
  ====
  
  For more information on how to control which assemble and run script is used by a source bulid,
  see: link:#override-builder-image-scripts[Override Builder Image Scripts]
  
  For a `*Docker*` build strategy you need to modify the `Dockerfile` and invoke
  shell commands with the https://docs.docker.com/engine/reference/builder/#run[`RUN` instruction].
  
  .Excerpt of `Dockerfile`
  ====
  
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]
  