You are not logged in. Click here to log in.

codeBeamer ALM
Tags:  not added yet

Collaborating with Version Control Systems

Browsing Version Control Systems on the Web

CodeBeamer has a built-in interface for SCM systems, and project members can browse the content of the SCM repository. SCM systems such as Subversion, Git & Mercurial are directly integrated, and integration is possible with various other SCM systems via CodeBeamer's API. The browsing capability includes user's requirements for tracking code changes, associating commits with bugs, browsing repository revisions, commits, branches, and tags.

Browsing Commits (Change Sets)

You can browse commits (changesets) in the SCM Repository browser.  When your cursor hovers over the SCM Repository area (tab), you'll see the tooltip menu: select Browse Commits.

Figure: Browse Commits by User

Browsing Repositories

You are also able to browse the files stored in the repository using the Repository Browser. This can be found under the SCM Repository tooltip menu (or more menu after SCM Repository tab has been selected) by clicking on Browse Repository.

Figure: Browse Repository

Integrating Version Control Systems with Wiki Pages

codeBeamer offers several wiki plugins to be inserted into pages to display live SCM related information.

Commit History Wiki Plugin

With the CommitTrends you can build your commit trends into your dashboard.
[{CommitTrends title='Subversion Activity'}]

Commit Statistics Wiki Plugin

With the CommitStatistic plugin you can display statistics about source code commits.

Example usage:


Source Code Summary Wiki Plugin

This plugin in not supported any more in codeBeamer 7.9

With the SourceCodeSummary plugin you can display statistical information about the source code of a project.

Example usage:

[{SourceCodeSummary title='Statistics' projectId='254'}]

Lines of Code Wiki Plugin

This plugin in not supported any more in codeBeamer 7.9

With the LOC Trends plugin you can display information about how the number of lines of code changes over time.

Example usage:

[{LocTrends projectId='4' period='This year'}]