Service outsourcing (version management and control tools) experimental report

Comprehensive application of version management and control tools

Experiment hours: 9
Experiment types: (Demonstration, Validation, √ Comprehensive, √ Design, Research)
Experiment Requirements: (√ Compulsory, Elective)

1. The purpose of the experiment

Through the study of this experiment, master the basic usage of popular and excellent version management and control tools, understand and master the necessity and practical significance of version management and control; combined with the theoretical knowledge of software service outsourcing, focus on the software project development Use version management and control tools to carry out overall management and control skills and methods, so as to improve the work efficiency of project development, reduce management and control costs, enhance the advantages of teamwork, and improve comprehensive practical ability.

2. Experimental content

Module 1: Construction and use of SVN environment;
Module 2: Integrated application of SVN and MyEclipse10.0;
Module 3: Construction and use of Git environment;

3. Experimental requirements

1. According to the software tools required by the three modules, build and configure the environment on your own computer;
2. First realize the installation and configuration of the server and client in the stand-alone operating environment, and secondly realize the local area network environment (two people The above is a group) installation and configuration of the server and client;
3. Combined with the use requirements of your own document management or project version management and control, give examples of the specific functions of the tool (mainly operate by yourself, and cannot paste other virtual materials);
4. Organize and write documents according to the following methods and steps, and strive to combine pictures and texts with reasonable layout;
5. The content of the report in the stand-alone environment is not allowed to be the same. No more than 2 people, and a list of team members must be attached;
6. The report format is based on this document, and only need to add detailed practice content under the corresponding experimental process system, and the document structure must not be changed;
7. The electronic documents of the report are unified with "" Student ID + name.docx”, and then submit it to the corresponding task of the Blue Mo Cloud class. The final version after the completion of the three experiments is submitted to the “final task at the end of the term”. (Class number: 9643988)
8. The completion period is one week, and the submission must be completed before December 25th.

Fourth, the experimental principle, method and steps

Module 3
Construction and use of Git environment
1) Construction and configuration of stand-alone environment; (Git client)
first go to the official website to download git, https://git-scm.com

Then all the way to continue button to install successfully.
Then configure environment variables

Check the version using the command line

Successful installation.
cd The current folder path.

Use git init to initialize the local warehouse, the .git folder will appear in the original directory, which stores information about git and version records.
Then add a file modification.
First use git status to view the modified files

Open the project through idea to commit and push

2) Network environment construction and configuration; (separation of server and client)
to create a new warehouse on Gitee

Create a viewing directory

Perform project initialization to be linked remotely

3. Integrated application of Git and IDEA
   Choose to import from version control

Create a new file and commit

View in remote gitee after push

View commit history

Pull code

Revert to recover files

Update code

Merge code

Change the code and submit

Compared with SVN:
Git is a distributed SCM, while SVN is server-based, that is to say, each developer has a set of git libraries locally, and each maintains his own version (or merges other people's versions), while SVN is each After the individual writes the code, he will checkin to the server in time for merging.

Git advantages:
1. The version library is localized, supports offline submission, and is relatively independent without affecting collaborative development. Each developer has his own version control library, and can perform actions such as committing code, creating branches, etc. at will on his own version library. For example, does the developer think there is a problem with the code they submitted? It doesn't matter, because the repository is its own, rolling back history, re-committing, and merging branches will not affect other developers.
2. Less "warehouse pollution". Git will only generate one .git directory for each project. All version control information of this project is in this directory, and will not generate a .svn directory in each directory like SVN.
3. Store the content as metadata and clone the repository completely. All version information is located in the .git directory, which is a clone of the repository on your machine that has everything on the central repository, such as tags, branches, version records, etc.
4. Supports quick switching of branches to facilitate merging, and has better merging performance. You can switch between different branches in the same directory, which is convenient for merging, and the speed of merging files is faster than SVN.
5. Distributed version library, no single point of failure, good content integrity. The content store uses the SHA-1 hashing algorithm. This ensures the integrity of the code content and ensures less damage to the repository in the event of disk failures and network problems.