Skip to content

rapids-datetime-string: like 'rapids-date-string', but second-precision #269

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.

Sign up for GitHub

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

Merged
rapids-bot merged 4 commits into from
Jul 31, 2026
Merged

rapids-datetime-string: like 'rapids-date-string', but second-precision #269

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
97870d5
rapids-date-string: also compute a second-precision RAPIDS_DATETIME_S…
jameslamb Jul 31, 2026
c06d4e7
rapids-datetime-string: like 'rapids-date-string', but second-precision
jameslamb Jul 31, 2026
aa6ab72
formatting
jameslamb Jul 31, 2026
22158fc
fix formatting
jameslamb Jul 31, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions tools/rapids-datetime-string
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
#!/bin/bash
#
# rapids-datetime-string
#
# Ensure the expected date-time environment variables used in
# package building are set.
#
# Example usage:
#
# source rapids-datetime-string
#
if [ "${CI:-false}" = "false" ]; then
# for local builds, just compute right here
RAPIDS_DATETIME_STRING="$(date -u +'%y%m%d%H%M%S')"
export RAPIDS_DATETIME_STRING
else
if [ -z "${RAPIDS_DATETIME_STRING:-}" ]; then
rapids-echo-stderr "Expected environment variable 'RAPIDS_DATETIME_STRING' to be set and non-empty."
exit 1
fi
fi
Loading