v0.0.46

Add additional output to `rapids-upload-artifacts-dir` (#47)

This PR adds some additional helpful output to the
`rapids-upload-artifacts-dir` command.

Specifically it:

- Indicates whether additional artifacts were found in the
`RAPIDS_ARTIFACTS_DIR` directory
- Adds a clickable URL to the page which contains all artifacts for a
given workflow

v0.0.45

Retry conda commands if a segfault occurs. (#46)

This PR makes `rapids-conda-retry` retry if the conda command segfaults.
In discussion with @AyodeAwe and @stadlmax, we believe that the segfault
is a temporary failure related to concurrent resource utilization (or
perhaps a network hiccup?) that can be fixed by sleeping and retrying.

Example:
```
/usr/local/bin/rapids-conda-retry: line 68:   155 Segmentation fault      (core dumped) ${condaCmd} ${args} 2>&1
       156 Done                    | tee "${outfile}"
[rapids-conda-retry] conda returned exit code: 139
[rapids-conda-retry] Exiting, no retryable mamba errors detected: 'ChecksumMismatchError:', 'ChunkedEncodingError:', 'CondaHTTPError:', 'CondaMultiError:', 'ConnectionError:', 'EOFError:', 'JSONDecodeError:', 'Multi-download failed', 'Timeout was reached'
[rapids-conda-retry] 
Error: Process completed with exit code 139.
```

https://github.com/rapidsai/cugraph-ops/actions/runs/4283919882/jobs/7460790452#step:6:387

v0.0.44

Modify rapids-twine to discover and upload all wheels (#45)

This changes rapids-twine to more closely resemble the anaconda upload;
all wheels are automatically discovered by looking for the
`wheel_python` string in the S3 path. Then, all the wheels are uploaded
with twine.

This way, the wheel publish workflows don't need to be aware of the
different wheel variants (python versions, architectures, CUDA toolkits,
etc.) that are being built.

v0.0.43

Add rapids-upload-artifacts-dir utility (#43)

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

References: https://github.com/rapidsai/shared-action-workflows/pull/42
https://github.com/rapidsai/cudf/pull/12750

---------

Co-authored-by: AJ Schmidt <aschmidt@nvidia.com>

v0.0.42

Add skip-existing flag to twine so that reruns wont fail (#44)

In case the twine upload fails with a spurious 500 gateway error (but
the upload actually succeeded), on rerun, if there would be a 409
conflict, `--skip-existing` would return a success code.

This helped us get unblocked during the 23.02 release when our pypi
index had some flakiness.

v0.0.41

Increase `RAPIDS_RETRY_SLEEP` value for `rapids-upload-to-anaconda` (…

v0.0.40

Update `rapids-is-release-build` (#41)

This PR updates `rapids-is-release-build` so that it accounts for
release tags for `ucx-py`.

`ucx-py` releases tags look like:

```
refs/tags/v0.30.00
```

whereas RAPIDS release tags look like:

```
refs/tags/v23.02.00
```

v0.0.39

Use commit for date string & update var name (#40)

@bdice pointed out that it's probably a better idea to get the date from
the commit rather than arbitrarily calling the `date` function.

This PR adjusts that implementation accordingly.

It also updates the variable name from `DATE_STRING` to
`RAPIDS_DATE_STRING` in accordance with our environment variable name
conventions.

v0.0.38

Add `DATE_STRING` environment variable for builds (#39)

This PR adds the `DATE_STRING` environment variable which will be used
in some upcoming conda recipe changes.

Assuming the changes work as intended, we should remove the conditional
block of code and remove `VERSION_SUFFIX` in favor of `DATE_STRING`
after the `23.02` release.

v0.0.37

Enable CI Scripts to Run Locally (#35)

This PR introduces some changes to our CI scripts that enable them to be
run locally.

In a nutshell, this PR effectively just adds some prompts that allow
users to provide values for environment variables that are typically
provided by GitHub Actions.

These environment variables ensure that the build and test scripts run
successfully outside of a GH Actions environment.

Breaking down the major changes in this PR by file:

- `tools/rapids-download-conda-from-s3`:
- the changes in this file prompt the user for the necessary env vars
that are needed to identify which artifacts should be downloaded from
downloads.rapids.ai
- `tools/rapids-download-from-s3`:
- the changes in this file ensure that artifacts are obtained from
downloads.rapids.ai (instead of via the `aws` CLI) when not in a CI
environment. VPN access is required to download these artifacts
- `tools/rapids-env-update`:
- sets `sccache` to use read-only mode (see
[here](https://github.com/mozilla/sccache/blob/412f7e00687f388b7fbe14543e307090db558c64/docs/S3.md))
since proper write credentials aren't available to devs running local
builds. sets sensible defaults for other build related vars.
- `tools/rapids-upload-conda-to-s3`:
- exits early before any uploads are attempted since upload should only
happen in GH Actions

The result of these changes is that devs can now volume mount their
locally checked out repository into our CI containers and effortlessly
run build / test scripts the same way CI does:

```sh
docker run \
  --rm \
  -it \
  --gpus all \
  -v $PWD:/cugraph -w /cugraph \
  rapidsai/ci:cuda11.4.1-ubuntu18.04-py3.8

## then inside the container...

./ci/test_cpp.sh
```

This will help developers easily reproduce any build/test failure that
they might encounter in CI with conda packages.