Closes #263

Background

We are moving away from the initial release database to a database serviced by tracking_services.

This PR removes the old release database workflow, adds a new one, and gets release data into a format defined in https://github.com/ACCESS-NRI/schema/blob/main/au.org.access-nri/tracking_services/release_provenance/telemetry/1-0-0.json

The PR

• Delete old build database infrastructure, in 4d0bd2d
• Create new scripts/release_provenance/tracking_services_data.py module
  • Created in b53f282
  • Tests created in 332f8c5
  • Module called in cd.yml in ebc595b
• Update deploy-* workflows to get data required for above module, in 4f81cc2 and 916f0fe
• Finally, updated all workflow_calls to v5, in 969c360

Testing

Unit Testing

Added testing infrastructure for the tracking_services_data.py module, under tests/scripts/release_provenance/test_tracking_services_data.py. To run:

python3 -m venv venv
./venv/bin/activate
pip install -r requirements-dev.txt
pytest tests/scripts/release_provenance/test_tracking_services_data.py

Workflow Testing

Workflow testing is ongoing via ACCESS-NRI/ACCESS-TEST#36, details will be added to this PR upon testing completion.

Prerelease - Manual Output Testing ✔️

Before testing the Release Workflow, I tested that the outputs given by the prerelease https://github.com/ACCESS-NRI/ACCESS-TEST/actions/runs/14746333987 are in a valid format.

Tested via:

gh run download 14746333987 --repo access-nri/access-test
python3 -m venv venv
. venv/bin/activate
pip install -r build-cd/scripts/release_provenance/requirements.txt
python -m scripts.release_provenance.tracking_services_data \
  --repository access-test \
  --root-spec access-test \
  --deployment-outputs ./deploy-outputs.Gadi \
  --metadata-outputs ./deploy-metadata.Gadi \
  --output ./output.json

I then uploaded the output.json to the staging area manually and verified its validity. The ACCESS-TEST model in the staging database can be found at https://reporting-dev.access-nri-store.cloud.edu.au/release-provenance/releases/20/.

Release - Outputs Posted Via Workflow ✔️

Using a test Gadi Release GitHub Environment, I merged (after fixes, multiple) PRs that ran through the entire workflow to success. Successfully posted provenance, see https://github.com/ACCESS-NRI/ACCESS-TEST/actions/runs/14767933751/job/41463262076#step:7:15, and the model in the staging database can be found at https://reporting-dev.access-nri-store.cloud.edu.au/release-provenance/releases/21/.