Linking Manual Deployments with Commit History in Harness
long-term
C
Coastal Partridge
Linking Manual Deployments with Commit History in Harness
Overview: Currently, Harness provides commit history linkage primarily for automated deployments triggered via CI/CD pipelines. However, in many real-world scenarios, deployments are executed manually—especially for hotfixes, patch releases, or in environments with strict change control processes. In these cases, the lack of linkage between manual deployments and the corresponding commit history creates a visibility gap for teams trying to audit, troubleshoot, or understand what code changes were deployed.
Problem:
Manual deployments in Harness do not currently associate with Git commit history by default.
This results in poor traceability, making it difficult to answer questions such as:
What code changes were included in this manual deployment?
Who made those changes and when?
Was this deployment aligned with the expected commits from the feature branch or hotfix?
The lack of commit traceability increases the risk during incident investigations and root cause analyses.
Log In
Canny AI
Merged in a post:
Linking manual deployments with Commit History in harness
C
Coastal Partridge
Currently, Harness provides commit history linkage primarily for automated deployments triggered via CI/CD pipelines. However, in many real-world scenarios, deployments are executed manually—especially for hotfixes, patch releases, or in environments with strict change control processes. In these cases, the lack of linkage between manual deployments and the corresponding commit history creates a visibility gap for teams trying to audit, troubleshoot, or understand what code changes were deployed.
Problem:
Manual deployments in Harness do not currently associate with Git commit history by default.
This results in poor traceability, making it difficult to answer questions such as:
What code changes were included in this manual deployment?
Who made those changes and when?
Was this deployment aligned with the expected commits from the feature branch or hotfix?
The lack of commit traceability increases the risk during incident investigations and root cause analyses.
Shylaja Sundararajan
long-term