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

Add rapids-upload-artifacts-dir utility #43

Merged
merged 7 commits into from
Feb 18, 2023

Conversation

davidwendt
Copy link
Contributor

Adds rapids-upload-artifacts-dir utility script for uploading individual files from the RAPIDS_ARTIFACTS_DIR directory.

References: rapidsai/shared-workflows#42 rapidsai/cudf#12750

davidwendt and others added 7 commits February 15, 2023 10:14
`-e` ensures that the file/dir in the current iteration exists on the filesystem.

this is to account for situations where the directory is empty.

adapted from this post: https://unix.stackexchange.com/q/239772
makes the exit code `0` for local uploads attempted with `rapids-upload-conda-to-s3`.

this makes it match `rapids-upload-artifacts-dir` and is probably the more appropriate setting.
@ajschmidt8 ajschmidt8 merged commit 37f3946 into rapidsai:main Feb 18, 2023
ajschmidt8 added a commit to rapidsai/shared-workflows that referenced this pull request Mar 20, 2023
This PR adds a step to run `rapids-upload-artifacts-dir` (added
[here](rapidsai/gha-tools#43)) to any shared
workflows that expose a `RAPIDS_ARTIFACTS_DIR` environment variable.

The new `Upload additional artifacts` step will _always_ run even if the
prior build/test steps fail.

This is helpful for uploading log files that result from failed builds.

It is the repository script's responsibility to ensure that log files
end up in the `RAPIDS_ARTIFACTS_DIR` after a failed build though.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants