mirror of
https://github.com/gradle/actions.git
synced 2026-11-13 00:47:45 +00:00
Iñaki Villar
445a164ce8
## Changes Follow-up to #1109. That PR left `suite-integ-test-other.yml` on `DV_SOLUTIONS_ACCESS_KEY`. `integ-test-inject-develocity.yml` now gets a GitHub OIDC token, in `solutions.develocity.cloud=<token>` form, from the same pre-step as #1109. The token goes where the access key went before: - **`inject-develocity`**: the `DEVELOCITY_ACCESS_KEY` / `GRADLE_ENTERPRISE_ACCESS_KEY` env var, set per matrix entry through `$GITHUB_ENV` - **`inject-develocity-with-access-key`**: the `develocity-access-key` input - **`inject-develocity-short-lived-token-failed`**: both env vars and the input - **`inject-develocity-with-access-key-from-input-actions`**: the `DEVELOCITY_ACCESS_KEY` env var setup-gradle exchanges the OIDC token at `/api/auth/token` the same way it exchanges an access key. The `DEVELOCITY_ACCESS_KEY` secret is removed from the reusable workflow. `id-token: write` is granted along the chain: `ci-integ-test*.yml` → `suite-integ-test-other.yml` → the jobs. Fork PRs are already skipped for these jobs. Part of gradle/dv#74660. After this merges, nothing in gradle/actions uses `DV_SOLUTIONS_ACCESS_KEY`. ## Verification - [ ] CI-integ-test on this PR: `develocity-injection` jobs green, Build Scans published to solutions.develocity.cloud