Published on Online Documentation for Altium Products (

Transcription

1 Published on Online Documentation for Altium Products ( Главная > Local Version Control Service Using Altium Documentation Modified by Jason Howie on May 8, 2018 Parent page: Altium NEXUS Server The Altium NEXUS Server installation provides localized (and centralized) version control, courtesy of its Version Control service. Essentially an SVN server (version 1.8), this service provides version control possibilities right there where you need them, locally, without searching, or paying for, external SVN management software. By defining design repositories in this centralized fashion, an oganization can fully control which repositories its designers can access and use. For more information on Design Repositories, and working with them through Altium NEXUS, see Working with a Design Repository. Key Advantages There are two key advantages to using this centralized Version Control service: 1. You have common users and rights management for both the Altium NEXUS Server and SVN. When you sign in to the Altium NEXUS Server, the Version Control service works with your session/credentials. 2. Repositories defined through the Altium NEXUS Server (through the VCS page (Admin - VCS) of the NEXUS Server's browser-based interface) are populated to the client automatically during login, so users do not have to worry about urls, protocols, password etc. It is simply configured once, on the server, and shared with the intended users as required. When a new user for the Altium NEXUS Server is created, the defined Password for that user is stored in both the NEXUS Server and the SVN service, since the latter cannot access the password from the former directly. Repository Creation Repositories can be created through the local Version Control service (SVN-only), or external repositories can be connected to (SVN or Git). Together, all repositories are centrally managed through the VCS page (Admin - VCS) of the NEXUS Server's browser-based interface, in terms of: Their displayed name, description and repository path. Their configured accessibility - which specific users can access them (or roles in the case of repositories defined through the local Version Control service). Their availability - add or remove them centrally, rather than individual designers having to create and connect to repositories independently. Two default Design Repositories are available, provided by the local Version Control service

2 and named DefaultRepository (an SVN repository) and Versioned Storage (a Git repository) respectively. The DefaultRepository repository cannot be renamed, but you can add a description for it, manage user access to it, or remove it, as required. The Versioned Storage repository, which is purely for the integrated storage of managed projects, cannot be renamed, shared, or removed. When a user signs in to the Altium NEXUS Server, the Design Repositories available to them will automatically be added to the Data Management - Design Repositories page of the Preferences dialog. Centrally define access to your organization's Design Repositories. Repositories can be internal to the Altium NEXUS Server installation, defined using the local Version Control service, or external through use of Altium NEXUS's built-in SVN, or third party SVN or Git service. Access control is performed through the VCS page of the Altium NEXUS Server's browser-based interface. When a user signs in to the Altium NEXUS Server, the Design Repositories available to them will automatically be added to the Data Management Design Repositories page of the Preferences dialog.

3 ADDING A REPOSITORY To add a Design Repository, simply click the button, located at the top-right of the page. The Add Repository window will appear, use this to define the repository. Only SVN-type repositories can be created through the local Version Control service. Existing (external) repositories can be linked to, and these can be either SVN or Git. The properties required depend on whether you are creating a new repository using the local Version Control service, or linking to an existing, external repository: New - simply give the repository a name and a description. Existing - in addition to a name and description, you need to supply the URL to the repository, and your credentials (User Name, Password) to access that repository (if required). When creating a repository that is internal to the NEXUS Server, the name should start with, and can contain A-Z, a-z, or 0-9. Underscores, dashes, and spaces are allowed within the middle of the name. You can not use the following words: AUX, COM1-COM9, LPT1-LPT9, CON, NUL, and PRN. There are no naming restrictions for an external repository. Create a new SVN-based Design Repository through the NEXUS Server's local Version Control service, or link to an existing repository (SVN or Git) that has been created external to the NEXUS Server. A linked, external Design Repository is distinguished in the list of repositories by its External property being ticked ( ). To edit the properties of a Design Repository at a later stage, simply click its associated Edit control ( ). To remove a Design Repository, simply click its associated Remove control ( ). The list of repositories is automatically sorted alphabetically by Name, with local

4 repositories defined through the Version Control service listed first, and then external repositories thereafter. The Git-based Versioned Storage repository always appears at the top of the list. SHARING A REPOSITORY Having centralized your Design Repositories, you need to ensure that those requiring access to a given repository - including the designers who will be working on board designs - have that access. This is achieved by sharing that repository, or rather managing its access permissions. To do this, simply click on the repository's associated Share control ( ). The Manage Permissions window will appear, with all the controls necessary to share the repository with other users. With Design Repositories centrally organized, sharing with others is simply a case of managing each repository's permissions. Things to be aware of: For a local repository created through the NEXUS Server's Version Control service (i.e. not external), that repository is shared, by default, with the user who created the repository, and the Administrators role. Both of these have full Read/Write access. For an external repository, it is shared with no-one by default - not even the user who added a connection to it through the interface. Only local repositories (not external) can be shared with defined roles for the NEXUS Server, or publically. Roles are listed after individual users. In terms of permissions, a user/role has Read/Write access when the Can Write option is enabled. If this option is disabled, they have Read access only. To remove an existing user/role from having shared access to a repository, click the associated Remove control ( ). Sharing a Local Repository with a NEXUS Server User

5 To share a local (not external) repository with another NEXUS Server user: 1. Click the Add User control in the Manage Permissions window. 2. In the Add Users window that appears, start typing the full name, username, or address of a NEXUS Server user in the Select Users to be added field, to pop-up a list of matching users. Select the required user from this list. Multiple users can be chosen. To remove a user, simply click the delete cross, to the far right of their name. 3. Set the permission for the user(s) using the Permission field. Use the drop-down to choose betwen Read access, or Read/Write access. 4. Click the button once ready, to effect addition of the user(s) and return to the Manage Permissions window.

6 5. Click the button in the Manage Permissions window. To edit the permissions for an existing user, simply use the Can Write option in the Manage Permissions window, to toggle between Read/Write access (enabled) or Read-only access (disabled). Sharing a Local Repository with a Defined Role If the repository has been created through the local Version Control service, rather than an external repository, then you also have the ability to share with roles defined for your Altium NEXUS Server. To share a local (not external) repository with another role: 1. Click the Add Role control in the Manage Permissions window. 2. In the Add Roles window that appears, start typing the name of a role in the Select Roles to be added field, to pop-up a list of matching roles. Select the required role from this list. Multiple roles can be chosen. To remove a role, simply click the delete cross, to the far right of its name.

7 3. Set the permission for the role(s) using the Permission field. Use the drop-down to choose betwen Read access, or Read/Write access. 4. Click the button once ready, to effect addition of the role(s) and return to the Manage Permissions window. 5. Click the button in the Manage Permissions window. To edit the permissions for an existing role, simply use the Can Write option in the Manage Permissions window, to toggle between Read/Write access (enabled) or Read-only access

8 (disabled). Sharing a Local Repository Publically If the repository has been created through the local Version Control service, rather than an external repository, then you also have the ability to share that repository publically - allowing all NEXUS Server users to access and use it. To share a local (not external) repository publically: 1. Click the Add Public control in the Manage Permissions window. 2. The Public entry will be added directly to the list of shared entities, and automatically shared for Read/Write access. 3. Click the button in the Manage Permissions window. To edit the permissions for the Public entity, simply use the Can Write option in the Manage Permissions window, to toggle between Read/Write access (enabled) or Read-only access (disabled). Sharing an External Repository with a NEXUS Server User To share an external repository with a NEXUS Server user: 1. Click the Add User control in the Manage Permissions window.

9 2. In the Add Users window that appears, start typing the full name, username, or address of a NEXUS Server user in the Select Users to be added field, to pop-up a list of matching users. Select the required user from this list. To remove the user, simply click the delete cross, to the far right of their name. In the SVN User field, enter the name to suit that user's particular SVN access - mapping the NEXUS Server user to the SVN user, as it were. While you can only add a single user at a time, you can define as many users for access to the external SVN repository as you need. NEXUS Server users can be mapped to any valid user name in the external SVN repository, and multiple NEXUS Server users may be mapped to a single user name in the external SVN repository. See example. 3. Click the button once ready, to effect addition of the user and return to the Manage Permissions window.

10 4. Click the button in the Manage Permissions window. Access itself (Read-only, or Read/Write) is determined externally as part of the SVN repository installation. The Altium NEXUS Server has no access to the external SVN repository's authz file, and so cannot manage these permissions from the server side. External Access to a Local SVN Design Repository A Design Repository that is created through the local Version Control Service can be accessed using an SVN client such as TortoiseSVN. Access is made using the regular network protocol (only svn:// is currently supported). The correct repository address can be copied from two places: The VCS page of the NEXUS Server's browser interface - within the Repository Path field for the target repository. From within Altium NEXUS, from the Data Management - Design Repositories page of the Preferences dialog - within the Repository field for the target repository.

11 The address will depend on whether you are accessing the repository from the same machine on which the NEXUS Server is installed (e.g. svn:// /<repositoryname>, or svn://localhost/<repositoryname>), or from a remote PC (e.g. svn://<computername>/<repositoryname>, where ComputerName is the name of the PC on which the NEXUS Server resides). Use the acquired address in your Subversion client's repository browsing facility. When a user is created in the NEXUS Server, the credentials are used by both the server itself, and the Version Control service. If the password is stored with the service, then access to the repository will be immediate. If the password is not stored, an intermediate Authentication dialog will appear. Enter your username only in this case, and click OK to access the repository. See Vault & VCS User Synchronization for more information.

12 Browsing the content of a Design Repository created through the Altium NEXUS Server installation's local SVN-based Version Control service. In the example above, the repository contains a couple of Managed Projects, providing the ideal foundation for centralized project management, and controlled collaboration between team members. A Design Repository that is created through the local Version Control service has its internal data stored in a corresponding sub-folder in the \ProgramData\Altium\NexusServerData\Repository folder (for a default installation of the Altium NEXUS Server). This folder should not be accessed in any way, other than by IT personnel for maintenance. Access from this folder using your Subversion client's repository browsing facility does not require authentication. Vault & VCS User Synchronization When a new user for the Altium NEXUS Server is created, the defined credentials (User Name and Password) for that user are stored in both the server's database and the Version Control service, since the latter cannot access the password from the former directly. The password is stored with the Version Control service in plain text format (in the \ProgramData\Altium\NexusServerData\Repository\passwd file). If this presents a security issue, you can simply remove these password entries manually.

13 In a default installation of the NEXUS Server, user credentials are stored for the Version Control service in the associated Passwd file. The passwords can be cleared manually. User synchronization between the NEXUS Server and the Version Control service can also be disabled completely, allowing you to specify usernames that feature Unicode symbols. This is made possible through use of an option in the LocalVault.ini file - VcsSync. For a default installation of the Altium NEXUS Server, the LocalVault.ini file can be found in the \Program Files (x86)\altium\altium NEXUS Server folder of the installation. By default, this option is enabled (set to '1'), which means user synchronization is enabled. By setting this option to '0', user synchronization is disabled. The result of disabling the option is that when a new user is added to the NEXUS Server, the passwd file will not be updated to add that new user to the list. IIS (NEXUS Server-related application pools) must be restarted after the change has been made and the INI file saved, in order for the change to be applied. With user

14 synchronization between the NEXUS Server and Version Control service disabled (VcsSync=0), a newly added user to the NEXUS Server will not be added to the local Version Control service's passwd file. The option allows synchronization to be stopped. It does not clear the password entries for synchronized users created previously. You can, however, simply remove these password entries manually. Note that while VcsSync=0, all actions relating to managed projects within local design repositories (SVN repositories created internal to the Version Control service, as well as the default Git repository - Versioned Storage) will be disabled. A new managed project can still be created, but only external repositories will be available for use as normal. Deleting a Repository To delete a repository from the NEXUS Server's Version Control service, simply click the Remove control ( ) associated with that repository, on the VCS page of the NEXUS Server's browser-based interface. Note that removing a repository from the Data Management - Design Repositories page of the Preferences dialog only removes that repository from being used by that instance of Altium NEXUS. It does not delete the repository from the NEXUS Server's Version Control service. If you sign out of the NEXUS Server and back in again, the repository will appear once more in the list of available repositories to that instance of Altium NEXUS. External repositories can be deleted, irrespective of whether or not they contain any projects. Local repositories on the other hand (those created internally through the NEXUS Server's Version Control service) can not be deleted if they contain one or more projects. You will be alerted to this, and should remove the projects first before being able to proceed with deletion. Even then, if a local repository has no projects, it will not actually be deleted, but rather moved to an archive directory (\ProgramData\Altium\NexusServerData\RepositoryDumps, for a default NEXUS Server installation). The repository will be contained within a Dump file, with a Unique ID prefix (e.g. 775f6c22-b9a1-468c-9f1f-4f217bb3be6b_central design repository.dump). Source URL: )