There was a recent build failure in the pull request tester, that made me notice that the pre-job cleanup in many of our Jenkins jobs isn't doing the right thing at the moment.

The failure was:
http://build.wiredtiger.com:8080/job/wiredtiger-pull-request-builds/1875/console

The file being complained about was added in a different pull request, that isn't yet merged into develop. The git clean -fdqx in our Jenkins jobs aims to leave the git directory in the same state as if it were cleanly cloned. The clean command is currently run from within the build_posix directory in many of our Jenkins jobs - which means it only applies to files underneath build_posix, where it should apply to all files in the cloned tree (documentation here: https://git-scm.com/docs/git-clean).

We need to fix the jobs so they clean the entire tree, and we should update the Jenkins audit script to catch places where the clean happens from a subdirectory rather than the root.