1.1Using Managed Subversion, Git & Mercurial Repositories
Watch a video on a Git or Mercurial/Subversion Repository here. 1.1.1What 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 1.1.2Creating Managed Repositories when Creating a New ProjectManaged 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.
1.1.3Creating Managed Repositories for Existing ProjectsManaged 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. 1.2Sharing Managed RepositoriescodeBeamer'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. 1.2.1Managing Access Permissions by RolesPlan your project's VCS access using For example:
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:
1.3Configuration noteIn 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: |
Fast Links
![]() codebeamer Overview codebeamer Knowledge Base Services by Intland Software |
This website stores cookies on your computer. These cookies are used to improve your browsing experience, constantly optimize the functionality and content of our website, and help us understand your interests and provide more personalized services to you, both on this website and through other media. With your permission, we and our partners may use precise geolocation data and identification through device scanning. You may click accept to consent to our and our partners’ processing as described above. Please be aware that some processing of your personal data may not require your consent, but you have a right to object to such processing. By using our website, you acknowledge this notice of our cookie practices. By accepting and continuing to browse this site, you agree to this use. Your preferences will apply to this website only.
Note that user-behavior analytics are being captured on this server to improve the Codebeamer user experience.