CN109656621A - A kind of method and device merging code - Google Patents
A kind of method and device merging code Download PDFInfo
- Publication number
- CN109656621A CN109656621A CN201811556643.9A CN201811556643A CN109656621A CN 109656621 A CN109656621 A CN 109656621A CN 201811556643 A CN201811556643 A CN 201811556643A CN 109656621 A CN109656621 A CN 109656621A
- Authority
- CN
- China
- Prior art keywords
- branch
- code
- test
- content
- combined
- 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
- G06F8/72—Code refactoring
-
- 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/3604—Software analysis for verifying properties of programs
- G06F11/3608—Software analysis for verifying properties of programs using formal methods, e.g. model checking, abstract interpretation
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the present application discloses a kind of method and device for merging code, at least one code to be combined is merged into corresponding exploitation branch, content in exploitation branch is tested, if test passes through, then the content developed in branch is merged into test branch, content in test branch is tested, if test passes through, the content in test branch is merged into trunk branch.In the embodiment of the present application, merging of the code to be combined to trunk file can be realized automatically, compared with the prior art in manually come realize code merge by way of, save the operating time, improve the development efficiency of software.
Description
Technical field
The present invention relates to computer fields, more particularly to a kind of method and device for merging code.
Background technique
In the development process of software, different functions can be developed in each exploitation branch by multiple developers.
Specifically, can correspond to each exploitation branch compiles corresponding code, the function of each exploitation branch is respectively corresponded, certainly,
When needing to be adjusted function, the code that can be formed to compiling is modified.The code that compiling is formed is merged into master
In dry branch, the corresponding function of each exploitation branch is had according to the software that the content of trunk branch is formed, it is thereby achieved that soft
The exploitation of part.
In the prior art, the code for corresponding to each exploitation branch is merged on exploitation trunk, it usually needs artificial next
It realizes, however, the demand with software development is gradually increased, the artificial code that merges generally requires longer time, influences software
Development efficiency, in addition, often there is many modifications in the development process of software, if every time by manually merging code,
The time needed is longer.
Summary of the invention
In order to solve the above technical problems, the embodiment of the present application provides a kind of method and device for merging code, it can be automatic
The code for developing branch is merged on exploitation trunk, the development efficiency of software is improved.
The embodiment of the present application provides a kind of method for merging code, which comprises
At least one code to be combined is merged into corresponding exploitation branch；
Content in the exploitation branch is merged into test branch；
Content in the test branch is tested, if test passes through, the content in the test branch is closed
And in trunk branch.
Optionally, it is described at least one code to be combined is merged into corresponding exploitation branch before, the method
Further include:
According to the store path of the code to be combined, at least one described code to be combined is obtained.
Optionally, the content by the exploitation branch is merged into test branch, comprising:
Content in the exploitation branch is tested, if test passes through, the content in the exploitation branch is closed
And in test branch.
Optionally, if not passing through to the content test in the exploitation branch, and/or, in the test branch
Hold test not pass through, is then prompted.
Optionally, the code to be combined has version number, the method also includes:
According to the version number of the code to be combined, the exploitation branch, the test branch and the trunk point are modified
The version number of branch.
Optionally, it if following any one carries out failure, is prompted: at least one described code to be combined is merged
It is merged into the test branch to the corresponding exploitation branch, by the content in the exploitation branch, divides the test
Content in branch is merged on the trunk.
The embodiment of the present application also provides a kind of device for merging code, described device includes:
First combining unit, at least one code to be combined to be merged into corresponding exploitation branch；
Second combining unit, for the content in the exploitation branch to be merged into test branch；
Third combining unit, for testing the content in test branch, if test passes through, by the test point
Content in branch is merged into trunk branch.
Optionally, described device further include:
It is described to be combined to obtain at least one for the store path according to the code to be combined for Code obtaining unit
Code, so that at least one code to be combined is merged into corresponding volume exploitation branch by first combining unit.
Optionally, second combining unit is specifically used for: testing the content in the exploitation branch, if test
Pass through, then the content in the exploitation branch is merged into test branch.
Optionally, the code to be combined has version number,
Then first combining unit is also used to: according to the version number of the code to be combined, modifying the exploitation branch
Version number；
Second combining unit is also used to: according to the version number of the code to be combined, modifying the test branch
Version number.
The third combining unit is also used to: according to the version number of the code to be combined, modifying the trunk branch
Version number.
Optionally, it if the test result of second combining unit and/or third combining unit is not pass through, is mentioned
Show.
Optionally, if one of first combining unit, the second combining unit and third combining unit execute
Merge failure, then can be prompted.
The embodiment of the present application provides a kind of method and device for merging code, at least one code to be combined is merged into
In corresponding exploitation branch, the content in exploitation branch is tested, if test passes through, the content in branch will be developed and closed
And in test branch, the content in test branch is tested, if test passes through, the content in test branch is merged
Onto trunk branch.In the embodiment of the present application, merging of the code to be combined to trunk file can be realized automatically, compared to existing
In technology manually come realize code merge by way of, save the operating time, improve the development efficiency of software.
Detailed description of the invention
In order to more clearly explain the technical solutions in the embodiments of the present application, make required in being described below to embodiment
Attached drawing is briefly described, it should be apparent that, the accompanying drawings in the following description is only some implementations as described in this application
Example, for those of ordinary skill in the art, is also possible to obtain other drawings based on these drawings.
Fig. 1 is a kind of flow chart of method for merging code provided by the embodiments of the present application；
Fig. 2 is a kind of structural block diagram of device for merging code provided by the embodiments of the present application.
Specific embodiment
Inventor has found that in the development process of software, it can be by multiple developers in each exploitation point
Different functions is developed in branch.Specifically, can correspond to each exploitation branch compiles corresponding code, each open is respectively corresponded
The function of branch is sent out, certainly, when needing to be adjusted function, the code that can be formed to compiling is modified.It will compiling
The code of formation is merged into trunk branch, then has each exploitation branch pair according to the software that the content in trunk branch is formed
The function of answering, it is thereby achieved that the exploitation of software.
However, the code that will correspond to each exploitation branch be merged on exploitation trunk, it usually needs it is artificial to realize, so
And as the demand of software development is gradually increased, the artificial code that merges generally requires longer time, influences the exploitation effect of software
Rate, in addition, often there is many modifications in the development process of software, if every time by manually merging code, need when
Between it is longer.
Based on this, the embodiment of the present application provides a kind of method and device for merging code, by least one generation to be combined
Code is merged into corresponding exploitation branch, is tested the content in exploitation branch, if test passes through, will be developed in branch
Content be merged into test branch, the content in test branch is tested, if test pass through, will be in test branch
Content is merged into trunk branch.In the embodiment of the present application, merging of the code to be combined to trunk file, phase can be realized automatically
Than in the prior art manually come realize code merge by way of, save the operating time, improve the development efficiency of software.
With reference to the accompanying drawing, a kind of method for merging code provided by the embodiments of the present application is described in detail by embodiment
And the specific implementation of device.A kind of process of method for merging code provided by the embodiments of the present application is shown with reference to Fig. 1
Figure, may comprise steps of.
At least one code to be combined is merged into corresponding exploitation branch by S101.
Code to be combined corresponds to the code in each exploitation branch (DEVELOP branch) of software, and exploitation branch is
Branch towards developer, it is each exploitation branch correspond to the software in each function, therefore, code to be combined also with it is soft
Part function is corresponding.
Code to be combined can be the code that first exploitation is formed, and be also possible to the generation modified by developer
Code.Usually, in the exploitation of software or debugging process, only the code in one of exploitation branch can be adjusted
Whole, then code to be combined can be a code in corresponding exploitation branch, can also be to the generation in multiple exploitation branches
Code is adjusted, and therefore, code to be combined is also possible to correspond to multiple codes of multiple exploitation branches.
Code to be combined can have version number, and for distinguishing the code of different editions, version number can be in generation to be combined
Code updates after completing compiling, updates before can also merging code, to distinguish difference according to the version number of code to be combined
The software of version.For example, the version number of code to be combined can be 2.0.
Code to be combined also can have engineering name, such as the engineering name of the corresponding code to be combined of the first exploitation branch can
To be first code, the engineering name of the corresponding code to be combined of the second exploitation branch can be second code.Pass through generation to be combined
The engineering name and version number of code can search code to be combined.Such as code to be combined can be first code 2.0, indicating should be to
Merge the code that code is corresponding second version of the first exploitation branch.
Code to be combined can store in code library, such as can store beyond the clouds, also can store in local, is closing
And before code, the store path of code to be combined can be obtained, thus according to storage according to the storage location of code to be combined
Path obtains code to be combined.The storage location of code to be combined is related to software, multiple codes to be combined of the same software
Storage location may be the same or different.The store path of code to be combined can be " ssh: //lirr@
10.10.142.183:29418/ $ engineering name ".
It is understood that the storage location of code to be combined can be determined according to software to be updated or software to be developed,
Such as the corresponding code default storage to be combined of a certain software is in a certain position, then it can be corresponding according to the acquisition of information of the software
Code to be combined.
At least one code to be combined is merged into corresponding exploitation branch, it can be to be opened specifically, pulling at least one
Branch is sent out, at least one code to be combined is merged into corresponding exploitation branch by merge operation, according to exploitation branch
Exploitation branch after store path storage merging.Therefore, the content in each exploitation branch includes that the exploitation branch is corresponding
Code to be combined or modified code to be combined after compiling, that is to say, that the exploitation branch after merging may be implemented
The corresponding function adjusted of the exploitation branch.
After being merged into code to be combined in corresponding exploitation branch, it can also be repaired according to the version number of code to be combined
Change the version number of exploitation branch, so that the version number of exploitation branch is consistent with the version number of code to be combined.
If the step that at least one code to be combined is merged into corresponding exploitation branch is carried out failure, can carry out
Prompt, so that developer checks the reason of merging failure.
The content developed in branch is merged into test branch by S102.
Test branch (RELEASE branch) is the branch towards tester, and the content in test branch may include each
Develop the content in branch.
The content developed in branch is merged into test branch, it can be to pass through merge specifically, pull test branch
At least one content developed in branch is merged into test branch by operation, is stored and is merged according to the store path of test branch
Test branch afterwards.Therefore, the content in test branch includes the generation to be combined after at least one corresponding compiling of exploitation branch
Code or modified code to be combined, that is to say, that it is corresponding that each exploitation branch may be implemented in the test branch after merging
Function adjusted.
It, can be with split for the reliability of code before the content developed in branch is merged into test branch
Content in hair branch is tested, specifically, can whether correct with content grammer in test development branch etc., it can be realized
Corresponding function etc..If test passes through, illustrates that the content developed in branch is more reliable, which can be merged into test
In branch.If test does not pass through, illustrates that the content developed in branch breaks down, then can be prompted, so as to developer
Carry out the modification of respective code and the merging of code.
After the content developed in branch is merged into test branch, it can also be repaired according to the version number of exploitation branch
Change the version number of test branch, so that the version number of test branch is consistent with code to be combined and the exploitation version number of branch.
If the content developed in branch, which is merged into the step in test branch, carries out failure, can be prompted, with
Just developer checks the reason of merging failure.
S103 tests the content in test branch, if test passes through, the content in test branch is merged into
In trunk branch.
Test branch is the branch towards tester, and the content tested in point branch may include in each exploitation branch
The corresponding function of each exploitation branch may be implemented in content, test branch.Therefore, the content developed in branch is being merged into survey
After trying in branch, for the reliability of test branch, the content in test branch can also be tested, with detection test point
Content in branch whether there is loophole, and whether can be realized the corresponding function of each exploitation branch etc..If to test branch
On content test pass through, then illustrate that the content in test branch is more reliable, which can be merged into trunk branch
In (MASTER branch).If not passing through to the content test in test branch, there are problems for the content for illustrating in test branch, then
It can be prompted, so that developer carries out the modification of code and reconsolidating for code.
Content in test branch is merged into trunk branch, it can be to pass through merge specifically, pull trunk branch
Content at least one test branch is merged into trunk branch by operation, is stored and is merged according to the store path of trunk branch
Trunk branch afterwards.Therefore, the corresponding function adjusted of each exploitation branch may be implemented in the trunk branch after merging.
After the content in test branch is merged into trunk branch, it can also be repaired according to the version number of test branch
Change the version number of trunk branch, so as to the version of the version number of trunk branch and code to be combined, exploitation branch and test branch
This number consistent.
If the content in test branch, which is merged into the step in trunk branch, carries out failure, can be prompted, with
Just developer checks the reason of merging failure.
After the content in test branch is merged into trunk branch, label can also be added for code to be combined, used
Merging is completed in characterizing code to be combined, in code merging process next time, by the merging without there is the code of label.
Content in trunk branch can be used for forming software, since the content in trunk branch is according to code to be combined
It is formed, and code to be combined is the functional development that developer is directed to software, therefore, the software formed according to trunk branch
With corresponding function, thus, realize the exploitation of software.
The embodiment of the present application provides a kind of method for merging code, at least one code to be combined is merged into corresponding
It develops in branch, the content in exploitation branch is tested, if test passes through, the content developed in branch is merged into survey
It tries to test the content in test branch in branch, if test passes through, the content in test branch is merged into trunk
In branch.In the embodiment of the present application, merging of the code to be combined to trunk file can be realized automatically, compared with the prior art in
Manually come realize code merge by way of, save the operating time, improve the development efficiency of software.
The method for merging code based on one of the above, the embodiment of the present application also provides a kind of device for merging code, ginsengs
It examines shown in Fig. 2, for a kind of structural block diagram for the device for merging code provided by the embodiments of the present application, may include:
First combining unit 110, at least one code to be combined to be merged into corresponding exploitation branch；
Second combining unit 120, for the content in the exploitation branch to be merged into test branch；
Third combining unit 130, for testing the content in test branch, if test passes through, by the survey
Content in examination branch is merged into trunk branch.
Optionally, described device further include:
It is described to be combined to obtain at least one for the store path according to the code to be combined for Code obtaining unit
Code, so that at least one code to be combined is merged into corresponding volume exploitation branch by first combining unit.
Optionally, second combining unit is specifically used for: testing the content in the exploitation branch, if test
Pass through, then the content in the exploitation branch is merged into test branch.
Optionally, the code to be combined has version number,
Then first combining unit is also used to: according to the version number of the code to be combined, modifying the exploitation branch
Version number；
Second combining unit is also used to: according to the version number of the code to be combined, modifying the test branch
Version number.
The third combining unit is also used to: according to the version number of the code to be combined, modifying the trunk branch
Version number.
Optionally, it if the test result of second combining unit and/or third combining unit is not pass through, is mentioned
Show.
Optionally, if one of first combining unit, the second combining unit and third combining unit execute
Merge failure, then can be prompted.
The embodiment of the present application provides a kind of device for merging code, at least one code to be combined is merged into corresponding
It develops in branch, the content in exploitation branch is tested, if test passes through, the content developed in branch is merged into survey
It tries to test the content in test branch in branch, if test passes through, the content in test branch is merged into trunk
In branch.In the embodiment of the present application, merging of the code to be combined to trunk file can be realized automatically, compared with the prior art in
Manually come realize code merge by way of, save the operating time, improve the development efficiency of software.
" first " in the titles such as " first ... " mentioned in the embodiment of the present application, " first ... " is used only to do name
Word mark, does not represent first sequentially.The rule is equally applicable to " second " etc..
As seen through the above description of the embodiments, those skilled in the art can be understood that above-mentioned implementation
All or part of the steps in example method can add the mode of general hardware platform to realize by software.Based on this understanding,
The technical solution of the application can be embodied in the form of software products, which can store is situated between in storage
In matter, such as read-only memory (English: read-only memory, ROM)/RAM, magnetic disk, CD etc., including some instructions to
So that a computer equipment (can be the network communication equipments such as personal computer, server, or router) executes
Method described in certain parts of each embodiment of the application or embodiment.
All the embodiments in this specification are described in a progressive manner, same and similar portion between each embodiment
Dividing may refer to each other, and each embodiment focuses on the differences from other embodiments.Especially for method reality
For applying example and apparatus embodiments, since it is substantially similar to system embodiment, so describe fairly simple, related place ginseng
See the part explanation of system embodiment.Equipment and system embodiment described above is only schematical, wherein making
It may or may not be physically separated for the module of separate part description, the component shown as module can be
Or it may not be physical module, it can it is in one place, or may be distributed over multiple network units.It can be with
Some or all of the modules therein is selected to achieve the purpose of the solution of this embodiment according to the actual needs.The common skill in this field
Art personnel can understand and implement without creative efforts.
The above is only the preferred embodiment of the application, is not intended to limit the protection scope of the application.It should refer to
Out, for those skilled in the art, it under the premise of not departing from the application, can also make several improvements
And retouching, these improvements and modifications also should be regarded as the protection scope of the application.
Claims (10)
1. a kind of method for merging code, which is characterized in that the described method includes:
At least one code to be combined is merged into corresponding exploitation branch；
Content in the exploitation branch is merged into test branch；
Content in the test branch is tested, if test passes through, the content in the test branch is merged into
In trunk branch.
2. the method according to claim 1, wherein at least one code to be combined is merged into correspondence described
Exploitation branch on before, the method also includes:
According to the store path of the code to be combined, at least one described code to be combined is obtained.
3. the method according to claim 1, wherein the content by the exploitation branch is merged into test
In branch, comprising:
Content in the exploitation branch is tested, if test passes through, the content in the exploitation branch is merged into
In test branch.
4. according to the method described in claim 3, it is characterized in that, if to it is described exploitation branch on content test do not pass through,
And/or the content test in the test branch is not passed through, then it is prompted.
5. method according to any of claims 1-4, which is characterized in that the code to be combined has version number,
The method also includes:
According to the version number of the code to be combined, the exploitation branch, the test branch and the trunk branch are modified
Version number.
6. method according to any of claims 1-4, which is characterized in that if following any one carries out failure,
It is prompted: at least one described code to be combined being merged into the corresponding exploitation branch, will be in the exploitation branch
Content is merged into the test branch, the content in the test branch is merged on the trunk.
7. a kind of device for merging code, which is characterized in that described device includes:
First combining unit, at least one code to be combined to be merged into corresponding exploitation branch；
Second combining unit, for the content in the exploitation branch to be merged into test branch；
Third combining unit, will be in the test branch if test passes through for testing the content in test branch
Content be merged into trunk branch.
8. device according to claim 7, which is characterized in that described device further include:
Code obtaining unit obtains at least one described code to be combined for the store path according to the code to be combined,
So that at least one code to be combined is merged into corresponding volume exploitation branch by first combining unit.
9. device according to claim 7, which is characterized in that second combining unit is specifically used for: to the exploitation
Content in branch is tested, if test passes through, the content in the exploitation branch is merged into test branch.
10. according to device described in claim 7-9 any one, which is characterized in that the code to be combined has version number,
Then first combining unit is also used to: according to the version number of the code to be combined, modifying the version of the exploitation branch
This number；
Second combining unit is also used to: according to the version number of the code to be combined, modifying the version of the test branch
Number.
The third combining unit is also used to: according to the version number of the code to be combined, modifying the version of the trunk branch
Number.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811556643.9A CN109656621A (en) | 2018-12-19 | 2018-12-19 | A kind of method and device merging code |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811556643.9A CN109656621A (en) | 2018-12-19 | 2018-12-19 | A kind of method and device merging code |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN109656621A true CN109656621A (en) | 2019-04-19 |
Family
ID=66114877
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811556643.9A Pending CN109656621A (en) | 2018-12-19 | 2018-12-19 | A kind of method and device merging code |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109656621A (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110633101A (en) * | 2019-09-25 | 2019-12-31 | 杭州港盛软件科技有限公司 | Program code management method, device and equipment and readable storage medium |
| CN110751797A (en) * | 2019-09-30 | 2020-02-04 | 南京紫津融畅信息科技服务有限公司 | ATM system fault processing method, system and storage medium |
| CN111783104A (en) * | 2020-07-02 | 2020-10-16 | 北京自如信息科技有限公司 | Vulnerability checking method, vulnerability checking method and device for continuous integrated codes |
| CN112506525A (en) * | 2020-12-03 | 2021-03-16 | 中国人寿保险股份有限公司 | Continuous integration and continuous delivery method, device, electronic equipment and storage medium |
| CN113138794A (en) * | 2021-04-28 | 2021-07-20 | 河南中烟工业有限责任公司 | Management method and management system for code version |
| WO2024113128A1 (en) * | 2022-11-29 | 2024-06-06 | Huawei Cloud Computing Technologies Co., Ltd. | A code branch managing system for comparing and/or updating a master code branch with a new code branch |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104461578A (en) * | 2014-12-26 | 2015-03-25 | 广州唯品会信息科技有限公司 | Automatic code merging method and system |
| US20150106790A1 (en) * | 2013-10-15 | 2015-04-16 | International Business Machines Corporation | Detecting merge conflicts and compilation errors in a collaborative integrated development environment |
| CN105183789A (en) * | 2015-08-21 | 2015-12-23 | 福建天晴数码有限公司 | File merging method and system based on git source code confliction |
| CN105404519A (en) * | 2015-12-07 | 2016-03-16 | 青岛海信电器股份有限公司 | Version control method, code testing method and system |
| CN106528071A (en) * | 2015-09-15 | 2017-03-22 | 阿里巴巴集团控股有限公司 | Selection method and device for target code |
| CN106933591A (en) * | 2017-03-15 | 2017-07-07 | 东软集团股份有限公司 | The method and device that code merges |
| CN107678773A (en) * | 2017-09-28 | 2018-02-09 | 郑州云海信息技术有限公司 | A kind of code development based on git and testing process management method |
| CN108984413A (en) * | 2018-07-24 | 2018-12-11 | 浙江数链科技有限公司 | Branch code management method and device |
-
2018
- 2018-12-19 CN CN201811556643.9A patent/CN109656621A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150106790A1 (en) * | 2013-10-15 | 2015-04-16 | International Business Machines Corporation | Detecting merge conflicts and compilation errors in a collaborative integrated development environment |
| CN104461578A (en) * | 2014-12-26 | 2015-03-25 | 广州唯品会信息科技有限公司 | Automatic code merging method and system |
| CN105183789A (en) * | 2015-08-21 | 2015-12-23 | 福建天晴数码有限公司 | File merging method and system based on git source code confliction |
| CN106528071A (en) * | 2015-09-15 | 2017-03-22 | 阿里巴巴集团控股有限公司 | Selection method and device for target code |
| CN105404519A (en) * | 2015-12-07 | 2016-03-16 | 青岛海信电器股份有限公司 | Version control method, code testing method and system |
| CN106933591A (en) * | 2017-03-15 | 2017-07-07 | 东软集团股份有限公司 | The method and device that code merges |
| CN107678773A (en) * | 2017-09-28 | 2018-02-09 | 郑州云海信息技术有限公司 | A kind of code development based on git and testing process management method |
| CN108984413A (en) * | 2018-07-24 | 2018-12-11 | 浙江数链科技有限公司 | Branch code management method and device |
Non-Patent Citations (2)
| Title |
|---|
| EASTONLIU: ""Git 使用教程(八)：标签(版本号)"", 《HTTPS://BLOG.CSDN.NET/LMJ19851117/ARTICLE/DETAILS/79670656》 * |
| 冒雨ING,: ""jenkins+gitlab自动化编译部署方案探索及服务端编译webpack实战"", 《HTTPS://WWW.CNBLOGS.COM/SAYSMY/P/8806975.HTML》 * |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110633101A (en) * | 2019-09-25 | 2019-12-31 | 杭州港盛软件科技有限公司 | Program code management method, device and equipment and readable storage medium |
| CN110751797A (en) * | 2019-09-30 | 2020-02-04 | 南京紫津融畅信息科技服务有限公司 | ATM system fault processing method, system and storage medium |
| CN111783104A (en) * | 2020-07-02 | 2020-10-16 | 北京自如信息科技有限公司 | Vulnerability checking method, vulnerability checking method and device for continuous integrated codes |
| CN111783104B (en) * | 2020-07-02 | 2021-04-06 | 北京自如信息科技有限公司 | Vulnerability checking method, vulnerability checking method and device for continuous integrated codes |
| CN112506525A (en) * | 2020-12-03 | 2021-03-16 | 中国人寿保险股份有限公司 | Continuous integration and continuous delivery method, device, electronic equipment and storage medium |
| CN113138794A (en) * | 2021-04-28 | 2021-07-20 | 河南中烟工业有限责任公司 | Management method and management system for code version |
| WO2024113128A1 (en) * | 2022-11-29 | 2024-06-06 | Huawei Cloud Computing Technologies Co., Ltd. | A code branch managing system for comparing and/or updating a master code branch with a new code branch |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109656621A (en) | A kind of method and device merging code | |
| US20200110693A1 (en) | Providing cognitive intelligence across continuous delivery pipeline data | |
| EP2641179B1 (en) | Method and apparatus for automatic diagnosis of software failures | |
| CN107145437B (en) | Java annotation test method and device | |
| US9372779B2 (en) | System, method, apparatus and computer program for automatic evaluation of user interfaces in software programs | |
| US20180137037A1 (en) | White box testing | |
| CA2773981C (en) | System and method of substituting parameter sets in self-contained mini-applications | |
| US10354031B2 (en) | Information processing by interpenetrating signal transmission channel in design for testability of chip | |
| US7680668B2 (en) | Method for generating a language-independent regression test script | |
| US20100192125A1 (en) | Method and system for determining interface compatibility based on component model | |
| JP2009087354A (en) | Automatic test generation system and method for web application | |
| CN105912375A (en) | Method and device for deploying application programs to servers | |
| Sanches et al. | J-swfit: A java software fault injection tool | |
| CN111259406A (en) | Automatic construction method and system for cloud native application vulnerability reproduction environment | |
| CN111767226A (en) | Method, system and equipment for testing cloud computing platform resources | |
| Yao et al. | Formal modeling and systematic black-box testing of sdn data plane | |
| US11663113B2 (en) | Real time fault localization using combinatorial test design techniques and test case priority selection | |
| CN107590064A (en) | A kind of application upgrade method of testing, device and system | |
| US20230359746A1 (en) | Systems and methods for shift left testing | |
| US20230185692A1 (en) | Highly Tested Systems | |
| CN107632912A (en) | A kind of memory diagnosis method of testing under windows systems | |
| US20200265123A1 (en) | Automatic cover point generation based on register transfer level analysis | |
| US11960385B2 (en) | Automatic generation of integrated test procedures using system test procedures | |
| US11740895B2 (en) | Generation of software program repair explanations | |
| Saadatmand | Towards automating integration testing of. NET applications using Roslyn |
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: 20190419 |