use 'rapids-init-pip' in wheel CI, other CI changes #917
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Proposes a batch of small, mostly-unrelated changes to building and packaging.
These are all part of RAPIDS-wide efforts to make it easier to reproduce CI locally and to use artifacts from one project's CI in another project's CI.
Contributes to rapidsai/shared-workflows#356
scriptto workflows using it, instead of relying on a default value coming from the workflow fileContributes to rapidsai/shared-workflows#337
run_scripttoscriptin uses of thecustom-jobworkflowContributes to rapidsai/build-planning#179
rapids-init-pipnear the beginning of all CI scripts that usepipPIP_CONSTRAINTin scripts, in favor of using the one set up byrapids-pip-initContributes to rapidsai/gha-tools#145
rapids-configure-conda-channelsin builds scripts usingrattler-build