rapidsai / rapidsai/shared-workflows

wheels CI: reduce CI time

Open
#505 1 comment 0 reactions 1 assignee View on GitHub

@jameslamb is already working on this.

Since Apr 2, 2026.

feature request
Dominant language
Shell
Stars
8
Forks
33
Avg merge
23h 51m
Merged PRs (30d)
19

Description

Description

The wheels-publish workflow is responsible for a pretty narrow purpose... downloading wheel artifacts built in CI and publishing them to package repositories (like https://pypi.anaconda.org/rapidsai-wheels-nightly/simple/).

It really only needs a Python interpreter and a couple tools like twine, the anaconda CLI, and the gh CLI.

Today, it uses the rapidsai/ci-wheel container images (build from rapidsai/ci-imgs), which are around 4.5 GB compressed (https://hub.docker.com/r/rapidsai/ci-wheel/tags).

The time to run that workflow is dominated by container-image pulling. For example, look at a recent wheels-publish-cudf job (build link):

Image

This issue tracks the work of designing and implementing changes to speed that up. Maybe some mix of:

  • using a slimmer container image (or just ubuntu-latest / ubuntu-slim runners without a container)
  • removing telemetry
  • using a shallow git checkout

Benefits of this work

Acceptance Criteria

  • wheels-publish workflows are faster than they were on February 17, 2026

Ideas

Just dumping some ideas here, this is not an implementation plan:

  • use ubuntu-latest / ubuntu-slim GitHub-hosted runners
  • use a smaller container image (like python:latest or python:3.13-slim)
  • create a new rapidsai/ci-wheel-publishing or similar image
    • publishing a new image does bring new legal / compliance requirements though, this might be a lot of effort
  • fiddle with the rapidsai/ci-wheel image
    • different compression?
    • fewer layers?
    • removing unused things?
  • use shallow git checkouts
  • remove telemetry (this workflow doesn't benefit much from it)

Approach

Related changes made since this started:

Notes

N/A

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.