codebeamer»Wiki»User's Guide»codebeamer ALM: Application Lifecycle Management»Version Control: Subversion (SVN), Git, MercurialUsing Managed Subversion, Git & Mercurial Repositories #8728/HEAD / v26111
Using Managed Subversion, Git & Mercurial Repositories
What is a Managed Repository?
codeBeamer's Managed Repository technology provides an easy-to-use, consistent, provider-independent repository management tool with project-, group- and role-based administration capabilities, across multiple repositories. The scope of control is definable from the repository level down to the directory level. The unified project/role/group based access is comparatively very efficient at organizing developers into teams, groups, projects and communities.
Managed repository capabilities are available for Subversion, Git and Mercurial version control systems.codeBeamer for Windows is shipped with Subversion, Git (since 6.0.3) and Mercurial managed repository capabilities out of the box, however the Linux/Unix version requires pre-installation of the required SCM system(s).
Managed Repository features:
See Tracing Source Code Changes to Requirements, Task and Bugs
Creating Managed Repositories when Creating a New Project
Managed repositories can easily be created in codeBeamer. You can create a managed repository when creating a project:
Explore your new project – it will be created immediately. However if a dump/bundle file is uploaded, then repository creation might continue in the background.
Creating Managed Repositories for Existing Projects
Managed Repositories can be also created/added to already existing projects. To do this, follow these steps:
For information on creating dump/bundle files see the VCS specific subsections of this document.
Sharing Managed Repositories
codeBeamer's managed repository service is designed for distributed, internet-based development teams. The managed repository service provides project managers with a complete web-based set of role-based repository access control tools. With managed repositories codeBeamer reflects the project member repository permissions (view and commit) into a repository authorization file. For example, if a project member's role has:
If permissions of a role are modified or a user is added to or removed from a project, the repository permissions will be automatically synchronized.
Managing Access Permissions by Roles
Plan your project's VCS access using Basics: Projects, Roles, Groups, Members and Users with different permissions using Authentication and Access Control in codeBeamer.
The users are assigned to different roles, and the roles are assigned different permissions. The permissions can be as fine- or coarse-grained as desired: from repository to directory-level access (directory-level access control is available only for Subversion).
The roles are assigned to users in the Members area (tab) of the project.
Figure: Assigning Roles to Users
After the roles and users are configured the administrators can configure the access to the SCM repositories by assigning the appropriate permissions to the roles. This can be configured for each repository using the Permissions tab on the Repository admin page:
In the background codeBeamer uses a script to establish the communication between the Subversion repository and the codeBeamer instance. This script is generated on every codeBeamer startup based on the actual configuration. One of the most important inputs of this script is the codeBeamer server URL. This URL is set based on the mail configuration in general.xml. More specifically:
Take this example configuration:
<mail serverPort="8080" serverScheme="https" usePersonal="true" localname="example.com">
This configuration defines the following URL: https://example.com:8080. For this the scmloop script will assume that the codeBeamer server is accessible on this url.
If these attributes are not configured explicitly codeBeamer uses the default URL, which is the is the following: http://localhost:8080
This url can be configured manually in general.xml or under the System Admin > Outgoing Email Connection menu. The last section on the configuration page shows the relevant properties:
codebeamer Knowledge Base
Services by Intland Software