CN113050981A - Code on-line automatic publishing method, server and storage medium - Google Patents
Code on-line automatic publishing method, server and storage medium Download PDFInfo
- Publication number
- CN113050981A CN113050981A CN202110310615.4A CN202110310615A CN113050981A CN 113050981 A CN113050981 A CN 113050981A CN 202110310615 A CN202110310615 A CN 202110310615A CN 113050981 A CN113050981 A CN 113050981A
- Authority
- CN
- China
- Prior art keywords
- code
- issued
- test
- issuing
- version information
- 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 32
- 238000012360 testing method Methods 0.000 claims abstract description 124
- 230000006870 function Effects 0.000 claims description 9
- 238000011056 performance test Methods 0.000 claims description 8
- 238000001514 detection method Methods 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 4
- 238000011990 functional testing Methods 0.000 description 4
- 238000012544 monitoring process Methods 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 230000003252 repetitive effect Effects 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000003068 static 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
-
- 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
-
- 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
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 Hardware Design (AREA)
- Quality & Reliability (AREA)
- Computer Security & Cryptography (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses an online automatic code release method, a server and a storage medium, which belong to the technical field of computers, and the method comprises the steps of receiving a code to be released, testing and generating corresponding version information, wherein the code to be released comprises a code text, then obtaining the version information and the code text, uploading the version information and the code text to a git tool end for marking, obtaining a code text corresponding to the marked version information, grabbing the code text corresponding to the marked version information from the git tool end based on a jenkins release end, compiling, and generating a release code corresponding to the code to be released; and finally, the jenkins issuing end pushes the generated issuing code to an online server to realize automatic issuing. The method and the system have the advantages that the code to be issued is tested for multiple times, the tested code to be issued is compiled through the git tool end mark and the jenkins issuing end, the generated issuing code is automatically issued from the online server, simplicity and high efficiency are realized, manual errors are avoided, and the accuracy is improved.
Description
Technical Field
The invention belongs to the technical field of data processing, and particularly relates to a data building method based on block chaining computing power equipment, a server and a storage medium.
Background
Today's internet companies, products are fast iterating with microservice architectures prevailing. The online code can be frequently updated to meet new requirements, and the online code is not suitable to be updated in the process in a traditional manual mode, so that the efficiency is low, the accuracy is not high, the process is complicated, and errors are easy to occur.
Disclosure of Invention
The invention provides an on-line automatic code release method, a server and a storage medium, and aims to solve the problems of low efficiency and low accuracy caused by complicated code release process, easy error.
In order to achieve the above object, the present invention provides an on-line automatic code publishing method, which comprises:
s1, receiving a code to be issued written by a developer for a certain project improvement, and generating version information of the code to be issued, wherein the code to be issued comprises a code text;
s2, acquiring the version information and the code text, uploading the version information and the code text to a git tool terminal for marking, and acquiring a code text corresponding to the marked version information of the code to be issued;
s3, based on a jenkins issuing end connected with the git tool end, grabbing a code text corresponding to the marked version information of the code to be issued from the git tool end, and compiling to generate an issuing code corresponding to the code to be issued;
s4, the jenkins issuing end pushes the generated issuing codes to an online server, and automatic issuing of the issuing codes corresponding to the certain project on the online server is achieved.
Preferably, the step S1 includes:
acquiring a code text of the code to be issued, executing a first test, and generating a first test result;
inserting the code text of the code to be issued into a position corresponding to a certain project improvement to execute a second test, and generating a second test result;
and when the first test result and the second test result both pass, completing the test of the code to be issued.
Preferably, the first test and the second test both include a performance test and a functional test on the code to be issued.
Preferably, when the first test result and/or the second test result do not pass, a test log which does not pass is generated for a developer to correct the code to be issued.
Preferably, the step S3 includes that the jenkins issuing end grabs the to-be-issued code from the git tool end at a preset cycle time to perform detection, so as to update the code text corresponding to the version information of the to-be-issued code.
In addition, to achieve the above object, the present invention further provides a server, including a memory and a processor, where the memory stores a code distribution program operable on the processor, and the code distribution program implements the following steps when executed by the processor:
the testing steps are as follows: receiving a code to be issued written by a developer for improving a certain project, testing and generating version information of the code to be issued, wherein the code to be issued comprises a code text;
an acquisition step: acquiring the version information and the code text, uploading the version information and the code text to a git tool terminal for marking, and acquiring a code text corresponding to the marked version information of the code to be issued;
compiling: compiling a code text corresponding to the version information of the code to be issued after the mark is grabbed from the git tool terminal based on a jenkins issuing terminal connected with the git tool terminal, and generating an issuing code corresponding to the code to be issued;
a release step: and the jenkins issuing end pushes the generated issuing code to an online server, so that the issuing code corresponding to a certain project is automatically issued on the online server.
Preferably, the testing step comprises:
acquiring a code text of the code to be issued, executing a first test, and generating a first test result;
inserting the code text of the code to be issued into a position corresponding to a certain project improvement to execute a second test, and generating a second test result;
and when the first test result and the second test result both pass, completing the test of the code to be issued.
Preferably, the first test and the second test both include a performance test and a functional test on the code to be issued.
Preferably, when the first test result and/or the second test result do not pass, a test log which does not pass is generated for a developer to correct the code to be issued.
In addition, to achieve the above object, the present invention further provides a computer-readable storage medium, which includes a code distribution program, and when the code distribution program is executed by a processor, the method for automatically distributing a code on a line as described in any one of the above embodiments can be implemented.
The invention provides an on-line automatic code release method, a server and a storage medium, wherein version information of a code to be released is generated by receiving a code to be released, which is compiled by a developer for improving a certain project, and the code to be released comprises a code text; then, the version information and the code text are acquired and uploaded to a git tool terminal for marking, and a code text corresponding to the marked version information of the code to be issued is obtained; compiling a code text corresponding to the version information of the code to be issued after the mark is grabbed from the git tool terminal based on a jenkins issuing terminal connected with the git tool terminal, and generating an issuing code corresponding to the code to be issued; and finally, the jenkins issuing end pushes the generated issuing code to an online server end, so that the issuing code corresponding to a certain project is automatically issued on the online server end. According to the method, the code to be issued is tested firstly, the tested code to be issued is marked by the git tool end, and the code text corresponding to the version information of the marked code to be issued is compiled through the jenkins issuing end, so that the corresponding issued code is generated and automatically issued from the online server, the method is simple and efficient, manual errors are avoided, and the accuracy is improved.
To more clearly illustrate the structural features and effects of the present invention, the present invention will be described in detail below with reference to the accompanying drawings and specific embodiments.
Drawings
FIG. 1 is a flow chart of a preferred embodiment of the on-line automatic code distribution method of the present invention;
FIG. 2 is a diagram of a server according to a preferred embodiment of the present invention;
FIG. 3 is a block diagram of a preferred embodiment of a code distribution program.
Detailed Description
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs; the terminology used in the description of the application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application; the terms "including" and "having," and any variations thereof, in the description and claims of this application and the description of the above figures are intended to cover non-exclusive inclusions. The terms "first," "second," and the like in the description and claims of this application or in the above-described drawings are used for distinguishing between different objects and not for describing a particular order.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.
The embodiment of the invention provides an on-line automatic code release method, which is a flow chart of a preferred embodiment of the on-line automatic code release method shown in figure 1, and comprises the following steps:
and S1, receiving a to-be-released code written by a developer for a certain project improvement, and generating version information of the to-be-released code, wherein the to-be-released code comprises a code text.
For example, in an optional embodiment, a small window in a certain web page is increased or improved, a corresponding code to be issued is written and a test is performed, the test includes a first test and a second test, and particularly, only after the first test and the second test are both completed, the test is passed and stored in a local memory, and corresponding version information is generated for the code to be issued after the test is completed.
Specifically, the step S1 includes:
acquiring a code text of the code to be issued, executing a first test, and generating a first test result;
inserting the code text of the code to be issued into a position corresponding to a certain project improvement to execute a second test, and generating a second test result;
and when the first test result and the second test result both pass, completing the test of the code to be issued.
In this embodiment, to ensure that the received written code to be issued is correct, the code to be issued needs to be tested twice, and each test includes a performance test and a function test on the code to be issued. The first test is to execute the test on the code text of the acquired code to be issued to generate a first test result, namely to test the code text; the second test is to insert the code text of the code to be issued into a position corresponding to a certain project improvement to execute the test, generate a second test result, namely, the whole code of a certain project runs once, test the correctness and compatibility of the code text in a certain project, and confirm whether the function of the code to be issued is displayed.
It should be noted that the performance test includes, but is not limited to, interface connection, code writing or code format, and the like, and the functional test includes, but is not limited to, the function shown by the code to be released, the state of display, the speed of reaction, or a pop-up window, and the like.
Furthermore, when the first test result and/or the second test result are/is failed, early warning is triggered to generate a failed test log, the log records the position of the error in the code to be issued, and developers can further correct the code to be issued according to the log record so as to better pass the test and complete the test.
And S2, acquiring the version information and the code text, uploading the version information and the code text to a git tool terminal for marking, and acquiring the code text corresponding to the marked version information of the code to be issued.
git is an open-source distributed version control system, which can effectively process the management of the version of the project from very small to very large at high speed.
And S3, based on a jenkins issuing end connected with the git tool end, grabbing a code text corresponding to the marked version information of the code to be issued from the git tool end, and compiling to generate an issuing code corresponding to the code to be issued.
jenkins is a sustainable integrated tool developed based on Java for monitoring continuous and repetitive work and project release. In this embodiment, the jenkins publishing end first captures a code text corresponding to the version information of the marked code to be published, and then compiles the code text to generate a publishing code corresponding to the code to be published of the corresponding step file, where the publishing code is a code to be published for a certain project. The release codes can be packed and compressed, and the storage space is reduced.
Preferably, the step S3 includes continuously integrating and monitoring projects based on a jenkins publishing terminal, where the jenkins publishing terminal captures the to-be-published code from the git tool terminal for detection at a preset cycle time, so as to update the code text corresponding to the version information of the to-be-published code. The preset period time may be set to 1 hour, based on the project requirement, and is not limited herein.
S4, the jenkins issuing end pushes the generated issuing codes to an online server, and automatic issuing of the issuing codes corresponding to the certain project on the online server is achieved.
In this embodiment, when the jenkins publishing terminal generates a publishing code corresponding to the code to be published, that is, the publishing code corresponding to a certain project, the jenkins publishing terminal only needs to push the publishing code to the online server, and the online server immediately publishes the publishing code according to the script file, so that the online automatic publishing of the code can be realized. Personnel are not needed to participate in the whole process, and the efficiency and the accuracy of code release are greatly improved.
Fig. 2 is a schematic diagram of a server according to a preferred embodiment of the present invention. The server 1 is a device capable of automatically performing numerical calculation and/or information processing in accordance with a command set or stored in advance. The server 1 may be a computer, or may be a single network server, a server group composed of a plurality of network servers, or a cloud composed of a large number of hosts or network servers based on cloud computing, where cloud computing is one of distributed computing and is a super virtual computer composed of a group of loosely coupled computers.
In the present embodiment, the server 1 may include, but is not limited to, a memory 11, a processor 12, and a display 13, which may be communicatively connected to each other through a system bus, and the memory 11 stores a code issuing program 10 that may run on the processor 12. It is noted that fig. 2 only shows the server 1 with components 11-13, but it is to be understood that not all of the shown components are required to be implemented, and that more or fewer components may be implemented instead.
The storage 11 includes a memory and at least one type of readable storage medium. The memory provides cache for the operation of the server 1; the readable storage medium may be a non-volatile storage medium such as flash memory, a hard disk, a multimedia card, a card type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Read Only Memory (ROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a Programmable Read Only Memory (PROM), a magnetic memory, a magnetic disk, an optical disk, etc. In some embodiments, the readable storage medium may be an internal storage unit of the server 1, such as a hard disk of the server 1; in other embodiments, the non-volatile storage medium may be an external storage device of the server 1, such as a plug-in hard disk provided on the server 1, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like. In this embodiment, the readable storage medium of the memory 11 is generally used for storing an operating system and various application software installed in the server 1, for example, storing the code publishing program 10 in an embodiment of the present invention. Further, the memory 11 may also be used to temporarily store various types of data that have been output or are to be output.
The processor 12 may be a Central Processing Unit (CPU), controller, microcontroller, microprocessor, or other data Processing chip in some embodiments. The processor 12 is generally used for controlling the overall operation of the server 1, such as performing control and processing related to data interaction or communication with the other devices. In this embodiment, the processor 12 is configured to run the program code stored in the memory 11 or process data, for example, run the code issuing program 10.
The code issuing program 10 is stored in the memory 11 and includes computer readable instructions stored in the memory 11 that are executable by the processor 12 to implement the methods of the embodiments of the present application.
In one embodiment, the code release program 10 implements the following steps when executed by the processor 12:
the testing steps are as follows: receiving a code to be issued written by a developer for improving a certain project, testing and generating version information of the code to be issued, wherein the code to be issued comprises a code text.
For example, in an optional embodiment, a small window in a certain web page is increased or improved, a corresponding code to be issued is written and a test is performed, the test includes a first test and a second test, and particularly, only after the first test and the second test are both completed, the test is passed and stored in a local memory, and corresponding version information is generated for the code to be issued after the test is completed.
Specifically, the testing step includes:
acquiring a code text of the code to be issued, executing a first test, and generating a first test result;
inserting the code text of the code to be issued into a position corresponding to a certain project improvement to execute a second test, and generating a second test result;
and when the first test result and the second test result both pass, completing the test of the code to be issued.
In this embodiment, to ensure that the received written code to be issued is correct, the code to be issued needs to be tested twice, and each test includes a performance test and a function test on the code to be issued. The first test is to execute the test on the code text of the acquired code to be issued to generate a first test result, namely to test the code text; the second test is to insert the code text of the code to be issued into a position corresponding to a certain project improvement to execute the test, generate a second test result, namely, the whole code of a certain project runs once, test the correctness and compatibility of the code text in a certain project, and confirm whether the function of the code to be issued is displayed.
It should be noted that the performance test includes, but is not limited to, interface connection, code writing or code format, and the like, and the functional test includes, but is not limited to, the function shown by the code to be released, the state of display, the speed of reaction, or a pop-up window, and the like.
Furthermore, when the first test result and/or the second test result are/is failed, early warning is triggered to generate a failed test log, the log records the position of the error in the code to be issued, and developers can further correct the code to be issued according to the log record so as to better pass the test and complete the test.
An acquisition step: and acquiring the version information and the code text, uploading the version information and the code text to a git tool terminal for marking, and acquiring the code text corresponding to the marked version information of the code to be issued.
git is an open-source distributed version control system, which can effectively process the management of the version of the project from very small to very large at high speed.
Compiling: and compiling the code text corresponding to the version information of the code to be issued after the mark is grabbed from the git tool end based on a jenkins issuing end connected with the git tool end, and generating an issuing code corresponding to the code to be issued.
jenkins is a sustainable integrated tool developed based on Java for monitoring continuous and repetitive work and project release. In this embodiment, the jenkins publishing end first captures a code text corresponding to the version information of the marked code to be published, and then compiles the code text to generate a publishing code corresponding to the code to be published of the corresponding step file, where the publishing code is a code to be published for a certain project. The release codes can be packed and compressed, and the storage space is reduced.
Preferably, the compiling step includes continuously integrating and monitoring projects based on a jenkins publishing end, and the jenkins publishing end captures the codes to be published from a git tool end at a preset cycle time to detect so as to update code texts corresponding to version information of the codes to be published. The preset period time may be set to 1 hour, based on the project requirement, and is not limited herein.
A release step: and the jenkins issuing end pushes the generated issuing code to an online server, so that the issuing code corresponding to a certain project is automatically issued on the online server.
In this embodiment, when the jenkins publishing terminal generates a publishing code corresponding to the code to be published, that is, the publishing code corresponding to a certain project, the jenkins publishing terminal only needs to push the publishing code to the online server, and the online server immediately publishes the publishing code according to the script file, so that the online automatic publishing of the code can be realized. Personnel are not needed to participate in the whole process, and the efficiency and the accuracy of code release are greatly improved.
Referring to FIG. 3, a program module diagram of a preferred embodiment of a code distribution program is shown. In one embodiment, the code publisher 10 includes: a testing module 101, an obtaining module 102, a compiling module 103 and a publishing module 104. The functions or operation steps implemented by the modules 101 and 104 are similar to those of the above-mentioned code line automatic issuing method, and are not detailed here, for example, where:
the test module 101 is configured to receive a to-be-released code written by a developer for a certain project improvement, and generate version information of the to-be-released code, where the to-be-released code includes a code text;
the obtaining module 102 is configured to obtain the version information and the code text, upload the version information and the code text to a git tool end, and mark the version information and the code text to obtain a code text corresponding to the marked version information of the code to be issued;
the compiling module 103 is configured to compile a code text corresponding to the version information of the code to be issued after the jenkins issuing end connected to the git tool end captures the mark from the git tool end, and generate an issuing code corresponding to the code to be issued;
the publishing module 104 is configured to push the generated publishing code to an online server by the jenkins publishing end, so as to implement automatic publishing of the publishing code corresponding to the certain project at the online server.
Furthermore, the present invention also provides a computer-readable storage medium, which includes a code distribution program, and when the code distribution program is executed by a processor, the code distribution program implements the following operations:
the testing steps are as follows: receiving a code to be issued written by a developer for improving a certain project, testing and generating version information of the code to be issued, wherein the code to be issued comprises a code text;
an acquisition step: acquiring the version information and the code text, uploading the version information and the code text to a git tool terminal for marking, and acquiring a code text corresponding to the marked version information of the code to be issued;
compiling: compiling a code text corresponding to the version information of the code to be issued after the mark is grabbed from the git tool terminal based on a jenkins issuing terminal connected with the git tool terminal, and generating an issuing code corresponding to the code to be issued;
a release step: and the jenkins issuing end pushes the generated issuing code to an online server, so that the issuing code corresponding to a certain project is automatically issued on the online server.
The specific implementation of the computer-readable storage medium of the present invention is substantially the same as the above-mentioned embodiments of the code line automatic issuing method and the server, and will not be described herein again.
The technical principle of the present invention has been described above with reference to specific embodiments, which are merely preferred embodiments of the present invention. The protection scope of the present invention is not limited to the above embodiments, and all technical solutions belonging to the idea of the present invention belong to the protection scope of the present invention. Other embodiments of the invention will occur to those skilled in the art without the exercise of inventive faculty, and such will fall within the scope of the invention.
Claims (10)
1. An on-line automatic code release method, comprising:
s1, receiving a code to be issued written by a developer for a certain project improvement, and generating version information of the code to be issued, wherein the code to be issued comprises a code text;
s2, acquiring the version information and the code text, uploading the version information and the code text to a git tool terminal for marking, and acquiring a code text corresponding to the marked version information of the code to be issued;
s3, based on a jenkins issuing end connected with the git tool end, grabbing a code text corresponding to the marked version information of the code to be issued from the git tool end, and compiling to generate an issuing code corresponding to the code to be issued;
s4, the jenkins issuing end pushes the generated issuing codes to an online server, and automatic issuing of the issuing codes corresponding to the certain project on the online server is achieved.
2. The automatic publishing method on a code line according to claim 1, wherein the step S1 comprises:
acquiring a code text of the code to be issued, executing a first test, and generating a first test result;
inserting the code text of the code to be issued into a position corresponding to a certain project improvement to execute a second test, and generating a second test result;
and when the first test result and the second test result both pass, completing the test of the code to be issued.
3. The method according to claim 2, wherein the first test and the second test each comprise a performance test and a function test of the code to be issued.
4. The method according to claim 2, wherein when the first test result and/or the second test result fail, a failed test log is generated for a developer to correct the code to be issued.
5. The method for automatically releasing the codes on the line according to claim 1, wherein the step S3 includes the jenkins releasing end grabbing the codes to be released from the git tool end at a preset cycle time for detection, so as to update the code text corresponding to the version information of the codes to be released.
6. A server, comprising a memory and a processor, the memory having stored therein a code distribution program executable on the processor, the code distribution program when executed by the processor implementing the steps of:
the testing steps are as follows: receiving a code to be issued written by a developer for improving a certain project, testing and generating version information of the code to be issued, wherein the code to be issued comprises a code text;
an acquisition step: acquiring the version information and the code text, uploading the version information and the code text to a git tool terminal for marking, and acquiring a code text corresponding to the marked version information of the code to be issued;
compiling: compiling a code text corresponding to the version information of the code to be issued after the mark is grabbed from the git tool terminal based on a jenkins issuing terminal connected with the git tool terminal, and generating an issuing code corresponding to the code to be issued;
a release step: and the jenkins issuing end pushes the generated issuing code to an online server, so that the issuing code corresponding to a certain project is automatically issued on the online server.
7. The server of claim 6, wherein the testing step comprises:
acquiring a code text of the code to be issued, executing a first test, and generating a first test result;
inserting the code text of the code to be issued into a position corresponding to a certain project improvement to execute a second test, and generating a second test result;
and when the first test result and the second test result both pass, completing the test of the code to be issued.
8. The server according to claim 1, wherein the first test and the second test each include a performance test and a function test on the code to be issued.
9. The server according to claim 1, wherein when the first test result and/or the second test result fail, a failed test log is generated for a developer to correct the code to be issued.
10. A computer-readable storage medium, wherein the computer-readable storage medium includes a code distribution program, and when the code distribution program is executed by a processor, the code distribution program can implement the on-line automatic distribution method of codes according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110310615.4A CN113050981A (en) | 2021-03-23 | 2021-03-23 | Code on-line automatic publishing method, server and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110310615.4A CN113050981A (en) | 2021-03-23 | 2021-03-23 | Code on-line automatic publishing method, server and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113050981A true CN113050981A (en) | 2021-06-29 |
Family
ID=76514678
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110310615.4A Pending CN113050981A (en) | 2021-03-23 | 2021-03-23 | Code on-line automatic publishing method, server and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113050981A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114217821A (en) * | 2022-02-21 | 2022-03-22 | 深圳市秦丝科技有限公司 | Multi-server code gray scale release method and device, electronic equipment and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105653287A (en) * | 2015-12-31 | 2016-06-08 | 北京元心科技有限公司 | Automatic program version issuing method and device |
| CN107315687A (en) * | 2017-06-29 | 2017-11-03 | 环球智达科技（北京）有限公司 | Code method for automatically releasing |
| CN107450933A (en) * | 2017-08-18 | 2017-12-08 | 郑州云海信息技术有限公司 | A kind of software continuous integrated approach and system |
| CN107678773A (en) * | 2017-09-28 | 2018-02-09 | 郑州云海信息技术有限公司 | A kind of code development based on git and testing process management method |
| CN109189400A (en) * | 2018-08-07 | 2019-01-11 | 北京趣拿软件科技有限公司 | Program dissemination method and device, storage medium, processor |
| CN109683899A (en) * | 2017-10-18 | 2019-04-26 | 中移(苏州)软件技术有限公司 | A kind of software integrating method and device |
-
2021
- 2021-03-23 CN CN202110310615.4A patent/CN113050981A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105653287A (en) * | 2015-12-31 | 2016-06-08 | 北京元心科技有限公司 | Automatic program version issuing method and device |
| CN107315687A (en) * | 2017-06-29 | 2017-11-03 | 环球智达科技（北京）有限公司 | Code method for automatically releasing |
| CN107450933A (en) * | 2017-08-18 | 2017-12-08 | 郑州云海信息技术有限公司 | A kind of software continuous integrated approach and system |
| CN107678773A (en) * | 2017-09-28 | 2018-02-09 | 郑州云海信息技术有限公司 | A kind of code development based on git and testing process management method |
| CN109683899A (en) * | 2017-10-18 | 2019-04-26 | 中移(苏州)软件技术有限公司 | A kind of software integrating method and device |
| CN109189400A (en) * | 2018-08-07 | 2019-01-11 | 北京趣拿软件科技有限公司 | Program dissemination method and device, storage medium, processor |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114217821A (en) * | 2022-02-21 | 2022-03-22 | 深圳市秦丝科技有限公司 | Multi-server code gray scale release method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9507688B2 (en) | Execution history tracing method | |
| CN103150188B (en) | The compatible video card fast initializing method of the x86 of non-x 86 instruction set computer | |
| US20120254662A1 (en) | Automated test system and automated test method | |
| CN109189756A (en) | Electronic device, the method for Data Migration and storage medium | |
| CN113778898B (en) | User interface automatic test method and device, electronic equipment and storage medium | |
| CN112286829B (en) | Test script generation method and device | |
| CN110928802A (en) | Test method, device, equipment and storage medium based on automatic generation of case | |
| CN113157347A (en) | Automatic probe deployment method, electronic device and storage medium | |
| CN113050981A (en) | Code on-line automatic publishing method, server and storage medium | |
| CN102662847B (en) | System and method for program debugging of embedded system based on flash memory application | |
| CN112685316A (en) | Code execution path acquisition method and device, computer equipment and storage medium | |
| CN113448614A (en) | Software project code management method and device, storage medium and electronic equipment | |
| CN116719579A (en) | AI model observability realization method and device, electronic equipment and storage medium | |
| CN109144524B (en) | Version release method of subject game on education platform and electronic equipment | |
| CN112463574A (en) | Software testing method, device, system, equipment and storage medium | |
| CN115794621A (en) | Code coverage test method, device, equipment and storage medium | |
| CN112100032B (en) | Log output recording method and system for embedded equipment | |
| CN113760696A (en) | Program problem positioning method and device, electronic equipment and storage medium | |
| CN116415599A (en) | IC card reading method, writing device, electronic device and storage medium | |
| CN112667874A (en) | Webpage data extraction method and device, electronic equipment and storage medium | |
| CN102750167A (en) | Method and device for starting application program and computer system | |
| CN112162954A (en) | User operation log generation method, user operation log generation device | |
| CN112231165A (en) | Memory fault simulation method based on link library injection and memory mapping mode | |
| CN101201872A (en) | Pre-mortem waveform trace generation for hardware description language simulators | |
| CN105607957A (en) | OPC DA based data collection and monitoring system and method |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210629 |