Skip to content

Adding Sphinx Output to CI #7561

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 29 commits into from
Oct 3, 2019
Merged

Conversation

scbedd
Copy link
Member

@scbedd scbedd commented Oct 2, 2019

This is CI only for now. I need to hook up the parts that generate and publish the landing page index, and add the versioning dropdown as part of a template. However, the devs will be able to check their sphinx output.

@adxsdk6
Copy link

adxsdk6 commented Oct 2, 2019

Can one of the admins verify this patch?

scbedd added 2 commits October 2, 2019 12:47
…he artifact to a single location for artifact publishing. time for CI adjustments!
@scbedd scbedd merged commit 7ef04a6 into Azure:master Oct 3, 2019
YijunXieMS pushed a commit to YijunXieMS/azure-sdk-for-python that referenced this pull request Oct 9, 2019
* support for single package site gen using tox. tox -e sphinx

* updating manifest files to include tests in the source distribution. this means that the examples will also be renderable on docs.ms

* Added steps to CI to generate documentation for targeted servicedirectory
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants