-
Notifications
You must be signed in to change notification settings - Fork 228
CI: Separate jobs to build and deploy documentation #3767
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
base: main
Are you sure you want to change the base?
Conversation
00ab410
to
689ee4c
Compare
689ee4c
to
78bf149
Compare
One disadvantage is that, the deployment job starts only after all the three matrix jobs in the Considering that the Windows job takes much longer (~ 7 minutes) than the Linux/macOS jobs (~ 3 minutes), maybe having separate jobs is not a good idea? |
Let's keep it in a single job now. Will revisit this PR later. |
eef1a0b
to
c0b595c
Compare
527a796
to
6c5be6d
Compare
Similar to #3742, it makes more sense to build and deploy documentation in separate jobs.
This PR splits the
ci_docs.yaml
workflow into two jobs:build-docs
: Build the documentation and upload the HTML files as artifactsdeploy-docs
: Download the HTML artifacts and deploy to the gh-pages branchThe HTML artifacts can also be uploaded as release assets when making a release. It will be done in separate PRs (addressing #3731).