The basic operation and understanding SVN_SVN

 

 

SVN What is? 

  svn Subversion is short, is a open source code version control system, svn is for people to develop the same project, to achieve the purpose of resource sharing tool.

 

Version control is what?

  Version Control (Revision control) refers to the management of the software development process in a variety of program code, configuration files and other documents and documentation changes. Each version can record information to facilitate problem tracking. Meanwhile version control also supports parallel development, can effectively improve the development efficiency

 

Why use SVN ?

  1, easy project backups, saving hard disk space;
  2, record each version, easy to trace the historical record.
  3, multiplayer collaborative development, sharing data;
  4, the details of the access control, allows the administrator to control the overall project

 

 

Part.1 SVN basic operations:

  1, svn workflow and architecture diagram;

    a) svn work:

  

    b) svn architecture diagram:

  

 

  

  2, svn server, client acquisition and installation:

    a) server: https://www.visualsvn.com/server/download/

    b) Client: https://tortoisesvn.net/downloads.html

     

    The default server port number 443 or 8443, after the installation is complete can be in the C: \ Program Files \ VisualSVN Server \ bin directory to find VisualSVN Server.msc server graphical application program window

    After the client TortoiseSVN-1.10.2.28392-x64-svn-1.10.3 default after installation is complete, in the folder, right-click SVN Checkout ... or TortoiseSVN appears stating that the installation was successful! [If not] restart

 

 

  3, svn server directory structure, user and permissions;

    a) Directory Structure:

      i.Repositories warehouse: storage of project files svn management, you can store source code, documentation, etc.;

      . ii  U SERS user: Create and edit user;

        II . I  G GROUPS security groups: creating and editing user groups;

    b) Creating a warehouse:

      Standard folder structure:

        1) branches branch: If you need to test new technology, or a wide range of modifications, copy the code branches to the trunk is carried out, the test may be incorporated into the backbone of the correct

        2) tags released: released version tags to put in;

        3) trunk trunk: The main development directory;

    c) create a user: Each developer needs to have its own svn account;

    d) create a group: configure different privileges for each department, easy to manage;

    e) assign permissions: a user / group to assign permissions warehouse or directory;

 

 

  4, svn common operations:

    a) checkout detection: initial download - svn first connection server corresponding to the time needed to download data warehouse (data warehouse if any);

    b) add new: svn new data to the server;

    c) update Update: update data - data checking svn server is consistent with local data, and if not then download the changed / new section, but does not remove local data;

    d) delete Delete: Delete svn data (need to match the commit command);

    e)revert 回滚:将指定版本的代码回滚到本地,如要提交到服务器需要搭配commit命令;

    f)代码冲突: 在多人同时开发一个类,提交的时候容易出现代码冲突,也可以理解为版本冲突;

     

     g)其他操作:

      i.下载指定版本号的文件;

      ii.代码对比工具;

      iii.账号保存与注销;


Guess you like

Origin www.cnblogs.com/1138720556Gary/p/11298766.html