BLD: Build and publish docs (sans API) as part of Travis jobs #6233
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(also fixed caching on py3)
Now that travis is down to 5 minutes #6227, and
doc builds have been accelerated as well #6179, it's possible to include a doc build as part
of our CI process without incurring long build times.
This PR runs the build process in the background so that we parallelize with the I/O
heavy parts of the test suite, the final result is a build that's still much faster then
where we were last week. If no docs were modified by the commit, the doc build
is skipped.
Compiled Docs (without API reference or R section) are pushed immediately to
http://pandas-docs.github.io/pandas-docs-travis/
and can be seen there a few minutes after the CI job is finished following
a commit to master. The version string on the docs is broken,pending #6217.
Here's to shorter cycles 👯 .