rapidsai / rapidsai/shared-workflows
conda workflows: re-enable sharded repodata
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8
- Forks
- 33
- Avg merge
- 23h 51m
- Merged PRs (30d)
- 19
Description
Description
Issues with sharded repodata publishing for the rapidsai conda channel blocked the 26.06 release, so we opted out of that metadata in https://github.com/rapidsai/shared-workflows/pull/564
It should be restored by reverting that PR, once the issues described in https://github.com/rapidsai/cugraph/pull/5542#discussion_r3360573913 are resolved.
Benefits of this work
- sharded repodata provides noticeable speedups to
condaandrattler-build(see https://github.com/rapidsai/build-planning/issues/240)
Acceptance Criteria
- sharded repodata is enabled for
condaandrattler-buildRAPIDS-wide
Approach
Revert https://github.com/rapidsai/shared-workflows/pull/564 and #567
Notes
N/A
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review shared-workflows PR 564 and #567, then read the linked cugraph PR discussion to confirm the sharded repodata issues are resolved. Revert the specified changes and verify that sharded repodata is enabled for conda and rattler-build across RAPIDS workflows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, shell
- Domain
- build-system, ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100