Tracing Source Code Changes to Requirements, Task and Bugs
Disciplined source code changes associated with valid tasks increase stability, consistency, transparency and traceability in collaborative software development environments.
When a managed repository is used, Codebeamer provides links to show the associations between a Task-ID and SCM commits by default. This level of traceability can also be explicitly configured for external repositories. The script that enables the Task-Commit associations is called SCMLoop. See Installing SCM Loop
In Codebeamer 5.5, commits can be edited. For further information, see Tracing Source Code Changes to Requirements, Task and Bugs, Version Control: Subversion (SVN), Git, Mercurial and CVS
When the SCMLoop script is enabled, it intercepts the source code commits and invokes Codebeamer to associate the commits with a Codebeamer tracker item (for example: a task or a bug)
When the SCMLoop is installed, either by default with a managed repository, or explicitly, use the following syntax in the commit messages when committing changes to your SCM:
#1234 Fixed an NPE
Where 1234 is the tracker item which the commit is to associate with. Enter, for example:
#1234, #3456,#4533 Fixed memory leak
Where 1234, 3456 and 4533 are the tracker items which the commit is to associate with. A space between the (,) and (#) is optional.
Entering, for example:
Fixed an NPE to resolve [BUG:1234]
Does not associate the commit with any tracker item, but:
#1234 Fixed an NPE. See [BUG:5678]
The commit syntax with # is configurable by adding the following regular expression to the System Admin
Application Configuration scc node:
Application Configuration scc node:"task_expression" : "#(([1-9][0-9]{3,9})((,|\s+)[1-9][0-9]{3,9})*)(?:\z|[\s.,;:)\-]+)",