SCM Software Configuration Management (2) SVN management platform establishment and detailed settings

Due to the problem of overwriting the new version of documents and mixed version during the cooperation process, these problems can be solved by using SVN version control, I just didn't play the real role of this platform. When you often worry about many versions, you will feel that SVN is powerful and a good tool for cooperation.

It manages the development of a team and enables the development of hundreds of developers. It groups users and assigns different permissions to users in different groups.

The following describes how to build the svn platform and how to set permissions for each user.

We can use subversion non-visual servers. This configuration of user permissions and user permissions can be difficult for first-time learners. It is mainly used inLinuxIn the system, we recommend that you use visual visualsvn server and tortoisesvn in combination on the window to make applications and settings easier.

[Installation]

It is easy to install. Just click "Next". tortoisesvn is bound with the window shell. After installation, it is as follows:

 

[Add User]

That is, the project manager is usually responsible for managing the entire project by setting the highest permissions, including reading, writing, deleting, and adding files. Other personnel are assigned different levels of permissions based on their responsibilities.

For example, add a manager and three users.

[Import project]

To import a project, you must use the tortoisesvn client. Right-click the resource manager and choose tortoisesvn> repo-browser ",

Then, right-click the pop-up browser and select "add folder" to add the project folder.

The completion figure is as follows:

This system uses a classic three-tier architecture, where each of the three persons is responsible for one layer and does not have the modification permission for the layer that they are not responsible. Only the project manager has the right to modify all projects.

[Permission settings]

In user settings, there is an everyone that represents the permissions of all people. setting this role as a read-only attribute in the general repository will facilitate the following settings, because in future projects, A Team member may only be responsible for a little bit of the project. If everyone is set to read/write, each team member will inherit this attribute and have read and write permissions on the project, you also need to set other parts of the project.

 

If you set everyone to readonly, you only need to modify the work content corresponding to each member. This is easier to set.

The procedure is as follows:

Right-click the BLL folder and choose Properties to set the user's permission to use the folder:

 

Other user settings are the same.

Now that the establishment of the svn platform is basically complete, you can start the next step of development. In the company, you usually need to set up the platform first to start your work.

It solves many problems such as team development, chaotic submission, version conflicts, and difficult project management.

Of course, SCM software is not limited to this type. With the development of software, there may be more convenient, concise, and more comprehensive development and management tools. We need to learn the opposite, only by analogy can we quickly master new technologies and knowledge.