kou commented on pull request #167: URL: https://github.com/apache/arrow-site/pull/167#issuecomment-984027433
I didn't touch `WARN_AS_ERROR` and get any error. What warnings are you faced? Did you fix them in master? It seems that there are no Doxygen related warnings in the latest docs job: https://dev.azure.com/ursacomputing/crossbow/_build/results?buildId=16538&view=logs&j=0da5d1d9-276d-5173-c4c4-9d4d4ed14fdb&t=d9b15392-e4ce-5e4c-0c8c-b69645229181&l=21283 I used `post-09-docs.sh` but needed to update it: ```diff @@ -34,20 +34,32 @@ release_tag="apache-arrow-${version}" branch_name=release-docs-${version} pushd "${ARROW_SITE_DIR}" -git checkout asf-site +git fetch --all --prune --tags --force -j$(nproc) +git checkout . +git branch -D asf-site || : +git checkout -b asf-site origin/asf-site +git rebase apache/asf-site +git branch -D ${branch_name} || : git checkout -b ${branch_name} +versioned_paths=() +for versioned_path in docs/*.0/; do + versioned_paths+=(${versioned_path}) +done rm -rf docs/* +git checkout "${versioned_paths[@]}" popd pushd "${ARROW_DIR}" git checkout "${release_tag}" -UBUNTU=20.10 archery docker run \ +archery docker run \ -v "${ARROW_SITE_DIR}/docs:/build/docs" \ -e ARROW_DOCS_VERSION="${version}" \ ubuntu-docs +git checkout - + : ${PUSH:=1} if [ ${PUSH} -gt 0 ]; then pushed "${ARROW_SITE_DIR}" + sudo chown -R ${USER}: docs || : # For Linux + git checkout docs/c_glib/index.html ``` One of the problems in `post-09-docs.sh` is the past versions of docs as you said. But there are mote problems such as https://github.com/apache/arrow/pull/11815 . I want to avoid building docs on local. I want to build docs in CI and just use built docs like our packaging tasks. I'm working on this. I'll open a pull request to update `post-09-docs.sh` in the work. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
