Compilation version automatic updating method and apparatus

Abstract

Embodiments of the invention disclose a compilation version automatic updating method and apparatus. The method comprises the steps of reading a version control file of an SVN end to obtain a version number of the SVN end; judging whether a version number of a local end is recorded in a difference record file or not; if not, copying and executing a target script from the SVN end, and storing the target script in the difference record file, thereby finishing the updating of a compilation version of the local end; if yes, further judging whether the version number of the local end is consistent with the version number of the SVN end or not; if the version number of the local end is inconsistent with the version number of the SVN end, indicating that the compilation version of the local end needs to be updated, at the moment, copying and executing the target script from the SVN end, and storing data in a generated changed file into the difference record file, thereby finishing the updating of the compilation version of the local end. According to the method, the local end can automatically finish the updating of the compilation version in the process, so that the problem caused by improper manual operation is effectively avoided and the working efficiency and security of updating the compilation version of the local end are improved.

Description

technical field [0001] The invention relates to the technical field of virtual machine compilation environment, in particular to a method and device for automatically updating a compiled version. Background technique [0002] The open source version control system (Subversion, SVN) adopts a branch management system, which distributes the overall information security functions of the system in a balanced and reasonable manner in different subsystems, so that the functions of each subsystem can be maximized. The systems complement each other, and the overall performance of the system is greater than the sum of the functions of each subsystem. [0003] Most of the latest VMware compilation environment in the current project is saved on the SVN side, and each R&D member will be equipped with his own VMware compilation environment on the local side. Since the VMware compilation environment on the SVN side is frequently updated, but because the R&D members do not know the version...

AI Technical Summary

Problems solved by technology

Since the VMware compilation environment on the SVN side is frequently updated, but because the R&D members do not know the version of the VMware compilation environment on the local side, they cannot know whether it is different from the VMware compilation environment on the SVN side, so differential updates cannot be performed, and only complete manual copy operations can be performed. , this will waste a lot of time, and there is a risk of mistakes in manual operations, and even some files will destroy their file types when copying, such as soft link files, etc., resulting in damage to the VMware compilation environment on the local side

Images