Nothing Special   »   [go: up one dir, main page]

CN111522580A - Method and device for establishing code branch and computer equipment - Google Patents

Method and device for establishing code branch and computer equipment Download PDF

Info

Publication number
CN111522580A
CN111522580A CN202010320875.5A CN202010320875A CN111522580A CN 111522580 A CN111522580 A CN 111522580A CN 202010320875 A CN202010320875 A CN 202010320875A CN 111522580 A CN111522580 A CN 111522580A
Authority
CN
China
Prior art keywords
code
branch
project
git
online
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
Application number
CN202010320875.5A
Other languages
Chinese (zh)
Inventor
张蕾
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Zhejiang Dasou Vehicle Software Technology Co Ltd
Original Assignee
Zhejiang Dasou Vehicle Software Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Zhejiang Dasou Vehicle Software Technology Co Ltd filed Critical Zhejiang Dasou Vehicle Software Technology Co Ltd
Priority to CN202010320875.5A priority Critical patent/CN111522580A/en
Publication of CN111522580A publication Critical patent/CN111522580A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management
    • G06F8/73Program documentation

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Library & Information Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The application relates to a code branch establishing method, a code branch establishing device and computer equipment, wherein the code branch establishing method comprises the following steps: responding to a code branch establishment request of a first authority user, and displaying a display box for collecting project keywords; receiving project keywords collected through a display box; the remote request to git builds a code branch named by the item key. By the method and the device, the problem that the code branch cannot be accurately deleted to occupy the storage space due to the fact that the naming of the code branch by a developer is not standard in the related technology is solved, the storage space occupied by the code branch is reduced, and the efficiency of pulling the code branch is improved.

Description

Method and device for establishing code branch and computer equipment
Technical Field
The present application relates to the field of internet, and in particular, to a method and an apparatus for establishing a code branch, and a computer device.
Background
In the internet industry, after an engineer who develops a service end develops a program, the engineer needs to deploy a program code or a compiling result to a server to run, so as to indirectly provide services for a user, and the process is called code release.
In the related technology, the process of releasing the code is that after the code developed by a developer is tested in a test environment by a tester, the developer marks the code and informs an operation and maintenance worker, the operation and maintenance worker finds a group leader for confirmation, then finds a corresponding online machine, manually executes an online script, and deploys the code to the corresponding online machine. In the process, the online operation needs to be released after developers, group leaders, operation and maintenance personnel and the like confirm layer by layer, and the online operation of the operation and maintenance personnel also needs to be released after a machine path is confirmed when the operation and maintenance personnel are online.
In the above scheme, the developer names the development items locally in git at will, and under the condition of not naming strictly according to the specification, when deleting the corresponding code branch at the git remote end, a large number of code branches with random names exist at the git remote end. When the code branches corresponding to the online codes need to be deleted after the codes are online, the code branches cannot be deleted at will because whether the code branches are online or not and the functions of the code branches are unclear, so that the code branches not only occupy space, but also can be repeatedly acquired by other developers when other projects are developed, and the development efficiency of the developers is influenced.
At present, no effective solution is provided for the problem that in the related art, due to the fact that naming of a code branch by a developer is not standard, the code branch cannot be accurately deleted and occupies a storage space.
Disclosure of Invention
The embodiment of the application provides a method and a device for establishing a code branch and computer equipment, so as to at least solve the problem that in the related art, because a developer does not specify the name of the code branch, the code branch cannot be accurately deleted and occupies a storage space.
In a first aspect, an embodiment of the present application provides a method for establishing a code branch, where the method includes:
responding to a code branch establishment request of a first authority user, and displaying a display box for collecting project keywords;
receiving project keywords collected through the display box;
and requesting to establish a code branch named by the item key words from the git remote end.
In some of these embodiments, the item keywords include at least one of: project name, project task type, project time.
In some of these embodiments, requesting from the git remote to establish a code branch named by the project key comprises:
carrying out validity check on the project key words;
under the condition that the validity of the project key words is successfully checked, requesting to establish a code branch named by the project key words from a git remote end; otherwise, displaying the display box of the failure of the collection of the project keywords.
In some of these embodiments, the method further comprises:
receiving a first code submission request of a second authorized user;
judging whether a second code submitting request in the process exists or not;
rejecting the first code submission request if it is determined that there is the second code submission request being processed; otherwise, sending the first code submission request to the git remotes to cause the git remotes to merge the code branches into a code main branch.
In some of these embodiments, determining whether there is a second code submission request being processed includes:
displaying a display frame for confirming the first code submission request;
and under the condition that the confirmation message of the first authorized user to the first code submission request is received, judging whether a second code submission request in the process exists or not.
In some of these embodiments, after sending the first code submission request to the git remote, the method further comprises:
displaying a display frame for collecting the code label number;
responding to the code label input by the first authority user, sending a labeling request to the git far end, and finishing the processing of the first code submitting request.
In some of these embodiments, after sending the first code submission request to the git remote, the method further comprises:
acquiring an online configuration table, wherein the online configuration table comprises an online catalog configuration table and an online script configuration table;
acquiring a script for code online according to the online script configuration table, and configuring parameters of the script according to the online catalog configuration table;
and executing the script to obtain the code main branch after the combination of the upper lines.
In some embodiments, after the merged code principal branch, the method further comprises:
and responding to the item key words input by the first authority user, sending a code branch deleting instruction to the git far end so as to delete the code branches named by the item key words on the git far end.
In a second aspect, the present application provides an apparatus for establishing a code branch, the apparatus comprising:
the first response module is used for responding to a code branch establishment request of a first authority user and displaying a display box for collecting project keywords;
the first receiving module is used for receiving the project keywords collected through the display box;
and the first establishing module is used for requesting the git remote end to establish the code branch named by the project keyword.
In a third aspect, the present application provides 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 for establishing a code branch according to the first aspect when executing the computer program.
Compared with the related art, the code branch establishing method, the code branch establishing device and the computer equipment provided by the embodiment of the application display the display box for collecting the project keywords by responding to the code branch establishing request of the first authorized user; receiving project keywords collected through a display box; the method for establishing the code branch named by the project keyword by requesting the git remote end solves the problem that the code branch cannot be accurately deleted and occupies the storage space due to the non-standard naming of the code branch by developers in the related technology, reduces the storage space occupied by the code branch and improves the efficiency of pulling the code branch.
The details of one or more embodiments of the application are set forth in the accompanying drawings and the description below to provide a more thorough understanding of the application.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
FIG. 1 is a flow diagram of a method of establishing a code branch according to an embodiment of the present application;
FIG. 2 is a block diagram of a computer device according to an embodiment of the present application;
FIG. 3 is an interaction flow diagram of a computer device according to an embodiment of the application;
FIG. 4 is a block diagram of an apparatus for establishing a code branch according to an embodiment of the present application;
fig. 5 is a hardware configuration diagram of a computer device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be described and illustrated below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments provided in the present application without any inventive step are within the scope of protection of the present application.
It is obvious that the drawings in the following description are only examples or embodiments of the present application, and that it is also possible for a person skilled in the art to apply the present application to other similar contexts on the basis of these drawings without inventive effort. Moreover, it should be appreciated that in the development of any such actual implementation, as in any engineering or design project, numerous implementation-specific decisions must be made to achieve the developers' specific goals, such as compliance with system-related and business-related constraints, which may vary from one implementation to another.
Reference in the specification to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the specification. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those of ordinary skill in the art will explicitly and implicitly appreciate that the embodiments described herein may be combined with other embodiments without conflict.
Unless defined otherwise, technical or scientific terms referred to herein shall have the ordinary meaning as understood by those of ordinary skill in the art to which this application belongs. Reference to "a," "an," "the," and similar words throughout this application are not to be construed as limiting in number, and may refer to the singular or the plural. The present application is directed to the use of the terms "including," "comprising," "having," and any variations thereof, which are intended to cover non-exclusive inclusions; for example, a process, method, system, article, or apparatus that comprises a list of steps or modules (elements) is not limited to the listed steps or elements, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. Reference to "connected," "coupled," and the like in this application is not intended to be limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. The term "plurality" as referred to herein means two or more. "and/or" describes an association relationship of associated objects, meaning that three relationships may exist, for example, "A and/or B" may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. Reference herein to the terms "first," "second," "third," and the like, are merely to distinguish similar objects and do not denote a particular ordering for the objects.
The method embodiment provided by the embodiment can be executed in computer equipment. The method for establishing a code branch according to the embodiment of the present invention will be described and explained below by taking a computer device as an example.
The embodiment provides a method for establishing a code branch. Fig. 1 is a flowchart of a method for establishing a code branch according to an embodiment of the present application, and as shown in fig. 1, the flowchart includes the following steps:
in step S101, the computer device displays a display box for collecting a keyword of an item in response to a code branch establishment request of a first authorized user.
In step S102, the computer device receives the item keywords collected through the display box.
Step S103, the computer equipment requests to establish a code branch named by the project key words from the git remote end.
git is an open source distributed version control system that can handle very small to very large project version management efficiently and at high speed. The biggest difference between a distributed version control system over a centralized version control system is that developers can submit to the local, each copying a complete git repository on the local machine by cloning (git clone).
In this embodiment, when receiving a task of code development, a first authorized user sends a code branch establishment request to a computer device, the computer device instructs a display box of the computer device to obtain a project keyword according to the received code branch establishment request of the first authorized user, and then requests to establish a code branch named by the project keyword from a git remote end according to the project keyword, so as to prevent developers from naming development projects at will in the related art, and in this embodiment, the computer device requests to establish a code branch named by the project keyword from the git remote end according to the project keyword, and also solve the problem that the code branch cannot be deleted accurately and occupies a storage space of the computer device due to non-normative naming of the code branch by the developers in the related art, and meanwhile, the computer device can also delete the code branch related to the project keyword accurately according to the project keyword, the problem of excessive code branches is avoided, the storage space occupied by the code branches is reduced, and the efficiency of pulling the code branches is improved.
In some embodiments, for more precise naming of the developed item, the item keywords in this embodiment include, but are not limited to: project name, project task type, project time. By the method, the problem that developers name development projects randomly in the related technology can be further solved, and the beneficial effect of further standardizing the naming of the development projects is achieved.
In some embodiments, to improve the reliability of the item keywords collected by the display box, the computer device may perform a validity check on the item keywords; under the condition that the validity of the project key words is successfully checked, establishing a code branch named by the project key words from a git remote end request; otherwise, displaying a display box of failed collection of the project keywords.
In this embodiment, the computer device may generally encrypt the authentication information using a symmetric encryption algorithm, where the symmetric encryption algorithm includes, but is not limited to: advanced encryption standard AES and data encryption standard DES in cryptography. In this embodiment, the computer device may increase the cracking cost of a malicious attacker by obfuscating the code, for example, using an array of commonly used global variable names and using a 16-ary index for access, so that the attacker cannot read and understand the code in a short time. By the method, the safety of information transmission is improved, and the difficulty of an attacker in cracking the man-machine verification is increased.
In some embodiments, the computer device may further receive a first code submission request from a second authorized user; judging whether a second code submitting request in the process exists or not; rejecting the first code submission request if it is determined that there is a second code submission request being processed; otherwise, a first code commit request is sent to the git remotes to cause the git remotes to merge the code branch into the code main branch.
In this embodiment, the computer device sends the first code submission request to the git remote end when judging that the second code submission request in the process does not exist, so that the git remote end merges the code branch into the code main branch, the merging of the code branch and the code main branch is realized, the problem of channel congestion in the merging of the code branch due to the fact that other code branches are merging when the code branch and the code main branch are merged can be prevented, meanwhile, the problems of version conflict and repeated online of the code branch can be avoided through the method, and the merging efficiency of the code branch is improved.
In some embodiments, the manner in which the computer device determines whether there is a second code submission request being processed may be, but is not limited to: displaying a display frame for confirming the first code submission request; in the case where an acknowledgement message of the first code submission request by the first authorized user is received, it is determined whether there is a second code submission request being processed.
In this embodiment, by determining whether there is a second code submission request being processed in a manner of receiving a confirmation message of a first authorized user for the first code submission request, it is possible to prevent a problem of a decrease in merging efficiency caused by merging of other code branches when the code branches are merged, and a method for determining whether there is a second code submission request being processed is provided.
In some of these embodiments, the computer device may also display a display box for collecting the code tag number after sending the first code submission request to the git remote; responding to the code label input by the first authority user, sending a labeling request to the git far end, and finishing the processing of the first code submitting request.
In this embodiment, the computer device tags the version of the corresponding code by sending a tagging request to the git remote end and ending the processing of the first code submission request, so as to facilitate the version rollback of the code branch.
In some embodiments, after sending the first code submission request to the git remote end, the computer device may further obtain an online configuration table, where the online configuration table includes an online catalog configuration table and an online script configuration table; acquiring a script for code online according to an online script configuration table, and configuring parameters of the script according to an online catalog configuration table; and executing the script to obtain the code main branch after the combination of the upper lines.
In this embodiment, the computer device obtains the online configuration table, and implements the online mode for the combined code main branch according to the online configuration table, so that the problem that operation and maintenance personnel are required to determine the online script when the code is online in the related art can be solved, the automatic online of the code main branch is implemented, and the online efficiency of the code main branch is improved.
It should be noted that the online catalog configuration table includes, but is not limited to: item name, online server IP, distribution directory. The online script configuration table includes but is not limited to: project name, script path, script library. The parameter in this embodiment may be, but is not limited to, an online server address, a distribution directory, and the like.
In some of these embodiments, after the inline merged main code branch, the computer device may also send a code branch delete instruction to the git distal end to delete the code branch named by the item key on the git distal end in response to the item key entered by the first authorized user.
In the embodiment, the computer device solves the problem that the code branches of the git far end are locally acquired by the git when the code branches of the git far end are too many in the related technology and occupy the git local resources by deleting the code branches named by the project keywords on the git far end, and the development efficiency of developers is improved.
The present application will now be described and illustrated with reference to the preferred embodiments and the accompanying drawings.
As shown in fig. 2, fig. 2 is a block diagram of a computer device according to an embodiment of the present application, which may include, but is not limited to, an online catalog configuration table, an online script configuration table, and an automatic online program, where fig. 2 further includes a client (which may be git local) and an online server.
As shown in fig. 3, fig. 3 is an interaction flow diagram of a computer device according to an embodiment of the present application, where the interaction flow includes:
step 301, when developing a new development project, the computer device obtains a project keyword input by the first terminal, where the project keyword includes but is not limited to a project name, a project task type, a version update, a project bug fix, and a project time, then the computer device generates a new branch at the git far end according to the project keyword (i.e. copying a master main branch to the git far end for new creation, deletion, and merging code branches), and unifies the naming of the code branches according to the project keyword, where the naming format of the code branches may be but is not limited to: project name-project task type-project time.
And step 302, the second terminal locally pulls a new code branch from the git remote end through the git, develops according to the code branch, and submits a request message for merging the code branch to the computer equipment after the code branch is developed.
Step 303, after receiving the local request message for merging code branches, the computer device sends a confirmation message for merging code branches to the computer device, and after sending the confirmation message for merging code branches to the first terminal, determines whether a code branch merging instruction sent by the first terminal is received, and if not, the computer device determines that the processing of the code branches is finished, the code branches are in a non-merging state, or determines that the code branches are in a merging failure state. If so, the computer device sends a code branch merging message to the git local, and the git local merges the code branch onto the code main branch (namely, the master main branch) according to the code branch merging message.
Step 304, after the git local code branches are merged successfully, the computer device judges whether a labeling instruction sent by the first terminal is received or not within a preset time, if not, the computer device judges that the processing of the code branches is finished, if so, the computer device sends a tag number confirmation message to the first terminal, and after the tag number is confirmed by the first terminal, the computer device sends labeling indication information to the computer device, and the computer device indicates the git remote end to label the merged code branches according to the labeling indication information.
Step 305, after the code branches are merged, if the computer device receives a code branch online message sent by the first terminal, the computer device enters a code branch online link, that is, the computer device can obtain a pre-configured online configuration table according to the code branch online message, pull some online parameters such as an online server address, an online directory, an online script path and the like corresponding to the code branch in the online configuration table, and then send the online configuration table to the online server.
Step 306, the online server executes the online script according to the online configuration table, wherein the online parameter in the online configuration table may be, but is not limited to, an address of the online server and an online directory.
Step 307, after the merged code branches are online, the first terminal may delete the code branch related to the project keyword from the computer device according to the project keyword, and may also delete the code branch related to the project keyword according to the project keyword, and only keep the code main branch (i.e., master main branch).
It should be noted that, in the above steps, the first terminal is a terminal to which the first authorized user logs in, and the second terminal is an account terminal to which the second authorized user logs in.
In summary, the beneficial effects achieved by the method for establishing a code branch in the embodiment of the present application at least include the following aspects:
(1) the computer equipment has the advantages that according to project keywords, code branches on the lines are clearly managed, and the project is subjected to a normative naming mode according to preset rules such as project names, project task types and project time, so that the problem that developers name the project at will is solved. And after the unified standard naming, even if some code branches are not deleted in time at the git far end, the item to which the code branch belongs can be clear according to the naming of the code branch, whether the code branch is on line or not is confirmed according to the on line record, and the branch is deleted if the code branch is on line, so that the problem that the git far end code branches in the related technology are too many is solved.
(2) The computer equipment checks whether the online configuration is accurate or not through the online server IP, the release directory and the script path which are configured in advance when each project/task is online. Compared with the prior art, the method and the device can be automatically completed without the cooperation of operation and maintenance personnel when the operation and maintenance personnel are online, and the operation and maintenance personnel only need to maintain the online script and other pre-configurations. Therefore, the first-right user can automatically perform online scripts under the condition of confirming the code branches, so that the repeated work of operation and maintenance personnel is saved, and the accuracy and the safety of an online path are ensured.
The present embodiment further provides a device for establishing a code branch, where the device is used to implement the foregoing embodiments and preferred embodiments, and the description of the device that has been already described is omitted. As used hereinafter, the terms "module," "unit," "subunit," and the like may implement a combination of software and/or hardware for a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.
Fig. 4 is a block diagram of a device for establishing a code branch according to an embodiment of the present application, and as shown in fig. 4, the device includes:
a first response module 410, configured to display a display box for collecting the project keywords in response to a code branch establishment request of a first authorized user;
a first receiving module 420 coupled to the first responding module 410 for receiving the item keywords collected through the display box;
a first establishing module 430, coupled to the first receiving module 420, for requesting from the git the establishment of a code branch named by the item keyword.
In some of these embodiments, the item keywords comprise at least one of: project name, project task type, project time.
In some embodiments, the apparatus for establishing a branch of code further comprises: the verification module is used for verifying the legality of the project key words; the second establishing module is used for requesting to establish a code branch named by the project key words from the git far end under the condition that the validity check of the project key words is successful; otherwise, displaying a display box of failed collection of the project keywords.
In some embodiments, the apparatus for establishing a branch of code further comprises: the second receiving module is used for receiving a first code submission request of a second authority user; and the first judging module is used for judging whether the second code submitting request in the process exists or not, refusing the first code submitting request under the condition that the second code submitting request in the process exists, and otherwise, sending the first code submitting request to the git remote end so that the git remote end merges the code branch into the code main branch.
In some embodiments, the apparatus for establishing a branch of code further comprises: the first display module is used for displaying a display frame for confirming the submission request of the first code; and the second judgment module is used for judging whether the second code submission request in the process exists or not under the condition of receiving the confirmation message of the first authorized user to the first code submission request.
In some embodiments, the apparatus for establishing a branch of code further comprises: the second display module is used for displaying a display frame for collecting the code label number; and the second response module is used for responding to the code label input by the first authority user, sending a labeling request to the git far end and finishing the processing of the first code submitting request.
In some embodiments, the apparatus for establishing a branch of code further comprises: the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring an online configuration table, and the online configuration table comprises an online catalog configuration table and an online script configuration table; the second acquisition module is used for acquiring scripts for code online according to the online script configuration table and configuring parameters of the scripts according to the online catalog configuration table; and the execution module is used for executing the script and the code main branch after the combination of the upper lines.
In some embodiments, the apparatus for establishing a branch of code further comprises: and the third response module is used for responding to the item keywords input by the first authority user and sending a code branch deleting instruction to the git far end so as to delete the code branches named by the item keywords on the git far end.
The above modules may be functional modules or program modules, and may be implemented by software or hardware. For a module implemented by hardware, the modules may be located in the same processor; or the modules can be respectively positioned in different processors in any combination.
In addition, the method for establishing the code branch in the embodiment of the present application described in conjunction with fig. 1 may be implemented by a computer device. Fig. 5 is a hardware structure diagram of a computer device according to an embodiment of the present application.
The computer device may comprise a processor 51 and a memory 52 in which computer program instructions are stored.
Specifically, the processor 51 may include a Central Processing Unit (CPU), or A Specific Integrated Circuit (ASIC), or may be configured to implement one or more Integrated circuits of the embodiments of the present Application.
Memory 52 may include, among other things, mass storage for data or instructions. By way of example, and not limitation, memory 52 may include a Hard Disk Drive (Hard Disk Drive, abbreviated HDD), a floppy Disk Drive, a Solid State Drive (SSD), flash memory, an optical Disk, a magneto-optical Disk, tape, or a Universal Serial Bus (USB) Drive or a combination of two or more of these. Memory 52 may include removable or non-removable (or fixed) media, where appropriate. The memory 52 may be internal or external to the data processing apparatus, where appropriate. In a particular embodiment, the memory 52 is a Non-Volatile (Non-Volatile) memory. In particular embodiments, Memory 52 includes Read-Only Memory (ROM) and Random Access Memory (RAM). The ROM may be mask-programmed ROM, Programmable ROM (PROM), Erasable PROM (EPROM), Electrically Erasable PROM (EEPROM), Electrically rewritable ROM (earrom) or FLASH Memory (FLASH), or a combination of two or more of these, where appropriate. The RAM may be a Static Random-Access Memory (SRAM) or a Dynamic Random-Access Memory (DRAM), where the DRAM may be a Fast Page Mode Dynamic Random-Access Memory (FPMDRAM), an Extended Data Output Dynamic Random Access Memory (EDODRAM), a Synchronous Dynamic Random Access Memory (SDRAM), and the like.
The memory 52 may be used to store or cache various data files that need to be processed and/or used for communication, as well as possible computer program instructions executed by the processor 51.
The processor 51 implements any one of the code branch establishment methods in the above embodiments by reading and executing computer program instructions stored in the memory 52.
In some of these embodiments, the computer device may also include a communication interface 53 and a bus 50. As shown in fig. 5, the processor 51, the memory 52, and the communication interface 53 are connected via the bus 50 to complete mutual communication.
The communication interface 53 is used for implementing communication between modules, apparatuses, units and/or devices in the embodiments of the present application. The communication interface 53 may also enable communication with other components such as: the data communication is carried out among external equipment, image/data acquisition equipment, a database, external storage, an image/data processing workstation and the like.
Bus 50 comprises hardware, software, or both coupling the components of the computer device to each other. Bus 50 includes, but is not limited to, at least one of the following: data Bus (Data Bus), Address Bus (Address Bus), Control Bus (Control Bus), Expansion Bus (Expansion Bus), and Local Bus (Local Bus). By way of example, and not limitation, Bus 50 may include an Accelerated Graphics Port (AGP) or other Graphics Bus, an Enhanced Industry Standard Architecture (EISA) Bus, a Front-Side Bus (FSB), a HyperTransport (HT) interconnect, an ISA (ISA) Bus, an InfiniBand (InfiniBand) interconnect, a Low Pin Count (LPC) Bus, a memory Bus, a Micro Channel Architecture (MCA) Bus, a Peripheral Component Interconnect (PCI) Bus, a PCI-Express (PCI-X) Bus, a Serial Advanced Technology Attachment (SATA) Bus, a Video electronics standards Association Local Bus (VLB) Bus, or other suitable Bus or a combination of two or more of these. Bus 50 may include one or more buses, where appropriate. Although specific buses are described and shown in the embodiments of the application, any suitable buses or interconnects are contemplated by the application.
The computer device may execute the method for establishing a code branch in the embodiment of the present application based on the acquired project keyword, thereby implementing the method for establishing a code branch described with reference to fig. 1.
In addition, in combination with the method for establishing a code branch in the above embodiments, the embodiments of the present application may provide a computer-readable storage medium to implement. The computer readable storage medium having stored thereon computer program instructions; the computer program instructions, when executed by a processor, implement the method of establishing a code branch of any of the above embodiments.
The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims (10)

1. A method for establishing a code branch, the method comprising:
responding to a code branch establishment request of a first authority user, and displaying a display box for collecting project keywords;
receiving project keywords collected through the display box;
and requesting to establish a code branch named by the item key words from the git remote end.
2. The method of claim 1, wherein the item key comprises at least one of: project name, project task type, project time.
3. The method for establishing a code branch according to claim 1, wherein requesting a git to establish a code branch named by the item keyword comprises:
carrying out validity check on the project key words;
under the condition that the validity of the project key words is successfully checked, requesting to establish a code branch named by the project key words from a git remote end; otherwise, displaying the display box of the failure of the collection of the project keywords.
4. The method of claim 1, further comprising:
receiving a first code submission request of a second authorized user;
judging whether a second code submitting request in the process exists or not;
rejecting the first code submission request if it is determined that there is the second code submission request being processed; otherwise, sending the first code submission request to the git remotes to cause the git remotes to merge the code branches into a code main branch.
5. The method of claim 4, wherein determining whether there is a second code submission request being processed comprises:
displaying a display frame for confirming the first code submission request;
and under the condition that a confirmation message of the first authorized user for the first code submission request is received, judging whether the second code submission request in the process exists or not.
6. The method of establishing a code branch according to claim 5, wherein after sending the first code commit request to the git remote, the method further comprises:
displaying a display frame for collecting the code label number;
responding to the code label input by the first authority user, sending a labeling request to the git far end, and finishing the processing of the first code submitting request.
7. The method of establishing a code branch according to claim 5, wherein after sending the first code commit request to the git remote, the method further comprises:
acquiring an online configuration table, wherein the online configuration table comprises an online catalog configuration table and an online script configuration table;
acquiring a script for code online according to the online script configuration table, and configuring parameters of the script according to the online catalog configuration table;
and executing the script to obtain the code main branch after the combination of the upper lines.
8. The method of claim 7, wherein after the merged code main branch, the method further comprises:
and responding to the item key words input by the first authority user, sending a code branch deleting instruction to the git far end so as to delete the code branches named by the item key words on the git far end.
9. An apparatus for establishing a code branch, the apparatus comprising:
the first response module is used for responding to a code branch establishment request of a first authority user and displaying a display box for collecting project keywords;
the first receiving module is used for receiving the project keywords collected through the display box;
and the first establishing module is used for requesting the git remote end to establish the code branch named by the project keyword.
10. A computer device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method of establishing a code branch according to any one of claims 1 to 8 when executing the computer program.
CN202010320875.5A 2020-04-22 2020-04-22 Method and device for establishing code branch and computer equipment Pending CN111522580A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010320875.5A CN111522580A (en) 2020-04-22 2020-04-22 Method and device for establishing code branch and computer equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010320875.5A CN111522580A (en) 2020-04-22 2020-04-22 Method and device for establishing code branch and computer equipment

Publications (1)

Publication Number Publication Date
CN111522580A true CN111522580A (en) 2020-08-11

Family

ID=71903046

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010320875.5A Pending CN111522580A (en) 2020-04-22 2020-04-22 Method and device for establishing code branch and computer equipment

Country Status (1)

Country Link
CN (1) CN111522580A (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112162742A (en) * 2020-08-21 2021-01-01 长沙市到家悠享网络科技有限公司 Code deployment method, device and equipment
CN113204369A (en) * 2021-04-28 2021-08-03 安徽智侒信信息技术有限公司 Intelligent monitoring tool for GitLab code warehouse activity
CN113535576A (en) * 2021-07-26 2021-10-22 未鲲(上海)科技服务有限公司 Method, apparatus and storage medium for checking code
CN115033276A (en) * 2022-06-22 2022-09-09 深圳依时货拉拉科技有限公司 Project release method, device, equipment and storage medium

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140101153A1 (en) * 2012-10-05 2014-04-10 Proplus Electronics Co., Ltd. Naming Methodologies for a Hierarchical System
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
CN109976801A (en) * 2019-04-24 2019-07-05 网宿科技股份有限公司 A kind of code development method, system and computer readable storage medium
CN110633101A (en) * 2019-09-25 2019-12-31 杭州港盛软件科技有限公司 Program code management method, device and equipment and readable storage medium

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140101153A1 (en) * 2012-10-05 2014-04-10 Proplus Electronics Co., Ltd. Naming Methodologies for a Hierarchical System
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
CN109976801A (en) * 2019-04-24 2019-07-05 网宿科技股份有限公司 A kind of code development method, system and computer readable storage medium
CN110633101A (en) * 2019-09-25 2019-12-31 杭州港盛软件科技有限公司 Program code management method, device and equipment and readable storage medium

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
李宁: "独门架构 Java Web开发应用详解", 31 October 2010, 北京:中国铁道出版社, pages: 394 - 397 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112162742A (en) * 2020-08-21 2021-01-01 长沙市到家悠享网络科技有限公司 Code deployment method, device and equipment
CN113204369A (en) * 2021-04-28 2021-08-03 安徽智侒信信息技术有限公司 Intelligent monitoring tool for GitLab code warehouse activity
CN113535576A (en) * 2021-07-26 2021-10-22 未鲲(上海)科技服务有限公司 Method, apparatus and storage medium for checking code
CN115033276A (en) * 2022-06-22 2022-09-09 深圳依时货拉拉科技有限公司 Project release method, device, equipment and storage medium

Similar Documents

Publication Publication Date Title
CN111522580A (en) Method and device for establishing code branch and computer equipment
CN108549580B (en) Method for automatically deploying Kubernets slave nodes and terminal equipment
US10491453B2 (en) Correlating computing network events
US9294464B2 (en) Automatic authorization of users and configuration of software development environment
CN110960856B (en) Game data management system, management method and storage medium
CN106105154B (en) Method, device and system for uploading data
CN112905437B (en) Method, device and storage medium for testing cases
CN112995357B (en) Domain name management method, device, medium and electronic equipment based on cloud hosting service
CN114546837A (en) Interface test method, device, equipment and storage medium
CN107786520B (en) Method and system for controlling resource access
CN112306973A (en) Picture importing system and method
CN112073374B (en) Information interception method, device and equipment
JP2019519849A (en) Method and device for preventing attacks on servers
CN112181599B (en) Model training method, device and storage medium
CN114268490A (en) Equipment authentication method, Internet of things system, server and storage medium
KR101745919B1 (en) User authentication method and system using software-based HSM without password exposure
CN110232570B (en) Information supervision method and device
CN113158146A (en) Script management method, script management platform, computing device and medium
CN112597118B (en) Shared file adding method and device
CN113592645A (en) Data verification method and device
CN114020313A (en) Application updating method and related equipment
CN117435829B (en) Catalog preheating method and device
CN116011000B (en) Access method, device and computing equipment
CN116032889B (en) IP address allocation method and device
US20240305621A1 (en) System, method, and information processing apparatus

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
RJ01 Rejection of invention patent application after publication
RJ01 Rejection of invention patent application after publication

Application publication date: 20200811