CN107450933A - A kind of software continuous integrated approach and system - Google Patents
A kind of software continuous integrated approach and system Download PDFInfo
- Publication number
- CN107450933A CN107450933A CN201710712296.3A CN201710712296A CN107450933A CN 107450933 A CN107450933 A CN 107450933A CN 201710712296 A CN201710712296 A CN 201710712296A CN 107450933 A CN107450933 A CN 107450933A
- Authority
- CN
- China
- Prior art keywords
- branch
- test
- acceptance
- exploitation
- code
- 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
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
-
- 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)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a kind of software continuous integrated approach and system.It is related to software development technique；Solve the problems, such as that existing continuous integration system can not meet existing complex software project continuous integrating demand.This method includes：Persistently monitor the exploitation branch of version control repository；When having new code to submit on detecting the exploitation branch, carry out an acceptance inspection test to new code；In Acceptance Test by rear, the exploitation branch is incorporated into issue branch, packed.Technical scheme provided by the invention is applied to the continuous integrating of the software development of more developers, realizes the continuous integrating management based on multiple-limb.
Description
Technical field
The present invention relates to software development technique, espespecially a kind of software continuous integrated approach and system.
Background technology
In cloud computing era, software development process, exploitation member is frequently necessary to oneself work to be integrated into project, leads to
Often each member at least integrates once daily.If project is smaller, the dependence to outside is also relatively small, then Integrated Simulation relates to
And flow and required system architecture it is all simpler.But current many software projects, particularly internet project, it is faced with
A series of problems, such as demand is indefinite, system architecture is complicated, task distribution is chaotic, so as to bring many difficulties to continuous integrating,
Also unnecessary risk is brought to whole project.
To sum up, existing continuous integration system can not meet existing complex software project continuous integrating demand.
The content of the invention
In order to solve the above-mentioned technical problem, the invention provides a kind of software continuous integrated approach and system, more points are passed through
Branch merges management continuous integrating process, while shortening test environment persistently builds the time, greatly improves the effect of research and development of software
Rate, solve the problems, such as that existing continuous integration system can not meet existing complex software project continuous integrating demand.
In order to reach the object of the invention, the invention provides a kind of software continuous integrated approach, including：
Persistently monitor the exploitation branch of version control repository；
When having new code to submit on detecting the exploitation branch, carry out an acceptance inspection test to new code；
In Acceptance Test by rear, the exploitation branch is incorporated into issue branch, packed.
Preferably, the version control repository includes at least two branches, and an exploitation point is included at least two branch
Zhi Yuyi issues branch.
Preferably, when having new code to submit on detecting the exploitation branch, carry out an acceptance inspection test to new code
The step of include：
When thering is new code to submit on detecting the exploitation branch, compiled code, code quality is tested；
After compiling successfully, engineering is packed, restarts test environment example；
Carry out an acceptance inspection test, detects whether the change that the new code is related to meets to check and accept bar defined in business demand
Part, judge that Acceptance Test passes through when meeting the acceptance condition.
Preferably, this method also includes：
Persistently monitor the issue branch of the version control repository.
Preferably, in Acceptance Test by rear, the exploitation branch is incorporated into the step of issuing branch, being packed and wrapped
Include：
In Acceptance Test by rear, the exploitation branch is incorporated into the issue branch；
When code change occurs on detecting the issue branch, packaging operation is carried out.
Present invention also offers a kind of software continuous integration system, including：
First monitoring module, for persistently monitoring the exploitation branch of version control repository；
Module is checked and accepted in test, for when having new code to submit on detecting the exploitation branch, entering to new code
Row Acceptance Test；
Packing and issuing module, in Acceptance Test, by rear, the exploitation branch being incorporated into issue branch, beaten
Bag.
Preferably, the version control repository includes at least two branches, and an exploitation point is included at least two branch
Zhi Yuyi issues branch, and module is checked and accepted in the test to be included：
Quality test unit, for when thering is new code to submit on detecting the exploitation branch, compiled code, testing
Code quality；
Test environment restarts unit, for after compiling successfully, being packed to engineering, restarts test environment example；
Acceptance Test unit, for the test that carries out an acceptance inspection, detect whether the change that the new code is related to meets business
Acceptance condition defined in demand, judge that Acceptance Test passes through when meeting the acceptance condition.
Preferably, the system also includes：
Second monitoring module, for persistently monitoring the issue branch of the version control repository.
Preferably, the packing and issuing module includes：
Branch's combining unit, for, by rear, the exploitation branch being incorporated into the issue branch in Acceptance Test；
Packaged unit, for when code change occurs on detecting the issue branch, carrying out packaging operation.
Preferably, the version control repository is realized by GitHub, and the test is checked and accepted module and run on using Docker
In the test environment built, the packing and issuing module is run on the continuous integrating server realized using Jenkins.
The invention provides a kind of software continuous integrated approach and system, the exploitation branch of version control repository is persistently monitored,
When having new code to submit on detecting the exploitation branch, carry out an acceptance inspection test to new code, passes through in Acceptance Test
Afterwards, the exploitation branch is incorporated into issue branch, is packed, realize the continuous integrating management based on multiple-limb, solved
The problem of existing continuous integration system can not meet existing complex software project continuous integrating demand.Using GitHub as
Version control repository, compared to similar projects edition system so that the merging (merge) of version branch (branch) is very convenient.
Test environment is built using Docker, the Docker virtual containers for realizing second level start, and to the utilization rate of system resource
It is very high.In addition, Docker management, migration and extension are also more easily effective.Using Jenkins as continuous integrating server,
So that the establishment of structure flow is very easy.Technical scheme provided by the invention persistently builds the same of time in shortening test environment
When, substantially increase the efficiency of research and development of software.
Other features and advantages of the present invention will be illustrated in the following description, also, partly becomes from specification
Obtain it is clear that or being understood by implementing the present invention.The purpose of the present invention and other advantages can be by specification, rights
Specifically noted structure is realized and obtained in claim and accompanying drawing.
Brief description of the drawings
Accompanying drawing is used for providing further understanding technical solution of the present invention, and a part for constitution instruction, with this
The embodiment of application is used to explain technical scheme together, does not form the limitation to technical solution of the present invention.
Fig. 1 is a kind of schematic flow sheet for software continuous integrated approach that embodiments of the invention one provide；
Fig. 2 is a kind of realization principle schematic diagram for software continuous integrated approach that embodiments of the invention one provide；
Fig. 3 is a kind of structural representation for software continuous integration system that embodiments of the invention two provide；
Fig. 4 is the structural representation that module 302 is checked and accepted in test in Fig. 3；
Fig. 5 is the structural representation of packing and issuing module 303 in Fig. 3.
Embodiment
For the object, technical solutions and advantages of the present invention are more clearly understood, below in conjunction with accompanying drawing to the present invention
Embodiment be described in detail.It should be noted that in the case where not conflicting, in the embodiment and embodiment in the application
Feature can mutually be combined.
Can be in the computer system of such as one group computer executable instructions the flow of accompanying drawing illustrates the step of
Perform.Also, although logical order is shown in flow charts, in some cases, can be with suitable different from herein
Sequence performs shown or described step.
In cloud computing era, software development process, exploitation member is frequently necessary to oneself work to be integrated into project, leads to
Often each member at least integrates once daily.If project is smaller, the dependence to outside is also relatively small, then Integrated Simulation relates to
And flow and required system architecture it is all simpler.But current many software projects, particularly internet project, it is faced with
A series of problems, such as demand is indefinite, system architecture is complicated, task distribution is chaotic, so as to bring many difficulties to continuous integrating,
Also unnecessary risk is brought to whole project.
Based on above mentioned problem, the embodiment provides a kind of software continuous integrated approach and system, pass through more points
Branch merges management continuous integrating process, while shortening test environment persistently builds the time, greatly improves the effect of research and development of software
Rate, solve the problems, such as that existing continuous integration system can not meet existing complex software project continuous integrating demand.
First with reference to accompanying drawing, embodiments of the invention one are illustrated.
The embodiments of the invention provide a kind of software continuous integrated approach, to use Git then to make as version control repository
Build test environment with Docker, finally using Jenkins as continuous integrating server exemplified by, realize that software continuous is integrated
Flow as shown in figure 1, including：
Step 101, the exploitation branch for persistently monitoring version control repository；
In the embodiment of the present invention, the version control repository includes at least two branches, is included at least two branch
One exploitation branch and an issue branch.
Specifically, version control repository is realized using GitHub in the embodiment of the present invention, including including dev and master two
Branch：
dev：Branch is developed, developer is safeguarded, newest code is submitted to this branch, Jenkins prisons by developer
Depending on this branch, any code, which changes, can all trigger automatic test；
master：Branch is issued, the version in this branch is version of the automatic test after, and automates packing
Monitor this branch.
In this step, to developing branch, i.e. dev branches, carry out continuing monitoring.
Step 102, when thering is new code to submit on detecting the exploitation branch, carry out an acceptance inspection survey to new code
Examination；
This step specifically includes：
(1) when having new code to submit on detecting the exploitation branch, compiled code, code quality is tested；
The dev branches of user (user) code library are monitored, when there is new code to submit every time, structure will be triggered automatically
Task.Compiled code, while generate code specification (code style), the form on code quality such as test coverage.Into
User-docker tasks will be triggered after work(；
(2) after compiling successfully, engineering is packed, restarts test environment example；
Packing user engineerings, user docker examples are restarted in order to the brand-new user bags of use.Will triggering after success
Test case (testcase) task.
(3) carry out an acceptance inspection test, detects whether the change that the new code is related to meets to test defined in business demand
Receipt part, judge that Acceptance Test passes through when meeting the acceptance condition；
Acceptance Test, detection change whether meet acceptance condition defined in business demand.Triggering merge is appointed after success
Business；
Step 103, in Acceptance Test by rear, by it is described exploitation branch be incorporated into issue branch, packed；
In this step, exploitation branch is incorporated into issue branch first, specifically, user dev branches merge is arrived
Master branches.
In the embodiment of the present invention, it can continue to monitor the issue branch of the version control repository, detect the hair
When code occurs in cloth branch changing, packaging operation is carried out, specifically, the master branches of monitoring user code libraries, when there is generation
When code changes, mvn package packaging operations are performed.
Implementation principle of the embodiment of the present invention is as shown in Figure 2.By the embodiment of the present invention, realize from code and be submitted to packing
Whole process automation.Exploitation member submits code to GitHub version control repositories first；Then realized by Jenkins
The monitoring of code change；Then call maven plug-in units to complete the project build of JAVA codes by Jenkins and be encapsulated as
Docker mirror images, while upload to Docker mirror sites；Instruction calls Docker mirror images are finally sent by Jenkins again, passed
It is sent to ICM5.0 environment and starts Docker mirror images.
Version control repository is used as using GitHub：Compared to similar projects edition system, GitHub has a highly significant
Advantage, be exactly version branch (branch) merging it is very convenient.As GitHub can easily contrast Liang Ge branches, know
Which is submitted and is not incorporated into another branch in one, road branch, and vice versa；For same project, GitHub can be set
The version repository (multi version storehouse) of different levels, or the control to issue is realized by different branch'ses (multiple-limb).
Test environment is built using Docker：As a kind of new virtualization mode, relative to traditional virtualization side
Formula has numerous advantages.The startup of Docker virtual containers can realize in second level, and to the utilization rate of system resource very
It is high.In addition, Docker management, migration and extension are also more easily effective, while solve under prior art background, in software point
Hair deployment when, excessively rely on first floor system environment the problem of.
Continuous integrating server is used as using Jenkins：Jenkins provides very effective lasting collection for developer
Management, its powerful plug-in system and clear and definite construction logic so that order line or script mode are used compared with conventional keeper,
Jenkins page makeup flow establishment is very easy, effectively the very cumbersome mode of operation of the keeper of solving over.
Below in conjunction with the accompanying drawings, embodiments of the invention two are illustrated.
The embodiments of the invention provide a kind of software continuous integration system, the structure of the system as shown in figure 3, including：
First monitoring module 301, for persistently monitoring the exploitation branch of version control repository；
Module 302 is checked and accepted in test, for when having new code to submit on detecting the exploitation branch, to new code
Carry out an acceptance inspection test；
Packing and issuing module 303, in Acceptance Test, by rear, the exploitation branch being incorporated into issue branch, entered
Row packing.
Preferably, the version control repository includes at least two branches, and an exploitation point is included at least two branch
Zhi Yuyi issue branch, it is described test check and accept module 302 structure as shown in figure 4, including：
Quality test unit 3021, for when thering is new code to submit on detecting the exploitation branch, compiled code,
Test code quality；
Test environment restarts unit 3022, for after compiling successfully, being packed to engineering, restarts test environment reality
Example；
Acceptance Test unit 3023, for the test that carries out an acceptance inspection, detect whether the change that the new code is related to meets
Acceptance condition defined in business demand, judge that Acceptance Test passes through when meeting the acceptance condition.
Preferably, the system also includes：
Second monitoring module 304, for persistently monitoring the issue branch of the version control repository.
Preferably, the packing and issuing module 303 structure as shown in figure 5, including：
Branch's combining unit 3031, for, by rear, the exploitation branch being incorporated into the issue point in Acceptance Test
Branch；
Packaged unit 3032, for when code change occurs on detecting the issue branch, carrying out packaging operation.
Preferably, the version control repository is realized by GitHub, and the test is checked and accepted module and run on using Docker
In the test environment built, the packing and issuing module is run on the continuous integrating server realized using Jenkins.
The embodiment provides a kind of software continuous integrated approach and system, persistently monitors opening for version control repository
Branch is sent out, when having new code to submit on detecting the exploitation branch, carry out an acceptance inspection test to new code, is surveyed checking and accepting
After pinging, the exploitation branch is incorporated into issue branch, is packed, realizes the continuous integrating pipe based on multiple-limb
Reason, solves the problems, such as that existing continuous integration system can not meet existing complex software project continuous integrating demand.Use
GitHub is as version control repository, compared to similar projects edition system so that the merging of version branch is very convenient.Use
Docker builds test environment, and the Docker virtual containers for realizing second level start, and very high to the utilization rate of system resource.
In addition, Docker management, migration and extension are also more easily effective.Continuous integrating server is used as using Jenkins so that structure
The establishment for building flow is very easy.Technical scheme provided by the invention is while shortening test environment persistently builds the time, greatly
The big efficiency for improving research and development of software.
By the present invention in that by the use of Git as version control repository, test environment then is built using Docker, is finally used
Jenkins builds an effective continuous integration system as continuous integrating server.
Although disclosed herein embodiment as above, described content be only readily appreciate the present invention and use
Embodiment, it is not limited to the present invention.Technical staff in any art of the present invention, taken off not departing from the present invention
On the premise of the spirit and scope of dew, any modification and change, but the present invention can be carried out in the form and details of implementation
Scope of patent protection, still should be subject to the scope of the claims as defined in the appended claims.
Claims (10)
- A kind of 1. software continuous integrated approach, it is characterised in that including：Persistently monitor the exploitation branch of version control repository；When having new code to submit on detecting the exploitation branch, carry out an acceptance inspection test to new code；In Acceptance Test by rear, the exploitation branch is incorporated into issue branch, packed.
- 2. software continuous integrated approach according to claim 1, it is characterised in that the version control repository includes at least two Individual branch, an exploitation branch and an issue branch are included at least two branch.
- 3. software continuous integrated approach according to claim 1, it is characterised in that have on the exploitation branch is detected When new code is submitted, the step of the testing that carried out an acceptance inspection to new code includes：When thering is new code to submit on detecting the exploitation branch, compiled code, code quality is tested；After compiling successfully, engineering is packed, restarts test environment example；Carry out an acceptance inspection test, detects whether the change that the new code is related to meets acceptance condition defined in business demand, Judge that Acceptance Test passes through when meeting the acceptance condition.
- 4. software continuous integrated approach according to claim 1, it is characterised in that this method also includes：Persistently monitor the issue branch of the version control repository.
- 5. software continuous integrated approach according to claim 4, it is characterised in that in Acceptance Test by rear, by described in Exploitation branch, which is incorporated into the step of issuing branch, being packed, to be included：In Acceptance Test by rear, the exploitation branch is incorporated into the issue branch；When code change occurs on detecting the issue branch, packaging operation is carried out.
- A kind of 6. software continuous integration system, it is characterised in that including：First monitoring module, for persistently monitoring the exploitation branch of version control repository；Module is checked and accepted in test, for when having new code to submit on detecting the exploitation branch, testing new code Acceptance Tests；Packing and issuing module, in Acceptance Test, by rear, the exploitation branch being incorporated into issue branch, packed.
- 7. software continuous integration system according to claim 6, it is characterised in that the version control repository includes at least two Individual branch, comprising an exploitation branch and an issue branch at least two branch, module is checked and accepted in the test to be included：Quality test unit, for when thering is new code to submit on detecting the exploitation branch, compiled code, testing code Quality；Test environment restarts unit, for after compiling successfully, being packed to engineering, restarts test environment example；Acceptance Test unit, for the test that carries out an acceptance inspection, detect whether the change that the new code is related to meets business demand Defined acceptance condition, judge that Acceptance Test passes through when meeting the acceptance condition.
- 8. software continuous integration system according to claim 6, it is characterised in that the system also includes：Second monitoring module, for persistently monitoring the issue branch of the version control repository.
- 9. software continuous integration system according to claim 8, it is characterised in that the packing and issuing module includes：Branch's combining unit, for, by rear, the exploitation branch being incorporated into the issue branch in Acceptance Test；Packaged unit, for when code change occurs on detecting the issue branch, carrying out packaging operation.
- 10. software continuous integration system according to claim 6, it is characterised in that the version control repository passes through GitHub realizes that the test is checked and accepted module and run in the test environment built using Docker, the packing and issuing module Run on the continuous integrating server realized using Jenkins.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710712296.3A CN107450933A (en) | 2017-08-18 | 2017-08-18 | A kind of software continuous integrated approach and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710712296.3A CN107450933A (en) | 2017-08-18 | 2017-08-18 | A kind of software continuous integrated approach and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN107450933A true CN107450933A (en) | 2017-12-08 |
Family
ID=60491448
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710712296.3A Pending CN107450933A (en) | 2017-08-18 | 2017-08-18 | A kind of software continuous integrated approach and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107450933A (en) |
Cited By (30)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108021842A (en) * | 2017-12-28 | 2018-05-11 | 广东蜂助手网络技术股份有限公司 | A kind of optimized treatment method of Quick Response Code |
| CN108196825A (en) * | 2017-12-28 | 2018-06-22 | 新华三大数据技术有限公司 | The construction method and system of software project |
| CN108319551A (en) * | 2017-12-29 | 2018-07-24 | 五八有限公司 | A kind of test method of software, device, computer equipment and readable storage medium storing program for executing |
| CN108491210A (en) * | 2018-03-27 | 2018-09-04 | 无锡华云数据技术服务有限公司 | Code continuous integrating method, apparatus, system and server |
| CN108549536A (en) * | 2018-03-29 | 2018-09-18 | 上海嘉银金融科技股份有限公司 | A kind of continuous integrating continues delivery system |
| CN109002307A (en) * | 2018-06-27 | 2018-12-14 | 郑州云海信息技术有限公司 | A kind of upgrading and automated testing method automatically |
| CN109032625A (en) * | 2018-09-04 | 2018-12-18 | 山东浪潮云投信息科技有限公司 | A kind of software continuous integrated approach and device |
| CN109240734A (en) * | 2018-07-17 | 2019-01-18 | 北京奇虎科技有限公司 | Code submits method and device |
| CN109408382A (en) * | 2018-10-11 | 2019-03-01 | 网宿科技股份有限公司 | A kind of continuous integrating method and continuous integration system |
| CN109597644A (en) * | 2018-12-05 | 2019-04-09 | 江苏风云科技服务有限公司 | Project dispositions method and device |
| CN109725910A (en) * | 2018-09-12 | 2019-05-07 | 网联清算有限公司 | Standardization dissemination method, distributing device and the delivery system of application program |
| CN109725906A (en) * | 2018-12-30 | 2019-05-07 | 上海创功通讯技术有限公司 | A kind of code compiling method and corresponding continuous integration system |
| CN109739543A (en) * | 2018-12-18 | 2019-05-10 | 杭州茂财网络技术有限公司 | A kind of code inspection method and its equipment |
| CN109947657A (en) * | 2019-04-03 | 2019-06-28 | 广东电网有限责任公司 | A kind of the mobility scale analysis method and system of enterprise-level information management system |
| CN109947458A (en) * | 2019-03-22 | 2019-06-28 | 广东电网有限责任公司 | A kind of offline source code security continuous integrating method |
| CN109960643A (en) * | 2017-12-22 | 2019-07-02 | 网宿科技股份有限公司 | A kind of code test method and device |
| CN109976762A (en) * | 2019-03-19 | 2019-07-05 | 深圳忆联信息系统有限公司 | A kind of method and its system improving solid state hard disk firmware testing efficiency |
| CN110244951A (en) * | 2018-03-09 | 2019-09-17 | 阿里巴巴集团控股有限公司 | Using dissemination method and device |
| CN110377335A (en) * | 2019-07-26 | 2019-10-25 | 上海携程商务有限公司 | Code integrates accelerated method and system |
| CN110597717A (en) * | 2019-08-29 | 2019-12-20 | 凡普数字技术有限公司 | Code testing method, device and storage medium |
| CN111338632A (en) * | 2018-12-19 | 2020-06-26 | 中国移动通信集团湖南有限公司 | Cloud platform mirror image construction method and device |
| CN111382988A (en) * | 2018-12-28 | 2020-07-07 | 浙江大学 | Event processing method and device for open source project |
| CN111651352A (en) * | 2020-05-29 | 2020-09-11 | 成都新潮传媒集团有限公司 | Warehouse code merging method and device |
| CN111767209A (en) * | 2020-06-11 | 2020-10-13 | Oppo广东移动通信有限公司 | Code testing method, device, storage medium and terminal |
| CN112579475A (en) * | 2020-12-31 | 2021-03-30 | 平安银行股份有限公司 | Code testing method, device, equipment and readable storage medium |
| CN113050981A (en) * | 2021-03-23 | 2021-06-29 | 深圳杰微芯片科技有限公司 | Code on-line automatic publishing method, server and storage medium |
| CN113050982A (en) * | 2021-03-23 | 2021-06-29 | 深圳杰微芯片科技有限公司 | Distributed code automatic publishing system and method |
| CN113127036A (en) * | 2021-04-16 | 2021-07-16 | 展讯通信（上海）有限公司 | Software development system, method, apparatus and medium for continuous integration of code |
| CN113688028A (en) * | 2020-05-19 | 2021-11-23 | 成都鼎桥通信技术有限公司 | Code submission method and device |
| CN117055930A (en) * | 2023-10-12 | 2023-11-14 | 北京时代凌宇科技股份有限公司 | System upgrading deployment method and system |
Citations (2)
| 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 |
| CN104156224A (en) * | 2013-05-14 | 2014-11-19 | 广东电网公司信息中心 | Continuous integration method and system for software construction |
-
2017
- 2017-08-18 CN CN201710712296.3A patent/CN107450933A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104156224A (en) * | 2013-05-14 | 2014-11-19 | 广东电网公司信息中心 | Continuous integration method and system for software construction |
| CN103336688A (en) * | 2013-06-20 | 2013-10-02 | 中标软件有限公司 | Software integrating method and system oriented to cloud computing software research and development process |
Cited By (37)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109960643A (en) * | 2017-12-22 | 2019-07-02 | 网宿科技股份有限公司 | A kind of code test method and device |
| CN109960643B (en) * | 2017-12-22 | 2022-07-22 | 网宿科技股份有限公司 | Code testing method and device |
| CN108196825A (en) * | 2017-12-28 | 2018-06-22 | 新华三大数据技术有限公司 | The construction method and system of software project |
| CN108021842A (en) * | 2017-12-28 | 2018-05-11 | 广东蜂助手网络技术股份有限公司 | A kind of optimized treatment method of Quick Response Code |
| CN108319551A (en) * | 2017-12-29 | 2018-07-24 | 五八有限公司 | A kind of test method of software, device, computer equipment and readable storage medium storing program for executing |
| CN108319551B (en) * | 2017-12-29 | 2021-12-17 | 五八有限公司 | Software testing method and device, computer equipment and readable storage medium |
| CN110244951B (en) * | 2018-03-09 | 2024-03-12 | 阿里巴巴集团控股有限公司 | Application publishing method and device |
| CN110244951A (en) * | 2018-03-09 | 2019-09-17 | 阿里巴巴集团控股有限公司 | Using dissemination method and device |
| CN108491210A (en) * | 2018-03-27 | 2018-09-04 | 无锡华云数据技术服务有限公司 | Code continuous integrating method, apparatus, system and server |
| CN108549536A (en) * | 2018-03-29 | 2018-09-18 | 上海嘉银金融科技股份有限公司 | A kind of continuous integrating continues delivery system |
| CN109002307A (en) * | 2018-06-27 | 2018-12-14 | 郑州云海信息技术有限公司 | A kind of upgrading and automated testing method automatically |
| CN109240734A (en) * | 2018-07-17 | 2019-01-18 | 北京奇虎科技有限公司 | Code submits method and device |
| CN109032625A (en) * | 2018-09-04 | 2018-12-18 | 山东浪潮云投信息科技有限公司 | A kind of software continuous integrated approach and device |
| CN109725910A (en) * | 2018-09-12 | 2019-05-07 | 网联清算有限公司 | Standardization dissemination method, distributing device and the delivery system of application program |
| CN109408382A (en) * | 2018-10-11 | 2019-03-01 | 网宿科技股份有限公司 | A kind of continuous integrating method and continuous integration system |
| CN109597644A (en) * | 2018-12-05 | 2019-04-09 | 江苏风云科技服务有限公司 | Project dispositions method and device |
| CN109739543A (en) * | 2018-12-18 | 2019-05-10 | 杭州茂财网络技术有限公司 | A kind of code inspection method and its equipment |
| CN111338632A (en) * | 2018-12-19 | 2020-06-26 | 中国移动通信集团湖南有限公司 | Cloud platform mirror image construction method and device |
| CN111382988A (en) * | 2018-12-28 | 2020-07-07 | 浙江大学 | Event processing method and device for open source project |
| CN109725906A (en) * | 2018-12-30 | 2019-05-07 | 上海创功通讯技术有限公司 | A kind of code compiling method and corresponding continuous integration system |
| CN109976762A (en) * | 2019-03-19 | 2019-07-05 | 深圳忆联信息系统有限公司 | A kind of method and its system improving solid state hard disk firmware testing efficiency |
| CN109976762B (en) * | 2019-03-19 | 2022-06-07 | 深圳忆联信息系统有限公司 | Method and system for improving solid state disk firmware test efficiency |
| CN109947458A (en) * | 2019-03-22 | 2019-06-28 | 广东电网有限责任公司 | A kind of offline source code security continuous integrating method |
| CN109947657A (en) * | 2019-04-03 | 2019-06-28 | 广东电网有限责任公司 | A kind of the mobility scale analysis method and system of enterprise-level information management system |
| CN110377335A (en) * | 2019-07-26 | 2019-10-25 | 上海携程商务有限公司 | Code integrates accelerated method and system |
| CN110377335B (en) * | 2019-07-26 | 2023-04-25 | 上海携程商务有限公司 | Code integration acceleration method and system |
| CN110597717A (en) * | 2019-08-29 | 2019-12-20 | 凡普数字技术有限公司 | Code testing method, device and storage medium |
| CN113688028A (en) * | 2020-05-19 | 2021-11-23 | 成都鼎桥通信技术有限公司 | Code submission method and device |
| CN113688028B (en) * | 2020-05-19 | 2023-08-15 | 成都鼎桥通信技术有限公司 | Code submitting method and device |
| CN111651352A (en) * | 2020-05-29 | 2020-09-11 | 成都新潮传媒集团有限公司 | Warehouse code merging method and device |
| CN111651352B (en) * | 2020-05-29 | 2023-03-14 | 成都新潮传媒集团有限公司 | Warehouse code merging method and device |
| CN111767209A (en) * | 2020-06-11 | 2020-10-13 | Oppo广东移动通信有限公司 | Code testing method, device, storage medium and terminal |
| CN112579475A (en) * | 2020-12-31 | 2021-03-30 | 平安银行股份有限公司 | Code testing method, device, equipment and readable storage medium |
| CN113050981A (en) * | 2021-03-23 | 2021-06-29 | 深圳杰微芯片科技有限公司 | Code on-line automatic publishing method, server and storage medium |
| CN113050982A (en) * | 2021-03-23 | 2021-06-29 | 深圳杰微芯片科技有限公司 | Distributed code automatic publishing system and method |
| CN113127036A (en) * | 2021-04-16 | 2021-07-16 | 展讯通信（上海）有限公司 | Software development system, method, apparatus and medium for continuous integration of code |
| CN117055930A (en) * | 2023-10-12 | 2023-11-14 | 北京时代凌宇科技股份有限公司 | System upgrading deployment method and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107450933A (en) | A kind of software continuous integrated approach and system | |
| CN105164644B (en) | Hook frame | |
| US9619375B2 (en) | Methods and systems for automatically testing software | |
| US20130132780A1 (en) | Method for Automatically Detecting and Excluding a Tracing Instruction from Further Trace Data Generation for a Software System, a Computer System, and a Computer Program Product | |
| US10496517B2 (en) | System and method for providing runtime diagnostics of executing applications | |
| US8789020B2 (en) | Interactive debugging environments and methods of providing the same | |
| Zhang et al. | Finding errors in multithreaded GUI applications | |
| Sahar et al. | Towards energy aware object-oriented development of android applications | |
| US8656361B2 (en) | Debugging code visually on a canvas | |
| US20150074646A1 (en) | Adopting an existing automation script to a new framework | |
| Mohammad et al. | Cloud services testing: An understanding | |
| Li et al. | Microservice patterns for the life cycle of industrial edge software | |
| CN112506612A (en) | Cluster inspection method, device and equipment and readable storage medium | |
| Macias et al. | Webjshrink: a web service for debloating java bytecode | |
| EP3311265A1 (en) | A computing platform and method thereof for searching, executing, and evaluating computational algorithms | |
| Wozniak et al. | MPI jobs within MPI jobs: A practical way of enabling task-level fault-tolerance in HPC workflows | |
| CN105094870A (en) | Compatible method of 64-bit Linux operating system for 32-bit application software | |
| CN104461890B (en) | Qt program memory using static test method for air traffic control training system | |
| Papoulias et al. | Mercury: Properties and design of a remote debugging solution using reflection | |
| Ghoshal et al. | Science capsule-capturing the data life cycle | |
| Voss et al. | Automated system health and performance benchmarking platform: High performance computing test harness with jenkins | |
| Barve et al. | Upsara: A model-driven approach for performance analysis of cloud-hosted applications | |
| CN115437940A (en) | API (application programming interface) testing method suitable for financial cloud platform | |
| CN107577518A (en) | A kind of virtual machine deployment method and device | |
| Lin et al. | Refactorings for android asynchronous programming |
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: 20171208 |