CN111897566A - Software development continuous integration method, device, equipment and medium - Google Patents
Software development continuous integration method, device, equipment and medium Download PDFInfo
- Publication number
- CN111897566A CN111897566A CN202010578184.5A CN202010578184A CN111897566A CN 111897566 A CN111897566 A CN 111897566A CN 202010578184 A CN202010578184 A CN 202010578184A CN 111897566 A CN111897566 A CN 111897566A
- Authority
- CN
- China
- Prior art keywords
- test
- project
- source code
- package
- branch source
- 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 39
- 230000010354 integration Effects 0.000 title claims description 32
- 238000012360 testing method Methods 0.000 claims abstract description 144
- 238000004519 manufacturing process Methods 0.000 claims abstract description 27
- 230000000391 smoking effect Effects 0.000 claims abstract description 16
- 238000012795 verification Methods 0.000 claims abstract description 8
- 238000004590 computer program Methods 0.000 claims description 15
- 238000010276 construction Methods 0.000 claims description 14
- 238000003860 storage Methods 0.000 claims description 7
- 230000002085 persistent effect Effects 0.000 claims description 2
- 238000011161 development Methods 0.000 abstract description 8
- 238000004806 packaging method and process Methods 0.000 abstract description 6
- 238000010586 diagram Methods 0.000 description 13
- 238000007726 management method Methods 0.000 description 8
- 238000012545 processing Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 230000007547 defect Effects 0.000 description 4
- 230000008439 repair process Effects 0.000 description 3
- 230000001960 triggered effect Effects 0.000 description 3
- 238000012550 audit Methods 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000001419 dependent effect Effects 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002688 persistence Effects 0.000 description 1
- 238000004904 shortening 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
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)
- Stored Programmes (AREA)
Abstract
The invention provides a method, a device, equipment and a medium for continuously integrating software development, wherein the method comprises the following steps: acquiring a project short branch source code, and merging the short branch source code into a main branch source code; constructing the main branch source code, and if the main branch source code is successfully constructed to obtain a publishing packet, uploading the publishing packet to a test application server; carrying out automatic smoking test on the issuing package under a Window system test environment, and setting the state of the project to be test completion if the issuing package passes the test; and acquiring whether the tested project passes the manual examination and verification, and automatically deploying the release package of the project to the production environment when the project passes the examination and verification. The software development continuation, device, equipment and medium provided by the invention realize the automatic flow operation from source code packaging, testing to production in the Window system environment, greatly save the repeated labor of development testing and production personnel, avoid errors and improve the production efficiency and quality.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a method, a device, equipment and a medium for continuously integrating software development.
Background
NET business process management is more and more complex, systems become more huge, and cooperation of a plurality of systems such as a system user authentication site and an SDK interface application site is involved, so that a plurality of systems are designed to be published in each publishing version, and a continuous integration method is generally adopted under the condition of lacking manpower and supporting of infrastructure of a development and compilation machine.
Net simple release schemes based on other languages or a small number of asp have been developed in the prior art, but there is no on-line automation scheme from development to deployment. In the background, the CI framework is introduced into the current main task, and the CI system is configured to complete the project according to a preset schedule.
However, there are some links requiring human intervention in the existing persistent integration schemes, such as: in the existing net issuing mode, developers send issuing packages of codes to operation and maintenance personnel, the operation and maintenance personnel cover the issuing packages to a production environment one by one, and the issuing is only carried out for 2-3 hours each time when the codes are on line, so that the issuing mode is time-consuming and labor-consuming, and the phenomena of losing, falling and the like are caused by manual operation; the testing environment also adopts pure manual testing, and the return testing of the next round after the release is finished needs about 3 to 4 hours, so that the time and the labor are consumed, and the project development progress is seriously influenced. In addition, the existing continuous integration schemes have no detailed scheme aiming at the asp.net project, lack of actual project application and form no closed link of submitting codes to online deployment.
Disclosure of Invention
The technical problem to be solved by the invention is to provide a method, a device, a system, equipment and a medium for continuously integrating software development, which can realize automatic construction and test in time after the branch code of a project is updated, and can automatically deploy to a production environment after the project is approved.
In a first aspect, the present invention provides a method for continuously integrating software development, comprising the following steps:
s10, acquiring short branch source codes of the items, and merging the short branch source codes into main branch source codes;
s20, constructing the main branch source code, and if the construction is successful, obtaining a release package, uploading the release package to a test application server;
s30, carrying out automatic smoking test on the release package under the Window system test environment, and if the release package passes the test, setting the state of the project as the test completion;
and S40, acquiring whether the tested project passes the manual examination, and automatically deploying the release package of the project to the production environment when the project passes the manual examination.
Preferably, the step S20 is further specifically:
the MSbuild tool is used for building the main branch source code, if the building is successful, a publishing package is obtained, and the publishing package is uploaded to a test application server according to a path specified by a project publishing source code configuration file; and if the construction fails, sending a first notice, and ending the step.
Preferably, the step S30 is further specifically:
carrying out Python automatic smoking test on the issuing packet under a Window system test environment, and if the issuing packet passes the test, setting the state of the issuing packet to be test completion; and if the test of the issuing packet is not passed, sending a second notice, and ending the step.
Preferably, the step S30 further includes:
and when the issuing packet passes the test, generating a test report.
In a second aspect, the present invention provides a continuous integration apparatus for software development, comprising: the system comprises a source code module, a construction module, an automatic test module and a deployment module;
the source code module is used for acquiring a short branch source code of a project and merging the short branch source code into a main branch source code;
the building module is used for building the main branch source code, and if the building is successful, a publishing packet is obtained and uploaded to a test application server;
the automatic test module is used for carrying out automatic smoking test on the issuing package under a Window system test environment, and setting the state of the project to be test completion if the issuing package passes the test;
the deployment module is used for acquiring whether the tested project passes the manual examination and verification or not, and automatically deploying the project publishing package to the production environment when the project passes the examination and verification.
Preferably, the building block is further specifically configured to:
the MSbuild tool is used for building the main branch source code, if the building is successful, a publishing package is obtained, and the publishing package is uploaded to a test application server according to a path specified by a project publishing source code configuration file; and if the construction fails, sending a first notice, and ending the step.
Preferably, the automated testing module is further specifically configured to:
carrying out Python automatic smoking test on the issuing packet under a Window system test environment, and if the issuing packet passes the test, setting the state of the issuing packet to be test completion; and if the test of the issuing packet is not passed, sending a second notice, and ending the step.
Preferably, the automated testing module is further configured to:
and when the issuing packet passes the test, generating a test report.
In a third aspect, the present invention provides an electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of the first aspect when executing the program.
In a fourth aspect, the invention provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the method of the first aspect.
One or more technical solutions provided in the embodiments of the present invention have at least the following technical effects or advantages:
1. a closed link is formed from code submission to online deployment, when the main branch code is updated successfully, an automatic updating script is triggered, and integration and testing are performed as soon as possible, so that the probability that defects are left in the deployment link is reduced;
2. the full-automatic updating and releasing of all links from packaging, testing to production are realized, the repeated manual labor and the error probability are reduced, and the production efficiency is greatly improved;
3. because the actions and the cases of the regression test are completely designed, the automatic regression test can automate fussy and repeated tasks, so that the test has consistency and repeatability, the test efficiency can be greatly improved, and the regression test time can be shortened; meanwhile, the test technicians can be liberated to invest more energy to design better test cases.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
Drawings
The invention will be further described with reference to the following examples with reference to the accompanying drawings.
FIG. 1 is a schematic flow chart of a method according to a first embodiment of the present invention;
FIG. 2 is a schematic structural diagram of an apparatus according to a second embodiment of the present invention;
fig. 3 is a schematic structural diagram of an electronic device according to a third embodiment of the invention;
fig. 4 is a schematic structural diagram of a medium according to a fourth embodiment of the present invention.
FIG. 5 is a flowchart of a method according to a fifth embodiment of the present invention;
FIG. 6 is a diagram illustrating a task of creating a single branch pipeline according to a fifth embodiment of the present invention;
fig. 7 is a schematic diagram of an interface of a web page for performing an automated testing under the Windows environment in the fifth embodiment of the present invention.
Detailed Description
The technical scheme in the embodiment of the application has the following general idea:
the technical scheme is a process-oriented solution, and the solution realizes the continuous integration of software development in the window system environment. According to the solution, after the short branch source code is uploaded to the main branch code, the latest main branch code is obtained and constructed by the integration tool, and automatic testing is performed, so that a series of operations of manual packaging, code release, uploading to a server and deployment are omitted, and the method is very convenient.
Example one
The embodiment provides a continuous integration method for software development, as shown in fig. 1, including;
s10, acquiring short branch source codes of the items, and merging the short branch source codes into main branch source codes;
s20, constructing the main branch source code, and if the construction is successful, obtaining a release package, uploading the release package to a test application server;
the step S20 may further specifically be:
the MSbuild tool is used for building the main branch source code, if the building is successful, a publishing package is obtained, and the publishing package is uploaded to a test application server according to a path specified by a project publishing source code configuration file; and if the construction fails, sending a first notice, and ending the step.
If the integrated server finds errors in the process of constructing the codes, the integrated server can send mails to inform developers to repair the codes in time.
S30, carrying out automatic smoking test on the release package under the Window system test environment, and if the release package passes the test, setting the state of the project as the test completion;
the step S30 may further specifically be:
carrying out Python automatic smoking test on the release packet under a Window system test environment, if the release packet passes the test, setting the state of the project as test completion, and generating a test report; and if the test of the issuing packet is not passed, sending a second notice, and ending the step.
If errors are found in the automatic smoking test stage, mails can be sent in time to inform developers to repair.
And S40, acquiring whether the tested project passes the manual examination, and automatically deploying the release package of the project to the production environment when the project passes the manual examination.
Before the project which is tested is deployed to the production environment, the project can be audited manually (such as a project manager), the project manager confirms that the project can be deployed to the production environment and then modifies the project audit state, and then the system automatically performs deployment operation, so that the deployment effectiveness is guaranteed.
According to the method and the device, a closed link is formed from code submission to online deployment, when the main branch code is updated successfully, the automatic updating script is triggered, integration and testing are performed as soon as possible, and the probability that defects are left in the deployment link is reduced; the automatic updating and releasing of all links from packaging, testing to production are realized, the repeated labor of workers and the error probability are reduced, the production efficiency is greatly improved, the repeated labor of development testing and production personnel is greatly saved, and the production enthusiasm is improved.
Based on the same inventive concept, the application also provides a device corresponding to the method in the first embodiment, which is detailed in the second embodiment.
Example two
In this embodiment, a software development continuous integration apparatus is provided, as shown in fig. 2, including: the system comprises a source code module, a construction module, an automatic test module and a deployment module;
the source code module is used for acquiring a short branch source code of a project and merging the short branch source code into a main branch source code;
the building module is used for building the main branch source code, and if the building is successful, a publishing packet is obtained and uploaded to a test application server;
the automatic test module is used for carrying out automatic smoking test on the issuing package under a Window system test environment, and setting the state of the project to be test completion if the issuing package passes the test;
the deployment module is used for acquiring whether the tested project passes the manual examination and verification or not, and automatically deploying the project publishing package to the production environment when the project passes the examination and verification.
The building module is further specifically configured to:
the MSbuild tool is used for building the main branch source code, if the building is successful, a publishing package is obtained, and the publishing package is uploaded to a test application server according to a path specified by a project publishing source code configuration file; and if the construction fails, sending a first notice, and ending the step.
The automated testing module is further specifically configured to:
carrying out Python automatic smoking test on the release packet under a Window system test environment, and if the release packet passes the test, setting the state of the project to be tested; and if the test of the issuing packet is not passed, sending a second notice, and ending the step.
The automated testing module is further configured to:
and when the issuing packet passes the test, generating a test report.
Since the apparatus described in the second embodiment of the present invention is an apparatus used for implementing the method of the first embodiment of the present invention, based on the method described in the first embodiment of the present invention, a person skilled in the art can understand the specific structure and the deformation of the apparatus, and thus the details are not described herein. All the devices adopted in the method of the first embodiment of the present invention belong to the protection scope of the present invention.
Based on the same inventive concept, the application provides an electronic device embodiment corresponding to the first embodiment, which is detailed in the third embodiment.
EXAMPLE III
The embodiment provides an electronic device, as shown in fig. 3, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, any one of the first embodiment modes may be implemented.
Since the electronic device described in this embodiment is a device used for implementing the method in the first embodiment of the present application, based on the method described in the first embodiment of the present application, a specific implementation of the electronic device in this embodiment and various variations thereof can be understood by those skilled in the art, and therefore, how to implement the method in the first embodiment of the present application by the electronic device is not described in detail herein. The equipment used by those skilled in the art to implement the methods in the embodiments of the present application is within the scope of the present application.
Based on the same inventive concept, the application provides a storage medium corresponding to the fourth embodiment, which is described in detail in the fourth embodiment.
Example four
The present embodiment provides a computer-readable storage medium, as shown in fig. 4, on which a computer program is stored, and when the computer program is executed by a processor, any one of the embodiments can be implemented.
EXAMPLE five
The present embodiment provides a method for continuously integrating software development, as shown in fig. 5 to 7, the method specifically includes:
s01, developing new function codes by developers, submitting the codes of the project to short branches, and merging the short branch codes with main branch codes;
s02, acquiring the latest source code in the source code management server by means of an integration tool Jenkins; acquiring the code by means of the integration tool Jenkins can reduce the time and the energy which are required by developers to check the change condition of the code which is interdependent with each other;
s03, after obtaining the latest code, constructing an application program through an MSbuild tool command provided by Microsoft to obtain a publishing packet;
s04, after the construction is successful, pubxml (project release source code configuration file) can designate the release path of the release package, and the release package is directly uploaded to the test application server through a Windows batch processing command;
s05, building a test environment, performing Python automated smoking test in a Windows test environment, and outputting a test report;
s06, writing an automatic test completion message into the project management tool after the test is completed;
s07, changing project states in the project management tool from a test state task to a production release task, and associating the Jenkins of the integration tool through a network hook in the project management tool;
and S08, changing the project management state, enabling the integration tool to automatically trigger an ftp command, and realizing automatic deployment of the distribution package to the production environment.
The continuous project pipeline flow under the windows environment is as follows:
1. developers submit short branch source codes GitLab servers of the project by git and then merge the short branch source codes with main branch codes. (ii) a
2. Installing a GitLab plug-in a continuous integration tool, and automatically acquiring a latest code by the continuous integration tool when a main branch source code changes;
3. the method comprises the steps that a msbuild command compiler is executed by a continuous integration tool in a Windows environment, if the compilation fails, a console can print out the reason of a compilation error and then is modified and resubmitted by developers, and if the compilation is successful, a compiled code can be generated in a working space;
4. after the compiling is successful, executing a Windows batch processing command to restart the web server, and enabling the updating code to take effect immediately;
5. after the Windows test environment is built, smoking test is carried out and an automatic test report is output, and if the test fails, an email is sent to inform a developer to revise and submit again;
6. after the automatic test is completed, the JIRA project management tool receives the test completion message, and the project manager can perform subsequent operation according to the specific conditions of the project;
7. and after the project manager sets the project state to be finished, the issuing package deploys the issuing package to the production environment server through an Ftp command.
8. If the integration server finds that the current version has problems and is not available in the deployment process, the integration server will roll back the deployment to the last version. So that there is always a version available on the server.
The persistence pipeline in the Windows environment is as follows:
submitting codes, namely combining short branch codes with main branch codes, Jenkins constructing and packaging, building a test environment, python automatic test, email, project management and audit plan, and ftp releasing to a production environment
As shown in fig. 6, according to the actual project requirements in the Windows environment, the configuration project pipeline syntax can connect all links in series, without manually executing each link, and concatenate the flows of acquiring the project code, compiling, constructing, issuing, automatically testing, notifying the mail, managing the project, and the like, and execute the flows in sequence.
As shown in FIG. 7, the project for performing the automated test in the windows environment can be previewed through a web page.
The continuous integration of the net project in the Windows environment reduces the change of developers in checking mutually dependent codes, carries out automatic test on project modules, reduces the workload of testers, reduces the waiting of the project personnel and improves the project development efficiency.
In the embodiment of the invention, a closed link is formed from code submission to online deployment, and when the main branch code is successfully updated, an automatic updating script is triggered, and integration and test are performed as soon as possible, so that the probability that defects are left to the deployment link is reduced; the full-automatic updating and releasing of all links from packaging, testing to production are realized, the repeated manual labor and the error probability are reduced, and the production efficiency is greatly improved; because the actions and the cases of the regression test are completely designed, the automatic regression test can automate fussy and repeated tasks, so that the test has consistency and repeatability, the test efficiency can be greatly improved, and the regression test time can be shortened; meanwhile, the test technicians can be liberated to invest more energy to design better test cases.
The continuous integration scheme can timely acquire changes after the short branch source codes of the project are updated, and automatically perform regression testing, so that problems can be found earlier, and the cost for solving the problems is obviously reduced; early integration and early testing reduce the chance that defects are left to the deployment link. In some cases, finding the error earlier also reduces the amount of work required to resolve the error; if the integrated server finds errors in the process of constructing the codes, the integrated server can send mails in time to be provided for developers to repair; the continuous integration shortens the time of each link of development, integration, test and deployment, thereby shortening the waiting time which can appear in the middle. Continuous integration means development, integration, testing, deployment are also continuous.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Although specific embodiments of the invention have been described above, it will be understood by those skilled in the art that the specific embodiments described are illustrative only and are not limiting upon the scope of the invention, and that equivalent modifications and variations can be made by those skilled in the art without departing from the spirit of the invention, which is to be limited only by the appended claims.
Claims (10)
1. A software development continuous integration method is characterized by comprising the following steps:
s10, acquiring short branch source codes of the items, and merging the short branch source codes into main branch source codes;
s20, constructing the main branch source code, and if the construction is successful, obtaining a release package, uploading the release package to a test application server;
s30, carrying out automatic smoking test on the release package under the Window system test environment, and if the release package passes the test, setting the state of the project as the test completion;
and S40, acquiring whether the tested project passes the manual examination, and automatically deploying the release package of the project to the production environment when the project passes the manual examination.
2. The method for continuously integrating software development according to claim 1, wherein the step S20 further comprises:
the MSbuild tool is used for building the main branch source code, if the building is successful, a publishing package is obtained, and the publishing package is uploaded to a test application server according to a path specified by a project publishing source code configuration file; and if the construction fails, sending a first notice, and ending the step.
3. The method for continuously integrating software development according to claim 1, wherein the step S30 further comprises:
carrying out Python automatic smoking test on the release packet under a Window system test environment, and if the release packet passes the test, setting the state of the project to be tested; and if the test of the issuing packet is not passed, sending a second notice, and ending the step.
4. The method for continuously integrating software development according to claim 1 or 3, wherein said step S30 further comprises:
and when the issuing packet passes the test, generating a test report.
5. A software development persistent integration apparatus, comprising: the system comprises a source code module, a construction module, an automatic test module and a deployment module;
the source code module is used for acquiring a short branch source code of a project and merging the short branch source code into a main branch source code;
the building module is used for building the main branch source code, and if the building is successful, a publishing packet is obtained and uploaded to a test application server;
the automatic test module is used for carrying out automatic smoking test on the issuing package under a Window system test environment, and setting the state of the project to be test completion if the issuing package passes the test;
the deployment module is used for acquiring whether the tested project passes the manual examination and verification or not, and automatically deploying the project publishing package to the production environment when the project passes the examination and verification.
6. The continuous integrated device for software development according to claim 5, wherein the building module is further specifically configured to:
the MSbuild tool is used for building the main branch source code, if the building is successful, a publishing package is obtained, and the publishing package is uploaded to a test application server according to a path specified by a project publishing source code configuration file; and if the construction fails, sending a first notice, and ending the step.
7. The continuous integrated device for software development according to claim 5, wherein the automated testing module is further specifically configured to:
carrying out Python automatic smoking test on the release packet under a Window system test environment, and if the release packet passes the test, setting the state of the project to be tested; and if the test of the issuing packet is not passed, sending a second notice, and ending the step.
8. The continuous integration device for software development according to claim 5 or 7, wherein the automated testing module is further configured to:
and when the issuing packet passes the test, generating a test report.
9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method according to any of claims 1 to 4 when executing the program.
10. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010578184.5A CN111897566A (en) | 2020-06-23 | 2020-06-23 | Software development continuous integration method, device, equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010578184.5A CN111897566A (en) | 2020-06-23 | 2020-06-23 | Software development continuous integration method, device, equipment and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111897566A true CN111897566A (en) | 2020-11-06 |
Family
ID=73206438
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010578184.5A Pending CN111897566A (en) | 2020-06-23 | 2020-06-23 | Software development continuous integration method, device, equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111897566A (en) |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112394949A (en) * | 2020-12-03 | 2021-02-23 | 中国科学院软件研究所 | Service version dynamic configuration method for continuous integration |
| CN112506525A (en) * | 2020-12-03 | 2021-03-16 | 中国人寿保险股份有限公司 | Continuous integration and continuous delivery method, device, electronic equipment and storage medium |
| CN112596782A (en) * | 2020-12-26 | 2021-04-02 | 中国农业银行股份有限公司 | Production program package generation method and related equipment |
| CN112596784A (en) * | 2020-12-28 | 2021-04-02 | 青岛海尔科技有限公司 | Iterative version deployment method and device |
| CN112612472A (en) * | 2020-12-11 | 2021-04-06 | 北京旷视科技有限公司 | Embedded model SDK development method and development platform |
| CN112732320A (en) * | 2021-01-14 | 2021-04-30 | 北京锐安科技有限公司 | Continuous integration method and device in software development process, electronic equipment and medium |
| CN112817623A (en) * | 2021-01-26 | 2021-05-18 | 北京自如信息科技有限公司 | Method and device for publishing application program, mobile terminal and readable storage medium |
| CN113254028A (en) * | 2021-04-30 | 2021-08-13 | 北京仁科互动网络技术有限公司 | Code processing method and device, electronic equipment and storage medium |
| CN113485916A (en) * | 2021-06-21 | 2021-10-08 | 上海百胜软件股份有限公司 | Detection method, system, device and storage medium based on JIRA code construction |
| CN114625630A (en) * | 2020-12-14 | 2022-06-14 | 福建天泉教育科技有限公司 | Testing method and testing system for multi-environment multi-role version release system |
| CN115357231A (en) * | 2022-10-20 | 2022-11-18 | 东方合智数据科技(广东)有限责任公司 | Application release system, application release method and medium based on DevOps |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107402765A (en) * | 2017-07-27 | 2017-11-28 | 郑州云海信息技术有限公司 | A kind of code inspection dissemination method and system |
| CN109032625A (en) * | 2018-09-04 | 2018-12-18 | 山东浪潮云投信息科技有限公司 | A kind of software continuous integrated approach and device |
| CN109683899A (en) * | 2017-10-18 | 2019-04-26 | 中移(苏州)软件技术有限公司 | A kind of software integrating method and device |
| CN109684215A (en) * | 2018-12-25 | 2019-04-26 | 中国科学院电子学研究所苏州研究院 | A kind of automated software Quality System Review and iteratively faster method |
| US20190243742A1 (en) * | 2018-02-02 | 2019-08-08 | Bank Of America Corporation | Smart tool for enterprise-wide software integration and deployment |
-
2020
- 2020-06-23 CN CN202010578184.5A patent/CN111897566A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107402765A (en) * | 2017-07-27 | 2017-11-28 | 郑州云海信息技术有限公司 | A kind of code inspection dissemination method and system |
| CN109683899A (en) * | 2017-10-18 | 2019-04-26 | 中移(苏州)软件技术有限公司 | A kind of software integrating method and device |
| US20190243742A1 (en) * | 2018-02-02 | 2019-08-08 | Bank Of America Corporation | Smart tool for enterprise-wide software integration and deployment |
| CN109032625A (en) * | 2018-09-04 | 2018-12-18 | 山东浪潮云投信息科技有限公司 | A kind of software continuous integrated approach and device |
| CN109684215A (en) * | 2018-12-25 | 2019-04-26 | 中国科学院电子学研究所苏州研究院 | A kind of automated software Quality System Review and iteratively faster method |
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112394949B (en) * | 2020-12-03 | 2022-04-22 | 中国科学院软件研究所 | Service version dynamic configuration method for continuous integration |
| CN112506525A (en) * | 2020-12-03 | 2021-03-16 | 中国人寿保险股份有限公司 | Continuous integration and continuous delivery method, device, electronic equipment and storage medium |
| CN112394949A (en) * | 2020-12-03 | 2021-02-23 | 中国科学院软件研究所 | Service version dynamic configuration method for continuous integration |
| CN112612472A (en) * | 2020-12-11 | 2021-04-06 | 北京旷视科技有限公司 | Embedded model SDK development method and development platform |
| CN112612472B (en) * | 2020-12-11 | 2022-08-23 | 北京旷视科技有限公司 | Embedded model SDK development method and development platform |
| CN114625630A (en) * | 2020-12-14 | 2022-06-14 | 福建天泉教育科技有限公司 | Testing method and testing system for multi-environment multi-role version release system |
| CN112596782A (en) * | 2020-12-26 | 2021-04-02 | 中国农业银行股份有限公司 | Production program package generation method and related equipment |
| CN112596784A (en) * | 2020-12-28 | 2021-04-02 | 青岛海尔科技有限公司 | Iterative version deployment method and device |
| CN112596784B (en) * | 2020-12-28 | 2023-11-28 | 青岛海尔科技有限公司 | Iterative version deployment method and device |
| CN112732320A (en) * | 2021-01-14 | 2021-04-30 | 北京锐安科技有限公司 | Continuous integration method and device in software development process, electronic equipment and medium |
| CN112732320B (en) * | 2021-01-14 | 2024-05-10 | 北京锐安科技有限公司 | Continuous integration method and device for software development process, electronic equipment and medium |
| CN112817623A (en) * | 2021-01-26 | 2021-05-18 | 北京自如信息科技有限公司 | Method and device for publishing application program, mobile terminal and readable storage medium |
| CN113254028A (en) * | 2021-04-30 | 2021-08-13 | 北京仁科互动网络技术有限公司 | Code processing method and device, electronic equipment and storage medium |
| CN113485916A (en) * | 2021-06-21 | 2021-10-08 | 上海百胜软件股份有限公司 | Detection method, system, device and storage medium based on JIRA code construction |
| CN115357231A (en) * | 2022-10-20 | 2022-11-18 | 东方合智数据科技(广东)有限责任公司 | Application release system, application release method and medium based on DevOps |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111897566A (en) | Software development continuous integration method, device, equipment and medium | |
| CN109960643B (en) | Code testing method and device | |
| CN111414172B (en) | Automatic deployment and release system and method for application software | |
| CN107463362B (en) | Method and system for continuous deployment based on multiple Jenkins | |
| US8745585B2 (en) | Meta-data for single development test environment | |
| CN109683899B (en) | Software integration method and device | |
| US8533676B2 (en) | Single development test environment | |
| CN111400119B (en) | Multi-project and multi-platform self-adaptive chip design FPGA prototype verification method and system | |
| US20130174124A1 (en) | Version numbering in single development and test environment | |
| CN110083369A (en) | A kind of continuous integrating and lasting delivery method based on container scheme | |
| CN111552644A (en) | Micro-service architecture-based software continuous integration method | |
| CN111324522A (en) | Automatic test system and method | |
| CN105955749A (en) | Continuous software project integration method and device | |
| AU2012201749B2 (en) | Single development test environment | |
| CN112561370B (en) | Method and device for managing software release, computer equipment and storage medium | |
| CN112596784A (en) | Iterative version deployment method and device | |
| CN114168213A (en) | Software release method and device based on Jenkins and electronic equipment | |
| CN112882724A (en) | Method for automatic deployment of OpenStack cloud platform pipeline | |
| CN112732561A (en) | Project deployment method and device, computer equipment and storage medium | |
| CN117111907A (en) | Software development system | |
| CN116820968A (en) | Automatic deployment method and system based on CICD full-function arrangement | |
| EP2503450A2 (en) | Version numbering in single development and test environment | |
| CN114115842A (en) | Visual configuration method and system for GitLab assembly line | |
| Bhadra | A Stochastic Petri net Model of Continuous Integration and Continuous Delivery | |
| CN110175112A (en) | The method and apparatus of Kernel-based methods management raising version testing efficiency |
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 | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20201106 |