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

One python version per container #22

Merged
merged 36 commits into from
Jun 1, 2023

Conversation

divyegala
Copy link
Member

No description provided.

@divyegala divyegala marked this pull request as draft May 24, 2023 16:17
Copy link
Member

@ajschmidt8 ajschmidt8 left a comment

Choose a reason for hiding this comment

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

awesome job. it's coming together.

left a few comments/thoughts.

Copy link
Member

Choose a reason for hiding this comment

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

Copy link
Member Author

Choose a reason for hiding this comment

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

Should I also rename merge.yml to build.yml like other RAPIDS repos then?

build.sh Outdated Show resolved Hide resolved
ci/compute-mx.sh Outdated Show resolved Hide resolved
axis.yaml Outdated Show resolved Hide resolved
@divyegala
Copy link
Member Author

@ajschmidt8 this is ready for a re-review

@divyegala divyegala requested a review from ajschmidt8 May 26, 2023 13:17
ci/compute-mx.jq Outdated Show resolved Hide resolved
.github/workflows/build-and-publish-images.yml Outdated Show resolved Hide resolved
.github/workflows/build-and-publish-images.yml Outdated Show resolved Hide resolved
.github/workflows/build-image.yml Outdated Show resolved Hide resolved
ci-wheel/Dockerfile Outdated Show resolved Hide resolved
Copy link
Collaborator

@vyasr vyasr left a comment

Choose a reason for hiding this comment

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

Some initial requests:

  • Move the deletion of the disabled workflows to a separate PR
  • Rename workflows to match the workflows used in our other repos (pr/build/test) assuming they follow the same logic (I don't think we need the equivalent of a "test" workflow nightly)
  • Let's leave the ci-wheel images named something with manylinux in them. Perhaps manylinux_cuda? I still want that use case to be clear.
  • Can we separate change to the manylinux containers from changes to the citestwheel images (separate PRs)?

@ajschmidt8
Copy link
Member

  • Let's leave the ci-wheel images named something with manylinux in them. Perhaps manylinux_cuda? I still want that use case to be clear.

Hmm. I was hoping to keep these as ci-wheel in anticipation of these images being merged into the https://github.com/rapidsai/ci-imgs/ repository.

Once that happens, I assumed we'd have two images in that repository: ci-conda and ci-wheel.

Any thoughts on this approach?

@divyegala divyegala marked this pull request as ready for review June 1, 2023 19:37
@ajschmidt8 ajschmidt8 changed the base branch from main to imgs-v2 June 1, 2023 20:17
Copy link
Collaborator

@vyasr vyasr left a comment

Choose a reason for hiding this comment

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

Images look good. Didn't review the rest.

@ajschmidt8 ajschmidt8 merged commit 83e3cbe into rapidsai:imgs-v2 Jun 1, 2023
vyasr pushed a commit to rapidsai/shared-workflows that referenced this pull request Jun 29, 2023
rapidsai/cibuildwheel-imgs#22 allowed for new
wheel containers to be built with only one python version per container
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.

3 participants