-
-
Notifications
You must be signed in to change notification settings - Fork 8.7k
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
[doc] Reference the R doc in sphinx document site. #11166
base: master
Are you sure you want to change the base?
Conversation
The integration is quite primitive. We can expand the integration after #11123 is merged if needed. Thank you @jameslamb for sharing the use of Spark and LightGBM both take a similar approach for document integration with additional customization. |
seems hung, will check again after the cancel is successful. https://app.readthedocs.org/projects/xgboost/builds/26846124/ |
I need some help from @hcho3 after he is back. We might want to cache the R pkgdown result in an S3 bucket, similar to the JVM documents. Building a whole chain of pkgdown dependencies on the RTD worker is not ideal. |
install dir. Restore. system dependencies. Update ubuntu version. work on script.
0adb726
to
dbfa528
Compare
still working in progress, need to upstream a docker image to the ops repo. |
@@ -35,7 +37,35 @@ | |||
release = xgboost.__version__ | |||
|
|||
|
|||
def run_doxygen(): | |||
# Witchcraft alert: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
took me a while to figure out how it works and that the existing code was broken after the CI revamp. Would be great if we could use a package manager like conda to handle R packages instead of spawning out a new CI workflow. Suggestions are welcome.
@david-cortes Please help review the output document: https://xgboost--11166.org.readthedocs.build/en/11166/ when you are available. (many like cc @hcho3 @jameslamb for CI changes, related: dmlc/xgboost-devops#6 I spawned a new CI workflow for building R documents with CUDA failures are not related, not sure what's updated there. Please ignore them for now. |
@@ -10,8 +10,8 @@ numpy | |||
scipy | |||
myst-parser | |||
ray[train] | |||
xgboost_ray |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this fetches an old version of xgboost from pypi.
|
||
cd R-package | ||
MAKEFLAGS=-j$(nproc) Rscript ./tests/helper_scripts/install_deps.R | ||
# Some examples are failing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cc @david-cortes The error message from pkgdown
is not particularly helpful for debugging example failures. I ran the R-package/tests/helper_scripts/run-example.R
, and some examples are failing. I only managed to eliminate some of the failures by checking various dependencies (a lot). Still need some work to fix the remaining.
|
||
if branch == "master": | ||
res = subprocess.run(["git", "rev-parse", "master"], stdout=subprocess.PIPE) | ||
else: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to check release branch?
ops/pipeline/build-r-docs.sh
Outdated
|
||
source ops/pipeline/get-docker-registry-details.sh | ||
|
||
IMAGE_URI=${DOCKER_REGISTRY_URL}/xgb-ci.cpu_build_r_doc:PR-6 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to change this back to main.
I think the core failure is:
Since the vignette is not being built through Also, looks like the TOC requires at least one deeper level: Currently appears to be limited at two. Perhaps something like this would do:
Some suggestions for the pkgdown site:
|
Hmm, not sure. I intentionally kept the navigation bar succinct.
The landing page for the pkgdown site is from the R package README file i believe. We can revise that file.
We add documents all the time, I think it's ok to not have this warning. Otherwise we need to annotate many more new docs.
Yes, I need to add a installation call before the knitr call. Will do it tomorrow. Great to have some initial feedback.
Good catch, need to investigate.
It's the read me file I think? Need to double check, it's hard linked, will change it back to stable if possible. |
If it needs to be hard-coded, guess "latest" is a better choice. But other internal links elsewhere point to the same version that one is currently browsing. |
I think it'd be helpful to have more levels. Especially for the python package docs. |
Found a related issue for the tex rendering r-lib/pkgdown#2704
System dependencies are handled by the docker image.
Will double check. |
I will leave other documentation modifications for future PRs and focus on getting the page to build. |
@hcho3 Do you think it's possible to use a github webhook to trigger readthedocs build, preferably called inside a github action? Currently, the JVM docs (and R docs in this PR) are built by github actions and downloaded by the read the docs build worker. However, there's no existing mechanism to synchronize the two services. As a result, it's necessary to manually trigger a rebuild in RTD to render the latest document. related: |
todos
pkgdown
error due to missing xgboost.