DOCS: Document best-practices for making doctr run only in one build

[choldgraf]

E.g., with after_success only in python == 3.6 builds.

[asmeurer]

Needs to be in script. after_success doesn’t cause the build to fail (there’s a note about this in the readme).

[choldgraf]

gotcha, so then just check for the python version w/in script and add the doctr code after that?

On Mon, Jul 3, 2017 at 1:51 PM Aaron Meurer [email protected] wrote:

Needs to be in script. after_success doesn’t cause the build to fail (there’s a note about this in the readme).

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/drdoctr/doctr/issues/208#issuecomment-312713473, or mute the thread https://github.com/notifications/unsubscribe-auth/ABwSHaaojpsTx9VoTIS0mF60idj_22urks5sKThAgaJpZM4OMf_0 .

[asmeurer]

Or check whatever environment variable you have your docs build set to.

[fredRos]

I'm using this in my code

script:
  # if any line in this section fails, build fails
  - set -e

  # build and run unit tests
  ...
  # build and deploy docs only for one python version and only for changes to master
  - if [[ $TRAVIS_PYTHON_VERSION == 3.6 ]]; then
       pip install doctr;
       make doc;
       doctr deploy . --built-docs doc/_build/;
    fi