Repository navigation
Provide TSMP2 commit hash in log #108
Copy link
Copy link
Open
Description
Activity
Go ahead @s-poll; reproducibility should be underlying the complete system.
@s-poll I suggest adding this feature in CMakeLists.txt so that you can take advantage of this existing function:
Lines 25 to 41 in 05414b5
function(get_model_version MODEL_DIR MODEL_VERSION) if(Git_FOUND) EXECUTE_PROCESS( COMMAND ${GIT_EXECUTABLE} describe --tags --always WORKING_DIRECTORY ${MODEL_DIR} OUTPUT_VARIABLE GIT_REPO_VERSION RESULT_VARIABLE GIT_DESCRIBE_RESULT OUTPUT_STRIP_TRAILING_WHITESPACE ) if (GIT_DESCRIBE_RESULT EQUAL 0) set(${MODEL_VERSION} ${GIT_REPO_VERSION} PARENT_SCOPE) else() message(WARNING "Failed to extract repo version from ${MODEL_DIR}. Error message: ${GIT_DESCRIBE_RESULT}") set(${MODEL_VERSION} "xxxxx" PARENT_SCOPE) endif() endif() endfunction() - moved this from New features to Housekeeping in TSMP2: Towards Stages/2026 support
on Jan 13, 2026 - linked a pull request that will close this issueSupport ICON `release-2026.04-public` standalone build #128
on May 8, 2026 - moved this from Housekeeping to Issues in TSMP2: Towards Stages/2026 support
on May 19, 2026 - removed a link to a pull requestSupport ICON `release-2026.04-public` standalone build #128
on May 19, 2026 - added a parent issue
on May 22, 2026
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
- StatusShow more project fieldsIssues
When reviewing the run logs, only the commits of the individual component models are recorded. However, the commit hash of TSMP2 itself is not included. This creates ambiguity when trying to reproduce runs or trace issues back to the exact TSMP2 version that was used.
Suggested change:
Also write TSMP2 commit hash to the log alongside the component model commits. This will improve traceability, reproducibility, and debugging across model configurations.