User tools for RAPIDS GitHub Actions workflows.
This tools repo can be installed from GitHub directly with git clone or wget commands. Examples:
- name: Download gha-tools with git clone
run: |
git clone https://github.com/rapidsai/gha-tools.git -b main /tmp/gha-tools
echo "/tmp/gha-tools/tools" >> "${GITHUB_PATH}"
- name: Download gha-tools release tarball with wget
run: |
wget https://github.com/rapidsai/gha-tools/releases/latest/download/tools.tar.gz -O - | tar -xz -C /usr/local/bin
In gha-tools we introduced some variable naming conventions:
RAPIDS_*
GITHUB_*
that are defined by GitHub ActionsList of variables that have had a RAPIDS_*
prefix added, which should be reflected by consumers switching from gpuci-tools to gha-tools:
CONDA_EXE
, CONDA_TOKEN
, CONDA_UPLOAD_LABEL
-> RAPIDS_CONDA_EXE
, RAPIDS_CONDA_TOKEN
, RAPIDS_CONDA_UPLOAD_LABEL
MAMBA_BIN
-> RAPIDS_MAMBA_BIN
PY_VER
-> RAPIDS_PY_VERSION
BUILD_TYPE
-> RAPIDS_BUILD_TYPE
GH_TOKEN
-> RAPIDS_GH_TOKEN
In GitHub Actions, the default secret GITHUB_TOKEN can be used by setting:
env:
RAPIDS_GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
This repo replaces rapidsai/gpuci-tools. All scripts called gpuci_*
, configured with GPUCI_*
env vars, are now called rapids-*
with the equivalent RAPIDS_*
env vars
The gpuci_*
tools in this project are wrappers around the new tools for backwards compatibility:
rapids-*
equivalentsGPUCI_*
env vars to the new RAPIDS_*
equivalentsSome enhancements have been made to the S3 tools for interacting with downloads.rapids.ai:
rapids-upload-wheels-to-s3
and rapids-download-wheels-from-s3
rapids-upload-to-s3
directlyhttps://downloads.rapids.ai/...
URL in the logs for conveniencerapids-package-name
takes a package type and generates the name (e.g. conda_cpp
-> rmm_conda_cpp_x86_64.tar.gz
)See CONTRIBUTING.md for instructions on how to test these scripts locally.