title: jenkins Wipe out repository and force clone vs Clean before checkout
body: <p>I am trying to understand the difference between the two options “Wipe out repository and force clone” and “Clean before checkout” for pulling a git repo. Looking at the help section for both options, both seem to have similar functionality and I can't make out the difference. Here's how they look:</p>
  <blockquote>
  <p>Wipe out repository &amp; force clone:</p>
  <blockquote>
  <p>Delete the contents of the workspace before building, ensuring a fully fresh workspace.</p>
  </blockquote>
  <p>Clean before checkout</p>
  <blockquote>
  <p>Clean up the workspace before every checkout by deleting all untracked files and directories, including those which are specified in .gitignore. It also resets all tracked files to their versioned state. This ensures that the workspace is in the same state as if you cloned and checked out in a brand-new empty directory, and ensures that your build is not affected by the files generated by the previous build.</p>
  </blockquote>
  </blockquote>
  <p>I couldn't find any comparison between the two options; neither in Jenkins/GitPlugin wiki, nor in stack overflow, and not even in google. We currently have both options, but we are planning to reduce build time by removing the “Wipe out repository and force clone” option. But I don't want to break any functionality while doing this. Please explain the difference if you're sure. Thanks in advance :)</p>