WEB: Fix deployment of the website #28529
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| @@ -171,7 +171,7 @@ jobs: | |||
| eq(variables['Build.SourceBranch'], 'refs/heads/master')) | |||
|
|
|||
| - script: | | |||
| cd doc/build/html | |||
| cd to_deploy | |||
There was a problem hiding this comment.
Where is to_deploy defined?
There was a problem hiding this comment.
It's created here, is the directory where the web and docs is copied together: https://github.com/pandas-dev/pandas/blob/master/azure-pipelines.yml#L136
There was a problem hiding this comment.
Sorry, I apparently wasn't on master (so my grep didn't find it).
proost
pushed a commit
to proost/pandas
that referenced
this pull request
Dec 19, 2019
proost
pushed a commit
to proost/pandas
that referenced
this pull request
Dec 19, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The master build is broken [1], because one directory wasn't updated in #28497 (the step only runs in master builds and not PR builds, so couldn't be detected).
This updates the directory, the deployment should work again.