CN111158696A - Version deployment method and device - Google Patents
Version deployment method and device Download PDFInfo
- Publication number
- CN111158696A CN111158696A CN201911329817.2A CN201911329817A CN111158696A CN 111158696 A CN111158696 A CN 111158696A CN 201911329817 A CN201911329817 A CN 201911329817A CN 111158696 A CN111158696 A CN 111158696A
- Authority
- CN
- China
- Prior art keywords
- version
- test environment
- deployment
- basic
- environment host
- 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
- 238000000034 method Methods 0.000 title claims abstract description 73
- 238000012360 testing method Methods 0.000 claims abstract description 84
- 238000011161 development Methods 0.000 claims abstract description 12
- 238000004806 packaging method and process Methods 0.000 claims description 19
- 230000005540 biological transmission Effects 0.000 claims description 6
- 238000012546 transfer Methods 0.000 claims description 5
- 238000011981 development test Methods 0.000 abstract description 4
- 238000010586 diagram Methods 0.000 description 12
- 238000012545 processing Methods 0.000 description 8
- 238000012856 packing Methods 0.000 description 6
- 230000008569 process Effects 0.000 description 6
- 238000004590 computer program Methods 0.000 description 4
- 230000009286 beneficial effect Effects 0.000 description 3
- 238000010276 construction Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000006872 improvement Effects 0.000 description 1
- 230000003287 optical 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/40—Transformation of program code
- G06F8/41—Compilation
- G06F8/44—Encoding
- G06F8/447—Target code generation
-
- 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/368—Test management for test version control, e.g. updating test cases to a new software version
-
- 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
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 a version deployment method and device, and relates to the technical field of development and testing. According to the invention, the project codes are obtained from the version management tool, the project codes are compiled, the compiled project codes are packaged to obtain the basic version, and the basic version is transmitted to the test environment host, so that the test environment host can carry out version deployment according to the basic version. Compared with the existing version deployment mode, the method and the system can automatically pull the code from the version management tool to construct the basic version without manual intervention, so that the version deployment efficiency can be improved, and the project development test efficiency is further improved.
Description
Technical Field
The invention relates to the technical field of development and testing, in particular to a version deployment method and device.
Background
Often, a large number of version iterations exist in the project development testing phase, and various tests aiming at different versions are accompanied in the version iteration process. When the version test is carried out, the efficiency of the project development test is closely related to the efficiency of the version deployment.
At present, the version deployment mode is generally as follows: manually pulling codes from a version management tool (such as Clearcase) to construct a basic version, modifying a configuration file according to different environments, packaging, transmitting a packaged version package to a target environment, and manually deploying restart service to realize version deployment.
However, in the existing version deployment manner, the processes of manually pulling a code from the version management tool to construct a basic version, manually deploying a restart service, and the like result in low version deployment efficiency, which seriously affects the efficiency of project development and testing.
Disclosure of Invention
The invention provides a version deployment method and a version deployment device, which can construct and deploy versions during version testing in a project development testing stage.
In a first aspect, an embodiment of the present invention provides a version deployment method, where the method is applied to a version server, where the version server is connected to a test environment host, and the method includes: acquiring a project code from a version management tool; compiling the project code, and packaging the compiled project code to obtain a basic version; transmitting the base version to a test environment host; wherein, the basic version is used for the test environment host to carry out version deployment.
Optionally, the acquiring the project code from the version management tool includes: the project code is pulled from the version management tool by the development tool.
Optionally, the compiling the item code and packaging the compiled item code to obtain a basic version includes: compiling the project code through an Ant tool to obtain a compiled project code; and packaging the compiled project codes to obtain a basic version.
Optionally, the transmitting the base version to the test environment host includes: and transmitting the basic version to a test environment host through a secure shell file transfer protocol.
In a second aspect, an embodiment of the present invention further provides a version deployment method, where the method is applied to a test environment host, and the test environment host is connected to a version machine, and the method includes: receiving a basic version transmitted by a version machine; the basic version is obtained by the version machine by acquiring a project code from a version management tool, compiling the project code and packaging the compiled project code; and carrying out version deployment according to the basic version.
Optionally, the performing version deployment according to the basic version includes: calling a shell script file to replace a configuration file of the test environment host; and calling a shell script file and deploying the basic version.
Optionally, before the calling the shell script file and replacing the configuration file of the test environment host, the method further includes: and backing up the original version of the test environment host to obtain a backup version. The calling shell script file, after the base version is deployed, the method further comprises: judging whether the basic version fails to be deployed or not; and if the deployment fails, returning the test environment host to the backup version.
In a third aspect, an embodiment of the present invention provides a version deployment apparatus, where the apparatus is applied to a version host, where the version host is connected to a test environment host, and the apparatus includes: the acquisition module is used for acquiring the project codes from the version management tool; the compiling module is used for compiling the project codes and packaging the compiled project codes to obtain a basic version; the transmission module is used for transmitting the basic version to the test environment host; wherein, the basic version is used for the test environment host to carry out version deployment.
Optionally, the obtaining module is specifically configured to pull the project code from the version management tool through a development tool.
Optionally, the compiling module includes: the compiling submodule is used for compiling the project code through an Ant tool to obtain a compiled project code; and the packing submodule is used for packing the compiled project codes to obtain a basic version.
Optionally, the transmission module is specifically configured to transmit the basic version to the test environment host through a secure shell file transfer protocol.
In a fourth aspect, an embodiment of the present invention further provides a version deployment apparatus, where the apparatus is applied to a test environment host, and the test environment host is connected to a version machine, and the apparatus includes: the receiving module is used for receiving the basic version transmitted by the version machine; the basic version is obtained by the version machine by acquiring a project code from a version management tool, compiling the project code and packaging the compiled project code; and the deployment module is used for carrying out version deployment according to the basic version.
Optionally, the deployment module comprises: the replacing submodule is used for calling the shell script file and replacing the configuration file of the test environment host; and the deployment submodule is used for calling the shell script file and deploying the basic version.
Optionally, the apparatus further comprises: the device comprises a backup module, a judgment module and a processing module. And the backup module is used for backing up the original version of the test environment host to obtain a backup version before the replacement submodule calls the shell script file to replace the configuration file of the test environment host. Correspondingly, the judging module is used for judging whether the basic version fails to be deployed or not; and the processing module is used for returning the test environment host to the backup version if the deployment fails.
In a fifth aspect, an embodiment of the present invention provides a version deployment device, including: a processor, a storage medium and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, when the version deployment device runs, the processor and the storage medium communicate through the bus, and the processor executes the machine-readable instructions to execute the version deployment method according to the first aspect.
In a sixth aspect, an embodiment of the present invention further provides a version deployment device, including: a processor, a storage medium and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, when the version deployment device is operated, the processor and the storage medium communicate through the bus, and the processor executes the machine-readable instructions to execute the version deployment method according to the second aspect.
In a seventh aspect, an embodiment of the present invention further provides a storage medium, where the storage medium stores a computer program, and the computer program is executed by a processor to perform the method according to the first aspect or the second aspect.
The invention has the beneficial effects that:
according to the embodiment of the invention, the project code is obtained from the version management tool, the project code is compiled, the compiled project code is packaged to obtain the basic version, and the basic version is transmitted to the test environment host, so that the test environment host can carry out version deployment according to the basic version. Compared with the existing version deployment mode, the embodiment of the invention can automatically pull the code from the version management tool to construct the basic version without manual intervention, thereby improving the version deployment efficiency and further improving the project development test efficiency.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained according to the drawings without inventive efforts.
Fig. 1 shows a flowchart of a version deployment method provided in an embodiment of the present invention;
FIG. 2 is a schematic flow chart illustrating a version deployment method according to an embodiment of the present invention;
FIG. 3 is a schematic flow chart of a version deployment method provided in the embodiment of the present invention;
FIG. 4 is a schematic flow chart illustrating a version deployment method according to an embodiment of the present invention;
FIG. 5 is a schematic flow chart of a version deployment method provided in the embodiment of the present invention;
FIG. 6 is a schematic flow chart illustrating a version deployment method according to an embodiment of the present invention;
FIG. 7 is a schematic flow chart illustrating a version deployment method according to an embodiment of the present invention;
fig. 8 is a schematic structural diagram of a version deployment apparatus provided in an embodiment of the present invention;
FIG. 9 is a diagram illustrating a structure of a compiling module according to an embodiment of the present invention;
fig. 10 is another schematic structural diagram of a version deployment apparatus provided in an embodiment of the present invention;
FIG. 11 is a schematic structural diagram of a deployment module provided in an embodiment of the present invention;
fig. 12 is a schematic structural diagram of a version deployment apparatus provided in an embodiment of the present invention;
fig. 13 shows a schematic structural diagram of a version deployment device according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. The components of embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. It should also be noted that the descriptions of "first", "second", "third", etc. are used in the present invention only to distinguish functions, and are not intended to represent relative importance.
The embodiment of the invention provides a version deployment method, which can construct and deploy versions during version testing in a project development testing stage. The version deployment method can be applied to a version machine, and the version machine is connected with a test environment host machine. The version machine may be a server or a computer, that is, an execution subject of the version deployment method may be the server or the computer, or may also be one or more processors in the server or the computer, and the present invention is not limited thereto. Similarly, the test environment host may also be a server or a computer, or other special test hosts, which are not described herein again.
Fig. 1 shows a flowchart of a version deployment method provided by an embodiment of the present invention.
As shown in fig. 1, the version deployment method may include:
and S101, acquiring the project code from the version management tool.
For example, the step of acquiring the project code from the version management tool may specifically refer to: the project code is pulled from the version management tool by the development tool. For example, the version management tool may be Clearcase.
And S102, compiling the project codes, and packaging the compiled project codes to obtain a basic version.
Fig. 2 is another flowchart illustrating a version deployment method according to an embodiment of the present invention.
Optionally, as shown in fig. 2, the step of compiling the item code and packaging the compiled item code to obtain the base version specifically may include:
s201, compiling the project code through an Ant tool to obtain a compiled project code.
S202, packaging the compiled project codes to obtain a basic version.
After the base version is obtained, the base version may be transmitted to the test environment host through the following step S103.
And S103, transmitting the basic version to a test environment host.
The basic version can be used for version deployment of the test environment host.
Optionally, the transmitting the basic version to the test environment host specifically includes: and transmitting the basic version to each test environment host through a Secure Shell File Transfer Protocol (SFTP).
As described above, in the embodiment of the present invention, the project code is acquired from the version management tool, the project code is compiled, the compiled project code is packaged to obtain the basic version, and the basic version is transmitted to the test environment host, so that the test environment host can perform version deployment according to the basic version. Compared with the existing version deployment mode, the embodiment of the invention can automatically pull the code from the version management tool to construct the basic version without manual intervention, thereby improving the version deployment efficiency and further improving the project development test efficiency.
Fig. 3 shows another flowchart of the version deployment method provided by the embodiment of the present invention.
Optionally, as shown in fig. 3, after the step of packaging the compiled project code to obtain the base version, the version deployment method may further include:
s301, judging whether the basic version is failed to be constructed.
If yes, go to step S302; if not, the foregoing step S103 is continuously executed.
And S302, outputting a version construction failure log.
After the version construction failure log is output, the flow of the version deployment method may be stopped.
The embodiment of the invention also provides a version deployment method, which is applied to the test environment host computer, the test environment host computer is connected with the version machine,
fig. 4 is a schematic flowchart illustrating a version deployment method according to an embodiment of the present invention.
As shown in fig. 4, the version deployment method may include:
s401, receiving the basic version transmitted by the version machine.
The basic version is obtained by the version machine by acquiring a project code from a version management tool, compiling the project code and packaging the compiled project code.
S402, carrying out version deployment according to the basic version.
Fig. 5 is a schematic flowchart illustrating a version deployment method according to an embodiment of the present invention.
Optionally, as shown in fig. 5, the performing version deployment according to the basic version specifically may include:
s501, calling a Shell script file to replace the configuration file of the test environment host.
And S502, calling a Shell (Shell) script file and deploying the basic version.
Optionally, before calling a Shell (Shell) script file to replace the configuration file of the test environment host, the version deployment method may further include: and backing up the original version of the test environment host to obtain a backup version.
Fig. 6 is a schematic flowchart illustrating a version deployment method according to an embodiment of the present invention.
Optionally, as shown in fig. 6, after the shell script file is called to deploy the base version, the version deployment method may further include:
s601, judging whether the basic version fails to be deployed.
If yes, go to step S602; if not, the process is ended.
S602, returning the test environment host to the backup version.
As described above, when the version deployment fails, the version can also be restored to the original version that has been backed up, thereby ensuring the availability of the version.
The following describes the version deployment method described in the foregoing embodiment with a specific implementation manner:
fig. 7 is a schematic flowchart illustrating a version deployment method according to an embodiment of the present invention.
As shown in fig. 7, the version deployment method may include:
and S701, the version machine pulls the project code from the version management tool through the development tool.
And S702, compiling the project code by the version machine through an Ant tool to obtain the compiled project code.
And S703, packing the compiled project codes by the version machine to obtain a basic version.
S704, the version machine judges whether the basic version is failed to be constructed.
If yes, go to step S705; if not, go to step S706.
S705, the version machine outputs a version construction failure log.
And S706, the version machine transmits the basic version to the test environment host through a secure shell file transmission protocol.
And S707, the test environment host receives the basic version transmitted by the version machine.
And S708, backing up the original version of the test environment host to obtain a backup version.
And S709, calling the shell script file by the test environment host to replace the configuration file of the test environment host.
And S710, calling the shell script file by the test environment host to deploy the basic version.
And S711, judging whether the basic version fails to be deployed.
If yes, go to step S712; if not, the process is ended.
And S712, returning the test environment host to the backup version.
The beneficial effects of the version deployment method have been described in the foregoing embodiments, and are not described herein again.
Based on the version deployment method described in the foregoing method embodiment, an embodiment of the present invention further provides a version deployment apparatus, where the version deployment apparatus is applied to a version machine, and the version machine is connected to a test environment host.
Fig. 8 shows a schematic structural diagram of a version deployment apparatus provided in an embodiment of the present invention.
As shown in fig. 8, the version deployment apparatus may include: an obtaining module 10, configured to obtain a project code from a version management tool; the compiling module 20 is used for compiling the project codes and packing the compiled project codes to obtain a basic version; a transmission module 30, configured to transmit the basic version to a test environment host; wherein, the basic version is used for the test environment host to carry out version deployment.
Optionally, the obtaining module 10 may be specifically configured to pull the project code from the version management tool through a development tool.
Fig. 9 is a schematic structural diagram of a compiling module provided by the embodiment of the invention.
Alternatively, as shown in fig. 9, the compiling module 20 may include: the compiling submodule 21 is configured to compile the item code through an Ant tool to obtain a compiled item code; and the packing submodule 22 is used for packing the compiled project codes to obtain a basic version.
Optionally, the transmission module 30 may be specifically configured to transmit the basic version to the test environment host through a secure shell file transfer protocol.
Correspondingly, the embodiment of the invention also provides a version deployment device, which is applied to the test environment host, and the test environment host is connected with the version machine.
Fig. 10 is another schematic structural diagram of a version deployment apparatus provided in an embodiment of the present invention.
As shown in fig. 10, the version deployment apparatus may include: a receiving module 40, configured to receive a basic version transmitted by a version machine; the basic version is obtained by the version machine by acquiring a project code from a version management tool, compiling the project code and packaging the compiled project code; and the deployment module 50 is used for carrying out version deployment according to the basic version.
Fig. 11 shows a schematic structural diagram of a deployment module provided in an embodiment of the present invention.
Alternatively, as shown in fig. 11, the deployment module 50 may include: the replacing submodule 51 is used for calling the shell script file and replacing the configuration file of the test environment host; and the deployment submodule 52 is used for calling the shell script file and deploying the basic version.
Fig. 12 is a schematic structural diagram of a version deployment apparatus according to an embodiment of the present invention.
Optionally, as shown in fig. 12, the version deployment apparatus may further include: a backup module 60, a determination module 70, and a processing module 80. The backup module 60 is configured to backup the original version of the test environment host to obtain a backup version before the replacement submodule 51 calls the shell script file to replace the configuration file of the test environment host. Accordingly, the determining module 70 is configured to determine whether the deployment of the base version fails; the processing module 80 is configured to return the test environment host to the backup version if the deployment fails.
It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working process of the apparatus described above may refer to the corresponding process of the method in the foregoing method embodiment, and is not described in detail herein.
The version deployment apparatus provided in the embodiment of the present invention corresponds to the version deployment method described in the foregoing method embodiment, and therefore, the version deployment apparatus described in the apparatus embodiment has all the beneficial effects of the version deployment method described in the foregoing method embodiment, and details are not described here again.
An embodiment of the present invention further provides version deployment equipment, where the version deployment equipment may be a server or a computer, and fig. 13 shows a schematic structural diagram of the version deployment equipment provided in the embodiment of the present invention.
As shown in fig. 13, the version deployment apparatus may include: the processor 100, the storage medium 200, and a bus (not shown), the storage medium 200 stores machine-readable instructions executable by the processor 100, when the version deployment apparatus is operated, the processor 100 communicates with the storage medium 200 via the bus, and the processor 100 executes the machine-readable instructions to perform the version deployment method as described in any one of the method embodiments. The specific implementation and technical effects are similar, and are not described herein again.
For ease of illustration, only one processor is described in the version deployment device described above. However, it should be noted that the version deploying device in the present invention may also comprise a plurality of processors, and thus, the steps performed by one processor described in the present invention may also be performed by a plurality of processors in combination or individually. For example, the processor of the version deployment device executes steps a and B, it is to be understood that steps a and B may also be executed by two different processors together or separately in one processor. For example, a first processor performs step a and a second processor performs step B, or the first processor and the second processor perform steps a and B together, etc.
In some embodiments, a processor may include one or more processing cores (e.g., a single-core processor (S) or a multi-core processor (S)). Merely by way of example, a Processor may include a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), an Application Specific Instruction Set Processor (ASIP), a Graphics Processing Unit (GPU), a Physical Processing Unit (PPU), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), a Programmable Logic Device (PLD), a controller, a microcontroller Unit, a Reduced Instruction Set computer (Reduced Instruction Set computer), a microprocessor, or the like, or any combination thereof.
An embodiment of the present invention further provides a storage medium, where a computer program is stored on the storage medium, and when the computer program is executed by a processor, the version deployment method described in the foregoing method embodiment is executed. The specific implementation and technical effects are similar, and are not described herein again.
Alternatively, the storage medium may be a U disk, a removable hard disk, a ROM, a RAM, a magnetic or optical disk, or the like.
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 spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (9)
1. A version deployment method is applied to a version machine, the version machine is connected with a test environment host machine, and the method comprises the following steps:
acquiring a project code from a version management tool;
compiling the project code, and packaging the compiled project code to obtain a basic version;
transmitting the base version to a test environment host; wherein, the basic version is used for the test environment host to carry out version deployment.
2. The method of claim 1, wherein the obtaining project code from a version management tool comprises:
the project code is pulled from the version management tool by the development tool.
3. The method of claim 2, wherein compiling the project code and packaging the compiled project code to obtain a base version comprises:
compiling the project code through an Ant tool to obtain a compiled project code;
and packaging the compiled project codes to obtain a basic version.
4. The method of claim 3, wherein said transmitting the base version to a test environment host comprises:
and transmitting the basic version to a test environment host through a secure shell file transfer protocol.
5. A version deployment method is applied to a test environment host, and the test environment host is connected with a version machine, and the method comprises the following steps:
receiving a basic version transmitted by a version machine; the basic version is obtained by the version machine by acquiring a project code from a version management tool, compiling the project code and packaging the compiled project code;
and carrying out version deployment according to the basic version.
6. The method of claim 5, wherein the performing version deployment according to the base version comprises:
calling a shell script file to replace a configuration file of the test environment host;
and calling a shell script file and deploying the basic version.
7. The method of claim 6, wherein prior to invoking the shell script file to replace the configuration file of the test environment host, the method further comprises:
backing up the original version of the test environment host to obtain a backup version;
the calling shell script file, after the base version is deployed, the method further comprises:
judging whether the basic version fails to be deployed or not;
and if the deployment fails, returning the test environment host to the backup version.
8. A version deployment apparatus, applied to a version host connected to a test environment host, comprising:
the acquisition module is used for acquiring the project codes from the version management tool;
the compiling module is used for compiling the project codes and packaging the compiled project codes to obtain a basic version;
the transmission module is used for transmitting the basic version to the test environment host; wherein, the basic version is used for the test environment host to carry out version deployment.
9. A version deployment apparatus, applied to a test environment host, the test environment host being connected to a version machine, the apparatus comprising:
the receiving module is used for receiving the basic version transmitted by the version machine; the basic version is obtained by the version machine by acquiring a project code from a version management tool, compiling the project code and packaging the compiled project code;
and the deployment module is used for carrying out version deployment according to the basic version.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911329817.2A CN111158696A (en) | 2019-12-20 | 2019-12-20 | Version deployment method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911329817.2A CN111158696A (en) | 2019-12-20 | 2019-12-20 | Version deployment method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111158696A true CN111158696A (en) | 2020-05-15 |
Family
ID=70557694
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911329817.2A Pending CN111158696A (en) | 2019-12-20 | 2019-12-20 | Version deployment method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111158696A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113626035A (en) * | 2021-07-23 | 2021-11-09 | 南方科技大学 | Neural network compiling method facing RISC-V equipment based on TVM |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103294514A (en) * | 2013-06-26 | 2013-09-11 | 深圳Tcl新技术有限公司 | System software release integrated method, compiling server and system |
| CN103336688A (en) * | 2013-06-20 | 2013-10-02 | 中标软件有限公司 | Software integrating method and system oriented to cloud computing software research and development process |
| CN106293811A (en) * | 2016-07-28 | 2017-01-04 | 北京中电普华信息技术有限公司 | A kind of packing and issuing method and device automatically |
| CN106919398A (en) * | 2017-03-06 | 2017-07-04 | 山东浪潮云服务信息科技有限公司 | A kind of software distribution method and device |
| CN107315596A (en) * | 2017-07-26 | 2017-11-03 | 郑州云海信息技术有限公司 | A kind of code is packed dispositions method and device automatically |
| CN107729066A (en) * | 2017-11-08 | 2018-02-23 | 重庆扬讯软件技术股份有限公司 | One kind is based on SVN resources banks automation structure dissemination method and device |
| CN108647037A (en) * | 2018-04-28 | 2018-10-12 | 新疆熙菱信息技术股份有限公司 | Automatically dispose method and system based on shell scripts |
| CN108897571A (en) * | 2018-06-29 | 2018-11-27 | 北京金山数字娱乐科技有限公司 | Program is packaged dispositions method, device, system, electronic equipment and storage medium |
-
2019
- 2019-12-20 CN CN201911329817.2A patent/CN111158696A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103336688A (en) * | 2013-06-20 | 2013-10-02 | 中标软件有限公司 | Software integrating method and system oriented to cloud computing software research and development process |
| CN103294514A (en) * | 2013-06-26 | 2013-09-11 | 深圳Tcl新技术有限公司 | System software release integrated method, compiling server and system |
| CN106293811A (en) * | 2016-07-28 | 2017-01-04 | 北京中电普华信息技术有限公司 | A kind of packing and issuing method and device automatically |
| CN106919398A (en) * | 2017-03-06 | 2017-07-04 | 山东浪潮云服务信息科技有限公司 | A kind of software distribution method and device |
| CN107315596A (en) * | 2017-07-26 | 2017-11-03 | 郑州云海信息技术有限公司 | A kind of code is packed dispositions method and device automatically |
| CN107729066A (en) * | 2017-11-08 | 2018-02-23 | 重庆扬讯软件技术股份有限公司 | One kind is based on SVN resources banks automation structure dissemination method and device |
| CN108647037A (en) * | 2018-04-28 | 2018-10-12 | 新疆熙菱信息技术股份有限公司 | Automatically dispose method and system based on shell scripts |
| CN108897571A (en) * | 2018-06-29 | 2018-11-27 | 北京金山数字娱乐科技有限公司 | Program is packaged dispositions method, device, system, electronic equipment and storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113626035A (en) * | 2021-07-23 | 2021-11-09 | 南方科技大学 | Neural network compiling method facing RISC-V equipment based on TVM |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR20190107664A (en) | Smart Contract Processing Method and Device | |
| US9311064B1 (en) | Systems and methods for automated centralized build/merge management | |
| EP3499364B1 (en) | Method and device for loading kernel module | |
| CN110888652B (en) | Multi-version construction method and terminal based on jenkins plug-in | |
| JP6922532B2 (en) | Test execution control program, test execution control method, and test execution control device | |
| AU2012201749B2 (en) | Single development test environment | |
| CN108121543A (en) | A kind of software code process of compilation method and device | |
| CN109491661B (en) | Universal cross-compiling method and device | |
| KR20150061203A (en) | Method for providing embedded software development tools for supporting embedded software development environment based on native building and apparatus thereof | |
| CN114995835A (en) | Application automation deployment method, system, equipment and readable storage medium | |
| CN111158696A (en) | Version deployment method and device | |
| CN106445541B (en) | Software construction method, software construction device and software construction system | |
| CN108874662B (en) | Test method and non-transitory computer readable medium storing program | |
| CN107678969B (en) | Test version release method and device, version control equipment and test machine | |
| CN111459530A (en) | Patching method, device and storage medium | |
| US20150007139A1 (en) | Optimizing error parsing in an integrated development environment | |
| CN111209197B (en) | Application continuous integration test method, system, equipment and storage medium | |
| EP2503450A2 (en) | Version numbering in single development and test environment | |
| CN111752735A (en) | SDK (software development kit) abnormity troubleshooting method and device and computer readable storage medium | |
| CN112711575A (en) | Deployment method, system and related device of database cluster | |
| CN112363733A (en) | Continuous integration method based on Docker container | |
| CN111240752B (en) | Operating system self-adaption method and system | |
| WO2013183249A1 (en) | Deployment device and deployment method | |
| CN112015427A (en) | Method and device for building multiple compiling environments and electronic equipment | |
| CN115639779A (en) | System and method for distributing and executing software extensions in an industrial controller |
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 | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20220914 Address after: 12 / F, 15 / F, 99 Yincheng Road, Pudong New Area pilot Free Trade Zone, Shanghai, 200120 Applicant after: Jianxin Financial Science and Technology Co.,Ltd. Address before: 25 Financial Street, Xicheng District, Beijing 100033 Applicant before: CHINA CONSTRUCTION BANK Corp. Applicant before: Jianxin Financial Science and Technology Co.,Ltd. |
|
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200515 |