Observing Code Commit as part of a Pipeline Run
Use cases for tracking commits
Here are a few ways that you can use commit tracking information:
Note: Most roles can be customized. Roles and their permissions might be different for your organization.
As a developer, when you commit a change to your SCM system, enter a commit message with the ID of the defect, user story, or quality story related to this change.
When the pipeline associated with your change runs, this information is passed to ALM Octane.
When you open the backlog items in ALM Octane, you and your team leader get a clear picture of the files that you changed for each backlog item you worked on.
As a dev team leader, view the team members' commits and how they relate to the items in the team backlog.
As a developer or DevOps engineer, match build failures to specific changed files and specific backlog items.
As a tester, after verifying that a pipeline run was successful and automated tests passed, determine the areas that contain significant changes and require manual testing.
As a developer, identify sensitive areas in your code, which are risky to change. You may want to simplify and refactor the code and increase testing around the functionality it covers. This should reduce the risk of future changes causing quality issues. For details, see Identify hotspots in your code.
As a developer or Dev tester, identify commits that seem to be related to failing automated tests. You can also see which commits are riskier than others because they affect hotspot files.
As a project manager or PMO, identify features with risky commits and consider increasing testing on these features, or postponing their release.