ci(doc): add doc build caching #2342
Open
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## master #2342 +/- ##
=======================================
Coverage 84.09% 84.10%
=======================================
Files 91 91
Lines 10522 10529 +7
=======================================
+ Hits 8849 8855 +6
- Misses 1673 1674 +1 |
PProfizi
commented
Jun 5, 2025
|
The documentation for this pull request will be available at https://dpf.docs.pyansys.com/pull/2342. Please allow some time for the documentation to be deployed. |
…] extension" This reverts commit 544630e.
|
Some tests with 'continue-on-error: true' have failed:
Created by continue-on-error-comment |
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 goal is to accelerate doc building using cached Sphinx build files whenever possible.
The caching logic is to retrieve, by order of priority:
The cache should only contain files where Sphinx can detect changes:
The cache could be based on the hash of a lock file, as differences in installed
graphicsdependencies could result in changes despite Sphinx not detecting changes in the actual scripts.That means however the cache will only work if no changes in dependencies.