Repository navigation
Tracking Services Release Provenance Schema Update - #80
Merged
Merged
Conversation
CodeGat
added a commit
to ACCESS-NRI/build-cd
that referenced
this pull request
Aug 20, 2026
…ld-db-pkgs.json file. Requires ACCESS-NRI/schema#80
aidanheerdegen
approved these changes
Aug 21, 2026
CodeGat
added a commit
to ACCESS-NRI/build-cd
that referenced
this pull request
Aug 21, 2026
* python3.12: Convert typing.Dict/List to dict/list * get_data_from_deployment: get resolved commits from spack version, try not to fatally error during deployment * tracking_services_data: raise errors from earlier script, no longer resolve spack version refs * Remove unneeded tests, update example * Remove secrets.TRACKING_SERVICES_REPO_FETCH_TOKEN * Resolve URLs in favor of ref-specific rather than just commit-specific * Encapsulate provenance into it's own dataclass, refactor class methods, get commit hash as well * Update tracking_services.py script to handle commit data from the build-db-pkgs.json file. Requires ACCESS-NRI/schema#80 * Update test data * Revert to 2-0-0 while tracking services doesn't support that schema * Update function comment
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
References ACCESS-NRI/build-cd#423
Background
We now require a commit hash for each model component, so we have a truly immutable reference for provenance - for example, tags (which are the most commit ref to use in our releases) could be updated or deleted on a component.
Since each schema is a new file, the diff is for a new file. For just the change I added, see 6109cb2
The PR
2-1-0.jsonofau.org.access-nri/tracking_services/release_provenance/telemetry, which adds a requiredcommit_hashto a spack model component. This is technically aREVISIONnot aMODELchange, as we haveadditionalProperties: true- so technically some old data would be in conformance with this updated spec.