Missed this when moving script around.
Refs #9639

Refs #9639

It is no longer applicable.
Refs #9639

This is never going to work with the parallel nature of ctest so we'll
stick with the script-based approach.
Refs #9639

The driver script for running the sphinx process can now be called by a
user without any special requirements. The main use case will be
running a doctest individually.

It should be noted that even restricting the run to a single file with the
new -R option will actually still cause Sphinx to read every source file
at least once. This is baked in to Sphinx and cannot be avoided. However,
the config pickling does mean that all source files are only read once and
then after this only changed files are reread.
Refs #9639
Refs #

In the case where MantidPlot acts in place of a standard script
interpreter then set any extra arguments after the filename as
sys arguments in the scripting environment, e.g. sys.argv in Python.
Refs #9639

Conflicts:
	Code/Mantid/Build/Jenkins/buildscript
	Code/Mantid/docs/CMakeLists.txt
	Code/Mantid/docs/runsphinx.py.in

Refs #9923

At warning level, the standard Jenkins builds see warnings about
some algorithms not existing and this gives a false impressions that there
are some warnings that need to be taken care of by a developer.
Refs #9923

Refs #9923

Refs #10053