Construction of SVN multi-version library environment

1. 

1. Start SVN 
sudo svnserve -d -r /home/data/svn/ 
where -d means daemon process, -r means execute 
/home/data/svn/ in the background, which is the installation directory of svn 
2. Close SVN 
and take it here
ps -ef|grep svnserve 
root 4967 1 0 Aug23 ? 00:00:00 svnserve -d -r repository/  
here kill -9 4967 kills the process, this 4967 is the process number  2 

, 

1, Determine the server 

2. Determine the configuration management tool (SVN)               

3. Build the root directory of the repository, as shown in the figure below, there are two libraries project1 and project2 in the svnroot root directory 


 


4. Create the first project project1, command: svnadmin create E:\svnroot\project1 

5. Create the second project project2, command: svnadmin create E:\svnroot\project2 

6. For the convenience of management, set the passwords and permissions of all repositories in the same file. The operation steps are as follows : 

  6.1 Take out the authz and passwd files in the conf folder under project1 to the svnroot root directory 

   6.2 Modify the svnserve.conf file under the conf folder of each repository directory, and change 

    # anon-access = read 

    #auth-access = write 

    # password-db = passwd 

    #authz-db = authz 

to: 

    anon-access = none 

    auth-access= write 

    password-db=../../passwd 

    authz-db=..  /../authz

(password-db=../ ../passwd,authz-db=../../ authz stands for relative path rather than absolute path) 

7. Define several roles for testing 

  7.1 Configuration administrator (svnadmin) to manage the entire library 

  7.2 Project manager (manage) for related management documents 

  7.3 Developer (dev) , test whether the development is normal 

8. Add a role below to 

   open the passwd file in the svnroot directory. The creation method is to add username = passwd under [user], remember the spaces before and after "=", as shown below: (svnadmin controls all projects and manages them uniformly. ) 


 

9. Assign permissions to roles: Suppose (quxin is the project manager of project1, huzhixin is the project manager of project2, dev1 and dev2 are developers of project1, dev3 and dev4 are developers of project2, test1 is the tester of project1, and test2 is The tester of project2) 

library directory and specific permissions are shown in the following figure: 

Library directory                           

 


permissions grouping: 


 


specific permissions: (in the root directory, svnadmin has all permissions, others only have read permissions, to set subdirectory permissions, you 

need to set the subdirectory superior Set the permissions of individual files as follows:) 


 



To start the SVN service, you can start it in the dos command, or you can install the SVN service in the service management 

and start the service in the DOS command: svnserve –d –r E:\ If svnroot 

installs the service in the service management, the simple way is to download a SVNService.exe file, put it under the bin folder of the subversion installation directory, and then run it in the dos command. The 

operation method is as follows: SVNService –install –d –rE :\svnroot 

10. Install the client, connect the server to the library to be accessed, if you access project1: svn://172.16.26.28/project1, use the same method to access project2, and so on to more repository projects. 

11. Tools 

    SVN Server: Subversion 1.5 

    Client: TrotoiseSVN 1.5 

12. Download address: www.iusesvn.com, you need to register to enter the download to download the relevant version of the tool. 

13. Definition of relevant roles 

Configuration administrator CM: 

      The entire configuration management library is managed by the configuration administrator. The configuration administrator is responsible for assigning and modifying the permissions of other members and maintaining all directories and configuration items. 

Project Manager: 

      The development manager is responsible for leading the completion of demand analysis and overall system design in this project, and is responsible for the overall progress of the project. The development manager has the right to read management documents and can read and write project documents; 

development team leader: 

       The development team leader has the task of organizing and managing the work of the team, and the development team leader also needs to undertake certain development tasks. Task. The development team leader has read permission on management documents, read permission on the modules responsible for the group, and read and write permissions on the modules they are responsible for; 

development engineer: 

     the development engineer completes specific development tasks and is responsible for the module directory Have read and write rights, and have read rights to management documents; 

test team leader:  The

       test team leader is responsible for organizing the test, giving the test plan and test plan, and verifying the test report. The test team leader has read permission to all directories and read and write permissions to the test directory; 

test engineer:  The

        test engineer is responsible for completing the test work, including test case development and test execution, and test report writing. Test engineers have read permissions on the modules they are responsible for, and read and write permissions on the test case directory. 

QA engineer: 
       QA engineer has read permission to all directories, and has read and write permission to QA document directory. 

Senior Manager: 

       Senior managers are responsible for the coordination of departments and various projects. It has read and write permissions to the department's public library PUB, and has read permissions to each project. 


Follow to get more it videos java springboot