CN116302082A - Version control automatic base changing method, device, equipment and medium - Google Patents
Version control automatic base changing method, device, equipment and medium Download PDFInfo
- Publication number
- CN116302082A CN116302082A CN202310587406.3A CN202310587406A CN116302082A CN 116302082 A CN116302082 A CN 116302082A CN 202310587406 A CN202310587406 A CN 202310587406A CN 116302082 A CN116302082 A CN 116302082A
- Authority
- CN
- China
- Prior art keywords
- base
- client
- branch code
- request
- code segment
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 45
- 238000012360 testing method Methods 0.000 claims abstract description 22
- 238000012544 monitoring process Methods 0.000 claims description 20
- 238000004891 communication Methods 0.000 claims description 19
- 238000012508 change request Methods 0.000 claims description 17
- 230000008859 change Effects 0.000 claims description 12
- 230000002159 abnormal effect Effects 0.000 claims description 5
- 238000004590 computer program Methods 0.000 claims description 4
- 239000000725 suspension Substances 0.000 claims description 3
- 238000012545 processing Methods 0.000 abstract description 5
- 230000001960 triggered effect Effects 0.000 abstract description 4
- 238000010586 diagram Methods 0.000 description 5
- 238000007726 management method Methods 0.000 description 4
- 230000009466 transformation Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008707 rearrangement Effects 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3604—Software analysis for verifying properties of programs
- G06F11/3616—Software analysis for verifying properties of programs using software metrics
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Quality & Reliability (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses an automatic base changing method, device, equipment and medium for version control. The method comprises the following steps: the branch code segments in the merging request input by the user are sent to the client; receiving a base changing request sent by a client based on a branch code segment, wherein the base changing request is generated when the client determines that a merging request state field in the branch code segment is opened and a testing flow state field is an initial default state; and carrying out automatic base changing operation on the branch code segments according to the base changing request to obtain positioning base changing points. The branch code segments are sent to the client, and the generated variable base request is verified according to the branch code segments by the client, so that the automatic variable base of the branch code segments is triggered, the submitted branch code segments can be timely subjected to the rebase processing, and a user does not need to manually perform the rebase button operation, so that the efficiency and convenience of the rebase operation are improved.
Description
Technical Field
The embodiment of the invention relates to the technical field of communication, in particular to an automatic base changing method, device, equipment and medium for version control.
Background
The Gitlab is a web service platform deployed on the basis of git as code management, and can effectively and quickly process project version management. Most of the current companies use git as a source code management tool during research and development, take gitlab of a web service platform as a source code warehouse for management, intuitively and effectively operate each project by utilizing the characteristic that each project and each branch are mutually independent, and combine the modified contents of the branches on the project into a backbone.
Under the same item, when the submission of the same multiple merging requests needs to enter a warehouse or is not the submission of the merging requests which are consistent with the master, none of the merging requests is submitted to be merge, and all merging requests in the period need a manager to frequently and timely perform rebase button clicking operation on different merging requests, which brings great inconvenience to the manager.
Disclosure of Invention
The embodiment of the invention provides an automatic base changing method, device, equipment and medium for version control, which are used for realizing automatic base changing under the version control.
In a first aspect, an embodiment of the present invention provides an automatic version control method, applied to a warehouse server, including:
the branch code segments in the merging request input by the user are sent to the client;
receiving a base change request sent by the client based on the branch code segment, wherein the base change request is generated when the client determines that a merging request state field in the branch code segment is opened and a testing flow state field is an initial default state;
and carrying out automatic base changing operation on the branch code segment according to the base changing request so as to obtain a positioning base changing point.
In a second aspect, an embodiment of the present invention provides an automatic version control base device, including: the branch code segment sending module is used for sending the branch code segments in the merging request input by the user to the client;
the base-changing request receiving module is used for receiving a base-changing request sent by the client based on the branch code segment, wherein the base-changing request is generated when the client determines that a merging request state field in the branch code segment is opened and a testing flow state field is an initial default state;
and the automatic base changing module is used for carrying out automatic base changing operation on the branch code segments according to the base changing request so as to obtain a positioning base changing point.
In a third aspect, embodiments of the present invention provide a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing a method as described above when executing the program.
In a fourth aspect, embodiments of the present invention provide a storage medium having computer-executable instructions stored thereon a computer program which, when executed by a processor, implements a method as described above.
According to the method and the device, the branch code segments are sent to the client, and the generated base changing request is verified on the branch code segments according to the client, so that the automatic base changing of the branch code segments is triggered, the submitted branch code segments can be timely processed in a rebase mode, a user does not need to manually operate a rebase button, and therefore efficiency and convenience of the rebase operation are improved.
Drawings
FIG. 1 is a flow chart of a version control automatic base changing method according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of an application scenario of an automatic version control provided in an embodiment of the present invention;
FIG. 3 is a flow chart of a version control automatic base changing method according to a second embodiment of the present invention;
fig. 4 is a schematic structural diagram of a version control automatic variable base device according to a third embodiment of the present invention;
fig. 5 is a schematic structural diagram of a computer device according to a fourth embodiment of the present invention.
Detailed Description
The invention is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting thereof. It should be further noted that, for convenience of description, only some, but not all of the structures related to the present invention are shown in the drawings.
Example 1
Fig. 1 is a flowchart of a version control automatic base changing method according to an embodiment of the present invention, where the embodiment is applicable to a version control situation where automatic base changing is performed, the method may be performed by a version control automatic base changing device, and the device may be implemented by software and/or hardware, and the method includes:
step S101, a branch code segment in the merging request input by the user is sent to the client.
In the case that, as shown in fig. 2, there is a merged merge into a repository when there are multiple merge requests submitted simultaneously in a project, and other merge requests all need to change the base, when no base, the branch submissions at three places A0, A1 and A2 will be merged into a backbone at B eventually, so the code structure will become very confusing, and the user's query on the history will be unfavorable. After the base-changing base is performed as shown in fig. 2, the code structure becomes clear, so that the user can conveniently inquire about the history record, and the base operation is automatically performed on the branch code segment mainly without the need of clicking the base key operation by the user. And the warehouse server in the embodiment is a Gitlab web, the client is a Jenkins job, and after receiving the merging request sent by the user, the warehouse server in the embodiment determines that the base change is needed in the merging process through interaction with the client, and automatically performs the rebase. In this embodiment, the rebase is mainly required to be involved in the version control of the software, so that the merge request in this embodiment is mainly applied to the version control.
Optionally, before sending the branch code segment in the merging request input by the user to the client, the method further includes: establishing communication connection with a client, and setting conditions for generating a variable base request by the client; and setting a triggering mode of generating a branch code segment acquisition request by the client.
Optionally, establishing a communication connection with the client includes: acquiring a designated address of a client; a communication connection is established with the client by accessing the specified address.
In this embodiment, url of the client may be preset, and when communication connection is established with the client, specifically, communication connection is established with the client by accessing url. For example, if url of the client is https:// www.sdgt.com, the repository server may establish a communication connection with the client by accessing https:// www.sdgt.com. Of course, this embodiment is merely illustrative, and in practical application, the client may be accessed by presetting an IP address of the client and accessing the preset IP address to establish a communication connection with the client, so the specific manner of connecting the client is not limited in this embodiment, and it is within the scope of the present application as long as the communication connection between the warehouse server and the client can be achieved.
Optionally, sending the branch code segment in the merging request input by the user to the client includes: testing the branch code segments in the merging request through a pipeline, and storing the branch code segments after the test is passed; sending monitoring information to a client through a monitoring module, and receiving a branch code segment acquisition request fed back by the client based on the monitoring information, wherein the monitoring information and the branch code segment acquisition request contain newly stored branch code segment identifiers; and based on the branch code segment acquisition request, all the branch code segments corresponding to the branch code segment identification are sent to the client.
Specifically, in this embodiment, the pipeline is run to test the branch code segment, and in the test, it is specifically detected whether the format of the branch code accords with the standard format preset by the repository server, if no sign is determined, the branch code segment cannot be saved in the repository server, and if the test is determined to pass, the branch code segment is saved. Since the monitoring module is included in the warehouse server, when it is determined that a new branch code segment is stored, monitoring information is sent to the client through the monitoring module based on a preset url, for example, the monitoring information in this embodiment may specifically be webhook information, and at this time, the sent webhook information only includes the identifier 001 of the newly stored branch code segment in the warehouse server, but does not include all the information of the branch code segment. Because the triggering mode of the client is preset as webhook information, after the client receives the webhook information, the client triggers the execution of the job, generates a branch code segment acquisition request, and the branch code segment acquisition request contains the identifier 001 of the newly stored branch code segment in the warehouse server, namely, requests the warehouse server to acquire all information of the 001 branch code segment. And after receiving the branch code segment acquisition request, the warehouse server transmits all the branch code segments corresponding to 001 to the client.
Step S102, a base change request sent by the client based on the branch code segment is received.
Specifically, after the client receives the branch code segment, the client analyzes the branch field through a pre-written script to obtain a merge request state field merge_request state and a test flow state field pipeline_state, and when the merge_request state is on, namely the merge_request state: open, and test flow status field pipeline_status is the initial default state, i.e., pipeline_status: and when False, generating a variable base request, namely a put rebase request, and sending the put rebase request to a warehouse server, wherein the corresponding warehouse server receives the variable base request sent by the client. It can be known that the client in this embodiment generates the base-change request only when the branch code segment is parsed and the acquired merge request status field and test flow status field are determined to be in the specified status.
It should be noted that, after the client acquires the two fields of the merge_request state and the pipeline_state, if the states of the two fields are not the two states required, the base change request is not generated at this time, that is, the condition of automatic base is not satisfied yet, and the corresponding warehouse server cannot acquire the base change request any more, so when the base change request is not received within the preset time range, the condition of automatic base is not satisfied currently, and therefore the warehouse server interrupts the communication connection with the client.
And step S103, performing automatic base changing operation on the branch code segments according to the base changing request to obtain positioning base changing points.
Specifically, when the repository server is acquiring the variant-base request, for example, the format of the variant-base request may be "/projects/project_id/merge_requests_id/rebase", indicating that the branch code segment in the merge request needs to be relocated on the backbone master. At this time, the warehouse server performs automatic base transformation on the branch code segments to obtain positioning base transformation points, where the positioning base transformation points may be specifically merging positions of the branch code segments on the master. Therefore, in the embodiment, when it is determined that the rebase operation is required for the merge request input by the user, the rebase can be automatically realized through information interaction between the warehouse server and the client without manual participation of the user, so that efficiency and accuracy of the rebase are remarkably improved.
Optionally, after performing the base change operation on the branch code segment according to the base change request to obtain the positioning base change point, the method further includes: generating a base changing operation completion message according to the positioning base changing point, and sending the base changing operation completion message to the client; and receiving a pipeline cancel instruction fed back by the client based on the base-changing operation completion message.
Optionally, after receiving the pipeline cancel instruction fed back by the client, the method further includes: acquiring the current state of the pipeline, wherein the current state comprises an operation state or an suspension state; when the current state of the pipeline is determined to be the running state, the pipeline is canceled.
It should be noted that, in this embodiment, after the repository server obtains the positioning base point through the rebase operation, a base-changing operation completion message is also generated, and the base-changing operation completion message is sent to the client, where the client knows that the repository server has rebase completed after obtaining the base-changing operation completion message, and then generates a pipeline cancel instruction, and sends the pipeline cancel instruction to the repository server. The warehouse server will fetch pipeline before executing the rebase operation according to the pipeline cancel instruction, and what state is currently, since the pipeline state generally includes running and aborting two states. Thus, when he determines that the current state of the pipeline is running, the pipeline in running may be canceled in order to avoid taking up additional resources, since the rebase operation has already been completed.
It should be noted that, after completing the rebase operation and the pipeline canceling operation, the warehouse server generates a prompt message for completing the corresponding operation, and sends the rebase operation completing prompt message or the pipeline canceling operation completing prompt message to the user side, so that the user can acquire the processing progress of the merging request in time.
According to the embodiment, the branch code segments are sent to the client, and the automatic base changing of the branch code segments is triggered according to the base changing request generated by the verification of the branch code segments by the client, so that the submitted branch code segments can be timely subjected to base changing processing, a user does not need to manually perform base button operation, and therefore the efficiency and convenience of base operation are improved.
Example two
Fig. 3 is a flowchart of a version control automatic base-changing method according to a second embodiment of the present application, where the embodiment is based on the above embodiment, and after performing a base-changing operation on a branch code segment according to a base-changing base request to obtain a location base-changing point, the method further includes: detecting a positioning variable base point, generating variable base failure prompt information when the positioning variable base point is abnormal, and feeding back the variable base failure prompt information to a user.
Step S201, a branch code segment in the merging request input by the user is sent to the client.
Optionally, before sending the branch code segment in the merging request input by the user to the client, the method further includes: establishing communication connection with a client, and setting conditions for generating a variable base request by the client; and setting a triggering mode of generating a branch code segment acquisition request by the client.
Optionally, establishing a communication connection with the client includes: acquiring a designated address of a client; a communication connection is established with the client by accessing the specified address.
Optionally, sending the branch code segment in the merging request input by the user to the client includes: testing the branch code segments in the merging request through a pipeline, and storing the branch code segments after the test is passed; sending monitoring information to a client through a monitoring module, and receiving a branch code segment acquisition request fed back by the client based on the monitoring information, wherein the monitoring information and the branch code segment acquisition request contain newly stored branch code segment identifiers; and based on the branch code segment acquisition request, all the branch code segments corresponding to the branch code segment identification are sent to the client.
Step S202, a base change request sent by a client based on a branch code segment is received.
And step S203, performing automatic base changing operation on the branch code segments according to the base changing request to acquire positioning base changing points.
Optionally, after performing the base change operation on the branch code segment according to the base change request to obtain the positioning base change point, the method further includes: generating a base changing operation completion message according to the positioning base changing point, and sending the base changing operation completion message to the client; and receiving a pipeline cancel instruction fed back by the client based on the base-changing operation completion message.
Optionally, after receiving the pipeline cancel instruction fed back by the client, the method further includes: acquiring the current state of the pipeline, wherein the current state comprises an operation state or an suspension state; when the current state of the pipeline is determined to be the running state, the pipeline is canceled.
And step S204, detecting a positioning variable base point, generating variable base failure prompt information when the positioning variable base point is abnormal, and feeding back the variable base failure prompt information to a user.
Specifically, after the positioning variable base point is obtained by automatically executing the rebase, detecting the positioning variable base point, for example, specifically detecting whether the original merging position of the positioning variable base point relative to the branch code segment is changed, and if not, indicating that the current rebase operation is invalid; if not, then the current rebase operation is indicated as valid.
And under the condition that the rebase operation is invalid, determining that the positioning base point is abnormal, and correspondingly generating base failure prompt information. The specific form of the base-change failure prompting information may be an image, a text or a sound, and is not limited in this embodiment, and is within the scope of protection of the present application as long as the user can be prompted.
According to the embodiment, the branch code segments are sent to the client, and the automatic base changing of the branch code segments is triggered according to the base changing request generated by the verification of the branch code segments by the client, so that the submitted branch code segments can be timely subjected to base changing processing, a user does not need to manually perform base button operation, and therefore the efficiency and convenience of base operation are improved.
Example III
Fig. 4 is a schematic structural diagram of a version control automatic base-changing device according to a third embodiment of the present invention, where the device may execute the version control automatic base-changing method according to the above embodiments. The device can be realized by adopting a software and/or hardware mode, as shown in fig. 4, the version control automatic variable base device comprises: a branch code segment sending module 310, a base request receiving module 320, and an automatic base module 330.
A branch code segment sending module 310, configured to send a branch code segment in the merge request input by the user to the client;
the base-change request receiving module 320 is configured to receive a base-change request sent by a client based on a branch code segment, where the base-change request is generated when the client determines that a merge request status field in the branch code segment is on and a test flow status field is an initial default status;
the automatic base changing module 330 is configured to perform an automatic base changing operation on the branch code segment according to the base changing request to obtain a positioning base changing point.
Optionally, the branch code segment sending module is used for testing the branch code segments in the merging request through a pipeline and storing the branch code segments after the test is passed;
sending monitoring information to a client through a monitoring module, and receiving a branch code segment acquisition request fed back by the client based on the monitoring information, wherein the monitoring information and the branch code segment acquisition request contain newly stored branch code segment identifiers;
and based on the branch code segment acquisition request, all the branch code segments corresponding to the branch code segment identification are sent to the client.
Optionally, the device further includes a pipeline cancellation instruction receiving module, configured to generate a base-changing operation completion message according to the positioning base-changing point, and send the base-changing operation completion message to the client;
and receiving a pipeline cancel instruction fed back by the client based on the base-changing operation completion message.
Optionally, the device further comprises a pipeline cancellation module, configured to obtain a current state of the pipeline, where the current state includes an running state or an abort state;
when the current state of the pipeline is determined to be the running state, the pipeline is canceled.
Optionally, the device further comprises a client setting module, which is used for establishing communication connection with the client and setting the condition of generating the base change request by the client;
and setting a triggering mode of generating a branch code segment acquisition request by the client.
Optionally, the device further comprises a communication connection module, configured to obtain a specified address of the client;
a communication connection is established with the client by accessing the specified address.
Optionally, the device further comprises a positioning variable base point detection module, which is used for detecting the positioning variable base point;
and generating a base change failure prompt message when the abnormal positioning base change point is detected and determined, and feeding back the base change failure prompt message to a user.
The version control automatic base changing device provided by the embodiment of the invention can execute the version control automatic base changing method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.
Example IV
Fig. 5 is a schematic structural diagram of a computer device according to a fourth embodiment of the present invention, and as shown in fig. 5, the computer device includes a processor 610, a memory 620, an input device 630 and an output device 640; the number of processors 610 in the computer device may be one or more, one processor 610 being illustrated in fig. 5; the processor 610, memory 620, input devices 630, and output devices 640 in the computer device may be connected by a bus or other means, for example in fig. 5 by a bus connection.
The memory 620 is a computer readable storage medium, and may be used to store a software program, a computer executable program, and modules, such as program instructions/modules corresponding to the automatic variant method of version control in the embodiments of the present invention. The processor 610 executes various functional applications of the computer device and data processing, i.e., implements the above-described automatic base-changing method of version control, by running software programs, instructions, and modules stored in the memory 620.
An automatic base changing method of version control, which is applied to a warehouse server, comprises the following steps:
the branch code segments in the merging request input by the user are sent to the client;
receiving a base changing request sent by a client based on a branch code segment, wherein the base changing request is generated when the client determines that a merging request state field in the branch code segment is opened and a testing flow state field is an initial default state;
and carrying out automatic base changing operation on the branch code segments according to the base changing request to obtain positioning base changing points.
The input device 630 may be used to receive entered numeric or character information and to generate key signal inputs related to user settings and function control of the computer device. The output device 640 may include a display device such as a display screen.
Example five
A fifth embodiment of the present invention also provides a storage medium containing computer-executable instructions, which when executed by a computer processor, are for performing an automatic version control method for a warehouse server, comprising:
the branch code segments in the merging request input by the user are sent to the client;
receiving a base changing request sent by a client based on a branch code segment, wherein the base changing request is generated when the client determines that a merging request state field in the branch code segment is opened and a testing flow state field is an initial default state;
and carrying out automatic base changing operation on the branch code segments according to the base changing request to obtain positioning base changing points.
Of course, the storage medium containing the computer executable instructions provided in the embodiments of the present invention is not limited to the above method operations, but may also perform the related operations in the version control automatic variant method provided in any embodiment of the present invention.
From the above description of embodiments, it will be clear to a person skilled in the art that the present invention may be implemented by means of software and necessary general purpose hardware, but of course also by means of hardware, although in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product, which may be stored in a computer readable storage medium, such as a floppy disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a FLASH Memory (FLASH), a hard disk or an optical disk of a computer, etc., including several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to execute the method of the embodiments of the present invention.
It should be noted that, in the embodiment of the automatic base-changing device for version control, each unit and module included are only divided according to the functional logic, but not limited to the above-mentioned division, so long as the corresponding functions can be implemented; in addition, the specific names of the functional units are also only for distinguishing from each other, and are not used to limit the protection scope of the present invention.
Note that the above is only a preferred embodiment of the present invention and the technical principle applied. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, while the invention has been described in connection with the above embodiments, the invention is not limited to the embodiments, but may be embodied in many other equivalent forms without departing from the spirit or scope of the invention, which is set forth in the following claims.
Claims (10)
1. An automatic base changing method for version control, which is applied to a warehouse server and comprises the following steps:
the method comprises the steps of sending branch code segments in a merging request input by a user to a client, wherein the merging request is applied to version control;
receiving a base change request sent by the client based on the branch code segment, wherein the base change request is generated when the client determines that a merging request state field in the branch code segment is opened and a testing flow state field is an initial default state;
and carrying out automatic base changing operation on the branch code segment according to the base changing request so as to obtain a positioning base changing point.
2. The method of claim 1, wherein the sending the branch code segment in the merge request entered by the user to the client comprises:
testing branch code segments in the merging request through a pipeline, and storing the branch code segments after the test is passed;
sending monitoring information to a client through a monitoring module, and receiving a branch code segment acquisition request fed back by the client based on the monitoring information, wherein the monitoring information and the branch code segment acquisition request contain newly-stored branch code segment identifiers;
and based on the branch code segment acquisition request, all the branch code segments corresponding to the branch code segment identification are sent to the client.
3. The method of claim 2, wherein after performing a base operation on the branch code segment according to the base request to obtain a location base point, further comprising:
generating a base changing operation completion message according to the positioning base changing point, and sending the base changing operation completion message to the client;
and receiving a pipeline cancel instruction fed back by the client based on the base-changing operation completion message.
4. The method of claim 3, further comprising, after receiving the pipeline cancel instruction fed back by the client:
acquiring the current state of the pipeline, wherein the current state comprises an operation state or an suspension state;
and canceling the pipeline when the current state of the pipeline is determined to be the running state.
5. The method of claim 2, wherein before sending the branch code segment in the merge request input by the user to the client, further comprising:
establishing communication connection with the client, and setting conditions for generating the base change request by the client;
and setting a triggering mode of the client for generating the branch code segment acquisition request.
6. The method of claim 5, wherein the establishing a communication connection with the client comprises:
acquiring a designated address of the client;
and establishing communication connection with the client by accessing the designated address.
7. The method of claim 1, wherein after performing a base operation on the branch code segment according to the base request to obtain a location base point, further comprising:
detecting the positioning variable base point;
and generating a base change failure prompt message when the positioning base change point is detected and determined to be abnormal, and feeding back the base change failure prompt message to a user.
8. A version-controlled automatic base-changing device, comprising:
the system comprises a branch code segment sending module, a client and a client, wherein the branch code segment sending module is used for sending a branch code segment in a merging request input by a user to the client, and the merging request is applied to version control;
the base-changing request receiving module is used for receiving a base-changing request sent by the client based on the branch code segment, wherein the base-changing request is generated when the client determines that a merging request state field in the branch code segment is opened and a testing flow state field is an initial default state;
and the automatic base changing module is used for carrying out automatic base changing operation on the branch code segments according to the base changing request so as to obtain a positioning base changing point.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of any of claims 1-7 when the program is executed by the processor.
10. A storage medium having stored thereon computer program of instructions, which when executed by a processor, performs the method of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310587406.3A CN116302082A (en) | 2023-05-24 | 2023-05-24 | Version control automatic base changing method, device, equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310587406.3A CN116302082A (en) | 2023-05-24 | 2023-05-24 | Version control automatic base changing method, device, equipment and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116302082A true CN116302082A (en) | 2023-06-23 |
Family
ID=86813534
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310587406.3A Pending CN116302082A (en) | 2023-05-24 | 2023-05-24 | Version control automatic base changing method, device, equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116302082A (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180060065A1 (en) * | 2016-09-01 | 2018-03-01 | Dropbox, Inc. | Advanced packaging techniques for improving work flows |
| CN113448862A (en) * | 2021-07-12 | 2021-09-28 | 上海哔哩哔哩科技有限公司 | Software version testing method and device and computer equipment |
| CN114528008A (en) * | 2022-01-28 | 2022-05-24 | 中银金融科技有限公司 | Code control method, device and medium based on distributed version control system |
-
2023
- 2023-05-24 CN CN202310587406.3A patent/CN116302082A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180060065A1 (en) * | 2016-09-01 | 2018-03-01 | Dropbox, Inc. | Advanced packaging techniques for improving work flows |
| CN113448862A (en) * | 2021-07-12 | 2021-09-28 | 上海哔哩哔哩科技有限公司 | Software version testing method and device and computer equipment |
| CN114528008A (en) * | 2022-01-28 | 2022-05-24 | 中银金融科技有限公司 | Code control method, device and medium based on distributed version control system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108196878B (en) | Method and device for generating application program installation package, electronic equipment and storage medium | |
| CN106572173B (en) | Configuration information updating method, device and system | |
| KR102317535B1 (en) | Methods and systems for implementing data tracking with software development kits | |
| EP3493057B1 (en) | Method and apparatus for awakening application by means of mobile browser | |
| CN110096424B (en) | Test processing method and device, electronic equipment and storage medium | |
| US11846972B2 (en) | Method and apparatus for generating software test reports | |
| CN109492181B (en) | Page jump method, device, computer equipment and storage medium | |
| CN113407383B (en) | Main and standby system switching method and device, server and main and standby system | |
| US9363107B2 (en) | Accessing and processing monitoring data resulting from customized monitoring of system activities | |
| CN110609755A (en) | Message processing method, device, equipment and medium for cross-block chain node | |
| CN111367531B (en) | Code processing method and device | |
| CN110968367A (en) | E-commerce commodity field configuration method, device, server and storage medium | |
| CN111294288A (en) | Traffic identification method and device, application program interface gateway and storage medium | |
| CN111639086B (en) | Data reconciliation method, device, equipment and storage medium | |
| CN106933932B (en) | Data processing method and device and application server | |
| CN111506339A (en) | Method and device for processing change information of Software Development Kit (SDK) | |
| JP2004102379A (en) | Patch application management program, method, and system | |
| CN116755719A (en) | Data processing method, device and data processing system of application component | |
| CN116302082A (en) | Version control automatic base changing method, device, equipment and medium | |
| CN107908629B (en) | Information query method, terminal and equipment | |
| CN112256820B (en) | Document positioning method and device | |
| CN110908763A (en) | Acceptance method, device, equipment and storage medium | |
| CN112261072A (en) | Service calling method, device, equipment and storage medium | |
| CN116521222A (en) | Automatic merging method, device, equipment and medium for version control | |
| CN113760631A (en) | Page loading duration determination method, device, 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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20230623 |
|
| RJ01 | Rejection of invention patent application after publication |