Skip to content

compute-build-details: switch to just producing the datetime - #608

Merged
rapids-bot[bot] merged 3 commits into
mainfrom
compute-build-details-pt2
Aug 3, 2026
Merged

compute-build-details: switch to just producing the datetime#608
rapids-bot[bot] merged 3 commits into
mainfrom
compute-build-details-pt2

Conversation

@jameslamb

@jameslamb jameslamb commented Jul 30, 2026

Copy link
Copy Markdown
Member

#603 added a compute-build-details workflow, to generate a stable version component for nightly packages.

This adjusts that based on feedback in rapidsai/cugraph-gnn#508 (comment) that we'd prefer to handle conda packages and wheels differently.

Notes for Reviewers

How I tested this

See "How I tested this" in rapidsai/cugraph-gnn#508

@jameslamb jameslamb changed the title WIP: compute-build-details: switch to just producing the datetime compute-build-details: switch to just producing the datetime Jul 31, 2026
@jameslamb
jameslamb marked this pull request as ready for review July 31, 2026 18:12
@jameslamb
jameslamb requested a review from a team as a code owner July 31, 2026 18:12
@jameslamb
jameslamb requested review from bdice and removed request for a team July 31, 2026 18:12
rapids-bot Bot pushed a commit to rapidsai/gha-tools that referenced this pull request Jul 31, 2026
…on (#269)

Contributes to rapidsai/build-planning#218

Complements rapidsai/shared-workflows#608

For conda builds, RAPIDS projects run `source rapids-date-string` and then thread the environment variable it sets (`RAPIDS_DATE_STRING`) through into conda package build strings, like this:

```shell
source rapids-date-string
```

([rapidsai/cuml - ci/build_cpp.sh](https://github.com/rapidsai/cuml/blob/74f5ffae8f72ca38618b55d84ad234067abd64c1/ci/build_cpp.sh#L8))

```yaml
context:
  ...
  date_string: '${{ env.get("RAPIDS_DATE_STRING") }}'
  ...

...

outputs:
  - package:
      name: libcuml
      version: ${{ version }}
      ...
      string: cuda${{ cuda_major }}_${{ date_string }}_${{ head_rev }}
```

([rapidsai/cuml - conda/recipes/libcuml/recipe.yaml](https://github.com/rapidsai/cuml/blob/74f5ffae8f72ca38618b55d84ad234067abd64c1/conda/recipes/libcuml/recipe.yaml#L100))

In rapidsai/build-planning#218 we're moving from `YYMMDD` date components to `YYMMDDhhmmss`, and prefer to have a different variable name (`RAPIDS_DATETIME_STRING`) ... this introduces a new `rapids-datetime-string` for that purpose.

## Notes for Reviewers

### We can remove `rapids-date-string` soon

From GitHub searches, it seems to me that `rapids-date-string` and environment variable `RAPIDS_DATE_STRING` are only used in CI builds of RAPIDS conda packages.

Once all repos are switched over to `rapids-datetime-string` / `RAPIDS_DATETIME_STRING`, we could remove `rapids-date-string`.

Nice side benefit... that'll cut out some GitHub API calls from our CI, because builds we'll no longer execute this on every  run of a `ci/build_{cpp,python}.sh` script:

https://github.com/rapidsai/gha-tools/blob/02ea00f8c3b257c8aeb94cb757724932e70ce0e2/tools/rapids-date-string#L5-L8

Authors:
  - James Lamb (https://github.com/jameslamb)

Approvers:
  - Bradley Dice (https://github.com/bdice)

URL: #269
@jameslamb

Copy link
Copy Markdown
Member Author

This is backwards-compatible (just modifies a not-used-anywhere workflow + an optional input to other workflows), so it should be safe to merge.

Merging so other PRs for rapidsai/build-planning#218 can target main. I'll go update rapidsai/cugraph-gnn#508 one more time after merging this, and if CI goes well there will put up PRs across the rest of RAPIDS.

@jameslamb

Copy link
Copy Markdown
Member Author

/merge

@rapids-bot
rapids-bot Bot merged commit 1bee82d into main Aug 3, 2026
2 checks passed
@jameslamb
jameslamb deleted the compute-build-details-pt2 branch August 3, 2026 20:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

improvement Improves an existing functionality non-breaking Introduces a non-breaking change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants