You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: azure-pipelines.yml
+41-41
Original file line number
Diff line number
Diff line change
@@ -122,48 +122,48 @@ jobs:
122
122
- script: |
123
123
source activate pandas-dev
124
124
# Next we should simply have `doc/make.py --warnings-are-errors`, everything else is required because the ipython directive doesn't fail the build on errors (https://github.com/ipython/ipython/issues/11547)
125
-
doc/make.py --warnings-are-errors | tee sphinx.log ; SPHINX_RET=${PIPESTATUS[0]}
125
+
doc/make.py --num-jobs=2 --warnings-are-errors | tee sphinx.log ; SPHINX_RET=${PIPESTATUS[0]}
# For `InstallSSHKey@0` to work, next steps are required:
146
-
# 1. Generate a pair of private/public keys (i.e. `ssh-keygen -t rsa -b 4096 -C "[email protected]"`)
147
-
# 2. Go to "Library > Secure files" in the Azure Pipelines dashboard: https://dev.azure.com/pandas-dev/pandas/_library?itemType=SecureFiles
148
-
# 3. Click on "+ Secure file"
149
-
# 4. Upload the private key (the name of the file must match with the specified in "sshKeySecureFile" input below, "pandas_docs_key")
150
-
# 5. Click on file name after it is created, tick the box "Authorize for use in all pipelines" and save
151
-
# 6. The public key specified in "sshPublicKey" is the pair of the uploaded private key, and needs to be set as a deploy key of the repo where the docs will be pushed (with write access): https://github.com/pandas-dev/pandas-dev.github.io/settings/keys
# # For `InstallSSHKey@0` to work, next steps are required:
146
+
# # 1. Generate a pair of private/public keys (i.e. `ssh-keygen -t rsa -b 4096 -C "[email protected]"`)
147
+
# # 2. Go to "Library > Secure files" in the Azure Pipelines dashboard: https://dev.azure.com/pandas-dev/pandas/_library?itemType=SecureFiles
148
+
# # 3. Click on "+ Secure file"
149
+
# # 4. Upload the private key (the name of the file must match with the specified in "sshKeySecureFile" input below, "pandas_docs_key")
150
+
# # 5. Click on file name after it is created, tick the box "Authorize for use in all pipelines" and save
151
+
# # 6. The public key specified in "sshPublicKey" is the pair of the uploaded private key, and needs to be set as a deploy key of the repo where the docs will be pushed (with write access): https://github.com/pandas-dev/pandas-dev.github.io/settings/keys
0 commit comments