Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

make conda installs in CI stricter #17013

Open
wants to merge 5 commits into
base: branch-24.12
Choose a base branch
from

Conversation

jameslamb
Copy link
Member

@jameslamb jameslamb commented Oct 8, 2024

Description

Contributes to rapidsai/build-planning#106

Proposes specifying the RAPIDS version in conda install calls in CI that install CI artifacts, to reduce the risk of CI jobs picking up artifacts from other releases.

Checklist

  • I am familiar with the Contributing Guidelines.
  • New or existing tests cover these changes.
  • The documentation is up to date with these changes.

@jameslamb jameslamb added 2 - In Progress Currently a work in progress improvement Improvement / enhancement to an existing function non-breaking Non-breaking change labels Oct 8, 2024
@jameslamb jameslamb changed the title WIP: make package installations in CI stricter WIP: make conda installs in CI stricter Oct 8, 2024
@jameslamb jameslamb changed the title WIP: make conda installs in CI stricter make conda installs in CI stricter Oct 8, 2024
@jameslamb jameslamb added 3 - Ready for Review Ready for review by team and removed 2 - In Progress Currently a work in progress labels Oct 8, 2024
@jameslamb jameslamb marked this pull request as ready for review October 8, 2024 15:35
@jameslamb jameslamb requested a review from a team as a code owner October 8, 2024 15:35
@@ -5,6 +5,8 @@ set -euo pipefail

. /opt/conda/etc/profile.d/conda.sh

RAPIDS_VERSION_MAJOR_MINOR="$(rapids-version-major-minor)"
Copy link
Contributor

@bdice bdice Oct 8, 2024

Choose a reason for hiding this comment

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

In build_docs.sh we export this, but here we're just setting it locally. I doubt it matters here but it might be worth establishing consistent patterns. Also applies to other files.

Copy link
Member Author

Choose a reason for hiding this comment

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

My thinking here was "export it if it's already exported (as in the docs example), otherwise make it local", since I thought that had the least risk of causing other surprising problems.

I clicked around a little, and I think:

  • RAPIDS_VERSION = does not even need to be set in docs-build scripts
  • RAPIDS_VERSION_MAJOR_MINOR = does not need to be exported
  • RAPIDS_VERSION_NUMBER = needs to be exported, for rapids-upload-docs (code link in gha-tools)

For all the other scripts that are not docs builds, this PR only introduces NEW variables, so I think not exporting them is slightly safer.

Just pushed 16367a5 doing that. If that works, I'll make similar changes in the other PRs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3 - Ready for Review Ready for review by team improvement Improvement / enhancement to an existing function non-breaking Non-breaking change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants