Skip to content
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

CONTRIB: Automate update of API documentation #10333

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

tvegas1
Copy link
Contributor

@tvegas1 tvegas1 commented Nov 26, 2024

What?

Move steps from wiki to script to help avoid/fix mistakes. Wiki will need to be updated.

How?

./contrib/api_update.sh upstream/v1.18.x
git push upstream HEAD:refs/heads/gh-pages.v1.18.0-rc1

@tvegas1 tvegas1 force-pushed the automate_update_api_doc branch from 4507466 to 9106af0 Compare November 26, 2024 14:50
rakhmets
rakhmets previously approved these changes Nov 28, 2024
contrib/api_update.sh Show resolved Hide resolved

set -x

sudo yum -y install doxygen doxygen-latex
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe also add support for ubuntu/debian?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

@tvegas1 tvegas1 force-pushed the automate_update_api_doc branch from c808e5f to e2261e3 Compare November 29, 2024 10:23
@tvegas1
Copy link
Contributor Author

tvegas1 commented Jan 15, 2025

@yosefe, can you please have a look?

@tvegas1
Copy link
Contributor Author

tvegas1 commented Jan 23, 2025

@brminich @yosefe , could you please review, this was used to generate latest docs.

brminich
brminich previously approved these changes Jan 23, 2025
@@ -0,0 +1,56 @@
#!/usr/bin/env bash
#
# Copyright (c) 2024 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# Copyright (c) 2024 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
# Copyright (c) 2025 NVIDIA CORPORATION & AFFILIATES. All rights reserved.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

brminich
brminich previously approved these changes Jan 23, 2025
# See file LICENSE for terms.
#

set -euE
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shall we pass it in the shebang?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed


set -euE

branch="${1?Specify remote version to use like "upstream/v1.18.x"}"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

need to document command line params

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

Comment on lines +30 to +49
if grep -qi "debian\|ubuntu" /etc/os-release 2>/dev/null
then
sudo apt-get -y install doxygen doxygen-latex
else
sudo yum -y install doxygen doxygen-latex
fi

git checkout "$branch"
git clean -xdf
git reset --hard

./autogen.sh
./configure --with-docs-only
make docs

git checkout "$remote"/gh-pages
mkdir api/"$version"
ln -snf "$version" api/latest

cp docs/doxygen-doc/ucx.pdf "api/$version/ucx-$version.pdf"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seems we want to do this step as part of release pipeline when a GA version is tagged?
and run it on a docker image that has latest doxygen, latex, etc.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

as discussed, will address comment, add can be done in secondary commit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants