Skip to content
This repository was archived by the owner on Aug 28, 2025. It is now read-only.

Conversation

@jayavenkatesh19
Copy link
Contributor

This work is towards moving build artifacts from downloads.rapids.ai to Github Artifact Store (see https://github.com/rapidsai/build-infra/issues/237)

As part of these changes, all wheel builds need to be in a specified temporary directory indicated by the environment variable RAPIDS_WHEEL_BLD_OUTPUT_DIR set on the ci-wheel Docker image used for building wheels. This lets us upload all wheel artifacts seamlessly to Github Artifacts.

@jayavenkatesh19 jayavenkatesh19 changed the title [WIP] Moving wheel builds to specified location and uploading build artifacts to Github Moving wheel builds to specified location and uploading build artifacts to Github Mar 24, 2025
@jayavenkatesh19 jayavenkatesh19 marked this pull request as ready for review March 24, 2025 22:50
@jayavenkatesh19 jayavenkatesh19 requested a review from a team as a code owner March 24, 2025 22:50
@ajschmidt8
Copy link
Member

/merge

@rapids-bot rapids-bot bot merged commit 857e95c into rapidsai:main Apr 2, 2025
49 checks passed
gmarkall added a commit to gmarkall/pynvjitlink that referenced this pull request May 4, 2025
- Update to CUDA 12.9 (rapidsai#138)
- feat(conda): port conda recipe to rattler-build (rapidsai#137)
- Download build artifacts from Github for CI (rapidsai#136)
- Moving wheel builds to specified location and uploading build artifacts to Github (rapidsai#135)
- Use mainline shared-workflows again (rapidsai#134)
@gmarkall gmarkall mentioned this pull request May 4, 2025
gmarkall added a commit that referenced this pull request May 4, 2025
- Update to CUDA 12.9 (#138)
- feat(conda): port conda recipe to rattler-build (#137)
- Download build artifacts from Github for CI (#136)
- Moving wheel builds to specified location and uploading build
artifacts to Github (#135)
- Use mainline shared-workflows again (#134)

<!--

Thank you for contributing to pynvjitlink :)

Here are some guidelines to help the review process go smoothly.

1. Please write a description in this text box of the changes that are
being
   made.

2. Please ensure that you have written units tests for the changes
made/features
   added.

3. If you are closing an issue please use one of the automatic closing
words as
noted here:
https://help.github.com/articles/closing-issues-using-keywords/

4. If your pull request is not ready for review but you want to make use
of the
continuous integration testing facilities please label it with `[WIP]`.

5. If your pull request is ready to be reviewed without requiring
additional
work on top of it, then remove the `[WIP]` label (if present) and
replace
it with `[REVIEW]`. If assistance is required to complete the
functionality,
for example when the C/C++ code of a feature is complete but Python
bindings
are still required, then add the label `[HELP-REQ]` so that others can
triage
and assist. The additional changes then can be implemented on top of the
same PR. If the assistance is done by members of the rapidsAI team, then
no
additional actions are required by the creator of the original PR for
this,
otherwise the original author of the PR needs to give permission to the
person(s) assisting to commit to their personal fork of the project. If
that
doesn't happen then a new PR based on the code of the original PR can be
opened by the person assisting, which then will be the PR that will be
   merged.

6. Once all work has been done and review has taken place please do not
add
features or make changes out of the scope of those requested by the
reviewer
(doing this just add delays as already reviewed code ends up having to
be
re-reviewed/it is hard to tell what is new etc!). Further, please do not
rebase your branch on main/force push/rewrite history, doing any of
these
   causes the context of any comments made by reviewers to be lost. If
   conflicts occur against main they should be resolved by merging main
   into the branch used for making the pull request.

Many thanks in advance for your cooperation!

-->
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants