CN112596784A - Iterative version deployment method and device - Google Patents
Iterative version deployment method and device Download PDFInfo
- Publication number
- CN112596784A CN112596784A CN202011589774.4A CN202011589774A CN112596784A CN 112596784 A CN112596784 A CN 112596784A CN 202011589774 A CN202011589774 A CN 202011589774A CN 112596784 A CN112596784 A CN 112596784A
- Authority
- CN
- China
- Prior art keywords
- version
- target account
- iterative
- deployment
- iteration
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 43
- 238000012360 testing method Methods 0.000 claims abstract description 57
- 238000004519 manufacturing process Methods 0.000 claims abstract description 23
- 238000004590 computer program Methods 0.000 claims description 18
- 238000012790 confirmation Methods 0.000 claims description 18
- 238000004806 packaging method and process Methods 0.000 claims description 10
- 238000013515 script Methods 0.000 claims description 8
- 238000005516 engineering process Methods 0.000 abstract description 5
- 238000010586 diagram Methods 0.000 description 11
- 238000012423 maintenance Methods 0.000 description 9
- 230000008569 process Effects 0.000 description 7
- 230000005540 biological transmission Effects 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 238000004891 communication Methods 0.000 description 3
- 238000011161 development Methods 0.000 description 3
- 238000012552 review Methods 0.000 description 3
- 238000011156 evaluation Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012856 packing Methods 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
- 238000000926 separation method Methods 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides an iterative version deployment method and device, wherein the method comprises the following steps: detecting that the iteration version is finished, and testing the iteration version; after the test is passed, determining whether the iterative version is agreed to be deployed through the first target account number; when the determination result is that the deployment is agreed, the iteration version is deployed through the production server, the problems that the codes of the existing BUG are easy to be on line due to the fact that the new iteration version is automatically packaged and deployed in the related technology, and production accidents occur once the codes of the BUG are on line, and large loss is caused can be solved.
Description
Technical Field
The invention relates to the field of communication, in particular to an iterative version deployment method and device.
Background
In the existing automatic deployment, a code version management server is monitored through Jenkins, and when the change of codes on the code version management server is found, the codes are automatically downloaded, compiled, packaged, deployed and the like. In the whole process, the method is carried out through a configured process, and the configured process comprises the current setting and written scripts of Jenkins.
In the existing Jenkins automatic deployment, codes can be automatically packaged and deployed, so that the codes of existing BUG BUGs are easy to be on line, and production accidents can happen once the codes of the BUG BUGs are on line, and great loss is caused.
Aiming at the problems that codes of the existing BUG are easy to be on line due to automatic packaging and deployment of a new iteration version in the related technology, and production accidents occur once the codes of the BUG are on line, so that great loss is caused, a solution is not provided.
Disclosure of Invention
The embodiment of the invention provides an iterative version deployment method and device, which at least solve the problems that codes of existing BUGs are easy to be on line due to automatic packaging and deployment of new iterative versions in related technologies, and production accidents occur once the codes of the BUGs are on line, so that great loss is caused.
According to an embodiment of the present invention, there is provided an iterative version deployment method including:
detecting that the iteration version is finished, and testing the iteration version;
after the test is passed, determining whether the iterative version is agreed to be deployed through the first target account number;
and in the case that the determination result is that the deployment is agreed, deploying the iteration version through the production server.
Optionally, before determining whether to approve deployment of the iterative version through the first target account number, the method further includes:
sending a work order carrying work order information to a third target account, wherein the work order information comprises an application to be issued, version information, a code warehouse global information tracking git address and a label tag;
and comparing the existing version on the line with the iteration version through the third target account to obtain a comparison result, and storing the code iteration version.
Optionally, before the iterative version is deployed by a production server, the method further comprises:
sending a deployment confirmation notification to the third target account, wherein the third target account is used for performing flow configuration and script writing;
and downloading the codes corresponding to the iterative versions according to the work order information, and packaging the codes corresponding to the iterative versions.
Optionally, determining whether to approve deployment of the iterative version by the target account number includes:
sending a confirmation request for determining the iteration version to the first target account, wherein the confirmation request carries the comparison result;
and receiving a determination message sent after the iterative version is determined by the first target account, wherein the determination message carries the determination result.
Optionally, the testing the iterative version comprises:
sending a test prompt for testing the iteration version to a second target account in a message or mail mode;
and receiving a test completion message sent after the second target account tests the iteration version and passes the test.
According to another embodiment of the present invention, there is also provided an iterative version deployment method, including:
the test module is used for detecting that the iteration version is finished and testing the iteration version;
the determining module is used for determining whether the iterative version is agreed to be deployed or not through the first target account number after the test is passed;
and the deployment module is used for deploying the iteration version through the production server under the condition that the determined result is that the deployment is agreed.
Optionally, the apparatus further comprises:
the first sending module is used for sending a work order carrying work order information to a third target account, wherein the work order information comprises an application to be issued, version information, a code warehouse git address and a label tag;
and the comparison module is used for comparing the existing version on the line with the iteration version through the third target account to obtain a comparison result and storing the code iteration version.
Optionally, the apparatus further comprises:
a second sending module, configured to send a deployment confirmation notification to the third target account, where the third target account is used to perform flow configuration and script writing;
and the packaging module is used for downloading the codes corresponding to the iterative versions according to the work order information and packaging the codes corresponding to the iterative versions.
Optionally, the determining module includes:
a first sending submodule, configured to send a confirmation request for determining the iterative version to the first target account, where the confirmation request carries the comparison result;
and the first receiving submodule is used for receiving a determination message sent after the iterative version is determined by the first target account, wherein the determination message carries the determination result.
Optionally, the test module comprises:
the second sending submodule is used for sending a test prompt for testing the iterative version to a second target account in a message or mail mode;
and the second receiving submodule is used for receiving a test completion message which is sent after the second target account tests the iteration version and passes the test.
According to a further embodiment of the present invention, a computer-readable storage medium is also provided, in which a computer program is stored, wherein the computer program is configured to perform the steps of any of the above-described method embodiments when executed.
According to yet another embodiment of the present invention, there is also provided an electronic device, including a memory in which a computer program is stored and a processor configured to execute the computer program to perform the steps in any of the above method embodiments.
According to the invention, the completion of the iteration version is detected, and the iteration version is tested; after the test is passed, determining whether the iterative version is agreed to be deployed through the first target account number; and under the condition that the determined result is that the deployment is agreed, the iterative version is deployed through the production server, so that the problems that the codes of the existing BUG are easy to be on line due to the fact that the new iterative version is automatically packaged and deployed in the related technology, and production accidents occur once the codes of the BUG are on line, and large loss is caused can be solved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:
fig. 1 is a block diagram of a hardware structure of a mobile terminal of an iterative version deployment method according to an embodiment of the present invention;
FIG. 2 is a flow diagram of an iterative version deployment method according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a Jenkins review based automated deployment process according to an embodiment of the present invention;
FIG. 4 is a block diagram of an iterative version deployment device according to an embodiment of the present invention;
FIG. 5 is a block diagram one of an iterative version deployment apparatus in accordance with a preferred embodiment of the present invention;
fig. 6 is a block diagram two of an iterative version deployment apparatus in accordance with a preferred embodiment of the present invention.
Detailed Description
The invention will be described in detail hereinafter with reference to the accompanying drawings in conjunction with embodiments. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.
It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.
Example 1
The method provided by the first embodiment of the present application may be executed in a mobile terminal, a computer terminal, or a similar computing device. Taking a mobile terminal as an example, fig. 1 is a hardware structure block diagram of a mobile terminal of an iterative version deployment method according to an embodiment of the present invention, and as shown in fig. 1, the mobile terminal may include one or more processors 102 (only one is shown in fig. 1) (the processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA), and a memory 104 for storing data, and optionally, the mobile terminal may further include a transmission device 106 for a communication function and an input/output device 108. It will be understood by those skilled in the art that the structure shown in fig. 1 is only an illustration, and does not limit the structure of the mobile terminal. For example, the mobile terminal may also include more or fewer components than shown in FIG. 1, or have a different configuration than shown in FIG. 1.
The memory 104 may be used to store a computer program, for example, a software program and a module of application software, such as a computer program corresponding to the iterative version deployment method in the embodiment of the present invention, and the processor 102 executes the computer program stored in the memory 104 to execute various functional applications and data processing, i.e., to implement the method described above. The memory 104 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include memory located remotely from the processor 102, which may be connected to the mobile terminal over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The transmission device 106 is used for receiving or transmitting data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider of the mobile terminal. In one example, the transmission device 106 includes a Network adapter (NIC) that can be connected to other Network devices through a base station to communicate with the internet. In one example, the transmission device 106 can be a Radio FrequeNcy (RF) module, which is used to communicate with the internet in a wireless manner.
Based on the foregoing mobile terminal or network architecture, an iterative version deployment method is provided in this embodiment, and fig. 2 is a flowchart of the iterative version deployment method according to the embodiment of the present invention, as shown in fig. 2, the flowchart includes the following steps:
step S202, detecting that the iteration version is finished, and testing the iteration version;
in an embodiment of the present invention, the step S202 may specifically include: and sending a test prompt for testing the iteration version to a second target account in a message or mail mode, and receiving a test completion message which is sent after the second target account tests the iteration version and passes the test, wherein the second target account corresponds to a tester, namely the tester uses the second target account to test the iteration version after receiving the test prompt.
Step S204, after the test is passed, whether the iterative version is agreed to be deployed is determined through the first target account;
in an embodiment of the present invention, the step S204 may specifically include: sending a confirmation request for determining the iterative version to the first target account, specifically, the confirmation request may further carry a third target account to compare an existing version on the line with the iterative version, so as to obtain a comparison result; and receiving a determination message sent after the iterative version is determined by the first target account, wherein the determination message carries the determination result, and the determination message determines whether to approve updating the iterative version according to a comparison result between the online existing version and the iterative version, wherein the project responsible person, the auditor, the project manager or the like corresponding to the first target account determines whether to approve updating the iterative version according to the first target account.
And step S206, under the condition that the determined result is that the deployment is agreed, the iterative version is deployed through the production server.
Through the steps S202 to S204, the iteration version is tested after the iteration version is detected to be completed; after the test is passed, determining whether the iterative version is agreed to be deployed through the first target account number; and under the condition that the determined result is that the deployment is agreed, the iterative version is deployed through the production server, so that the problems that the codes of the existing BUG are easy to be on line due to the fact that the new iterative version is automatically packaged and deployed in the related technology, and production accidents occur once the codes of the BUG are on line, and large loss is caused can be solved.
In an optional embodiment, before determining whether to agree to deploy the iterative version through the first target account, sending a work order carrying work order information to a third target account, where the work order information includes an application to be released, version information, a code warehouse git address, and a tag; and comparing the existing version on the line with the iterative version through the third target account to obtain a comparison result, and storing the code iterative version, wherein the third target account corresponds to a maintainer, namely the maintainer performs operation maintenance through the third target account.
In another optional embodiment, before the iterative version is deployed through a production server, a confirmation deployment notification is sent to the third target account, where the third target account is used for performing process configuration and script writing; and downloading the codes corresponding to the iterative versions according to the work order information, and packaging the codes corresponding to the iterative versions, namely downloading the codes corresponding to the iterative versions from a code warehouse according to the application to be released, the version information, the code warehouse git address and the label tag.
According to the embodiment of the invention, through manual review (through the first target account number), the separation of development and deployment is realized, and the flow and responsibility are defined. The wrong operation caused by the fact that the server environment is not known in development is reduced, developers are enabled to be concentrated on research and development of products, operation and maintenance are concentrated on operation and maintenance of the production server, production accidents caused by artificial reasons are reduced, the production environment is enabled to be more stable, and losses are reduced.
The project manager in the embodiment of the invention is a responsible person of the project and an external interface person of the project; the operation and maintenance personnel are the server and the management and maintenance personnel for the server to operate the application; and the tester is used for testing the quality of the system developed by the developer. The application management system in the embodiment of the invention is an internal development system, and the functions of the application management system comprise application management, work order management and the like, wherein the application management comprises basic information of application basic data, versions, responsible persons and the like. The Jenkins open source system is a continuous integrated tool for opening sources. The version control system controls the application version for global information tracking git, svn, and the like, and for convenience of description, git is used as an example for description.
After a project or an iterative version of the project is completed, a project manager gives a tester to test, after the test is passed, the project manager determines whether the project manager agrees to deploy the iterative version through an application management platform, and after the project manager agrees, the operation and maintenance personnel configure Jenkins jobs, fig. 3 is a schematic diagram of an automatic deployment process based on Jenkins revieweable according to an embodiment of the present invention, and as shown in fig. 3, the method includes:
step S301, a project manager initiates a work order and fills in work order information, including information of applications to be released and versions, git addresses (code warehouse addresses), tag tags, and the like.
Step S302, the application management system informs operation and maintenance personnel through mails, short messages and the like.
Step S303, the operation and maintenance personnel receive the notification, compare the interfaces and functions of the existing version and the version to be deployed on the line to obtain a comparison result, store the comparison result in the application management system and then return the comparison result to the application management system;
step S304, the application management system confirms the work order.
In step S305, the application management system delivers the project manager to confirm the information.
Step S306, the project manager confirms deployment, specifically, the project manager confirms the version and function of the online system, and evaluates the influence and impact on other online systems that depend on the updated new version, and then confirms deployment and evaluation, which may specifically include: the degree of influence of the deployment iteration version on the existing associated system is large, and if the influence is large, the deployment is determined not to be agreed; the emergency degree of the iteration version can be also considered, and if the emergency degree is larger, the evaluation result can be directly determined to be the same deployment.
And step S307, after receiving the deployment confirmation notification, the operation and maintenance personnel configure the Jenkins Job, wherein the Jenkins Job comprises flow configuration, script compiling and the like.
In steps S308-S311, Jenkins executes tasks, including downloading code according to the provided code warehouse address (i.e., git address), compiling, packaging, deploying, etc.
The embodiment of the invention has the advantages that the process of repeated confirmation during deployment can effectively reduce problems caused by automatic deployment, and one-step manual review operation is added to ensure the correctness of the deployment version.
Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.
Example 2
The present embodiment further provides an iterative version deployment apparatus, which is used to implement the foregoing embodiments and preferred embodiments, and the description of the apparatus that has been already made is omitted. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.
Fig. 4 is a block diagram of an iterative version deployment apparatus according to an embodiment of the present invention, as shown in fig. 4, including:
a test module 42, configured to detect that the iteration version is completed, and test the iteration version;
a determining module 44, configured to determine, through the first target account, whether to agree to deploy the iterative version after the test passes;
and the deployment module 46 is configured to deploy the iteration version through the production server if the determination result is that the deployment is agreed.
Fig. 5 is a block diagram one of an iterative version deployment apparatus according to a preferred embodiment of the present invention, as shown in fig. 5, the apparatus further includes:
the first sending module 52 is configured to send a work order carrying work order information to the third target account, where the work order information includes an application to be released, version information, a code warehouse git address, and a tag;
and the comparison module 54 is configured to compare the existing version of the line with the iterative version through the third target account to obtain a comparison result, and store the code iterative version.
Fig. 6 is a block diagram ii of an iterative version deployment apparatus according to a preferred embodiment of the present invention, as shown in fig. 6, the apparatus further includes:
a second sending module 62, configured to send a deployment confirmation notification to the third target account, where the third target account is used to perform flow configuration and script writing;
and the packing module 64 is configured to download the code corresponding to the iterative version according to the work order information, and pack the code corresponding to the iterative version.
Optionally, the determining module 44 includes:
a first sending submodule, configured to send a confirmation request for determining the iterative version to the first target account, where the confirmation request carries the comparison result;
and the first receiving submodule is used for receiving a determination message sent after the iterative version is determined by the first target account, wherein the determination message carries the determination result.
Optionally, the test module 42 includes:
the second sending submodule is used for sending a test prompt for testing the iterative version to a second target account in a message or mail mode;
and the second receiving submodule is used for receiving a test completion message which is sent after the second target account tests the iteration version and passes the test.
It should be noted that, the above modules may be implemented by software or hardware, and for the latter, the following may be implemented, but not limited to: the modules are all positioned in the same processor; alternatively, the modules are respectively located in different processors in any combination.
Example 3
Embodiments of the present invention also provide a storage medium having a computer program stored therein, wherein the computer program is arranged to perform the steps of any of the above method embodiments when executed.
Alternatively, in the present embodiment, the storage medium may be configured to store a computer program for executing the steps of:
s1, detecting that the iteration version is finished, and testing the iteration version;
s2, after the test is passed, determining whether the iterative version is agreed to be deployed through the first target account number;
and S3, in case that the determination result is that the deployment is agreed, deploying the iteration version through the production server.
Optionally, in this embodiment, the storage medium may include, but is not limited to: a usb disk, a Read-ONly Memory (ROM), a RaNdom Access Memory (RAM), a removable hard disk, a magnetic disk, or an optical disk, which can store computer programs.
Example 4
Embodiments of the present invention also provide an electronic device comprising a memory having a computer program stored therein and a processor arranged to run the computer program to perform the steps of any of the above method embodiments.
Optionally, the electronic apparatus may further include a transmission device and an input/output device, wherein the transmission device is connected to the processor, and the input/output device is connected to the processor.
Optionally, in this embodiment, the processor may be configured to execute the following steps by a computer program:
s1, detecting that the iteration version is finished, and testing the iteration version;
s2, after the test is passed, determining whether the iterative version is agreed to be deployed through the first target account number;
and S3, in case that the determination result is that the deployment is agreed, deploying the iteration version through the production server.
Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments and optional implementation manners, and this embodiment is not described herein again.
It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. An iterative version deployment method, comprising:
detecting that the iteration version is finished, and testing the iteration version;
after the test is passed, determining whether the iterative version is agreed to be deployed through the first target account number;
and in the case that the determination result is that the deployment is agreed, deploying the iteration version through the production server.
2. The method of claim 1, wherein prior to determining whether to approve deployment of the iterative version via the first target account number, the method further comprises:
sending a work order carrying work order information to a third target account, wherein the work order information comprises an application to be issued, version information, a code warehouse global information tracking address and a label;
and comparing the existing version on the line with the iteration version through the third target account to obtain a comparison result, and storing the code iteration version.
3. The method of claim 2, wherein prior to deploying the iterative version by a production server, the method further comprises:
sending a deployment confirmation notification to the third target account, wherein the third target account is used for performing flow configuration and script writing;
and downloading the codes corresponding to the iterative versions according to the work order information, and packaging the codes corresponding to the iterative versions.
4. The method of claim 2, wherein determining whether deployment of the iterative version is approved by the target account number comprises:
sending a confirmation request for determining the iteration version to the first target account, wherein the confirmation request carries the comparison result;
and receiving a determination message sent after the iterative version is determined by the first target account, wherein the determination message carries the determination result.
5. The method of any of claims 1-4, wherein testing the iterative version comprises:
sending a test prompt for testing the iteration version to a second target account in a message or mail mode;
and receiving a test completion message sent after the second target account tests the iteration version and passes the test.
6. An iterative version deployment method, comprising:
the test module is used for detecting that the iteration version is finished and testing the iteration version;
the determining module is used for determining whether the iterative version is agreed to be deployed or not through the first target account number after the test is passed;
and the deployment module is used for deploying the iteration version through the production server under the condition that the determined result is that the deployment is agreed.
7. The apparatus of claim 6, further comprising:
the first sending module is used for sending a work order carrying work order information to a third target account, wherein the work order information comprises an application to be issued, version information, a code warehouse global information tracking address and a label;
and the comparison module is used for comparing the existing version on the line with the iteration version through the third target account to obtain a comparison result and storing the code iteration version.
8. The apparatus of claim 7, further comprising:
a second sending module, configured to send a deployment confirmation notification to the third target account, where the third target account is used to perform flow configuration and script writing;
and the packaging module is used for downloading the codes corresponding to the iterative versions according to the work order information and packaging the codes corresponding to the iterative versions.
9. A computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to carry out the method of any one of claims 1 to 5 when executed.
10. An electronic device comprising a memory and a processor, wherein the memory has stored therein a computer program, and wherein the processor is arranged to execute the computer program to perform the method of any of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011589774.4A CN112596784B (en) | 2020-12-28 | 2020-12-28 | Iterative version deployment method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011589774.4A CN112596784B (en) | 2020-12-28 | 2020-12-28 | Iterative version deployment method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112596784A true CN112596784A (en) | 2021-04-02 |
| CN112596784B CN112596784B (en) | 2023-11-28 |
Family
ID=75203387
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011589774.4A Active CN112596784B (en) | 2020-12-28 | 2020-12-28 | Iterative version deployment method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112596784B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113762916A (en) * | 2021-07-29 | 2021-12-07 | 北京思特奇信息技术股份有限公司 | Version management system and method for business requirements |
| CN113778461A (en) * | 2021-09-09 | 2021-12-10 | 北京炎黄新星网络科技有限公司 | Method and system for realizing automatic application deployment |
| CN113791953A (en) * | 2021-09-16 | 2021-12-14 | 平安普惠企业管理有限公司 | Test scheduling and log management method and device, computer equipment and storage medium |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108363580A (en) * | 2018-03-12 | 2018-08-03 | 平安普惠企业管理有限公司 | Application program installation method, device, computer equipment and storage medium |
| CN111309336A (en) * | 2020-01-21 | 2020-06-19 | 浪潮软件股份有限公司 | Distributed application deployment method and device |
| CN111309441A (en) * | 2020-02-19 | 2020-06-19 | 北京中数智汇科技股份有限公司 | Micro-service deployment method for realizing DevOps based on Jenkins |
| CN111352632A (en) * | 2020-03-02 | 2020-06-30 | 北京字节跳动网络技术有限公司 | Software product detection device, system, method and storage medium |
| US20200241865A1 (en) * | 2019-01-29 | 2020-07-30 | Salesforce.Com, Inc. | Release orchestration for performing pre-release, version specific testing to validate application versions |
| CN111580832A (en) * | 2020-04-29 | 2020-08-25 | 电科云(北京)科技有限公司 | Application release system and method applied to heterogeneous multi-cloud environment |
| CN111897566A (en) * | 2020-06-23 | 2020-11-06 | 福建升腾资讯有限公司 | Software development continuous integration method, device, equipment and medium |
| CN112035122A (en) * | 2019-06-04 | 2020-12-04 | 中移(苏州)软件技术有限公司 | Interface deployment method, system and storage medium |
| CN112036825A (en) * | 2020-08-28 | 2020-12-04 | 航天科工网络信息发展有限公司 | Automatic operation and maintenance management system based on work order |
-
2020
- 2020-12-28 CN CN202011589774.4A patent/CN112596784B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108363580A (en) * | 2018-03-12 | 2018-08-03 | 平安普惠企业管理有限公司 | Application program installation method, device, computer equipment and storage medium |
| US20200241865A1 (en) * | 2019-01-29 | 2020-07-30 | Salesforce.Com, Inc. | Release orchestration for performing pre-release, version specific testing to validate application versions |
| CN112035122A (en) * | 2019-06-04 | 2020-12-04 | 中移(苏州)软件技术有限公司 | Interface deployment method, system and storage medium |
| CN111309336A (en) * | 2020-01-21 | 2020-06-19 | 浪潮软件股份有限公司 | Distributed application deployment method and device |
| CN111309441A (en) * | 2020-02-19 | 2020-06-19 | 北京中数智汇科技股份有限公司 | Micro-service deployment method for realizing DevOps based on Jenkins |
| CN111352632A (en) * | 2020-03-02 | 2020-06-30 | 北京字节跳动网络技术有限公司 | Software product detection device, system, method and storage medium |
| CN111580832A (en) * | 2020-04-29 | 2020-08-25 | 电科云(北京)科技有限公司 | Application release system and method applied to heterogeneous multi-cloud environment |
| CN111897566A (en) * | 2020-06-23 | 2020-11-06 | 福建升腾资讯有限公司 | Software development continuous integration method, device, equipment and medium |
| CN112036825A (en) * | 2020-08-28 | 2020-12-04 | 航天科工网络信息发展有限公司 | Automatic operation and maintenance management system based on work order |
Non-Patent Citations (1)
| Title |
|---|
| 林伟岩: "产品经理如何进行APP版本迭代", pages 1 - 5, Retrieved from the Internet <URL:https://zhuanlan.zhihu.com/p/25431241?utm_id=0> * |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113762916A (en) * | 2021-07-29 | 2021-12-07 | 北京思特奇信息技术股份有限公司 | Version management system and method for business requirements |
| CN113778461A (en) * | 2021-09-09 | 2021-12-10 | 北京炎黄新星网络科技有限公司 | Method and system for realizing automatic application deployment |
| CN113791953A (en) * | 2021-09-16 | 2021-12-14 | 平安普惠企业管理有限公司 | Test scheduling and log management method and device, computer equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112596784B (en) | 2023-11-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112596784B (en) | Iterative version deployment method and device | |
| CN111414172B (en) | Automatic deployment and release system and method for application software | |
| CN109960643B (en) | Code testing method and device | |
| CN109683899B (en) | Software integration method and device | |
| CN107463362B (en) | Method and system for continuous deployment based on multiple Jenkins | |
| CN109766269A (en) | Continuous integrating automated testing method, device, equipment and medium | |
| CN110597531B (en) | Distributed module upgrading method and device and storage medium | |
| CN111324522A (en) | Automatic test system and method | |
| CN109902005B (en) | Automatic testing method and system | |
| US20150100832A1 (en) | Method and system for selecting and executing test scripts | |
| CN101853173A (en) | Software upgrading method and device of programmable logic device of distributed system | |
| CN108228190B (en) | Persistent integration and delivery methods, systems, devices, and computer-readable storage media | |
| CN111651352B (en) | Warehouse code merging method and device | |
| CN111258913A (en) | Automatic algorithm testing method and device, computer system and readable storage medium | |
| CN110990289B (en) | Method and device for automatically submitting bug, electronic equipment and storage medium | |
| CN110908708B (en) | Code release method, device and system | |
| CN115113890A (en) | Automatic deployment method, system, equipment and medium of terminal software | |
| CN116069341A (en) | Automatic deployment method, equipment and storage medium for application program | |
| CN117827665A (en) | Project deployment method and device, storage medium and electronic device | |
| CN108319551B (en) | Software testing method and device, computer equipment and readable storage medium | |
| CN113434405A (en) | Method and device for determining test file, storage medium and electronic device | |
| CN111767218A (en) | Automatic testing method, equipment and storage medium for continuous integration | |
| CN115840617A (en) | Debugging method, system and related device | |
| CN112015436A (en) | Short message platform deployment method and device, computing equipment and computer storage medium | |
| CN110618943B (en) | Security service test method and device, electronic equipment and readable storage medium |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |