Skip to content

Use rapids-init-pip in pip-based CI scripts #179

@jameslamb

Description

@jameslamb

Description

rapidsai/gha-tools#180 introduced a new tool in gha-tools, rapids-init-pip, which does the following:

  • ensures that environment variable PIP_CONSTRAINT is set
  • ensures that the file it points to exists
  • does not modify PIP_CONSTRAINT if it is already set

This allows CI scripts to unconditionally refer to PIP_CONSTRAINT.
That should reduce the diversity of approaches to "constrain what pip installs" in RAPIDS CI, which should make it easier to modify that for exercises like "use wheels from this cuvs PR over in CI on this cuml PR".

This issue documents the work of rolling out use of that tool across RAPIDS.

Benefits of this work

Acceptance Criteria

  • across RAPIDS, all CI scripts using pip to install packages (e.g. ci/build_wheel_*.sh, ci/test_wheel_*.sh):
    • call source rapids-init-pip
    • include --constraint "${PIP_CONSTRAINT} if there are any other uses of --constraint
    • append to, instead of overwriting, the file pointed to by ${PIP_CONSTRAINT}

Approach

Ensure this list includes all repos we want to update:

And roll out these changes to all those repos.

Notes

This is a small change... to save CI resources and reviewer time, consider batching it up together with other small, touch-a-lot-of-repos changes like #178

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions