Skip to content

docs: update docs for changes in noarch builds #714

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.

Sign up for GitHub

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

Open
gforsyth wants to merge 3 commits into
base: main
Choose a base branch
from
Open

docs: update docs for changes in noarch builds #714

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
184dfb8
docs: add note about usage of `rapids-package-name` in reproducing ci
gforsyth Dec 4, 2025
6b18939
docs: add example of using `--noarch` flag with `rapids-get-pr-artifact`
gforsyth Dec 10, 2025
551f16e
update example
gforsyth Dec 12, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
37 changes: 37 additions & 0 deletions resources/github-actions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -457,6 +457,43 @@ source ./ci/use_conda_packages_from_prs.sh
**Note:** By default `rapids-get-pr-artifact` uses the most recent commit from the specified PR.
A commit hash from the dependent PR can be added as an optional 4th argument to pin testing to a specific commit.

**Example 3:** Testing `cudf` with a `noarch` build of `dask-cuda`

```shell
#!/bin/bash
# Copyright (c) 2025, NVIDIA CORPORATION.

# download CI artifacts
DASK_CUDA_CHANNEL=$(RAPIDS_PY_NOARCH_SUFFIX="noarch" rapids-get-pr-artifact dask-cuda 1595 python conda --noarch)

# For `rattler` builds:
#
# Add these channels to the array checked by 'rapids-rattler-channel-string'.
# This ensures that when conda packages are built with strict channel priority enabled,
# the locally-downloaded packages will be preferred to remote packages (e.g. nightlies).
#
RAPIDS_PREPENDED_CONDA_CHANNELS=("${DASK_CUDA_CHANNEL}")

export RAPIDS_PREPENDED_CONDA_CHANNELS

# For tests and `conda-build` builds:
#
# Add these channels to the system-wide conda configuration.
# This results in PREPENDING them to conda's channel list, so
# these packages should be found first if strict channel priority is enabled.
#
for _channel in "${RAPIDS_PREPENDED_CONDA_CHANNELS[@]}"
do
conda config --system --add channels "${_channel}"
done
```

Then copy the following into every script in the `ci/` directory that is doing `conda` installs.

```shell
source ./ci/use_conda_packages_from_prs.sh
```

### Using Wheel CI Artifacts in Other PRs

To use wheels produced by other PRs' CI:
Expand Down
7 changes: 6 additions & 1 deletion resources/reproducing-ci.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -155,7 +155,12 @@ In CI, this process happens transparently.

Local builds lack the context provided by the CI environment and therefore require some user-supplied input in order to ensure that the correct artifacts are downloaded.

Any time the `rapids-download-{conda,wheels}-from-github` command (e.g. [here](https://github.com/rapidsai/cugraph/blob/6200e99714113ea08fef6c8ae05d93c5516e9a13/ci/test_cpp.sh#L11)) is encountered in a local test run, the user will be prompted for any necessary environment variables that are missing.
Any time the `rapids-download-{conda,wheels}-from-github` command (e.g.
[here](https://github.com/rapidsai/cugraph/blob/6200e99714113ea08fef6c8ae05d93c5516e9a13/ci/test_cpp.sh#L11))
or the `rapids-download-from-github "$(rapids-package-name ...)"` command (e.g.
[here](https://github.com/rapidsai/cuxfilter/blob/b9964b157db60a647421bba719a661afb9994a83/ci/test_python.sh#L13))
is encountered in a local test run, the user will be prompted for any necessary
environment variables that are missing.

The screenshot below shows an example.

Expand Down