CN110716737A - System application version management system and system application version management method - Google Patents
System application version management system and system application version management method Download PDFInfo
- Publication number
- CN110716737A CN110716737A CN201910808543.9A CN201910808543A CN110716737A CN 110716737 A CN110716737 A CN 110716737A CN 201910808543 A CN201910808543 A CN 201910808543A CN 110716737 A CN110716737 A CN 110716737A
- Authority
- CN
- China
- Prior art keywords
- image file
- source code
- module
- application version
- storage module
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims abstract description 50
- 238000003860 storage Methods 0.000 claims abstract description 76
- 238000012360 testing method Methods 0.000 claims abstract description 46
- 238000011161 development Methods 0.000 claims abstract description 41
- 238000012795 verification Methods 0.000 claims abstract description 28
- 238000004519 manufacturing process Methods 0.000 claims description 54
- 230000006870 function Effects 0.000 claims description 30
- 238000009826 distribution Methods 0.000 claims 1
- 238000013507 mapping Methods 0.000 claims 1
- 238000000034 method Methods 0.000 description 20
- 238000011144 upstream manufacturing Methods 0.000 description 9
- 230000008901 benefit Effects 0.000 description 7
- 238000010276 construction Methods 0.000 description 6
- 230000008569 process Effects 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 4
- 230000010354 integration Effects 0.000 description 3
- 230000007547 defect Effects 0.000 description 2
- 230000006872 improvement Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000007613 environmental effect Effects 0.000 description 1
- 238000012804 iterative process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008054 signal transmission Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Abstract
The invention relates to the technical field of internet, in particular to a system application version management system and a system application version management method. The system comprises: the application source code receiving module is used for receiving the source code of the application; the source code function verification module is used for receiving the source code and verifying the functional integrity of the source code; the source code storage module is used for receiving and storing the source code; the mirror image file making module is used for receiving the source code and making a mirror image file of the source code; the mirror image file storage module is used for receiving and storing a mirror image file; the image file publishing module is used for receiving and publishing the image file; and the application version information storage module is used for receiving and storing the mirror image file, the development environment release result and the test environment release result. The invention stores the information of the application version released in each environment, solves the problem of disordered management of the application version in different environments, and greatly improves the version release efficiency and safety.
Description
Technical Field
The invention relates to the technical field of internet, in particular to a system application version management system and a system application version management method.
Background
Typically, the versions of software or applications (or items) are continually updated as the needs of the user change. After the code of the new version of the application program is developed, the code needs to be tested or released in the environments of development, testing and the like so as to reduce the number of bugs (defects or problems) in the new version of the application program as much as possible, and the number of the bugs is reduced to be below the required number, so that the bugs can be released to a production environment for mass production and formal use. In the existing software development cycle process, the continuous iteration speed is increasingly accelerated. Project versioning is a troublesome problem because, often, confusing versioning causes various problems with projects in an iterative process. Patent No. 201710472691.9 discloses a software version management method, device, apparatus and storage medium, which aims to realize the automation of software version integration construction.
At present, in terms of version control, a project based on a k8s (kubernets, a container cluster management system) system architecture is mainly based on tagging a main branch of a source code library with a tag (a log classification mode) and tagging a mirror image (the source code can be made into a mirror image only under the condition of complete functions), and the specific flow is as follows: after a developer submits a code, a tag mark version is manually marked on a corresponding branch, then a construction request is initiated, and when the mirror image is manufactured, a tag is marked for the mirror image. The method can only simply manage the project version, and does not control the release management and the authority management of the project version. Therefore, the existing management method has the following defects: 1. in the version iteration process, records are not made for different environments in the project iteration process, so that the version records of the corresponding environments cannot be acquired later, and the situation of version confusion occurs in the next iteration process. For example: the A application carries out version iteration in a test environment, the version is upgraded from V1.0.1 to V1.0.4, no record is made in the upgrading process, and in the next iteration, the subsequent iteration is disordered because the version of the A application running in the environment is unknown. 2. Due to the fact that the application rollback is disordered, due to the fact that the latest version information of the current environment operation and the last release operation version cannot be obtained, when the rollback is needed, the version to which the rollback is conducted is not known. 3. The cross-environment release causes production environment release accidents, for example, the new version of the application is directly released to the production environment without being released and tested in the development and test environments, and the production environment accidents may be caused by the new version of the bug.
Therefore, a system application version management system and a system application version management method are urgently needed.
Disclosure of Invention
The invention provides a system application version management system and a system application version management method, which are convenient for managing different version information of an application and are convenient to use.
In one aspect of the present invention, a system application version management system is provided, including:
the application source code receiving module is used for receiving the source code of the application and sending the source code to the source code function verification module and the source code storage module;
the source code function verification module is used for receiving the source code and verifying the function integrity of the source code, and if the verification is successful, the source code is sent to the image file manufacturing module;
the source code storage module is used for receiving and storing the source code;
the image file making module is used for receiving the source code, making an image file of the source code and sending the image file to the image file storage module, the image file release module and the application version information storage module;
the mirror image file storage module is used for receiving and storing a mirror image file;
the image file publishing module is used for receiving the image file, publishing the image file in a development environment and a test environment to obtain a development environment publishing result and a test environment publishing result, and sending the development environment publishing result and the test environment publishing result to the application version information storage module;
and the application version information storage module is used for receiving and storing the mirror image file, the development environment release result and the test environment release result.
Further, the image file making module comprises:
the source code language type identification unit is used for receiving the source code sent by the source code function verification module, identifying the language type of the source code, sending the source code to the image file making unit, and sending the identified language type to the image file making model calling unit;
the image file manufacturing model calling unit is used for receiving the language type, calling a pre-stored manufacturing model mapped by the language type and sending the manufacturing model to the image file manufacturing unit;
and the image file making unit is used for receiving the source code and the making model, obtaining an image file of the source code according to the source code and the making model, and sending the image file to the image file storage module, the image file release module and the application version information storage module.
Further, the mirror image file making module further comprises a making model pre-storing unit for pre-storing the making model mapped by the language type.
Further, the application version information storage module stores the mirror image file, the development environment release result and the test environment release result by taking the application version as a tag.
Further, the image file release module is electrically connected with the application version information storage module in a wired or wireless mode.
In a second aspect of the present invention, there is provided a system application version management method implemented based on any one of the above systems, including the following steps:
when the application source code receiving module receives the source code of the application, the source code is sent to the source code function verification module and the source code storage module;
the source code function verification module receives the source code and verifies the function integrity of the source code, and if the verification is successful, the source code is sent to the image file manufacturing module;
the source code storage module receives and stores the source code;
the image file making module receives the source code and makes an image file of the source code, and sends the image file to the image file storage module, the image file release module and the application version information storage module;
the mirror image file storage module receives and stores the mirror image file;
the image file publishing module receives and publishes the image file in a development environment and a test environment to obtain a publishing result of the development environment and a publishing result of the test environment and sends the publishing result of the development environment and the publishing result of the test environment to the application version information storage module;
and the application version information storage module receives and stores the mirror image file, the development environment release result and the test environment release result.
Further, the mirror image file making module comprises a source code language type identification unit, a mirror image file making model retrieving unit and a mirror image file making unit, wherein,
the source code language type identification unit receives a source code sent by the source code function verification module, identifies the language type of the source code, sends the source code to the image file making unit, and sends the identified language type to the image file making model calling unit;
the image file manufacturing model calling unit receives the language type, calls a pre-stored manufacturing model mapped by the language type and sends the manufacturing model to the image file manufacturing unit;
the image file making unit receives the source code and the making model, obtains an image file of the source code according to the source code and the making model, and sends the image file to the image file storage module, the image file publishing module and the application version information storage module.
Further, the method also comprises the following steps: and pre-storing a manufacturing model mapped by the language type by using a manufacturing model pre-storing unit in the mirror image file manufacturing module.
Compared with the prior art, the system application version management system and the system application version management method provided by the invention have the following advantages that:
according to the invention, the release result of the application version released in the development environment and the test environment is stored, so that the problem of disordered application version management in different environments is solved, the version release efficiency and safety are greatly improved, and the method and the structure have the advantages of simple structure and method operation, low cost and high application version management efficiency.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
FIG. 1 is a block diagram of a device connection of a system application version management system according to an embodiment of the present invention;
fig. 2 is a flowchart of a system application version management method according to an embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
It will be understood by those skilled in the art that, unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the prior art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
The embodiment provides a system application version management system and a system application version management method.
As shown in fig. 1 (the arrow in fig. 1 is the signal transmission direction), the system application version management system of the present embodiment includes:
the application source code receiving module is used for receiving the source code of the application and sending the source code to the source code function verification module and the source code storage module;
the source code function verification module is used for receiving the source code and verifying the function integrity of the source code, and if the verification is successful, the source code is sent to the image file manufacturing module;
the source code storage module is used for receiving and storing the source code;
the image file making module is used for receiving the source code, making an image file of the source code and sending the image file to the image file storage module, the image file release module and the application version information storage module;
the mirror image file storage module is used for receiving and storing a mirror image file;
the image file publishing module is used for receiving the image file, publishing the image file in a development environment and a test environment to obtain a development environment publishing result and a test environment publishing result, and sending the development environment publishing result and the test environment publishing result to the application version information storage module;
and the application version information storage module is used for receiving and storing the mirror image file, the development environment release result and the test environment release result.
According to the invention, the release result of the application version released in the development environment and the test environment is stored, so that the problem of disordered management of the application version in different environments is solved, the version release efficiency and safety are greatly improved, and the method has the advantages of simple structure, low cost and high application version management efficiency.
The development environment and the test environment are environments at least required to be verified or released before the application new version is released, and in specific implementation, according to the needs of a user, the image file releasing module can also release the image file in other releasing environments, such as a production environment and the like, and store the releasing result, so that the management efficiency of the application version can be improved.
As shown in fig. 1, in specific implementation, the image file creation module includes:
the source code language type identification unit is used for receiving the source code sent by the source code function verification module, identifying the language type of the source code, sending the source code to the image file making unit, and sending the identified language type to the image file making model calling unit;
the image file manufacturing model calling unit is used for receiving the language type, calling a pre-stored manufacturing model mapped by the language type and sending the manufacturing model to the image file manufacturing unit;
and the image file making unit is used for receiving the source code and the making model, obtaining an image file of the source code according to the source code and the making model, and sending the image file to the image file storage module, the image file release module and the application version information storage module.
In specific implementation, different production models can be selected according to different language types of the source code, for example, if the source code is a Java language type, the production model mapped by the source code is a construction tool jenkins (which is an open source software project and is a continuous integration tool developed based on Java). The technology for manufacturing the mirror image file of the source code by using jenkins is mature and easy to realize. In specific implementation, the user can also adopt other tools to make the image file according to the needs.
In specific implementation, the mirror image file making module further comprises a making model pre-storing unit for pre-storing the making model mapped by the language type. For example, if the source code is of java language type, the production model mapped by the source code is the construction tool jenkins.
In specific implementation, the application version information storage module stores the mirror image file, the development environment release result and the test environment release result by taking the application version as a tag. Each application version corresponds to one image file and a plurality of release results, and the image files and the release results under various environments are classified and stored according to different application versions, so that the image files and the release results under various environments are convenient to search, call and use.
When the method is specifically implemented, the image file release module is electrically connected with the application version information storage module in a wired or wireless mode. The wired mode can be a cable, the wireless mode can be any one of 3G or 4G or WIFI mode, the several radio connection modes are mature in technology and easy to implement and maintain, and the specific connection mode can be selected and set according to the requirements of users.
As shown in fig. 2, a system application version management method implemented based on the system in the foregoing embodiment of the present embodiment includes the following steps:
s1, when the application source code receiving module receives the source code of the application, the source code is sent to the source code function verification module and the source code storage module;
s2, the source code function verification module receives the source code and verifies the function integrity of the source code, and if the verification is successful, the source code is sent to the image file making module;
s3, the source code storage module receives and stores the source code;
s4, the image file making module receives the source code and makes the image file, and sends the image file to the image file storage module, the image file release module and the application version information storage module;
s5, the mirror image file storage module receives and stores the mirror image file;
s6, the image file release module receives and releases the image file in the development environment and the test environment to obtain a release result of the development environment and a release result of the test environment, and sends the release results to the application version information storage module;
and S7, the application version information storage module receives and stores the mirror image file, the development environment release result and the test environment release result.
According to the invention, the release result of the application version released in the development environment and the test environment is stored, so that the problem of disordered management of the application version in different environments is solved, the version release efficiency and safety are greatly improved, and the method has the advantages of simple operation, low cost and high management efficiency of the application version.
The development environment and the test environment are environments at least required to be verified or released before the application new version is released, and in specific implementation, the image file release module can also release the image file in other release environments, such as a production environment and the like, according to the requirements of a user, so that the management efficiency of the application version can be improved.
In specific implementation, the mirror image file making module comprises a source code language type identification unit, a mirror image file making model calling unit and a mirror image file making unit, wherein,
the source code language type identification unit receives a source code sent by the source code function verification module, identifies the language type of the source code, sends the source code to the image file making unit, and sends the identified language type to the image file making model calling unit;
the image file manufacturing model calling unit receives the language type, calls a pre-stored manufacturing model mapped by the language type and sends the manufacturing model to the image file manufacturing unit;
the image file making unit receives the source code and the making model, obtains an image file of the source code according to the source code and the making model, and sends the image file to the image file storage module, the image file publishing module and the application version information storage module.
In specific implementation, different production models can be selected according to different language types of the source code, for example, if the source code is a Java language type, the production model mapped by the source code is a construction tool jenkins (which is an open source software project and is a continuous integration tool developed based on Java). The technology for manufacturing the mirror image file of the source code by using jenkins is mature and easy to realize. In specific implementation, the user can also adopt other tools to make the image file according to the needs.
In specific implementation, the mirror image file making module further comprises a making model pre-storing unit for pre-storing the making model mapped by the language type.
When the method is implemented specifically, the method further comprises the following steps: and pre-storing a manufacturing model mapped by the language type by using a manufacturing model pre-storing unit in the mirror image file manufacturing module. For example, if the source code is of java language type, the production model mapped by the source code is the construction tool jenkins.
In specific implementation, the application version information storage module stores the mirror image file, the development environment release result and the test environment release result by taking the application version as a tag. Each application version corresponds to one image file and a plurality of release results, and the image files and the release results under various environments are classified and stored according to different application versions, so that the image files and the release results under various environments are convenient to search, call and use.
When the method is specifically implemented, the image file release module is electrically connected with the application version information storage module in a wired or wireless mode. The wired mode can be a cable, the wireless mode can be any one of 3G or 4G or WIFI mode, the several radio connection modes are mature in technology and easy to implement and maintain, and the specific connection mode can be selected and set according to the requirements of users.
The improvement in the above system embodiment also belongs to the improvement in the above method embodiment, and is not described in detail in the method embodiment.
A workflow embodiment of the system application version management method of this embodiment is as follows: after the source code of an application new version is edited, sending the source code to an application source code receiving module, and after the application source code receiving module receives the source code, sending the received source code to a source code function verification module and a source code storage module; the source code storage module stores the source code; the source code function verifying module verifies the integrity of the source code function, and if the verification is successful, namely the source code function is complete (the source code can be operated according to a preset rule, and whether the function is complete or not is verified), the source code is sent to the image file manufacturing module; the method comprises the following steps that a mirror image file making module firstly identifies the language type of a source code, such as java language or c language type, and different making models are called according to different language types, and also can make a docker mirror image of an application source code through a self-defined docker file; the mirror image file storage module stores the mirror image file; the image file publishing module publishes the image file in a development environment and a test environment (namely, tests the image file to reduce bugs), obtains publishing results (such as information of development environment test time, obtained bugs, solution or not, test or not and the like) under each environment, and sends the publishing results under each environment to the application version information storage module; the application version information storage module receives and stores the image file and the release result under each environment (which may be referred to as version information corresponding to the application or the image file). If the 0.1 version of an application is released in a development environment, the number of the acquired bugs is 10 as a release result, the release starting time is x months and x days in x years, the release ending time is x months and x days in x years, and the test is completed/succeeded; and issuing under a test environment, wherein the number of the acquired bugs is 10 as a result of issuing, the issuing starting time is x months and x days in x years, the ending time is x months and x days in x years, and the test is completed/succeeded.
An embodiment of a usage flow of the system application version management method of the present embodiment is as follows: after receiving the release instruction, the release platform triggers and starts the release task through a release task module of the release platform, after the release task is started, the release component applies the version information corresponding to the id number to the version information storage module according to the unique id number (such as the application version number) of the application, if the version information exists in the application version information storage module, the release system is triggered, and if the version information does not exist in the version information base, the information without the release information is fed back to related personnel. Before the application release, the release system may also obtain the latest release result of the upstream environment (the upstream environment of the application release is the development environment and the test environment, and the upstream environment of the test environment is the development environment) from the application version information storage module, if the release result of the upstream environment exists, the next link is entered, the application is released according to the release type provided in the release information, for example, if the release type is release, the release type is rollback, and the corresponding rollback is the specified application version and the release result in each environment; and if the release result of the upstream environment does not exist, proving that the application of the version is not verified in the upstream environment, prohibiting release, and feeding back release prohibition information.
The invention makes the version information of each application clear and transparent through recording the version information and checking the release result of the upstream environment when releasing, all the version information is in a traceable state, the upstream environment can be checked when releasing each version, the application can be randomly released to the downstream environment without verification, accidents caused by chaos of different environment versions are avoided, and the version information of the upstream environment is ensured to be always preferred to the downstream environment. By the implementation of the version management scheme, the management problem of the application version, the version disorder problem of different environments and the environmental accident problem caused by unconditional release are effectively solved, the version release efficiency and safety are greatly improved, and the automatic release and version iteration process is more perfect and healthy.
For simplicity of explanation, the method embodiments are described as a series of acts or combinations, but those skilled in the art will appreciate that the embodiments are not limited by the order of acts described, as some steps may occur in other orders or concurrently with other steps in accordance with the embodiments of the invention. Further, those skilled in the art will appreciate that the embodiments described in the specification are presently preferred and that no particular act is required to implement the invention.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (10)
1. A system application version management system, comprising:
the application source code receiving module is used for receiving the source code of the application and sending the source code to the source code function verification module and the source code storage module;
the source code function verification module is used for receiving the source code and verifying the function integrity of the source code, and if the verification is successful, the source code is sent to the image file manufacturing module;
the source code storage module is used for receiving and storing the source code;
the image file making module is used for receiving the source code, making an image file of the source code and sending the image file to the image file storage module, the image file release module and the application version information storage module;
the mirror image file storage module is used for receiving and storing a mirror image file;
the image file publishing module is used for receiving the image file, publishing the image file in a development environment and a test environment to obtain a development environment publishing result and a test environment publishing result, and sending the development environment publishing result and the test environment publishing result to the application version information storage module;
and the application version information storage module is used for receiving and storing the mirror image file, the development environment release result and the test environment release result.
2. The system application version management system according to claim 1, wherein the image file creation module comprises:
the source code language type identification unit is used for receiving the source code sent by the source code function verification module, identifying the language type of the source code, sending the source code to the image file making unit, and sending the identified language type to the image file making model calling unit;
the image file manufacturing model calling unit is used for receiving the language type, calling a pre-stored manufacturing model mapped by the language type and sending the manufacturing model to the image file manufacturing unit;
and the image file making unit is used for receiving the source code and the making model, obtaining an image file of the source code according to the source code and the making model, and sending the image file to the image file storage module, the image file release module and the application version information storage module.
3. The system application version management system according to claim 2, wherein the image file creation module further comprises a creation model pre-storing unit for pre-storing a creation model of the language type mapping.
4. The system application version management system according to claim 3, wherein the application version information storage module stores the mirroring file, the development environment release result, and the test environment release result with the application version as a tag.
5. The system application version management system according to claim 4, wherein the image file distribution module is electrically connected to the application version information storage module in a wired or wireless manner.
6. A system application version management method implemented based on the system of claim 1, comprising the steps of:
when the application source code receiving module receives the source code of the application, the source code is sent to the source code function verification module and the source code storage module;
the source code function verification module receives the source code and verifies the function integrity of the source code, and if the verification is successful, the source code is sent to the image file manufacturing module;
the source code storage module receives and stores the source code;
the image file making module receives the source code and makes an image file of the source code, and sends the image file to the image file storage module, the image file release module and the application version information storage module;
the mirror image file storage module receives and stores the mirror image file;
the image file publishing module receives and publishes the image file in a development environment and a test environment to obtain a publishing result of the development environment and a publishing result of the test environment and sends the publishing result of the development environment and the publishing result of the test environment to the application version information storage module;
and the application version information storage module receives and stores the mirror image file, the development environment release result and the test environment release result.
7. The system application version management method according to claim 6, wherein the image file creation module includes a source code language type identification unit, an image file creation model retrieval unit, and an image file creation unit, wherein,
the source code language type identification unit receives a source code sent by the source code function verification module, identifies the language type of the source code, sends the source code to the image file making unit, and sends the identified language type to the image file making model calling unit;
the image file manufacturing model calling unit receives the language type, calls a pre-stored manufacturing model mapped by the language type and sends the manufacturing model to the image file manufacturing unit;
the image file making unit receives the source code and the making model, obtains an image file of the source code according to the source code and the making model, and sends the image file to the image file storage module, the image file publishing module and the application version information storage module.
8. The system application version management method according to claim 7, further comprising the steps of: and pre-storing a manufacturing model mapped by the language type by using a manufacturing model pre-storing unit in the mirror image file manufacturing module.
9. The system application version management method according to claim 8, wherein the application version information storage module stores the mirroring file, the development environment release result, and the test environment release result with the application version as a tag.
10. The system application version management method according to claim 9, wherein the image file release module is electrically connected to the application version information storage module in a wired or wireless manner.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910808543.9A CN110716737A (en) | 2019-08-29 | 2019-08-29 | System application version management system and system application version management method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910808543.9A CN110716737A (en) | 2019-08-29 | 2019-08-29 | System application version management system and system application version management method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110716737A true CN110716737A (en) | 2020-01-21 |
Family
ID=69209499
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910808543.9A Pending CN110716737A (en) | 2019-08-29 | 2019-08-29 | System application version management system and system application version management method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110716737A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112148329A (en) * | 2020-09-18 | 2020-12-29 | 湖南联盛网络科技股份有限公司 | Code version automatic updating method and device, computer equipment and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103677765A (en) * | 2012-08-31 | 2014-03-26 | 腾讯科技（深圳）有限公司 | Version automatic issuing method, device and storage medium |
| CN106775760A (en) * | 2017-01-04 | 2017-05-31 | 郑州云海信息技术有限公司 | The method and system of container mirror image to mirror image warehouse are uploaded based on source code library |
| CN107391127A (en) * | 2017-07-06 | 2017-11-24 | 上海斐讯数据通信技术有限公司 | Software version information store method and system |
| US20180253296A1 (en) * | 2015-10-30 | 2018-09-06 | Hewlett Packard Enterprise Development Lp | Software kit release management |
| CN109814889A (en) * | 2019-01-30 | 2019-05-28 | 北京百度网讯科技有限公司 | Method and apparatus for updating source code library |
| CN109960643A (en) * | 2017-12-22 | 2019-07-02 | 网宿科技股份有限公司 | A kind of code test method and device |
-
2019
- 2019-08-29 CN CN201910808543.9A patent/CN110716737A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103677765A (en) * | 2012-08-31 | 2014-03-26 | 腾讯科技（深圳）有限公司 | Version automatic issuing method, device and storage medium |
| US20180253296A1 (en) * | 2015-10-30 | 2018-09-06 | Hewlett Packard Enterprise Development Lp | Software kit release management |
| CN106775760A (en) * | 2017-01-04 | 2017-05-31 | 郑州云海信息技术有限公司 | The method and system of container mirror image to mirror image warehouse are uploaded based on source code library |
| CN107391127A (en) * | 2017-07-06 | 2017-11-24 | 上海斐讯数据通信技术有限公司 | Software version information store method and system |
| CN109960643A (en) * | 2017-12-22 | 2019-07-02 | 网宿科技股份有限公司 | A kind of code test method and device |
| CN109814889A (en) * | 2019-01-30 | 2019-05-28 | 北京百度网讯科技有限公司 | Method and apparatus for updating source code library |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112148329A (en) * | 2020-09-18 | 2020-12-29 | 湖南联盛网络科技股份有限公司 | Code version automatic updating method and device, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9940225B2 (en) | Automated error checking system for a software application and method therefor | |
| US7917895B2 (en) | Automated software testing and validation system | |
| US8150674B2 (en) | Automated testing platform for event driven systems | |
| CN111158674B (en) | Component management method, system, device and storage medium | |
| WO1998027488A1 (en) | Software release metric reporting system and method | |
| CN107992404A (en) | A kind of Software Automatic Testing Method and device | |
| US11055078B2 (en) | Systems and methods for deploying software products to environments | |
| CN113111000B (en) | Continuous integrated automatic test system and method, electronic equipment and storage medium | |
| US10824541B1 (en) | System and method for test data fabrication | |
| WO2015096661A1 (en) | Project creation method and device based on configuration system, project test method and device, and background test method and device for configuration system | |
| CN113448854A (en) | Regression testing method and device | |
| US20210124575A1 (en) | Providing build avoidance without requiring local source code | |
| CN117009243A (en) | Chip performance automatic test method, device, computer equipment and storage medium | |
| CN110716737A (en) | System application version management system and system application version management method | |
| US6240529B1 (en) | Debugging method and debugging apparatus for microcomputer system and recording medium on which debug program is recorded | |
| CN112069073A (en) | Test case management method, terminal and storage medium | |
| CN115408032A (en) | Data model management method, device, server, medium and product | |
| CN110750435A (en) | Test case management method and device | |
| CN114996127A (en) | Intelligent test method and system for solid state disk firmware module | |
| CN115204810A (en) | Project management method, device and storage medium based on RPA and automation script | |
| CN115328524A (en) | Patch merging method and device, computer equipment and storage medium | |
| CN113934758A (en) | Vehicle fault repairing method and device, vehicle-mounted terminal, server and storage medium | |
| US20160275002A1 (en) | Image capture in application lifecycle management for documentation and support | |
| CN117573564B (en) | Method for automatically identifying differences based on gitlab code submitted log | |
| US20220365868A1 (en) | System and method for performing end-to-end simulation and testing of an iot application |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200121 |