Skip to content

ci: resolve the GDAL runtime build run in deploy-apps when not given - #257

Merged
Joaquín Rivero (jQuinRivero) merged 1 commit into
mainfrom
feat/deploy-resolve-package-run
Nov 2, 2026
Merged

Joaquín Rivero (jQuinRivero) merged 1 commit into
mainfrom
feat/deploy-resolve-package-run

Conversation

@jQuinRivero

Copy link
Copy Markdown
Contributor

Makes gdal_package_run_id optional on deploy-apps.yml.

  • Blank resolves to the successful gdal-runtime-build run for the deployed commit (gh run list --commit).
  • If none exists, the job fails with a message to run that workflow on the commit or pass an ID.
  • An explicit ID still works; the SHA match, checksum and attestation verification are unchanged for both paths.
  • The hastegeo wheel resolve step now keys off whether packages were downloaded (swa-only deployments), so it keeps its previous behavior.

Validation: workflow YAML parses; the lookup returns the expected run for main's SHA and empty for an unknown SHA. A full deploy run is pending.

A blank gdal_package_run_id now selects the successful gdal-runtime-build run for the deployed commit and fails with a clear message when none exists. The existing SHA, checksum and attestation checks still apply to the resolved run.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jQuinRivero
Joaquín Rivero (jQuinRivero) merged commit 07f5624 into main Nov 2, 2026
21 checks passed
@jQuinRivero
Joaquín Rivero (jQuinRivero) deleted the feat/deploy-resolve-package-run branch November 2, 2026 18:17

This branch was successfully deployed

1 active deployment
gdal-runtime-build — b2ba49bd Deployed Nov 2, 2026 by jQuinRivero via build #25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants