anchor.diff:  utility (the `tar` command available in `*$PATH*`) and the command line
   interpreter (the `/bin/sh` command); this allows your image to use the fastest
   possible build path. If the `tar` or `/bin/sh` command is not available, the
  -`sti build` process is forced to automatically perform an additional Docker build
  +`s2i build` process is forced to automatically perform an additional Docker build
   to put both the sources and the scripts inside the image, and only then run the
  -usual `sti build` procedure.
  +usual `s2i build` procedure.
   
   See the following diagram for the basic S2I build workflow:
   
  
positive.code: #!/bin/bash
  
  # restore build artifacts
  if [ "$(ls /tmp/sti/artifacts/ 2>/dev/null)" ]; then
      mv /tmp/sti/artifacts/* $HOME/.
  fi
  
  # move the application source
  mv /tmp/sti/src $HOME/src
  
  # build application artifacts
  pushd ${HOME}
  
negative.code: 
  . Build the image.
  . Run the image to verify the *_usage_* script.
  . Run `s2i build` to verify the *_assemble_* script.
  . Run `s2i build` again to verify the *_save-artifacts_* and *_assemble_* scripts save and restore artifacts functionality. (optional)
  . Run the image to verify the test application is working.
  
  See the link:s2i_testing.html[Testing S2I Images] topic for more information.
  