Releases: rapidsai/gha-tools
Releases · rapidsai/gha-tools
v0.0.66
Trigger CI img rebuilds (#73) Configures the release workflow to trigger `build-and-publish-images` workflow of `ci-imgs` due to being an upstream dependency.
v0.0.65
Remove rapids_twine_new (#71) This tool is now completely redundant, rapids_twine can always be used instead. Closes #54
v0.0.64
Revert "Fix `rapids-date-string` (#68)" (#70) This reverts commit #68, which unintentionally broke some things in CI.
v0.0.63
Fix `rapids-date-string` (#68) As it turns out, using the `YYMMDD` format in `rapids-date-string` for wheels broke some things. This PR adjusts `rapids-date-string` to generate both `YYMMDD` strings and "seconds since epoch" strings for wheels. Since the new wheel scripts all call `rapida-date-string` without any arguments, the default argument is set to "second". The default argument should be removed once `rapids-env-update` is deprecated and the individual repositories have been updated to call `rapids-date-string` in this new format. `rapids-env-update` has also been updated to pass the `day` argument since all conda workflows currently get their `RAPIDS_DATE_STRING` value through that script. To avoid having to pass arguments from the calling scripts in the future, we could create two new `gha-tools` scripts (e.g. `rapids-wheel-date-string` and `rapids-conda-date-string`) that call a "private" script (`_rapids-date-string`) with the appropriate arguments.
v0.0.62
Add VPN access note for documentation preview environments (#67) This PR is a follow up to #66. It adds a header and note about VPN access for the documentation preview URLs. --------- Co-authored-by: Bradley Dice <bdice@bradleydice.com>
v0.0.61
enable docs preview in prs (#66) PR enables docs uploads to S3 on pull requests (using the `rapids-uploads-docs` script).
v0.0.60
Enable wheels CI scripts to run locally (#57) Taking inspiration from #35 and #62 This PR adds / updates: - `rapids-configure-sccache` (new) : configures sccache for CI/local, with the intention being to remove this information from CI containers - `rapids-date-string` (new) : configures date string - `rapids-configure-conda-channels` (new) : modifies conda channels based on build type - `rapids-env-update` (modified) : calls the `rapids-configure-sccache` - `rapids-prompt-local-repo-config` (new) : consolidates prompts for users to configure repo information locally - `rapids-download-wheels/conda-from-s3` (updated) : uses `rapids-prompt-local-repo-config` - `rapids-upload-wheels-to-s3` (modifed) : guards to ensure local builds don't try to upload
v0.0.59
Make rapids-twine look like rapids-twine-new (#63) We know the `-new` version also works, so to minimize disruptions with existing workflows it'll be easiest to just modify the original script then eventually remove the `-new` version once nothing is using the legacy workflows that call it. Part of #54
v0.0.58
Fix prompts for running a nightly build/test locally (#62) RAPIDS CI supports running CI builds locally using the instructions here: https://docs.rapids.ai/resources/reproducing-ci/ When a build step requires downloading from S3, the tools script will prompt for the needed environment variable settings. ``` export RAPIDS_BUILD_TYPE=pull-request # or "branch" or "nightly" export RAPIDS_REPOSITORY=rapidsai/cugraph export RAPIDS_REF_NAME=pull-request/3258 # or "branch-YY.MM" for "branch"/"nightly" builds ``` The steps for reproducing a `nightly` test were not working and produced the following result. ``` [rapids-download-conda-from-s3] Local run detected. [rapids-download-conda-from-s3] NVIDIA VPN connectivity is required to download workflow artifacts. Enter workflow type (one of: pull-request|branch|nightly): nightly Suppress this prompt in the future by setting the 'RAPIDS_BUILD_TYPE' environment variable: export RAPIDS_BUILD_TYPE=nightly Enter org/repository name (e.g. rapidsai/cudf): rapidsai/cudf Suppress this prompt in the future by setting the 'RAPIDS_REPOSITORY' environment variable: export RAPIDS_REPOSITORY=rapidsai/cudf Enter pull-request number (e.g. 1546): branch-23.08 Suppress this prompt in the future by setting the 'RAPIDS_REF_NAME' environment variable: export RAPIDS_REF_NAME=pull-request/branch-23.08 Using HEAD commit for artifact commit hash. Overwrite this by setting the 'RAPIDS_SHA' environment variable: export RAPIDS_SHA=1854ac86d08e545376704959436ec370bdd8117a /usr/local/bin/rapids-s3-path: line 40: RAPIDS_NIGHTLY_DATE: unbound variable ``` The nightly build requires the `RAPIDS_NIGHTLY_DATE` date in `YYYY-MM-DD` format and the `RAPIDS_REF_NAME` is expected to be the branch name. This PR updates the prompt logic to allow running a nightly build locally.
v0.0.57
Make `rapids-get-artifact` work locally (#59) This PR ensures that `rapids-get-artifact` works locally. This request was made by @bdice who was attempting to use the script locally to debug some CUDA 12 issues. I've moved the logic for downloading, extracting, and printing the artifact's path to a new script, `_rapids-download-from-s3`. This script is then called by both `rapids-download-from-s3` and `rapids-get-artifact`. In the future, I would like to rework some of the scripts regarding artifact uploading/downloading, but I think we need to finish reworking the wheel workflows before that will be feasible.