Code reading and writing management method, device and system

Abstract

The present invention provides a code reading and writing management method, device and system, which can be used in the field of information security technology. The method comprises: obtaining user information according to an access request transmitted by a user; querying whether there is corresponding work order information according to the user information, and if so, performing permission verification on the access request according to the work order information; if the verification passes, performing corresponding reading and writing operations on the code repository according to the access request. The present invention can realize automatic permission verification of user access requests without manual intervention, thereby avoiding permission verification problems caused by manual operation errors.

Description

Technical Field

[0001] The present invention relates to the field of code management security technology, in particular to the field of information security technology, and more particularly to a code reading and writing management method, device and system. Background Art

[0002] Source code or source program is one of the most important and core assets of software products, and is also the main object of software configuration management engineering. The scale of modern software products is getting larger and larger, and a software product often involves a large number of people. Code security control has always been an important issue that enterprises need to face, and code permission management of personnel is the top priority.

[0003] In modern mainstream distributed code management platforms, codes are usually stored and managed in the form of code repositories. Developers need to open code repository permissions through authorization before they can obtain the code and perform related operations. Relying on the functions natively provided by various code management platforms to manage code access rights requires offline communication and manual operations between personnel, which is complex, cumbersome, and time-consuming. Some companies use secondary development to call relevant service interfaces provided by various code management platforms to implement online approval processes and automated authorization functions, but the legality and timeliness of permission opening cannot get rid of dependence on people. Summary of the invention

[0004] One object of the present invention is to provide a code reading and writing management method to realize automatic permission verification of user access requests without manual intervention, thereby avoiding permission verification problems caused by manual operation errors. Another object of the present invention is to provide a code reading and writing management device. Another object of the present invention is to provide a code reading and writing management system. Another object of the present invention is to provide a computer device. Another object of the present invention is to provide a readable medium.

[0005] In order to achieve the above objectives, the present invention discloses a code reading and writing management method, comprising:

[0006] Obtaining user information according to an access request transmitted by the user;

[0007] Query whether there is corresponding work order information according to the user information, and if so, perform permission verification on the access request according to the work order information;

[0008] If the verification passes, the corresponding read and write operations are performed on the code repository according to the access request.

[0009] Preferably, the method further comprises the step of obtaining all work order information in advance:

[0010] Access the work order management system and obtain all work order information in the work order management system.

[0011] Preferably, the work order information includes user name, number, code repository name, status and permission management rules.

[0012] Preferably, obtaining user information according to the access request transmitted by the user specifically includes:

[0013] According to the access request transmitted by the user, the user name, the name of the code repository to be accessed, the branch name, the read or write flag, and the program change list are obtained.

[0014] Preferably, the querying whether corresponding work order information exists according to the user information specifically includes:

[0015] Determine a user name according to the user information;

[0016] The user name is compared with the user names of all work order information respectively to determine whether there is work order information corresponding to the same user name as the user name in the user information.

[0017] Preferably, the method further comprises, before performing permission verification on the access request according to the work order information:

[0018] Determine whether the status of the work order information is normal according to the status of the work order information.

[0019] Preferably, the performing permission verification on the access request according to the work order information specifically includes:

[0020] Determine whether the branch name of the user information matches the number of the work order information;

[0021] If they match, determine whether there is a branch corresponding to the branch name in the code repository based on the number;

[0022] If so, perform permission verification on the access request according to the permission control rule; if not, perform permission verification on the access request according to the permission control rule after creating a branch in the code repository.

[0023] The present invention also discloses a code reading and writing management device, comprising:

[0024] An information receiving module, used to obtain user information according to an access request transmitted by the user;

[0025] An authority verification module is used to query whether there is corresponding work order information according to the user information, and if so, to perform an authority verification on the access request according to the work order information;

[0026] The read-write control module is used to perform corresponding read and write operations on the code repository according to the access request if the verification passes.

[0027] The present invention also discloses a code reading and writing management system, including a user terminal, a code reading and writing management device and a code warehouse;

[0028] The code reading and writing management device is used to receive an access request transmitted by a user terminal to obtain user information, and query whether there is corresponding work order information based on the user information. If so, the access request is subjected to permission verification based on the work order information. If the verification passes, corresponding reading and writing operations are performed on the code repository based on the access request.

[0029] The present invention also discloses a computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor.

[0030] When the processor executes the program, the method described above is implemented.

[0031] The present invention also discloses a computer readable medium having a computer program stored thereon.

[0032] When the program is executed by a processor, the method described above is implemented.

[0033] The present invention obtains user information by analyzing the access request transmitted by the user, and determines whether corresponding work order information exists based on the user information. When work order information exists, the access request is checked for permissions based on the work order information. If the check passes, the code repository is subjected to corresponding read and write operations based on the access request. The present invention realizes automated permission verification of code repository access rights by reading relevant work order information in the work order. Thus, during the user access process, permission verification will be automatically performed based on the user's access request, and no manual intervention is required for all steps of the entire process, truly realizing automated processing and minimizing problems caused by manual operation errors. In addition, the present invention does not need to access a third-party system for permission verification, and there is basically no delay, and the permission verification result can take effect in real time. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0035] Figure 1 A structural diagram showing a specific embodiment of the code reading and writing management system of the present invention;

[0036] Figure 2 A flowchart showing a specific embodiment of the code reading and writing management method of the present invention;

[0037] Figure 3 A flowchart showing a work order information query of a specific embodiment of the code reading and writing management method of the present invention is shown;

[0038] Figure 4 A flowchart showing permission verification of a specific embodiment of the code reading and writing management method of the present invention is shown;

[0039] Figure 5 A structural diagram showing a specific embodiment of the code reading and writing management device of the present invention;

[0040] Figure 6 A schematic diagram showing the structure of a computer device suitable for implementing an embodiment of the present invention is shown. DETAILED DESCRIPTION

[0041] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0042] It should be noted that the code reading and writing management method, device and system disclosed in the present application can be used in the field of information security technology, and can also be used in any field outside the field of information security technology. The application field of the code reading and writing management method, device and system disclosed in the present application is not limited.

[0043] In modern mainstream distributed code management platforms, such as Gerrit, GitLab, and GitHub, codes are usually stored and managed in the form of code repositories. Developers need to open code repository permissions through authorization before they can obtain code and perform related operations. Relying on the functions natively provided by various code management platforms to manage code access rights requires offline communication and manual operations between personnel, which is complex, cumbersome, and time-consuming. Some companies use secondary development to call relevant service interfaces provided by various code management platforms to implement online approval processes and automated authorization functions, but the legality and timeliness of permission opening cannot get rid of dependence on people. In addition, after the code management platform opens permissions for users, relevant personnel can access and modify any code in the code repository at will, which cannot achieve more fine-grained management requirements, and there is no supporting permission exit mechanism, which is easy to cause safety production problems.

[0044] Figure 1 Schematic diagram of the structure of the code reading and writing management system provided by the embodiment of the present invention. Figure 1 As shown, the code reading and writing management system provided by the embodiment of the present invention includes a user terminal 1, a code reading and writing management device 2 and a code warehouse 3.

[0045] The user may send an access request to the code reading and writing management device 2 through the user terminal 1 to request to read and write the code in the code repository 3 .

[0046] The code reading and writing management device 2 can obtain user information based on the access request transmitted by the user; query whether there is corresponding work order information based on the user information, and if so, perform permission verification on the access request based on the work order information; if the verification passes, perform corresponding reading and writing operations on the code repository 3 according to the access request.

[0047] It is understandable that the user terminal may include a smart phone, a tablet electronic device, a network set-top box, a portable computer, a desktop computer, a personal digital assistant (PDA), a vehicle-mounted device, a smart wearable device, etc. Among them, the smart wearable device may include smart glasses, a smart watch, a smart bracelet, etc.

[0048] The above-mentioned user terminal may have a communication module (i.e., a communication unit), which can be connected to the code reading and writing management device for communication, and realize data transmission with the code reading and writing management device. The code reading and writing management device and the user terminal can communicate using any suitable network protocol, including network protocols that have not been developed on the filing date of this application. The network protocol may include, for example, TCP / IP protocol, UDP / IP protocol, HTTP protocol, HTTPS protocol, etc. Of course, the network protocol may also include, for example, RPC protocol (Remote Procedure Call Protocol) and REST protocol (Representational State Transfer) used on top of the above-mentioned protocols.

[0049] The following takes the code reading and writing management device as an example to illustrate the implementation process of the code reading and writing management method provided by the embodiment of the present invention. It is understandable that the execution subject of the code reading and writing management method provided by the embodiment of the present invention includes but is not limited to the code reading and writing management device.

[0050] According to one aspect of the present invention, this embodiment discloses a code reading and writing management method. Figure 2 As shown, in this embodiment, the method includes:

[0051] S100: Obtaining user information according to an access request transmitted by the user;

[0052] S200: Query whether there is corresponding work order information according to the user information, and if so, perform permission verification on the access request according to the work order information;

[0053] S300: If the verification passes, perform corresponding read and write operations on the code repository according to the access request.

[0054] The present invention obtains user information by analyzing the access request transmitted by the user, and determines whether corresponding work order information exists based on the user information. When work order information exists, the access request is checked for permissions based on the work order information. If the check passes, the code repository is subjected to corresponding read and write operations based on the access request. The present invention realizes automated permission verification of code repository access rights by reading relevant work order information in the work order. Thus, during the user access process, permission verification will be automatically performed based on the user's access request, and no manual intervention is required for all steps of the entire process, truly realizing automated processing and minimizing problems caused by manual operation errors. In addition, the present invention does not need to access a third-party system for permission verification, and there is basically no delay, and the permission verification result can take effect in real time.

[0055] In a preferred embodiment, the method further comprises a step S000 of pre-acquiring all work order information:

[0056] S010: Access the work order management system 4 and obtain all work order information in the work order management system.

[0057] Specifically, it is well known to those skilled in the art that the work order system is used to record, process and track the completion of a job. In the work order management system 4, work order information can be formed in various forms such as user input and tracking of user operations, and the work order information contains all relevant information of a job or task. Preferably, the work order management system 4 can be accessed in advance and all work order information in the work order management system can be read out and stored locally in the read-write management device, so that when the user's access request is received, the access request can be directly compared with the local work order information to verify the work order information. Of course, in actual applications, the work order system can also be accessed in real time to obtain the work order information corresponding to the access request transmitted by the user, and the present invention is not limited to this.

[0058] In a preferred embodiment, the work order information in the work order management system 4 includes information such as user name, number, code repository name, status, and permission control rules. Therefore, when the access request transmitted by the user contains key information such as the user name, the user access request can be associated with the work order information obtained from the work order management system 4 through the user name and other information, and then the user's access request is checked for permissions through the associated work order information, so that the user's access request is automatically checked for access permissions based on the work order information. All steps in the entire permission verification process do not require manual intervention, truly realizing automated processing and minimizing problems caused by manual operation errors.

[0059] In a preferred embodiment, the step S100 of obtaining user information according to the access request transmitted by the user may specifically include:

[0060] S110: Obtain the user name, the name of the code repository to be accessed, the branch name, the read or write flag, and the program change list according to the access request transmitted by the user.

[0061] Specifically, if a user name is set in the user's access request, the user name can be used to determine whether there is work order information corresponding to the user name in all work order information, that is, to determine whether there is work order information with the same user name as the user name in the access request transmitted by the user. Furthermore, after obtaining the work order information corresponding to the user information through username association, it can be determined through the work order information whether the user corresponding to the username in the user information has the authority to access the code repository to be accessed in the access request. If the user information permission check passes, it can be determined that the program change list in the access request transmitted by the user can be updated to the code repository. Furthermore, if the user information includes a branch name, the branch name in the user information can be checked for permissions at the same time to achieve refined management of branch-based user code read and write permissions.

[0062] In a preferred embodiment, Figure 3 As shown, the step S200 of querying whether there is corresponding work order information according to the user information specifically includes:

[0063] S211: Determine a user name according to the user information.

[0064] S212: Compare the user name with the user names of all work order information respectively to determine whether there is work order information corresponding to the same user name as the user name in the user information.

[0065] Specifically, in this preferred implementation, the user information includes information such as the user name, and the user name is obtained by analyzing the access request transmitted by the user. The work order information also includes the user name, and then it is queried from all the work order information whether there is work order information including the user name in the user information. If so, it is considered that the work order information is the work order information related to the access request transmitted by the user, which can be used to verify the user's authority for the access request and determine whether the user's access request is legal. If it is legal, the user is allowed to operate the code of the code repository, and if it is illegal, the access is denied.

[0066] In a preferred embodiment, the method further comprises, before performing permission verification on the access request according to the work order information:

[0067] S020: Determine whether the status of the work order information is normal according to the status of the work order information.

[0068] Specifically, in this preferred implementation, it is necessary to determine whether the status of the work order information is normal based on the relevant information in the work order information. If the status of the work order information is abnormal, it means that there may be an abnormality in the information in the work order information, which may affect the permission verification of the user's access request. Therefore, when it is determined that the status of the work order information is normal, the user's access request is verified based on the work order information, and when it is determined that the status of the work order information is abnormal, the work order information is ignored, and the work order information with an abnormal status is not used to verify the user's access request, so as to prevent the permission verification of the user's access request from being affected.

[0069] In a preferred embodiment, Figure 4 As shown, the S200 may specifically include:

[0070] S221: Determine whether the branch name of the user information matches the number of the work order information.

[0071] S222: If there is a match, determine whether there is a branch corresponding to the branch name in the code repository according to the number.

[0072] S223: If so, perform permission verification on the access request according to the permission control rule; if not, perform permission verification on the access request according to the permission control rule after creating a branch in the code repository.

[0073] Specifically, in this preferred implementation, it is necessary to determine whether the branch name of the user information matches the number of the work order information, and further determine whether the target branch corresponding to the number exists in the code repository. Among them, the work order contains two basic information: user identification, requirement identification and defect identification. Among them, the user identification can be information indicating the user identity such as a user name or a user number. The requirement identification may include numbers such as a project number, a task number, a requirement item number, a requirement item number and a requirement sub-item number. The defect identification is generally the defect problem number of the feature, which can be determined according to the project management method and granularity. The code branch in the code repository generally creates a corresponding feature branch based on the requirement or defect, and the branch is directly named with the requirement identification and defect identification. Therefore, it can be determined whether there is a number in the work order information that is the same as the branch name of the user information to determine whether the branch name of the user information matches the number of the work order information. If there is a branch corresponding to the branch name in the code repository, the user information can be verified according to the permission control rules pre-set in the work order information. Among them, the permission management rules may include rules such as the target, file, and branch where the code in the code repository accessible to the user is located. The access request is verified through the management rules to determine whether the code to be accessed by the user's access request conforms to the code in the code repository accessible to the user in the permission management rules, thereby achieving refined management of user access rights.

[0074] According to another aspect of the present invention, this embodiment also discloses a code reading and writing management device. Figure 5 As shown, the device includes an information receiving module 11, an authority checking module 12 and a read-write control module 13.

[0075] The information receiving module 11 is used to obtain user information according to an access request transmitted by the user.

[0076] The permission verification module 12 is used to query whether there is corresponding work order information according to the user information, and if so, perform permission verification on the access request according to the work order information.

[0077] The read / write control module 13 is used to perform corresponding read / write operations on the code repository according to the access request if the verification passes.

[0078] The present invention obtains user information by analyzing the access request transmitted by the user, and determines whether corresponding work order information exists based on the user information. When work order information exists, the access request is checked for permissions based on the work order information. If the check passes, the code repository is subjected to corresponding read and write operations based on the access request. The present invention realizes automated permission verification of code repository access rights by reading relevant work order information in the work order. Thus, during the user access process, permission verification will be automatically performed based on the user's access request, and no manual intervention is required for all steps of the entire process, truly realizing automated processing and minimizing problems caused by manual operation errors. In addition, the present invention does not need to access a third-party system for permission verification, and there is basically no delay, and the permission verification result can take effect in real time.

[0079] In a preferred embodiment, the information receiving module 11 is further used to pre-access the work order management system and obtain all work order information in the work order management system.

[0080] Specifically, it is well known to those skilled in the art that the work order system is used to record, process and track the completion of a job. In the work order management system 4, work order information can be formed in various forms such as user input and tracking of user operations, and the work order information contains all relevant information of a job or task. Preferably, the work order management system 4 can be accessed in advance and all work order information in the work order management system can be read out and stored locally in the read-write management device, so that when the user's access request is received, the access request can be directly compared with the local work order information to verify the work order information. Of course, in actual applications, the work order system can also be accessed in real time to obtain the work order information corresponding to the access request transmitted by the user, and the present invention is not limited to this.

[0081] In a preferred embodiment, the work order information in the work order management system 4 includes information such as user name, number, code repository name, status, and permission control rules. Therefore, when the access request transmitted by the user contains key information such as the user name, the user access request can be associated with the work order information obtained from the work order management system 4 through the user name and other information, and then the user's access request is checked for permissions through the associated work order information, so that the user's access request is automatically checked for access permissions based on the work order information. All steps in the entire permission verification process do not require manual intervention, truly realizing automated processing and minimizing problems caused by manual operation errors.

[0082] In a preferred embodiment, the information receiving module 11 can be specifically used to obtain the user name, the name of the accessed code repository, the branch name, the read or write flag, and the program change list according to the access request transmitted by the user.

[0083] Specifically, if a user name is set in the user's access request, the user name can be used to determine whether there is work order information corresponding to the user name in all work order information, that is, to determine whether there is work order information with the same user name as the user name in the access request transmitted by the user. Furthermore, after obtaining the work order information corresponding to the user information through username association, it can be determined through the work order information whether the user corresponding to the username in the user information has the authority to access the code repository to be accessed in the access request. If the user information permission check passes, it can be determined that the program change list in the access request transmitted by the user can be updated to the code repository. Furthermore, if the user information includes a branch name, the branch name in the user information can be checked for permissions at the same time to achieve refined management of branch-based user code read and write permissions.

[0084] In a preferred embodiment, the permission verification module 12 is specifically used to determine the user name according to the user information, and compare the user name with the user names of all work order information to determine whether there is work order information corresponding to the same user name as the user name in the user information.

[0085] Specifically, in this preferred implementation, the user information includes information such as the user name, and the user name is obtained by analyzing the access request transmitted by the user. The work order information also includes the user name, and then it is queried from all the work order information whether there is work order information including the user name in the user information. If so, it is considered that the work order information is the work order information related to the access request transmitted by the user, which can be used to verify the user's authority for the access request and determine whether the user's access request is legal. If it is legal, the user is allowed to operate the code of the code repository, and if it is illegal, the access is denied.

[0086] In a preferred embodiment, the permission verification module 12 is further configured to perform permission verification on the access request according to the work order information, and before that, determine whether the status of the work order information is normal according to the status of the work order information.

[0087] Specifically, in this preferred implementation, it is necessary to determine whether the status of the work order information is normal based on the relevant information in the work order information. If the status of the work order information is abnormal, it means that there may be an abnormality in the information in the work order information, which may affect the permission verification of the user's access request. Therefore, when it is determined that the status of the work order information is normal, the user's access request is verified based on the work order information, and when it is determined that the status of the work order information is abnormal, the work order information is ignored, and the work order information with an abnormal status is not used to verify the user's access request, so as to prevent the permission verification of the user's access request from being affected.

[0088] In a preferred embodiment, the permission verification module 12 is specifically used to determine whether the branch name of the user information matches the number of the work order information. If they match, determine whether there is a branch corresponding to the branch name in the code repository based on the number. If so, perform permission verification on the access request based on the permission control rules. If not, perform permission verification on the access request based on the permission control rules after creating a branch in the code repository.

[0089] Specifically, in this preferred implementation, it is necessary to determine whether the branch name of the user information matches the number of the work order information, and further determine whether the target branch corresponding to the number exists in the code repository. Among them, the work order contains two basic information: user identification, requirement identification and defect identification. Among them, the user identification can be information indicating the user identity such as a user name or a user number. The requirement identification may include numbers such as a project number, a task number, a requirement item number, a requirement item number and a requirement sub-item number. The defect identification is generally the defect problem number of the feature, which can be determined according to the project management method and granularity. The code branch in the code repository generally creates a corresponding feature branch based on the requirement or defect, and the branch is directly named with the requirement identification and defect identification. Therefore, it can be determined whether there is a number in the work order information that is the same as the branch name of the user information to determine whether the branch name of the user information matches the number of the work order information. If there is a branch corresponding to the branch name in the code repository, the user information can be verified according to the permission control rules pre-set in the work order information. Among them, the permission management rules may include rules such as the target, file, and branch where the code in the code repository accessible to the user is located. The access request is verified through the management rules to determine whether the code to be accessed by the user's access request conforms to the code in the code repository accessible to the user in the permission management rules, thereby achieving refined management of user access rights.

[0090] Since the principle of solving the problem by the device is similar to that of the above method, the implementation of the device can refer to the implementation of the method and will not be repeated here.

[0091] According to another aspect of the present invention, this embodiment discloses a code reading and writing management system. The code reading and writing management system includes a user terminal, a code reading and writing management device and a code warehouse.

[0092] The code reading and writing management device is used to receive an access request transmitted by a user terminal to obtain user information, and query whether there is corresponding work order information based on the user information. If so, the access request is subjected to permission verification based on the work order information. If the verification passes, corresponding reading and writing operations are performed on the code repository based on the access request.

[0093] Since the principle of solving the problem by this system is similar to that of the above method, the implementation of this system can refer to the implementation of the method and will not be repeated here.

[0094] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer device, and specifically, the computer device may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0095] In a typical example, a computer device specifically includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the method described above is implemented when the processor executes the program.

[0096] Reference below Figure 6 , which shows a schematic diagram of the structure of a computer device 600 suitable for implementing an embodiment of the present application.

[0097] like Figure 6 As shown, the computer device 600 includes a central processing unit (CPU) 601, which can perform various appropriate operations and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage part 608 to a random access memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the system 600 are also stored. The CPU 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0098] The following components are connected to the I / O interface 605: an input section 606 including a keyboard, a mouse, etc.; an output section 607 including a cathode ray tube (CRT), a liquid crystal feedback device (LCD), etc., and a speaker, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a LAN card, a modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to the I / O interface 605 as needed. A removable medium 611, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 610 as needed, so that a computer program read therefrom is installed as needed as the storage section 608.

[0099] In particular, according to an embodiment of the present invention, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present invention includes a computer program product, which includes a computer program tangibly contained on a machine-readable medium, and the computer program includes program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication part 609, and / or installed from the removable medium 611.

[0100] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0101] For the convenience of description, the above device is described in various units according to their functions. Of course, when implementing the present application, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0102] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0103] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0104] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0105] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0106] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0107] The present application may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0108] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0109] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A code reading and writing management method, characterized in that: include: Obtaining user information according to an access request transmitted by the user, the user information including a user name, a code repository name to be accessed, a branch name, a read or write flag, and a program change list; Query whether there is corresponding work order information according to the user information, and if so, perform permission verification on the access request according to the work order information; The work order information includes user name, number, code repository name, status and permission management rules, requirement identifier and defect identifier; The performing permission verification on the access request according to the work order information specifically includes: Determine whether the branch name of the user information matches the number of the work order information; If they match, determine whether there is a branch corresponding to the branch name in the code repository based on the number; If yes, perform permission check on the access request according to the permission control rule; if no, perform permission check on the access request according to the permission control rule after creating a branch in the code repository; branches in the code repository are named according to requirement identifiers and defect identifiers; The permission control rules include the targets, files, and branches of the code in the code repository accessible to the user; The performing permission verification on the access request according to the permission control rule comprises: determining whether the code to be accessed by the user access request complies with the code in the code repository accessible to the user in the permission control rule; If the verification passes, the corresponding read and write operations are performed on the code repository according to the access request.

2. The code reading and writing management method according to claim 1, characterized in that: Further steps are included to obtain all work order information in advance: Access the work order management system and obtain all work order information in the work order management system.

3. The code reading and writing management method according to claim 2, characterized in that: The querying whether there is corresponding work order information according to the user information specifically includes: Determine a user name according to the user information; The user name is compared with the user names of all work order information respectively to determine whether there is work order information corresponding to the same user name as the user name in the user information.

4. The code reading and writing management method according to claim 1, characterized in that: The method further includes, before performing permission verification on the access request according to the work order information: Determine whether the status of the work order information is normal according to the status of the work order information.

5. A code reading and writing management device, characterized in that: The device is used to implement the method according to any one of claims 1 to 4, and the device comprises: An information receiving module, used to obtain user information according to an access request transmitted by the user; An authority verification module is used to query whether there is corresponding work order information according to the user information, and if so, to perform an authority verification on the access request according to the work order information; The read-write control module is used to perform corresponding read and write operations on the code repository according to the access request if the verification passes.

6. A code reading and writing management system, characterized in that: The system is used to implement the method according to any one of claims 1 to 4, and the system includes a user terminal, a code reading and writing management device, and a code warehouse; The code reading and writing management device is used to receive an access request transmitted by a user terminal to obtain user information, and query whether there is corresponding work order information based on the user information. If so, the access request is subjected to permission verification based on the work order information. If the verification passes, corresponding reading and writing operations are performed on the code repository based on the access request.

7. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the method according to any one of claims 1 to 4 is implemented.

8. A computer readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 4 is implemented.

Images