Software packaging and publishing management method

Abstract

The invention discloses a software packaging and publishing management method. According to the method, after iterative content of a version is confirmed, a corresponding version number is selected during packaging, only a needed script is generated, the content needing to be published is precisely controlled, and codes which are not tested are prevented from being deployed into a formal environment; when script packaging is executed, components with source codes not updated are not recompiled, therefore, only changed parts are compiled, compiling time is shortened, and incremental compiling is realized; based on version tracing of historical version logs, a log directory is generated every time packaging is performed; and when a user needs to generate a historical version of a certain time, logs of the needed historical version are selected, a packaging script is selected from the logs, and a script command is executed to generate a needed package. In this way, it is not needed to back up generated packages every time packaging is performed, only the package generated this time is stored, therefore, storage space is reduced, and maintenance of the historical version is realized with little hard-disk space.

Description

technical field [0001] The invention belongs to the technical field of continuous integration, and relates to a method for managing software package release. Background technique [0002] Jenkins is a widely used open source continuous integration software, compatible with various forms of compilation and packaging work, supports multiple SCM protocols, has good support for MAVEN-based compilation and packaging, and supports automatic timing and scripting. However, it uses the svn address + the latest version mode for packaging, which cannot perform fine control of component versions. When packaging, it uses full compilation, and the compilation command will be executed regardless of whether the code has been changed, which takes a lot of time. Therefore the following problems may arise: [0003] 1. After testing, the previously submitted code and the JAR package deployed to the private server will be incorporated into the latest release package, and there will be risks bro...

AI Technical Summary

Problems solved by technology

[0003] 1. After testing, the previously submitted code and the JAR package deployed to the private server will be incorporated into the latest release package, and there will be risks brought by untested code in the production environment;

[0004] 2. Some codes that have been tested but failed will affect the release of the version, especially when modifying existing products and functions that have already been launched, the version will not be released;

[0005] 3. The version backtracking can only be backed up manually by means of backup, which takes up a lot of space and the status of each component contained in it is a black box state