CN108415694A - A kind of Android agile development system and methods based on GitFlow workflows - Google Patents
A kind of Android agile development system and methods based on GitFlow workflows Download PDFInfo
- Publication number
- CN108415694A CN108415694A CN201810168659.6A CN201810168659A CN108415694A CN 108415694 A CN108415694 A CN 108415694A CN 201810168659 A CN201810168659 A CN 201810168659A CN 108415694 A CN108415694 A CN 108415694A
- Authority
- CN
- China
- Prior art keywords
- module
- branch
- main split
- code
- branch module
- 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/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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a kind of Android agile development system and methods based on GitFlow workflows, including central code library, the code information for storing all uploads；Main split's module connects above-mentioned central code library；Branch module is developed, the interim task for completing main split's module publication；Functional branch module is formed by the duplication of exploitation branch module and for adding new function in completing corresponding interim task；Bug repair modules connect main split's module and complete the Bug reparations of main split's module；Test module, the interim task completed for test development branch module.The Android agile developments system and method based on GitFlow workflows is compared with prior art, preferably put into practice the thinking of agile development, by the way that development system is configured to several modular constructions, it provides and more smoothly links up and cooperate, make the segregation of duties of project personnel definitely, simple flow promotes team's efficiency of research and development, highly practical.
Description
Technical field
The present invention relates to field of computer technology, specifically a kind of highly practical, based on GitFlow workflows
Android agile development system and methods.
Background technology
What traditional Android software development process was to determine, it is measurable, as long as being collected into needs at the very start
Information and make plan, be then designed according to schedule-exploitation-test-issue a series of this set flow should be just
It can succeed.However, gradually terminating with the demographic dividend epoch, internet traffic increment is stagnated, internet industry it is whole by
Developing market switchs to stock market, what demand was no longer to determine, but continually changing, this has newly the exploitation iteration of software
Requirement and challenge, it is desirable that more science quickly copes with variation, makes adaptation and adjustment at any time.This iteratively faster and adaptation
Property development thinking, the exactly agile development that refers to of the present invention.
Agile development can be more smoothly put into practice by means of rational tool, is based on this, this provides one kind and is based on clearly
The agile development technology of GitFlow code management tools, the technology are provided several flat by GitFlow code management tools
Platform improves the efficiency of exploitation.
Invention content
The technical assignment of the present invention is to be directed to the above shortcoming, provide it is a kind of it is highly practical, be based on GitFlow workflows
Android agile development system and methods.
The present invention provides a kind of Android agile development systems based on GitFlow workflows, including,
Central code library, the code information for storing all uploads；
Main split's module connects above-mentioned central code library, appoints for release code information and by what several interim tasks formed
Business information, and the code information for task of completing is uploaded to central code library after the completion of task；
Branch module is developed, the interim task for completing main split's module publication；
Functional branch module is formed by the duplication of exploitation branch module and for adding new work(in completing corresponding interim task
Energy；
Bug repair modules connect main split's module and complete the Bug reparations of main split's module, and reparation after the completion is sent to out
Send out branch module and characteristic branch module；
Test module, for the interim task that test development branch module is completed, and after test passes through by test result and
The content of test is sent to exploitation branch module and main split's module.
Main split's module is used to receive the code information from Bug repair modules and test module transmission, and will connect
It is issued after the code information addition label received, the label refers to the version number of code；The mission bit stream is based on existing version
This code information is issued by main split's module.
The exploitation branch module is sent periodically in main split's module, that is, develops branch module periodically through test
Module testing and being sent in main split's module is issued.
The functional branch module may be configured with several and each functional branch module and can delete, corresponding, often
A functional branch module, which corresponds to, completes at least one new function.
The Bug repair modules are for repairing Bug existing for existing version code, after the completion of reparation, will repair code hair
It send into main split's module and exploitation branch module.
A kind of Android agile development methods based on GitFlow workflows, realization process be,
Step 1: first by main split's module creation and release task message, the mission bit stream is based in central code library
Existing code information creates；
Step 2: being copied by developing the interim task in branch module reception mission bit stream, and by exploitation branch module
Several functional branch modules, the new function for providing development platform by functional branch module to require in development phase property task；
Step 3: after the completion of exploitation, the interim task that main split's module is completed is tested by test module, and pass through in test
The content of test result and test is sent to exploitation branch module and characteristic branch module afterwards, by main split's module.
In step 1, main split's module receives the code stored in central code library, and is issued after adding label to it,
The label is the version number of code；Corresponding, in step 3, after the completion of exploitation, main split's module receives test module
Code, and issued after adding label to it.
In the step 2, functional branch module may be configured with several and each function according to the difference of interim task
Branch module can be deleted, corresponding, and each functional branch module, which corresponds to, completes at least one new function, and completes new work(
After capable of developing, the code information in the block of functional branch mould is uploaded to exploitation branch module and deletes the functional branch module.
Further include the steps that Bug is repaired before mission bit stream publication in step 1：When the task of main split's module publication
In information based on existing code information, i.e., existing for existing version code when Bug, Bug repair modules carry out Bug reparations, it is complete
Code will be repaired after reparation after is sent to exploitation branch module and characteristic branch module.
A kind of Android agile development system and methods based on GitFlow workflows of the present invention have following excellent
Point：
A kind of Android agile development system and methods based on GitFlow workflows of the present invention are developed in Android and are lived
In dynamic, the thinking of agile development is preferably put into practice, by the way that development system is configured to several modular constructions, is provided more smooth
Communication and cooperation, make the segregation of duties of project personnel definitely, simple flow promotes team's efficiency of research and development, more quickly
Response demand variation, persistently improve code, be finally reached high quality delivery, it is highly practical, it is applied widely, be easy to push away
Extensively.
Description of the drawings
It, below will be to embodiment or existing for the clearer technical solution for illustrating the embodiment of the present invention or the prior art
Attached drawing is briefly described needed in technology description, it should be apparent that, the accompanying drawings in the following description is only this hair
Some bright embodiments for those of ordinary skill in the art without creative efforts, can be with root
Other attached drawings are obtained according to these attached drawings.
Attached drawing 1 is the realization schematic diagram of present system.
Attached drawing 2 is the implementation flow chart of the method for the present invention.
Specific implementation mode
In order to enable those skilled in the art to better understand the solution of the present invention, with reference to the accompanying drawings and detailed description
The present invention is described in further detail.Obviously, described embodiments are only a part of the embodiments of the present invention, rather than
Whole embodiments.Based on the embodiments of the present invention, those of ordinary skill in the art are not making creative work premise
Lower obtained every other embodiment, shall fall within the protection scope of the present invention.
As shown in Fig. 1, the present invention provides a kind of Android agile development systems based on GitFlow workflows,
One software development workflow of GitFlow tool specifications is built on version control tool Git.Git is version pipe
One kind of reason system, different from the centralized edition management system such as CVS, SVN, Git uses the mode in distributed version library, no
Must server software support that every computer locally can do version management all there are one version repository.
For GitFlow workflows using a central code storage, it is the Information clearing-house of all developers, developer
Exploitation is locally completed, branch code is then pushed to central repository again.The core of GitFlow is division to branch and more
Cooperation between a branch, branch is divided into several classifications by GitFlow, and is assigned with very explicitly for different branches
Role defines the usage scenario and usage of different branches：
Central code library, the code information for storing all uploads；
Main split's module connects above-mentioned central code library, appoints for release code information and by what several interim tasks formed
Business information, and the code information for task of completing is uploaded to central code library after the completion of task；
Branch module is developed, the interim task for completing main split's module publication；
Functional branch module is formed by the duplication of exploitation branch module and for adding new work(in completing corresponding interim task
Energy；
Bug repair modules connect main split's module and complete the Bug reparations of main split's module, and reparation after the completion is sent to out
Send out branch module and characteristic branch module；
Test module, for the interim task that test development branch module is completed, and after test passes through by test result and
The content of test is sent to exploitation branch module and main split's module.
Main split's module, i.e. Master branches are used to receive the generation from Bug repair modules and test module transmission
Code information：Stablize relatively, shielded branch, history is issued for preserving official.Developer cannot be direct in Master branches
Exploitation directly cannot carry out the operations such as Push, Merge to Master branches, can only be from other branches（Release branches,
Hotfix branches）Merging comes.It is labelled for all submissions on Master using version number（tag）Also easily and will receive
To code information addition label after issue, the mission bit stream is sent out based on the code information of existing version by main split's module
Cloth.
The exploitation branch module, i.e. Develop branches are sent periodically in main split's module, exploitation branch module week
Phase property is tested and is sent in main split's module by test module and issued.By checking that Develop branches just can know that
Which function is next release have.Develop is to be branched away in Master, and can periodically be merged into Master at the beginning
In, it is merged into Master each time, indicates the exploitation for completing a stage, generates a stable version.Likewise, developer is not
It can directly develop, can only merge from Feature branches etc. in Develop branches.
The functional branch module is Feature branches, and may be configured with several and each functional branch module can delete
It removes, corresponding, each functional branch module, which corresponds to, completes at least one new function.It is cloned, is used based on Develop branches
In each new function of exploitation.Feature branches can create multiple, belong to interim branch, function can delete branch after realizing.
In this process, multiple branches do not need any communication, can concurrently develop.Developer can directly develop in this branch.
The Bug repair modules are Hotfix branches, for repairing Bug existing for existing version code, after the completion of reparation,
Code will be repaired to be sent in main split's module and exploitation branch module.It is created that come from Master branches, reach the standard grade for repairing
The urgent Bug of application.Interim branch is also belonged to, Bug can delete branch after repairing.It is significant to note that being changed in Bug
After good, it to be merged into Master branches and Develop branches simultaneously.Developer can directly develop in this branch.
The test module is Release branches：Test branch is cloned based on Develop branches, is used for project
Some preparations of testing and reach the standard grade comprehensively before line.Developer can directly develop in this branch, and what is found in test process is small
Bug is directly repaired in this branch.This branch also belongs to interim branch, this branch can be deleted after the completion of test.
A kind of Android agile development methods based on GitFlow workflows, realization process be,
Step 1: first by main split's module creation and release task message, the mission bit stream is based in central code library
Existing code information creates；
Step 2: being copied by developing the interim task in branch module reception mission bit stream, and by exploitation branch module
Several functional branch modules, the new function for providing development platform by functional branch module to require in development phase property task；
Step 3: after the completion of exploitation, the interim task that main split's module is completed is tested by test module, and pass through in test
The content of test result and test is sent to exploitation branch module and characteristic branch module afterwards, by main split's module.
In step 1, main split's module receives the code stored in central code library, and is issued after adding label to it,
The label is the version number of code；Corresponding, in step 3, after the completion of exploitation, main split's module receives test module
Code, and issued after adding label to it.
In the step 2, functional branch module may be configured with several and each function according to the difference of interim task
Branch module can be deleted, corresponding, and each functional branch module, which corresponds to, completes at least one new function, and completes new work(
After capable of developing, the code information in the block of functional branch mould is uploaded to exploitation branch module and deletes the functional branch module.
Further include the steps that Bug is repaired before mission bit stream publication in step 1：When the task of main split's module publication
In information based on existing code information, i.e., existing for existing version code when Bug, Bug repair modules carry out Bug reparations, it is complete
Code will be repaired after reparation after is sent to exploitation branch module and characteristic branch module.
Based on the above method, in conjunction with agile development thinking, the practice of Android agile developments is carried out in practical applications
Process is as shown in Fig. 2：
One new R＆D cycle, product manager need first big functional requirement split into several referables, can experience it is small
Project, and ensure to decouple between small project, can independent test publication, distinguish the priority of disparity items, be then directed to different item
Mesh forms PRD documents, carries out a surname in detail and passes through；
Research and development manager determines research and development waiting, small project responsible person and specific developer, and ultimately form waiting according to small project
Gantt chart；
Next it can enter development phase, the task that different developers are connected to according to oneself, it is necessary first to based on Develop points
Branch respectively creates a new Feature branch, and the name of Feature branches needs that different function, such as sharing function can be distinguished,
It can refer to naming method feature_share；In development cycle, every morning carries out standing meeting, for looking back progress yesterday,
Formulate plan today, and the problem of encountering in exposure exploitation, everybody discusses solution, the variation in during which functional and demand can and
When propose, timely respond to change, notice that meeting is centainly rapid, cannot be dilatory, otherwise just deviated from quick principle；
After the completion of basic functional development, developer can beat test bag, give tester and carry out functional test, to what is tested
Bug is repaired, and after reparation completion test passes through, can propose that the functional branch completed is merged into Develop points by one
The request of branch（Merge Request）, and specify respective item responsible person into line code Review；
Project leader, which needs timely processing Merge Request, Review to determine after code is out of question, can be merged into Develop
Branch, at this point, corresponding Feature branches can delete；According to waiting, all Feature branches in the current iteration period are complete
Portion completes exploitation test, and after Merge to Develop branches, illustrates that the development of current period is complete, at this time project
Responsible person can make a call to a Release branch based on Develop branches, this branch dedicated for the preparation before publication, including
Some cleaning works, comprehensive test, the update of document and other preparations, while survey is beaten based on Release branches
Examination packet, tester test all periods new function that needs to reach the standard grade comprehensively, and the Bug developer tested can be straight
This branch is connected on to be repaired；
After the completion of all Bug of Release branches are repaired, this Release branch can be merged into Master by project leader
Branch, and tag labels are beaten, meanwhile, Release branches have to be merged into Develop branches, after the completion of merging, Release points
Branch can delete；New edition launch phase is may then enter into, is packaged based on Master branches, gray scale publication is carried out（Gated
Launch）, i.e., upgrading only is prompted to surveying user in part, go wrong to adjust in time, can be into after gray scale issues 2-3 days
Row is formal to be packaged, and is reinforced, publication is reached the standard grade；
Application after reaching the standard grade needs to make a call to a Hotfix based on Master branches if it find that urgent Bug needs to repair immediately
It is branched off, developer repairs this Bug in this branch, then remerges go back to Master branches, beats tag labels, leads to
It crosses the integrated hot recovery scenario of code and carries out emergency repair to being applied on line, meanwhile, Hotfix branches must synchronize and be merged into
Develop branches, after the completion of merging, Hotfix branches can delete.
So far, a complete Android application iteration cycle terminates, agile development requirement short cycle iteratively faster, and one
A period need to control within one month.
Method using the present invention has：
Higher efficiency：Multiple Feature branch parallels exploitations, are mutually independent of each other, function, which has not been developed, will not influence version
Publication, greatly improves development efficiency, can guarantee the iteratively faster of product；
More smoothly link up：Tens of people R＆D teams are divided into several quick team according to project, utilize the agilities such as standing meeting
Element, the exchange that Team Member is seamless；
Less problem：GitFlow has done considered critical to the modification authority of different branches, it is necessary to by project leader's
Review post codes could merge, and improve code specification, and the difficulty of project management greatly reduces Bug productions while reduction
Raw possibility.
Above-mentioned specific implementation mode is only the specific case of the present invention, and scope of patent protection of the invention includes but not limited to
Above-mentioned specific implementation mode, a kind of any Android agile developments system based on GitFlow workflows for meeting the present invention and
The appropriate change or replacement that the those of ordinary skill of claims of method and any technical field does it, all
It shall fall within the protection scope of the present invention.
Claims (9)
1. a kind of Android agile development systems based on GitFlow workflows, which is characterized in that including,
Central code library, the code information for storing all uploads；
Main split's module connects above-mentioned central code library, appoints for release code information and by what several interim tasks formed
Business information, and the code information for task of completing is uploaded to central code library after the completion of task；
Branch module is developed, the interim task for completing main split's module publication；
Functional branch module is formed by the duplication of exploitation branch module and for adding new work(in completing corresponding interim task
Energy；
Bug repair modules connect main split's module and complete the Bug reparations of main split's module, and reparation after the completion is sent to out
Send out branch module and characteristic branch module；
Test module, for the interim task that test development branch module is completed, and after test passes through by test result and
The content of test is sent to exploitation branch module and main split's module.
2. a kind of Android agile development systems based on GitFlow workflows according to claim 1, feature exist
It is used to receive the code information sent from Bug repair modules and test module in, main split's module, and will receive
It is issued after code information addition label, the label refers to the version number of code；Generation of the mission bit stream based on existing version
Code information is issued by main split's module.
3. a kind of Android agile development systems based on GitFlow workflows according to claim 1, feature exist
In the exploitation branch module is sent periodically in main split's module, that is, develops branch module periodically through test module
It tests and is sent in main split's module and issued.
4. a kind of Android agile development systems based on GitFlow workflows according to claim 1, feature exist
In the functional branch module may be configured with several and each functional branch module and can delete, corresponding, each function
Branch module, which corresponds to, completes at least one new function.
5. a kind of Android agile development systems based on GitFlow workflows according to claim 1, feature exist
In the Bug repair modules are for repairing Bug existing for existing version code, after the completion of reparation, will repair code and are sent to master
In branch module and exploitation branch module.
6. a kind of Android agile development methods based on GitFlow workflows, which is characterized in that its realization process is,
One, first by main split's module creation and release task message, the mission bit stream is based on existing in central code library
Code information creates；
Two, by develop branch module receive mission bit stream in interim task, and will exploitation branch module be copied into it is several
Functional branch module, the new function for providing development platform by functional branch module to require in development phase property task；
Three, after the completion of developing, the interim task that main split's module is completed is tested by test module, and will after test passes through
Test result and the content of test are sent to exploitation branch module and characteristic branch module, by main split's module.
7. a kind of Android agile development methods based on GitFlow workflows according to claim 6, feature exist
In in step 1, main split's module receives the code stored in central code library, and is issued after adding label to it, the mark
Label are the version number of code；Corresponding, in step 3, after the completion of exploitation, main split's module receives the code of test module,
And it is issued after adding label to it.
8. a kind of Android agile development methods based on GitFlow workflows according to claim 6, feature exist
In in the step 2, functional branch module may be configured with several and each functional branch according to the difference of interim task
Module can delete, corresponding, and each functional branch module, which corresponds to, completes at least one new function, and is opened completing new function
After hair, the code information in the block of functional branch mould is uploaded to exploitation branch module and deletes the functional branch module.
9. a kind of Android agile development methods based on GitFlow workflows according to claim 6, feature exist
In further including the steps that Bug is repaired before the publication of mission bit stream in step 1：When the mission bit stream of main split's module publication
In based on existing code information, i.e., existing for existing version code when Bug, Bug repair modules carry out Bug reparations, after the completion
Reparation after will repair code and be sent to exploitation branch module and characteristic branch module.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810168659.6A CN108415694A (en) | 2018-02-28 | 2018-02-28 | A kind of Android agile development system and methods based on GitFlow workflows |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810168659.6A CN108415694A (en) | 2018-02-28 | 2018-02-28 | A kind of Android agile development system and methods based on GitFlow workflows |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN108415694A true CN108415694A (en) | 2018-08-17 |
Family
ID=63129469
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810168659.6A Pending CN108415694A (en) | 2018-02-28 | 2018-02-28 | A kind of Android agile development system and methods based on GitFlow workflows |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108415694A (en) |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109522025A (en) * | 2018-10-30 | 2019-03-26 | 深圳市小赢信息技术有限责任公司 | A kind of code delivery system based on git |
| CN109726114A (en) * | 2018-09-07 | 2019-05-07 | 网联清算有限公司 | Code quality management-control method, device and electronic equipment |
| CN110069260A (en) * | 2019-03-16 | 2019-07-30 | 平安城市建设科技(深圳)有限公司 | Distribution management method, device, equipment and the storage medium of cross-version |
| CN110163524A (en) * | 2019-05-29 | 2019-08-23 | 四川长虹电器股份有限公司 | A kind of work cooperating management platform based on agile development management |
| CN110413309A (en) * | 2019-08-02 | 2019-11-05 | 浪潮云信息技术有限公司 | A kind of item code branch management method and system based on gitlab |
| CN110865806A (en) * | 2019-11-20 | 2020-03-06 | 腾讯科技（深圳）有限公司 | Code processing method, device, server and storage medium |
| CN111124466A (en) * | 2018-10-31 | 2020-05-08 | 上海哔哩哔哩科技有限公司 | Differentiated notification method, differentiated notification system, computer equipment and readable storage medium |
| CN111930423A (en) * | 2020-09-17 | 2020-11-13 | 四川新网银行股份有限公司 | Method for tracing software release version based on microservice |
| CN112000334A (en) * | 2020-07-20 | 2020-11-27 | 北京达佳互联信息技术有限公司 | Page development method, device, server and storage medium |
| CN112860307A (en) * | 2019-11-12 | 2021-05-28 | 纬创资通股份有限公司 | Version management system, method and non-volatile computer readable recording medium |
| CN113687859A (en) * | 2021-08-18 | 2021-11-23 | 上海浦东发展银行股份有限公司 | Branch management method and device for software development, electronic equipment and medium |
| US11321083B2 (en) | 2020-02-18 | 2022-05-03 | The Toronto-Dominion Bank | Automated branching workflow for a version control system |
| CN115586919A (en) * | 2022-10-13 | 2023-01-10 | 上海雷昶科技有限公司 | Code management method and device based on git |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102509197A (en) * | 2011-12-01 | 2012-06-20 | 中国移动通信集团广东有限公司 | Workflow management system and workflow management method |
| US20140289280A1 (en) * | 2013-03-15 | 2014-09-25 | Perforce Software, Inc. | System and Method for Bi-directional Conversion of Directed Acyclic Graphs and Inter-File Branching |
| US20150286558A1 (en) * | 2013-05-14 | 2015-10-08 | Noblis, Inc. | Method and system to automatically enforce a hybrid branching strategy |
| CN105487912A (en) * | 2015-11-30 | 2016-04-13 | 西安闻泰电子科技有限公司 | Public problem modification multi-branch maintenance system and method |
| CN105893035A (en) * | 2016-03-30 | 2016-08-24 | 乐视控股（北京）有限公司 | Distributed code management method and system |
| CN107678773A (en) * | 2017-09-28 | 2018-02-09 | 郑州云海信息技术有限公司 | A kind of code development based on git and testing process management method |
| CN107728996A (en) * | 2017-10-11 | 2018-02-23 | 郑州云海信息技术有限公司 | A kind of GIT branch managements method and device |
-
2018
- 2018-02-28 CN CN201810168659.6A patent/CN108415694A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102509197A (en) * | 2011-12-01 | 2012-06-20 | 中国移动通信集团广东有限公司 | Workflow management system and workflow management method |
| US20140289280A1 (en) * | 2013-03-15 | 2014-09-25 | Perforce Software, Inc. | System and Method for Bi-directional Conversion of Directed Acyclic Graphs and Inter-File Branching |
| US20150286558A1 (en) * | 2013-05-14 | 2015-10-08 | Noblis, Inc. | Method and system to automatically enforce a hybrid branching strategy |
| CN105487912A (en) * | 2015-11-30 | 2016-04-13 | 西安闻泰电子科技有限公司 | Public problem modification multi-branch maintenance system and method |
| CN105893035A (en) * | 2016-03-30 | 2016-08-24 | 乐视控股（北京）有限公司 | Distributed code management method and system |
| CN107678773A (en) * | 2017-09-28 | 2018-02-09 | 郑州云海信息技术有限公司 | A kind of code development based on git and testing process management method |
| CN107728996A (en) * | 2017-10-11 | 2018-02-23 | 郑州云海信息技术有限公司 | A kind of GIT branch managements method and device |
Non-Patent Citations (4)
| Title |
|---|
| VINCENT DRIESSEN: "A successful Git branching model", 《NIVE.COM》 * |
| 刘悦之等: "基于Git的分布式版本控制系统的设计与实现", 《科技传播》 * |
| 敏捷的水: "Git 在团队中的最佳实践--如何正确使用Git Flow", 《博客园》 * |
| 朱守园等: "基于GIT的软件开发模式探究", 《信息通信》 * |
Cited By (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109726114A (en) * | 2018-09-07 | 2019-05-07 | 网联清算有限公司 | Code quality management-control method, device and electronic equipment |
| CN109522025A (en) * | 2018-10-30 | 2019-03-26 | 深圳市小赢信息技术有限责任公司 | A kind of code delivery system based on git |
| CN109522025B (en) * | 2018-10-30 | 2021-07-20 | 深圳市小赢信息技术有限责任公司 | Code issuing system based on git |
| CN111124466A (en) * | 2018-10-31 | 2020-05-08 | 上海哔哩哔哩科技有限公司 | Differentiated notification method, differentiated notification system, computer equipment and readable storage medium |
| CN110069260A (en) * | 2019-03-16 | 2019-07-30 | 平安城市建设科技(深圳)有限公司 | Distribution management method, device, equipment and the storage medium of cross-version |
| CN110163524A (en) * | 2019-05-29 | 2019-08-23 | 四川长虹电器股份有限公司 | A kind of work cooperating management platform based on agile development management |
| CN110413309A (en) * | 2019-08-02 | 2019-11-05 | 浪潮云信息技术有限公司 | A kind of item code branch management method and system based on gitlab |
| CN112860307B (en) * | 2019-11-12 | 2024-04-19 | 纬创资通股份有限公司 | Version management system, method and non-volatile computer readable recording medium |
| CN112860307A (en) * | 2019-11-12 | 2021-05-28 | 纬创资通股份有限公司 | Version management system, method and non-volatile computer readable recording medium |
| CN110865806A (en) * | 2019-11-20 | 2020-03-06 | 腾讯科技（深圳）有限公司 | Code processing method, device, server and storage medium |
| CN110865806B (en) * | 2019-11-20 | 2023-08-18 | 腾讯科技（深圳）有限公司 | Code processing method, device, server and storage medium |
| US11321083B2 (en) | 2020-02-18 | 2022-05-03 | The Toronto-Dominion Bank | Automated branching workflow for a version control system |
| CN112000334A (en) * | 2020-07-20 | 2020-11-27 | 北京达佳互联信息技术有限公司 | Page development method, device, server and storage medium |
| CN111930423B (en) * | 2020-09-17 | 2021-08-24 | 四川新网银行股份有限公司 | Method for tracing software release version based on microservice |
| CN111930423A (en) * | 2020-09-17 | 2020-11-13 | 四川新网银行股份有限公司 | Method for tracing software release version based on microservice |
| CN113687859A (en) * | 2021-08-18 | 2021-11-23 | 上海浦东发展银行股份有限公司 | Branch management method and device for software development, electronic equipment and medium |
| CN113687859B (en) * | 2021-08-18 | 2024-04-19 | 上海浦东发展银行股份有限公司 | Branch management method and device for software development, electronic equipment and medium |
| CN115586919A (en) * | 2022-10-13 | 2023-01-10 | 上海雷昶科技有限公司 | Code management method and device based on git |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108415694A (en) | A kind of Android agile development system and methods based on GitFlow workflows | |
| CN109086071A (en) | A kind of method and server of management software version information | |
| CN106708509A (en) | Automatic software project development all-link configuration management system | |
| CN111352651A (en) | Code branch management method and device | |
| CN101615269A (en) | Backing method in a kind of Workflow Management System and device | |
| CN109146081A (en) | It is a kind of for quickly creating the method and device of model item in machine learning platform | |
| CN111324538A (en) | Micro-service parallel test environment management method based on dynamic routing | |
| CN113050929A (en) | Intelligent contract development, operation and maintenance integrated platform based on HyperLegger Fabric | |
| CN115526578A (en) | Method and device for generating project flow, electronic equipment and storage medium | |
| KR101381231B1 (en) | System and method for developing web-based enterprise applications under agile process | |
| Cagnin et al. | PARFAIT: Towards a framework-based agile reengineering process | |
| CN110196712A (en) | Software development methodology and server based on Cloud Server | |
| CN115185561A (en) | CICD system based on service Jenkins and implementation method | |
| Ahmed et al. | Best practices of RUP® in software product line development | |
| Teppe | The ARNO project: Challenges and experiences in a large-scale industrial software migration project | |
| Chen et al. | Design and Practice of DevOps Platform via Cloud Native Technology | |
| Pastrana-Pardo et al. | Approach to the Best Practices in Software Development Based on DevOps and SCRUM Used in Very Small Entities | |
| Faizi et al. | Implementing Large Enterprise Resource Planning Systems with Agile Methods | |
| Dasoriya | SIGNIFICANCE OF SOFTWARE DEVELOPMENT MODELS. | |
| Li et al. | Implementation of agile development software based on project management | |
| CN115543969B (en) | Data migration method, device, equipment and medium | |
| Cugola et al. | An experience in setting-up a configuration management environment | |
| US20140123100A1 (en) | System and method for implementing information systems | |
| Chang | A distributed integrated fare collection and accounting system for metropolitan railway transit | |
| Xiuli et al. | Research on Digital Agile Information System Based on Microservice Architecture |
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 |
Application publication date: 20180817 |
|
| RJ01 | Rejection of invention patent application after publication |