Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
4 changes: 2 additions & 2 deletions .github/workflows/build.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ concurrency:
jobs:
wheel-build:
secrets: inherit
uses: rapidsai/shared-workflows/.github/workflows/wheels-build.yaml@branch-25.06
uses: rapidsai/shared-workflows/.github/workflows/wheels-build.yaml@branch-25.08
with:
build_type: branch
script: ci/build_wheel.sh
Expand All @@ -29,7 +29,7 @@ jobs:
wheel-publish:
needs: wheel-build
secrets: inherit
uses: rapidsai/shared-workflows/.github/workflows/wheels-publish.yaml@branch-25.06
uses: rapidsai/shared-workflows/.github/workflows/wheels-publish.yaml@branch-25.08
with:
build_type: branch
package-name: rapids-cli
Expand Down
4 changes: 2 additions & 2 deletions .github/workflows/pr.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ jobs:
- name: Run pre-commit
uses: pre-commit/action@v3.0.1
build-wheel:
uses: rapidsai/shared-workflows/.github/workflows/wheels-build.yaml@branch-25.06
uses: rapidsai/shared-workflows/.github/workflows/wheels-build.yaml@branch-25.08
needs: [checks]
with:
build_type: pull-request
Expand All @@ -32,7 +32,7 @@ jobs:
wheel-tests:
needs: [build-wheel]
secrets: inherit
uses: rapidsai/shared-workflows/.github/workflows/custom-job.yaml@branch-25.06
uses: rapidsai/shared-workflows/.github/workflows/custom-job.yaml@branch-25.08
with:
build_type: pull-request
node_type: "gpu-l4-latest-1"
Expand Down
2 changes: 0 additions & 2 deletions ci/build_wheel.sh
Original file line number Diff line number Diff line change
Expand Up @@ -9,5 +9,3 @@ python -m pip wheel \
--disable-pip-version-check \
-w "${RAPIDS_WHEEL_BLD_OUTPUT_DIR}" \
.

Choose a reason for hiding this comment

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

If we don't upload the wheels, what do we put them now, just push them to pypi or directly or something after building them?

Copy link
Member Author

Choose a reason for hiding this comment

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

They're getting uploaded to the GitHub Actions artifact store.

via this:

https://github.com/rapidsai/shared-workflows/blob/e62a069ab2266fa1508081ffff59869f68a78a33/.github/workflows/wheels-build.yaml#L249-L254

Which gets called because we use it here:

build-wheel:
uses: rapidsai/shared-workflows/.github/workflows/wheels-build.yaml@branch-25.06

You can see those artifacts at the end of any CI run here, by scrolling down to the "Artifacts" section. For example, from this PR: https://github.com/rapidsai/rapids-cli/actions/runs/15287088447?pr=98

Screenshot 2025-05-28 at 8 55 20 AM

Choose a reason for hiding this comment

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

Thanks, that makes sense : )

Copy link
Member Author

Choose a reason for hiding this comment

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

Yep no prob! Happy to answer any other question you have, there's a TON of indirection involved here.

RAPIDS_PY_WHEEL_NAME="rapids-cli" rapids-upload-wheels-to-s3 python "${RAPIDS_WHEEL_BLD_OUTPUT_DIR}"