CN113485913A - Branch management method, system, equipment and storage medium - Google Patents
Branch management method, system, equipment and storage medium Download PDFInfo
- Publication number
- CN113485913A CN113485913A CN202110645500.0A CN202110645500A CN113485913A CN 113485913 A CN113485913 A CN 113485913A CN 202110645500 A CN202110645500 A CN 202110645500A CN 113485913 A CN113485913 A CN 113485913A
- Authority
- CN
- China
- Prior art keywords
- branch
- current task
- task state
- development
- task
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention provides a branch management method, a system, equipment and a storage medium, wherein the branch management method comprises the following steps: acquiring a current task state of a current task; when the current task state is 'in progress', creating a development branch through a Git system; when the current task state is 'to be tested', integrating a preposed task to the development branch; when the current task state is 'in test', testing and accepting the development branch; and when the current task state is 'completed', merging the development branch to the source branch of the current task. The branch management method, the system, the equipment and the storage medium provided by the invention take the current task state as the dimension, reasonably control the branch granularity, and realize small-step trial and error and timely feedback of development branches; collecting codes with the same characteristics submitted for multiple times, and only reserving a submission record for one time; and integrating the preposed tasks to the development branches according to the preset logical relationship, so that the tests of the development branches are more accurate.
Description
Technical Field
The present invention relates to the field of code detection technologies, and in particular, to a branch management method, system, device, and storage medium.
Background
Git is used as an open source distributed version control system, can effectively process the management of project versions from very small to very large at high speed, does not need the support of server-side software, and ensures that the release and the communication of source codes are very convenient; in general, technicians manage a published project by creating a main branch, and add and adjust functions or bug fixes of the project by creating a development branch on the basis of the main branch.
However, in the prior art, since the granularity of the development branch is difficult to control, the problem that the development branch has long duration, wide function range, high conflict probability when being merged with the main branch and the like may occur when the main branch is repaired or adjusted; for the same problem, technicians may have the situation of multiple submissions, so that code review, problem positioning and version rollback are influenced; the maintenance of the development branch is carried out manually, so that the stability of the main branch is ensured to a certain extent, the burden of technicians is increased, and the working efficiency of the technicians is reduced.
In summary, the branch management method in the prior art has the problems that the granularity is difficult to control, the repeated code submission is not beneficial to subsequent processing, the stability of the main branch cannot be guaranteed, and the like.
Disclosure of Invention
In view of the above disadvantages of the prior art, an object of the present invention is to provide a branch management method, system, device and storage medium, which are used to overcome the technical problems in the branch management method in the prior art, such as difficulty in controlling granularity, inconvenience in subsequent processing due to multiple code submissions, and incapability of ensuring the stability of main branches.
To achieve the above and other related objects, the present invention provides a branch management method for receiving a plurality of tasks having logical relationships; for each task, the branch management method comprises the following steps:
acquiring a current task state of a current task;
judging the current task state, executing a corresponding branch task and updating the current task state:
when the current task state is 'in progress', creating a development branch through a Git system, and updating the current task state to 'to be tested';
when the current task state is 'to be tested', judging whether a preposed task exists in the current task according to the logical relation, if so, integrating the preposed task to the development branch, and updating the current task state to 'in-test'; if not, directly updating the current task state to be in the test;
when the current task state is 'in test', testing and accepting the development branch, and updating the current task state to 'finished';
merging the development branch to a source branch of the current task when the current task state is "completed".
In an embodiment of the present invention, when the current task state is "in progress", the step of creating a development branch through the Git system and updating the task state to "to be tested" includes:
when the task state is 'in progress', judging whether the development subtask has a corresponding source code project;
if the source code engineering exists:
judging whether the development subtask has a corresponding source branch, if not, taking a default branch corresponding to the source code engineering as the source branch;
and according to the source branch, creating the development branch through a Git system, and updating the task state to be tested.
In an embodiment of the present invention, when the current task state is "in progress", the step of creating a development branch through the Git system and updating the task state to "to be tested" further includes:
pulling the latest code in the remote configuration file of the Git system and modifying the latest code;
submitting the modified code to the development branch;
merging the modified code with the development branch.
In an embodiment of the present invention, the step of submitting the modified code to the development branch further includes:
deleting the previously submitted code when the previously submitted code is present in the development branch.
In an embodiment of the present invention, the submission information corresponding to the code includes task information of the current task.
In an embodiment of the present invention, when the current task state is "under test", it is determined whether a pre-task exists in the current task according to the logical relationship, and if so, the pre-task is integrated into the development branch, and the current task state is updated to "under test"; if not, the step of directly updating the current task state to 'under test' comprises the following steps:
when the current task state is 'to be tested', judging whether the current task has a corresponding preposed task according to the logical relation;
if so, cloning the preposed task, integrating the preposed task to the development branch, and updating the current task state to be in a test;
if not, directly updating the current task state to be in the test.
In an embodiment of the present invention, the method further includes:
and when the current task state is changed, sending the changed current task state through a third-party platform.
The invention also discloses a branch management system, which adopts the branch management method, and the branch management system comprises:
the task state acquisition module is used for acquiring the current task state of the current task;
the branch task execution module is used for judging the current task state, executing a corresponding branch task and updating the current task state;
the branch task module comprises:
a development branch unit, configured to create a development branch through a Git system when the current task state is "in progress", and update the current task state to "to be tested";
a pre-task judging unit, configured to, when the current task state is "to be tested", judge whether a pre-task exists in the current task according to the logical relationship, and if the pre-task exists, integrate the pre-task to the development branch, and update the current task state to "under test"; if not, directly updating the current task state to be in the test;
a test acceptance unit, configured to, when the current task state is "in test", perform test acceptance on the development branch, and update the current task state to "completed";
and the development branch merging unit is used for merging the development branches to the source branch in the current task when the current task state is 'completed'.
The invention also discloses branch management equipment, which comprises a processor, wherein the processor is coupled with a memory, the memory stores program instructions, and the branch management method is realized when the program instructions stored in the memory are executed by the processor.
The present invention also discloses a computer-readable storage medium containing a program which, when run on a computer, causes the computer to execute the above-described branch management method.
In summary, the branch management method, system, device and storage medium provided by the invention take the current task state of the current task as the dimension, reasonably control the branch granularity, and realize small-step trial and error, fast iteration and timely feedback of developing branches; collecting the codes with the same characteristics submitted for many times, and only keeping a submission record once, so that the process of submitting the codes is linearized; and integrating the preposed tasks to the development branches according to the preset logical relationship, so that the tests of the development branches are more accurate.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a flowchart illustrating a branch management method according to an embodiment of the invention.
Fig. 2 is a schematic structural diagram of a branch management system according to an embodiment of the invention.
FIG. 3 is a block diagram of a branch task execution module according to an embodiment of the present invention.
Fig. 4 is a schematic structural diagram of a branch management apparatus according to an embodiment of the invention.
Description of the element reference numerals
100. A branch management system:
110. a task state acquisition module;
120. a branch task execution module;
121. a development branch creation unit;
122. a pre-task judging unit;
123. a test acceptance unit;
124. developing a branch merging unit;
200. a task management device;
201. a processor;
202. a memory.
Detailed Description
The embodiments of the present invention are described below with reference to specific embodiments, and other advantages and effects of the present invention will be easily understood by those skilled in the art from the disclosure of the present specification. The invention is capable of other and different embodiments and of being practiced or of being carried out in various ways, and its several details are capable of modification in various respects, all without departing from the spirit and scope of the present invention. It is to be noted that the features in the following embodiments and examples may be combined with each other without conflict. It is also to be understood that the terminology used in the examples is for the purpose of describing particular embodiments only, and is not intended to limit the scope of the present invention. Test methods in which specific conditions are not specified in the following examples are generally carried out under conventional conditions or under conditions recommended by the respective manufacturers.
Please refer to fig. 1-4. It should be understood that the structures, ratios, sizes, and the like shown in the drawings are only used for matching the disclosure of the present disclosure, and are not used for limiting the conditions of the present disclosure, so that the present disclosure is not limited to the technical essence, and any modifications of the structures, changes of the ratios, or adjustments of the sizes, can still fall within the scope of the present disclosure without affecting the function and the achievable purpose of the present disclosure. In addition, the terms "upper", "lower", "left", "right", "middle" and "one" used in the present specification are for clarity of description, and are not intended to limit the scope of the present invention, and the relative relationship between the terms and the terms is not to be construed as a scope of the present invention.
When numerical ranges are given in the examples, it is understood that both endpoints of each of the numerical ranges and any value therebetween can be selected unless the invention otherwise indicated. Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs and the description of the present invention, and any methods, apparatuses, and materials similar or equivalent to those described in the examples of the present invention may be used to practice the present invention.
In daily work, Git is an open-source distributed version control system, and can manage project versions efficiently and at high speed.
Referring to fig. 1, a system flow chart of a branch management method in this embodiment is shown, where in this embodiment, the branch management method is used for receiving a plurality of tasks having a logical relationship, and the branch management method includes:
s100, acquiring a real-time task state of a current task;
when the branch management method in this embodiment receives an external task, the real-time task state of the current task is acquired, and preferably, a task is received from the JIRA system as the current task, and the JIRA system is used as a project and transaction tracking tool, and is widely applied to the work fields of defect tracking, customer service, demand collection, process approval, task tracking, project tracking, agile management, and the like. Furthermore, the user may perform different operations during the life cycle of a task, and each operation may change the current task state of the current task. For example: when the received current task is just created in this embodiment, the current task state of the current task is "in progress"; when the current task creates a development branch successfully, the corresponding current task state is changed into 'to be tested'; when the development branch of the current task is successfully checked, the corresponding current task state is changed to be 'completed'.
Specifically, the tasks that have logical relationships come from the same system, e.g., multiple tasks each come from a JIRA system.
In this embodiment, in order to obtain the current task state of the current task in real time, the current task needs to be monitored in real time.
By monitoring the current task, the corresponding current task state can be acquired at the first time when the task state of the current task is updated, the current task is created and the current task is deleted.
In other preferred embodiments, the branch management method may also be used to receive tasks of other systems, and may be able to adjust the corresponding processing logic according to the received tasks.
Step S200, judging the current task state, executing the corresponding branch task and updating the current task state:
when the current task state is 'in progress', creating a development branch through a Git system, and updating the current task state to 'to be tested';
firstly, judging whether a corresponding source code project exists in a current task; if the source code project does not exist, the development branch is not created, the current task is stopped to be executed, and an alarm is sent out; if the source code engineering exists, continuously judging whether the current task has a corresponding source branch, and if the corresponding source branch does not exist, taking a default branch corresponding to the source code engineering as the source branch of the current task; then creating a development branch through the Git system according to the source branch, judging whether the creation is successful, and if the creation is successful, updating the current task state of the current task to be 'to be tested'; and if the creation is unsuccessful, stopping executing the current task and sending an alarm.
Specifically, the development branch is titled as a question key of a parent task (i.e., a story) of the current task.
Furthermore, the latest code in the remote configuration file is pulled to the local through a Git pull command in the Git system, and then the latest code is modified by switching to a development branch through a Git check out command so as to perform a corresponding coding task and a unit test task; subsequently submitting the modified code to a development branch; and merging the modified code with the development branch.
In the process of modifying the latest code, technicians can submit the code at any time, so that the situation of submitting the code for multiple times can exist, and when the code is submitted for the first time, the submission information is set as the task information of the current task, preferably, the task information comprises at least one of a question key of a story and a title of the story; when the codes are submitted subsequently, the submission information used when the codes are submitted for the first time is called, and when the codes submitted before exist in the development branch, the codes submitted before are deleted; for example, when the code is submitted for the second time, the submission information used when the code is submitted for the first time is used, and the code submitted for the first time is deleted after the submission is completed, when the code is submitted for the third time, the submission information used when the code is submitted for the first time is still used, and the code submitted for the second time is deleted after the submission is completed.
By using the same submission information, multiple code submissions are grouped into the same time, so that the multiple code submissions under the same development branch only reserve one submission record.
When the current task state is 'to be tested', judging whether the current task has a preposed task according to the logical relation, if so, integrating the preposed task to a development branch, and updating the current task state to 'under test'; if not, directly updating the current task state to be in the test;
when the current task state is 'to be tested', judging whether the current task has a corresponding preposed task according to the logical relation; if yes, cloning the preposed task, integrating the preposed task to a development branch, and updating the current task state to be in a test state; if not, the current task state is directly updated to be in the test.
In the branch management method of this embodiment, a logical relationship exists among a plurality of tasks, and the logical relationship includes a context when the plurality of tasks are executed and task information of a pre-task corresponding to each task; preferably, the task information of the pre-task may include a task title, a task code, and the like, and the pre-task obtained by matching the current task is integrated into the current development branch according to the logical relationship to call the relevant function of the pre-task.
In the life cycle of a task, a plurality of versions of updating tasks or a plurality of encoding tasks may be performed, a plurality of past tasks correspondingly exist, and the past tasks are merged into a source branch after being successfully checked and accepted and are pulled to the local by a current development branch as a part of the latest code; in the present embodiment, the tasks that have a dependency relationship with the current task may also have a task that is developed at the same time, and are defined as a pre-task, preferably, a Git base command in the Git system is adopted to automatically integrate the pre-task into the source branch, and at this time, the latest code of the remote current task is updated, and the latest code is updated to the current development branch by using the Git pull command again.
Preferably, the integrated state of the preposed task and the development branch is judged, if the integration fails, the current task is stopped to be executed, and an alarm is sent out; and if the integration is successful, updating the current task state of the current task to be in the test.
When the current task state is 'in test', testing and accepting the development branch, judging whether the acceptance is successful or not, if the acceptance is failed, stopping executing the current task, and sending an alarm; if the acceptance is successful, updating the current task state to be 'finished';
when the current task state is "completed," the development branch is merged to the source branch of the current task.
Specifically, the update of the current task state is changed by technicians according to the current task.
At this time, the test environment of the development branch is released, and the development branch and the source branch are automatically merged by utilizing a git base command, so that the submission history in the source branch is linearized.
Preferably, the merging state of the development branch and the source branch is judged, if merging fails, the current task is stopped to be executed, and an alarm is sent out; if the merging is successful, the development branch is deleted.
The above-mentioned manner of giving an alarm includes at least one of sound prompt, light prompt and picture prompt, and also includes sending prompt information to the corresponding technician, and the embodiment does not limit the form of giving an alarm, but all should be included in the scope of protection of the present application.
The branch management method in this embodiment further includes:
and when the current task state is changed, sending the changed current task state through the third-party platform.
Preferably, when the current task state of the current task changes, the updated current task state is sent to the responsible person corresponding to each preset current task state, so as to prompt the technical staff to perform corresponding branch management.
As shown in fig. 2, the present embodiment further provides a branch management system 100, and with the above branch management method, the branch management system 100 includes:
a task state obtaining module 110, configured to obtain a current task state of a current task;
the branch task execution module 120 is configured to determine a current task state, execute a corresponding branch task, and update the current task state:
further, the branch task execution module 120 includes:
a development branch creating unit 121, configured to create a development branch through the Git system and update the current task state to "to be tested" when the current task state is "in progress";
a pre-task determining unit 122, configured to determine whether the current task exists in the pre-task according to the logical relationship when the current task state is "to be tested", and if the current task exists in the pre-task, integrate the pre-task into the development branch, and update the current task state to "under test"; if not, directly updating the current task state to be in the test;
a test acceptance unit 123, configured to, when the current task state is "in test", perform test acceptance on the development branch, and update the current task state to "completed";
and the development branch merging unit 124 is used for merging the development branches to the source branch of the current task when the current task state is 'completed'.
As shown in fig. 3, the present embodiment further proposes a branch management device 200, where the task management device 200 includes a processor 201 and a memory 202, the processor 201 is coupled to the memory 202, and the memory 202 stores program instructions, and when the program instructions stored in the memory 202 are executed by the processor 201, the branch management device is implemented. The Processor 201 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; or a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, or a discrete hardware component; the Memory 202 may include a Random Access Memory (RAM), and may further include a Non-Volatile Memory (Non-Volatile Memory), such as at least one disk Memory. The Memory 202 may also be an internal Memory of a Random Access Memory (RAM) type, and the processor 201 and the Memory 202 may be integrated into one or more independent circuits or hardware, such as: application Specific Integrated Circuit (ASIC). It should be noted that the computer program in the memory 202 can be implemented in the form of software functional units and stored in a computer readable storage medium when the computer program is sold or used as a stand-alone product. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, an electronic device, or a network device) to perform all or part of the steps of the method according to the embodiments of the present invention.
The present embodiment also proposes a computer-readable storage medium storing computer instructions for causing a computer to execute the branch management apparatus described above. The storage medium may be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system or a propagation medium. The storage medium may also include a semiconductor or solid state memory, magnetic tape, a removable computer diskette, a Random Access Memory (RAM), a read-only memory (ROM), a rigid magnetic disk and an optical disk. Optical disks may include compact disk-read only memory (CD-ROM), compact disk-read/write (CD-RW), and DVD.
In summary, the branch management method, system, device and storage medium provided by the invention take the current task state of the current task as the dimension, reasonably control the branch granularity, and realize small-step trial and error, fast iteration and timely feedback of developing branches; collecting the codes with the same characteristics submitted for many times, and only keeping a submission record once, so that the process of submitting the codes is linearized; and integrating the preposed tasks to the development branches according to the preset logical relationship, so that the tests of the development branches are more accurate. Therefore, the invention effectively overcomes various defects in the prior art and has high industrial utilization value.
The foregoing embodiments are merely illustrative of the principles and utilities of the present invention and are not intended to limit the invention. Any person skilled in the art can modify or change the above-mentioned embodiments without departing from the spirit and scope of the present invention. Accordingly, it is intended that all equivalent modifications or changes which can be made by those skilled in the art without departing from the spirit and technical spirit of the present invention be covered by the claims of the present invention.
Claims (10)
1. A branch management method for accepting a plurality of tasks having logical relationships; for each task, the branch management method comprises the following steps:
acquiring a current task state of a current task;
judging the current task state, executing a corresponding branch task and updating the current task state:
when the current task state is 'in progress', creating a development branch through a Git system, and updating the current task state to 'to be tested';
when the current task state is 'to be tested', judging whether a preposed task exists in the current task according to the logical relation, if so, integrating the preposed task to the development branch, and updating the current task state to 'in-test'; if not, directly updating the current task state to be in the test;
when the current task state is 'in test', testing and accepting the development branch, and updating the current task state to 'finished';
merging the development branch to a source branch of the current task when the current task state is "completed".
2. The branch management method according to claim 1, wherein the step of creating a development branch by the Git system when the current task state is "in progress" and updating the task state to "to be tested" comprises:
when the task state is 'in progress', judging whether the development subtask has a corresponding source code project;
if the source code engineering exists:
judging whether the development subtask has a corresponding source branch, if not, taking a default branch corresponding to the source code engineering as the source branch;
and according to the source branch, creating the development branch through a Git system, and updating the task state to be tested.
3. The branch management method according to claim 2, wherein the step of creating a development branch through a Git system and updating the task status to "to be tested" when the current task status is "in progress" further comprises:
pulling the latest code in the remote configuration file of the Git system and modifying the latest code;
submitting the modified codes and submission information corresponding to the codes to the development branch;
merging the modified code with the development branch.
4. The branch management method of claim 3, wherein the step of submitting modified code to the development branch further comprises:
deleting the previously submitted code when the previously submitted code is present in the development branch.
5. The branch management method according to claim 3, wherein the submission information corresponding to the code includes task information of the current task.
6. The branch management method according to claim 1, wherein when the current task status is "under test", it is determined whether a pre-task exists in the current task according to the logical relationship, and if so, the pre-task is integrated into the development branch, and the current task status is updated to "under test"; if not, the step of directly updating the current task state to 'under test' comprises the following steps:
when the task state is 'to be tested', judging whether the current task has a corresponding preposed task according to the logical relation;
if so, cloning the preposed task, integrating the preposed task to the development branch, and updating the current task state to be in a test;
if not, directly updating the current task state to be in the test.
7. The branch management method according to claim 1, further comprising:
and when the current task state is changed, sending the changed current task state through a third-party platform.
8. A branch management system, characterized in that, with the branch management method according to any one of claims 1 to 7, the branch management system comprises:
the task state acquisition module is used for acquiring the current task state of the current task;
the branch task execution module is used for judging the current task state, executing a corresponding branch task and updating the current task state;
the branch task module comprises:
a development branch unit, configured to create a development branch through a Git system when the current task state is "in progress", and update the current task state to "to be tested";
a pre-task judging unit, configured to, when the current task state is "to be tested", judge whether a pre-task exists in the current task according to the logical relationship, and if the pre-task exists, integrate the pre-task to the development branch, and update the current task state to "under test"; if not, directly updating the current task state to be in the test;
a test acceptance unit, configured to, when the current task state is "in test", perform test acceptance on the development branch, and update the current task state to "completed";
and the development branch merging unit is used for merging the development branches to the source branch of the current task when the current task state is 'completed'.
9. A branch management device comprising a processor coupled to a memory, the memory storing program instructions that, when executed by the processor, implement the branch management method of any of claims 1-7.
10. A computer-readable storage medium characterized by comprising a program which, when run on a computer, causes the computer to execute the branch management method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110645500.0A CN113485913B (en) | 2021-06-10 | 2021-06-10 | Branch management method, system, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110645500.0A CN113485913B (en) | 2021-06-10 | 2021-06-10 | Branch management method, system, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113485913A true CN113485913A (en) | 2021-10-08 |
| CN113485913B CN113485913B (en) | 2023-04-07 |
Family
ID=77934555
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110645500.0A Active CN113485913B (en) | 2021-06-10 | 2021-06-10 | Branch management method, system, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113485913B (en) |
Citations (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080263505A1 (en) * | 2007-04-03 | 2008-10-23 | Ldra Technology, Inc. | Automated management of software requirements verification |
| US20110191746A1 (en) * | 2010-02-01 | 2011-08-04 | Raymond Packbier | Tracking device and method for very large-scale software development projects |
| US20140282400A1 (en) * | 2013-03-14 | 2014-09-18 | Jay Moorthi | Systems and methods for managing software development environments |
| US20140344557A1 (en) * | 2013-05-14 | 2014-11-20 | Noblis, Inc. | Method and system to automatically enforce a hybrid branching strategy |
| 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 |
| CN109240738A (en) * | 2018-08-30 | 2019-01-18 | 广州虎牙信息科技有限公司 | Data base authority management method, device and computer equipment |
| US20190205126A1 (en) * | 2017-12-28 | 2019-07-04 | Semmle Limited | Commit history linearization |
| CN109976801A (en) * | 2019-04-24 | 2019-07-05 | 网宿科技股份有限公司 | A kind of code development method, system and computer readable storage medium |
| CN110069260A (en) * | 2019-03-16 | 2019-07-30 | 平安城市建设科技(深圳)有限公司 | Distribution management method, device, equipment and the storage medium of cross-version |
| CN110708232A (en) * | 2019-09-12 | 2020-01-17 | 上海麦克风文化传媒有限公司 | Method and system for realizing JIRA message real-time notification |
| CN111078274A (en) * | 2019-12-09 | 2020-04-28 | 北京五八信息技术有限公司 | Code development method and device, electronic equipment and computer storage medium |
| CN111443940A (en) * | 2020-05-08 | 2020-07-24 | 南京大学 | Complete software life cycle management method and platform based on DevOps |
| CN111782186A (en) * | 2020-07-03 | 2020-10-16 | 携程旅游网络技术（上海）有限公司 | Workflow management method, system, device and storage medium |
| CN112416451A (en) * | 2020-10-15 | 2021-02-26 | 福建升腾资讯有限公司 | Method, device and medium for automatically converting issue state based on JIRA system |
| CN112527380A (en) * | 2020-12-04 | 2021-03-19 | 中国航空工业集团公司成都飞机设计研究所 | Continuous integration method oriented to embedded high-security software |
| CN112631554A (en) * | 2020-12-30 | 2021-04-09 | 中国农业银行股份有限公司 | Project demand management method, device and equipment |
| CN112783622A (en) * | 2021-01-13 | 2021-05-11 | 上海百胜软件股份有限公司 | JIRA system-based task management method, system, device and storage medium |
-
2021
- 2021-06-10 CN CN202110645500.0A patent/CN113485913B/en active Active
Patent Citations (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080263505A1 (en) * | 2007-04-03 | 2008-10-23 | Ldra Technology, Inc. | Automated management of software requirements verification |
| US20110191746A1 (en) * | 2010-02-01 | 2011-08-04 | Raymond Packbier | Tracking device and method for very large-scale software development projects |
| US20140282400A1 (en) * | 2013-03-14 | 2014-09-18 | Jay Moorthi | Systems and methods for managing software development environments |
| US20140344557A1 (en) * | 2013-05-14 | 2014-11-20 | Noblis, Inc. | Method and system to automatically enforce a hybrid branching strategy |
| US20190205126A1 (en) * | 2017-12-28 | 2019-07-04 | Semmle Limited | Commit history linearization |
| 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 |
| CN109240738A (en) * | 2018-08-30 | 2019-01-18 | 广州虎牙信息科技有限公司 | Data base authority management method, device and computer equipment |
| CN110069260A (en) * | 2019-03-16 | 2019-07-30 | 平安城市建设科技(深圳)有限公司 | Distribution management method, device, equipment and the storage medium of cross-version |
| CN109976801A (en) * | 2019-04-24 | 2019-07-05 | 网宿科技股份有限公司 | A kind of code development method, system and computer readable storage medium |
| CN110708232A (en) * | 2019-09-12 | 2020-01-17 | 上海麦克风文化传媒有限公司 | Method and system for realizing JIRA message real-time notification |
| CN111078274A (en) * | 2019-12-09 | 2020-04-28 | 北京五八信息技术有限公司 | Code development method and device, electronic equipment and computer storage medium |
| CN111443940A (en) * | 2020-05-08 | 2020-07-24 | 南京大学 | Complete software life cycle management method and platform based on DevOps |
| CN111782186A (en) * | 2020-07-03 | 2020-10-16 | 携程旅游网络技术（上海）有限公司 | Workflow management method, system, device and storage medium |
| CN112416451A (en) * | 2020-10-15 | 2021-02-26 | 福建升腾资讯有限公司 | Method, device and medium for automatically converting issue state based on JIRA system |
| CN112527380A (en) * | 2020-12-04 | 2021-03-19 | 中国航空工业集团公司成都飞机设计研究所 | Continuous integration method oriented to embedded high-security software |
| CN112631554A (en) * | 2020-12-30 | 2021-04-09 | 中国农业银行股份有限公司 | Project demand management method, device and equipment |
| CN112783622A (en) * | 2021-01-13 | 2021-05-11 | 上海百胜软件股份有限公司 | JIRA system-based task management method, system, device and storage medium |
Non-Patent Citations (9)
| Title |
|---|
| DEVOPS云学堂: "PPT：基于Jenkins实现需求与代码基线关联", 《HTTPS://CLOUD.TENCENT.COM/DEVELOPER/ARTICLE/1558964》 * |
| DRPRINCESS: "Git-rebase 黑魔法之打造完美的线性历史", 《HTTPS://BLOG.CSDN.NET/QQ_32452623/ARTICLE/DETAILS/79459842》 * |
| GIT提交历史的修改删除合并等实践: "熊建刚", 《HTTPS://ZHUANLAN.ZHIHU.COM/P/31989869?FROM_VOTERS_PAGE=TRUE》 * |
| K8S技术圈: "开源端到端流水线实践-需求与代码管理", 《HTTPS://JISHUIN.PROGINN.COM/P/763BFBD310C6》 * |
| LIANGSHU: "软件团队使用Jira的基本知识和常见问题解释", 《HTTPS://WWW.CNBLOGS.COM/LIANGSHU/P/13763250.HTML》 * |
| WEIXIN_39971435: "gitlab合并分支到master_准时下班的秘密：集成 GitLab && JIRA 实现自动化工作流...", 《HTTPS://BLOG.CSDN.NET/WEIXIN_39971435/ARTICLE/DETAILS/110662299》 * |
| 如不來: "Git——分支管理", 《HTTPS://BLOG.CSDN.NET/RUBULAI/ARTICLE/DETAILS/84553889》 * |
| 张丙振，檀飞翔: "《饿了么质量体系搭建实战》", 31 January 2021 * |
| 番茄番茄我是西瓜: "git rebase使用及详解", 《HTTPS://ZHUANLAN.ZHIHU.COM/P/76921124》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113485913B (en) | 2023-04-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10430319B1 (en) | Systems and methods for automatic software testing | |
| US8954930B2 (en) | System and method for reducing test effort by object risk analysis | |
| US9032371B2 (en) | Method and apparatus for automatic diagnosis of software failures | |
| US20110167042A1 (en) | Continuous integration of business intelligence software | |
| US10169002B2 (en) | Automated and heuristically managed solution to quantify CPU and path length cost of instructions added, changed or removed by a service team | |
| US11138097B2 (en) | Automated web testing framework for generating and maintaining test scripts | |
| US11119901B2 (en) | Time-limited dynamic testing pipelines | |
| CN110673936B (en) | Breakpoint continuous operation method and device for arrangement service, storage medium and electronic equipment | |
| CN111274154A (en) | Automatic testing method, device, equipment and storage medium | |
| CN113485913B (en) | Branch management method, system, equipment and storage medium | |
| CN111767218B (en) | Automatic test method, equipment and storage medium for continuous integration | |
| CN111782679B (en) | Supervision method and device for data processing process, computer equipment and storage medium | |
| CN112148614A (en) | Regression testing method and device | |
| US20080172659A1 (en) | Harmonizing a test file and test configuration in a revision control system | |
| US20090105863A1 (en) | Automated integration of feedback from field failure to order configurator for dynamic optimization of manufacturing test processes | |
| CN115113909A (en) | Project automation operation and maintenance method, system, electronic equipment and storage medium | |
| CN113485916A (en) | Detection method, system, device and storage medium based on JIRA code construction | |
| CN113535560A (en) | Test execution method and device, storage medium and computing equipment | |
| CN113094267A (en) | Test result collection method and device | |
| CN116149707B (en) | Method and device for detecting and avoiding upgrading risk of distributed system | |
| CN116541270B (en) | Method and device for testing adaptation verification of operating system | |
| CN115374012A (en) | Automatic regression testing method and device, electronic equipment and storage medium | |
| CN115827469A (en) | Project test management method and system | |
| CN115291940A (en) | APP version generation processing method and device, development processing system and storage medium | |
| CN115237762A (en) | Software performance testing method and device, electronic equipment and storage medium |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |