Stop uploading notebook test results to downloads.rapids.ai
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 87
- Forks
- 59
- Avg merge
- 22h 56m
- Merged PRs (30d)
- 4
Description
Description
This project currently runs a bunch of RAPIDS notebooks, collects their logs in a few tarballs, and uploads those tarballs to downloads.rapids.ai.
See paths like the following at downloads.rapids.ai:
ci/docker/pull-request/{pr_number}/{commit_sha}/test_notebooks_output_*.tar.gz
That comes from here:
Those uploads should either be removed (if they are determined to be unused) or switched to using the GitHub Actions artifact store.
Benefits of this work
- another step towards removing
downloads.rapids.aicompletely - would allow contributors who don't work at NVIDIA to access those test result outputs from CI
Acceptance Criteria
- this repo does not depend on
downloads.rapids.aiin any way - docs accurately reflect artifact-handling in this repo
Approach
Try using actions/upload-artifact in test workflows, similar to this:
Notes
N/A
Contributor guide
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
Start with .github/workflows/test-notebooks.yml around line 108 and search this repository for downloads.rapids.ai references. Compare the notebook workflow with the shared-workflows wheels-build.yaml artifact example. Done means the repository no longer depends on downloads.rapids.ai and its documentation accurately describes artifact handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100