CN112181480A - Authority management method and device of version management system - Google Patents
Authority management method and device of version management system Download PDFInfo
- Publication number
- CN112181480A CN112181480A CN202011051736.3A CN202011051736A CN112181480A CN 112181480 A CN112181480 A CN 112181480A CN 202011051736 A CN202011051736 A CN 202011051736A CN 112181480 A CN112181480 A CN 112181480A
- Authority
- CN
- China
- Prior art keywords
- file
- authority
- account identifier
- management system
- version management
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims description 162
- 238000000034 method Methods 0.000 claims abstract description 33
- 238000010586 diagram Methods 0.000 description 5
- 238000004590 computer program Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000001960 triggered effect Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 238000007792 addition Methods 0.000 description 1
- 238000012550 audit Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/901—Indexing; Data structures therefor; Storage structures
- G06F16/9017—Indexing; Data structures therefor; Storage structures using directory or table look-up
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
- G06F21/105—Arrangements for software license management or administration, e.g. for managing licenses at corporate level
Abstract
The disclosure relates to a method and a device for managing authority of a version management system, and particularly discloses: acquiring an authority file, wherein the authority file is positioned under a target directory, and at least one first account identifier with the control authority of the target directory is recorded in the authority file; reading at least one first account identifier in the permission file; and updating the account identification with the control authority of the target directory into the read at least one first account identification in the authority configuration file of the version management system, so that the user of the at least one first account identification has the control authority of the target directory.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a method and an apparatus for managing permissions of a version management system.
Background
At present, an svn (version) of an open source code is generally adopted in a version management system, and efficient management of a branch management system is adopted, so that a plurality of developers can conveniently develop the same project together, and shared resources and centralized management are realized.
The SVN provides a relatively perfect authority management capability, and can control read-write authorities of different users under different directories. Under the default function provided by the SVN, the strategy of authority management is that a system administrator modifies a global authority configuration file through the SVN, and modifies the authority of related personnel in the authority configuration file.
By adopting the existing mode, because the authority for modifying the authority configuration file is only owned by the SVN administrator, each time the authority is changed, the personnel needing to be changed contact the SVN administrator to operate, if more developers use the same code warehouse, the operations of adding, deleting and modifying the authority of the personnel can be frequent, the workload of the SVN administrator is increased, the bottleneck is easy to form, and the authority management efficiency of the version management system is reduced.
Disclosure of Invention
The present disclosure provides a method and an apparatus for managing rights of a version management system, so as to at least solve the problem of low rights management efficiency of the version management system in the related art. The technical scheme of the disclosure is as follows:
according to a first aspect of the embodiments of the present disclosure, there is provided a rights management method of a version management system, including: acquiring a permission file, wherein the permission file is positioned under a target directory, and at least one first account identifier with the control permission of the target directory is recorded in the permission file; reading the at least one first account identifier in the permission file; and updating the account identifier with the control authority of the target directory into the read at least one first account identifier in an authority configuration file of the version management system, so that the user of the at least one first account identifier has the control authority of the target directory.
Optionally, the method further comprises: receiving a first operation command for indicating control operation on the authority file, wherein the first operation command carries a second account identifier; and searching the second account identifier in the permission configuration file, and if the second account identifier is searched and the second account identifier is recorded in the permission configuration file to have the control permission of the target directory, executing the control operation corresponding to the first operation command on the permission file.
Optionally, the control operation corresponding to the first operation command includes: and adding or deleting at least one first account identifier in the authority file.
Optionally, before acquiring the rights file, the method further includes: receiving an authority updating command; before reading the first account identification in the rights file, the method further comprises: and judging whether the information recorded in the current authority file is the same as the information recorded in the authority file when the authority updating command is received last time, and if so, executing the step of reading the at least one first account identifier in the authority file.
Optionally, in the authority configuration file of the version management system, updating the account identifier having the control authority of the target directory to the read at least one first account identifier includes: generating a new authority configuration file, and recording the account identifier with the control authority of the target directory in the new authority configuration file as the read at least one first account identifier; and replacing the current authority configuration file of the version management system with the new authority configuration file.
Optionally, after the updating of the account identifier having the control authority of the target directory to the read at least one first account identifier, the method further includes: receiving a second operation command from a first client, wherein the first client logs in the version management system by using the first account identifier, the second operation command indicates that a control operation is performed on a target file, and the target file comprises: files under the target directory and/or files under subdirectories under the target directory; and executing the control operation corresponding to the second operation command on the target file.
Optionally, before acquiring the rights file, the method further includes: receiving a third operation command from a second client, wherein the second client logs in the version management system by using an administrator identification of the version management system, the third operation command indicates that the authority file is created under the target directory, and the target directory comprises: a root target of the version management system; creating the authority file and recording the at least one first account identifier in the authority file, wherein the at least one first account identifier comprises: the administrator identification.
According to a second aspect of the embodiments of the present disclosure, there is provided a rights management apparatus of a version management system, including: the acquisition unit is configured to execute acquisition of a permission file, wherein the permission file is located under a target directory, and at least one first account identifier with the control permission of the target directory is recorded in the permission file; a reading unit configured to perform reading of the at least one first account identifier in the rights file; and the updating unit is configured to update the account identifier with the control authority of the target directory into the read at least one first account identifier in the authority configuration file of the version management system, so that the user of the at least one first account identifier has the control authority of the target directory.
Optionally, the apparatus further comprises: a first receiving unit, configured to execute a first operation command that indicates a control operation on the authority file, where the first operation command carries a second account identifier; and the first control unit is configured to search the second account identifier in the permission configuration file, and if the second account identifier is found and the second account identifier is recorded in the permission configuration file to have the control permission of the target directory, perform a control operation corresponding to the first operation command on the permission file.
Optionally, the method further comprises: a second receiving unit configured to perform receiving a rights update command before acquiring the rights file; and the judging unit is configured to execute the judgment of whether the information recorded in the current authority file is the same as the information recorded in the authority file when the authority updating command is received last time, and if the information recorded in the current authority file is different from the information recorded in the authority file when the authority updating command is received last time, the reading unit is triggered to read the at least one first account identifier in the authority file.
Optionally, the updating unit updates the account identifier having the control authority of the target directory to the read at least one first account identifier by: generating a new authority configuration file, and recording the account identifier with the control authority of the target directory in the new authority configuration file as the read at least one first account identifier; and replacing the current authority configuration file of the version management system with the new authority configuration file.
Optionally, the apparatus further comprises: a third receiving unit configured to perform receiving a second operation command from a first client, wherein the first client logs in the version management system using the first account identifier, the second operation command indicates a control operation on a target file, and the target file includes: files under the target directory and/or files under subdirectories under the target directory; a second control unit configured to perform a control operation corresponding to the second operation command on the target file.
Optionally, the apparatus further comprises: a fourth receiving unit configured to perform receiving a third operation command from a second client, wherein the second client logs in to the version management system using an administrator identification of the version management system, the third operation command indicates that the authority file is created under the target directory, and the target directory includes: a root target of the version management system; a third control unit configured to perform creating the rights file and recording the at least one first account identifier in the rights file, wherein the at least one first account identifier includes: the administrator identification.
According to a third aspect of the embodiments of the present disclosure, there is provided a rights management apparatus of a version management system, including: a processor; a memory for storing the processor-executable instructions; wherein the processor is configured to execute the instructions to implement the rights management method of the version management system as described above.
According to a fourth aspect of the embodiments of the present disclosure, there is provided a storage medium, when instructions in the storage medium are executed by a processor in a rights management device of a version management system, so that the rights management device of the version management system can perform the rights management method of the version management system as described above.
According to a fifth aspect of embodiments of the present disclosure, there is provided a computer program product comprising at least one non-transitory computer-readable medium storing instructions translatable by at least one processor for implementing the aforementioned method of rights management of a version management system.
The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects: the method comprises the steps of adding a permission file under a target directory, recording at least one first account identifier with the control permission of the target directory in the permission file, reading the at least one first account identifier from the permission file, and then updating the account identifier with the control permission of the target directory into the read at least one first account identifier in a permission configuration file of the version management system, so that a user of the at least one first account identifier has the control permission of the target directory. Therefore, the authority of the target directory can be maintained by the user who already has the authority of the target directory, so that the pressure of a system administrator is shared, and the authority management efficiency of the version management system is improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the disclosure and are not to be construed as limiting the disclosure.
FIG. 1 is a flow diagram illustrating a method of rights management for a version management system in accordance with an exemplary embodiment;
FIG. 2 is a block diagram illustrating a rights management apparatus of a version management system in accordance with an exemplary embodiment;
fig. 3 is a block diagram illustrating a rights management apparatus of a version management system according to yet another exemplary embodiment.
Detailed Description
In order to make the technical solutions of the present disclosure better understood by those of ordinary skill in the art, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the disclosure described herein are capable of operation in sequences other than those illustrated or otherwise described herein. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
As described above, for a project jointly developed by dozens of users (developers) and even hundreds of users, a version management system may encounter a scenario where a rights management policy is frequently changed, and if a manager of the version management system is centralized to modify a rights configuration file for rights management, the efficiency of rights management may be low.
Fig. 1 is a flowchart illustrating a rights management method 100 of a version management system according to an exemplary embodiment, and as shown in fig. 1, the rights management method 100 of the version management system may be used in a server, including the following steps.
In step S102, a permission file is obtained, where the permission file is located under a target directory, and at least one first account identifier having a control permission of the target directory is recorded in the permission file.
In a possible implementation manner, a permission file may be created under each directory under the version management system, and the account identifier having the control permission corresponding to the target directory is recorded by the permission file. In S102, the rights file under each directory is acquired.
In one example, the rights file may include a plurality of rights files, i.e., the rights file is included under each of a plurality of target directories of the version management system. For example, a first right file is included in the first directory, and user identifications D and E are recorded in the first right file; a second authority file is included in the second directory, and a user identifier F is recorded in the second authority file; a third authority file is included in the third directory, and user identifications G and H are recorded in the third authority file; and the like. Therefore, the number of the rights files that can be acquired in step S102 is plural, for example, all the rights files such as the first rights file, the second rights file, and the third rights file are acquired.
Optionally, the step may use a traversal mode to traverse all directories of the version management system to obtain each permission file.
In step S104, the at least one first account identifier in the rights file is read.
In one possible implementation, step S102 may be performed after receiving the permission update command. Alternatively, the authority update command may be a commit command of the version management system, i.e., a command indicating an operation to perform a code update of the version management system.
Alternatively, the commit command may be triggered by the client user. In one example, the client is configured with a commit button, and a commit command can be issued to the server by clicking the commit button after locally updating the code of the version management system, wherein the commit command is used for triggering the server to execute the operation of updating the code.
The SVN is provided with a post-submission (post-commit) script, which is a hook function, and may update data in a version library of the version management system according to a code of a client user locally updating the version management system, and synchronize the data in the version library to a website directory, so that, in one example, after receiving a commit command, the content of the post-commit script, that is, an operation of performing a code update, may be executed.
In a possible implementation manner, when the permission update command is received, whether the permission file is updated or not may be determined, if yes, step S104 is executed, and if not, the next permission update command may be waited to save the process. Therefore, in this possible implementation, before step S104, the method may further include: and judging whether the information recorded in the current authority file is the same as the information recorded in the authority file when the authority updating command is received last time, and if so, executing the step S104.
For example, after receiving the commit command, a code update is performed, and during the code update, whether the authority file is updated or not can be detected. That is, whether the content of the rights file is changed or not can be judged in the execution process of the post-commit script. For example, whether a user identifier is added to the authority file or not, whether a user identifier is decreased or not, and the like are detected.
The first user identification(s) in the rights file have operating rights to the target directory. It will be appreciated that the target directory may include a number of other files, such as a repository file for storing code, in addition to the rights file described above. Moreover, there may be sub-directories under the target directory, so the operation authority for the target directory mentioned in this embodiment includes not only the operation authority for the authority file (because the authority file is located under the target directory), but also the operation authority for other files besides the authority file under the target directory and the authority file under the sub-directories thereof. The operation rights mentioned in this embodiment are, for example, rights of addition, deletion, modification, viewing, and the like.
In one example, the target directory is a root directory, and a owner file (i.e., a rights file) is included under the root directory, and the owner file includes three user identifications recorded therein: A. b and C, the information expressed by the owner file is that A, B, C three users have the operation authority of the root directory, that is, A, B and C three users can add new user identifications in the owner file, and certainly delete existing user identifications; A. the three users B and C may also have operation rights (e.g., change, delete rights, etc.) to other files in the root directory and its subdirectories.
In step S106, in the authority configuration file of the version management system, the account identifier having the control authority of the target directory is updated to the read at least one first account identifier, so that the user of the at least one first account identifier has the control authority of the target directory. That is, in step S106, the read authority file updates the authority configuration file of the version management system.
It will be appreciated that the rights configuration file of the version management system may comprise all rights information of the version management system, e.g. the rights configuration file of the version management system comprises a plurality of user identities, and for which directory(s) of (each of) the plurality of user identities has rights (add, delete, etc.) to, etc.
In a possible implementation manner, in step S106, a new permission configuration file may be generated, the account identifier having the control permission of the target directory is recorded in the new permission configuration file as the read at least one first account identifier, and then the current permission configuration file of the version management system is replaced by the new permission configuration file. Through the possible implementation mode, the completeness of the authority configuration can be guaranteed when the authority configuration file is updated.
In one possible implementation manner, the account id having the control authority of a certain target directory may perform a control operation on the authority file under the target directory. Thus, in this possible implementation, the method may further include: receiving a first operation command for indicating control operation on the authority file, wherein the first operation command carries a second account identifier; and searching the second account identifier in the permission configuration file, and if the second account identifier is searched and the second account identifier is recorded in the permission configuration file to have the control permission of the target directory, executing the control operation corresponding to the first operation command on the permission file. For example, at least one of the first account identifications is added or deleted in the rights file.
In a possible implementation manner, after step S106, the first account identifier has a control authority of the target directory, and may perform a control operation on the target directory and files under the subdirectories of the target directory. Thus, in this possible implementation, the method may further include: receiving a second operation command from a first client, wherein the first client logs in the version management system by using the first account identifier, the second operation command indicates that a control operation is performed on a target file, and the target file comprises: files under the target directory and/or files under subdirectories under the target directory; and executing the control operation corresponding to the second operation command on the target file. In a specific application, when a second operation command is received, whether a first account identifier for sending the second operation command is recorded in an authority configuration file of the version management system may be searched, if so, whether the first account identifier has a control authority of the target directory may be further determined, and if so, a control operation corresponding to the second operation command is executed, for example, a target file is newly created, a target file is modified, a target file is deleted, or a target file is checked.
In the embodiment of the present disclosure, if the control authority of a certain target directory needs to be modified, a user having the control authority of the target directory may modify a authority file under the target directory, and record at least one first account identifier having the control authority of the target directory in the authority file. For example, in one possible implementation, before step S102, the method may include: receiving a third operation command from a second client, wherein the second client logs in the version management system by using an administrator identification of the version management system, the third operation command indicates that the authority file is created under the target directory, and the target directory comprises: a root target of the version management system; creating the authority file and recording the at least one first account identifier in the authority file, wherein the at least one first account identifier comprises: the administrator identification. In this possible implementation manner, an administrator of the version management system may log in the version management system using the administrator identifier, create a permission file under a root directory of the version management system, and record at least one first account identifier in the permission file, that is, grant permission for the at least one first account identifier to operate the root directory, so that the at least one first account identifier may create or modify the permission file under the root directory and its respective sub-directories.
According to the authority management method of the version management system, the authority file is added under the target directory, at least one first account identifier with the control authority of the target directory is recorded in the authority file, the at least one first account identifier is read from the authority file, then the account identifier with the control authority of the target directory is updated to the read at least one first account identifier in the authority configuration file of the version management system, and therefore the user of the at least one first account identifier has the control authority of the target directory. Therefore, the authority of the target directory can be maintained by the user who already has the authority of the target directory, so that the pressure of a system administrator is shared, and the authority management efficiency of the version management system is improved.
Meanwhile, the version control capability of the version management system can be used, users and specific contents of each change in the authority file can be accurately known, and the subsequent audit on the change of the authority information is facilitated.
To describe the rights management method of the version management system provided in the present disclosure in detail, the SVN system will be described as an example.
The embodiment of the present disclosure realizes the control of the access authority of the SVN directory by modifying a certain file content (i.e. the user identifier in the aforementioned authority file) in the SVN code repository, and there are three problems here:
the first problem is how the file content expresses the rights information. Resources in the SVN code repository are organized in directories and files, so setting an access right is actually specifying what user can do under what directory. Two elements are mainly involved here: user, directory. The disclosed embodiment expresses this information using a file named owner (i.e. the target rights file), whose contents are a list of users, each user name occupying one row. The directory to which the owner file belongs is the directory to which the authority information is to be set, so that the information of the user and the directory can express an authority configuration, that is, the owner file in each SVN can completely express an authority information.
For example, a owner file is created under the root directory, and the file contents are:
A
B
C
then the information that this owner file can express is A, B, C the rights of three users to have the root directory.
The second problem is how to translate the information of the owner file into the content of the rights configuration file auth. Because the owner file is also within the SVN repository, changes to the contents of the owner file are ultimately committed to the SVN server using the commit command.
The SVN provides a post-commit script, and the SVN server executes the content of the post-commit script after each commit, so that in the embodiment, it may be determined in the post-commit script whether the commit involves a change in the content of an owner file, if so, all directories of the SVN may be traversed, each owner file may be obtained, and a new file auth. And after the reconstruction process is finished, replacing the original auth.
A third problem is how a user who already has a right maintains the right. Because users who already have a certain directory right can see and update the owner file under the directory, the users can complete the right management under the directory by themselves by changing the owner file and committing the content of the file.
A generally large SVN code repository may be divided into several large subdirectories at the root directory level, and then the SVN administrator may add an owner file in the root directory and write its own user name (i.e., account id) in the owner file of the root directory. Then, the owner files are respectively added in the large subdirectories, and the users who want to bear the management authority are respectively added in the owner files, so that the authority management under the current subdirectory can be self-completed by other users who already have the authority, and only when a new subdirectory needs to be added in the root directory, the SVN administrator needs to perform initialization operation.
For example, an SVN code repository directory structure is such that:
thus, rights management after/abc and/def directories can be done by a and B respectively, if a new directory ghi needs to be added/down, then an administrator is required to create the new directory and at the same time create an owner file to specify who owns the rights of the new directory.
The SVN authority management method provided by the present disclosure: the user who has the authority can bear the responsibility of maintaining the authority of the directory where the user is located, the pressure of an administrator is shared, and the large project can be more easily supported to be smoothly developed; the owner file is convenient for users who have authority to check and modify, and can check the owner file at any time to know the authority setting information of the current system; the owner file uses the version control capability of the svn because of being submitted to the code warehouse, so that users and specific contents of each change can be accurately known, and the change of the authority information can be audited conveniently to confirm the reasonability of the authority change.
The authority management method of the version management system uses the basic capability combination of the prior SVN to realize the scheme, has strong practicability and low development cost; the authority configuration information of the code warehouse is managed in a code mode, and the code authority and the authority for managing the code authority are unified together, so that the understanding and the operation are convenient.
Fig. 2 is a block diagram illustrating a rights management apparatus 200 of a version management system according to an exemplary embodiment, the apparatus 200 corresponding to the server of the version management system mentioned in the previous embodiment. Referring to fig. 3, the apparatus 200 includes a code acquiring unit 202, a reading unit 204, and an updating unit 206.
In this embodiment, the obtaining unit 202 is configured to perform obtaining of a rights file, where the rights file is located under a target directory, and at least one first account identifier having a control right of the target directory is recorded in the rights file; a reading unit 204 configured to perform reading the at least one first account identifier in the rights file; an updating unit 206 configured to execute updating, in the authority configuration file of the version management system, the account identifier having the control authority of the target directory to the read at least one first account identifier, so that the user of the at least one first account identifier has the control authority of the target directory.
According to the authority management device of the version management system, the obtaining unit 202 obtains the authority file, the reading unit 204 reads at least one first account identifier recorded in the authority file, and the updating unit 206 updates the account identifier having the control authority of the target directory to the read at least one first account identifier in the authority configuration file of the version management system, so that a user of the at least one first account identifier has the control authority of the target directory. Therefore, the user of the first account identifier having the authority of the target directory can bear the role of maintaining the authority of the target directory, the pressure of an administrator is shared, the authority management efficiency is improved, and the smooth development of large projects is supported more easily.
Further, as a possible implementation manner, the apparatus may further include:
a first receiving unit, configured to execute a first operation command that indicates a control operation on the authority file, where the first operation command carries a second account identifier;
and the first control unit is configured to search the second account identifier in the permission configuration file, and if the second account identifier is found and the second account identifier is recorded in the permission configuration file to have the control permission of the target directory, perform a control operation corresponding to the first operation command on the permission file.
Further, as a possible implementation manner, the apparatus may further include:
a second receiving unit configured to perform receiving a rights update command before acquiring the rights file;
and the judging unit is configured to execute the judgment of whether the information recorded in the current authority file is the same as the information recorded in the authority file when the authority updating command is received last time, and if the information recorded in the current authority file is different from the information recorded in the authority file when the authority updating command is received last time, the reading unit is triggered to read the at least one first account identifier in the authority file.
Further, as a possible implementation manner, the updating unit 206 updates the account identifier having the control authority of the target directory to the read at least one first account identifier by:
generating a new authority configuration file, and recording the account identifier with the control authority of the target directory in the new authority configuration file as the read at least one first account identifier;
and replacing the current authority configuration file of the version management system with the new authority configuration file.
Further, as a possible implementation manner, the apparatus may further include:
a third receiving unit configured to perform receiving a second operation command from a first client, wherein the first client logs in the version management system using the first account identifier, the second operation command indicates a control operation on a target file, and the target file includes: files under the target directory and/or files under subdirectories under the target directory;
a second control unit configured to perform a control operation corresponding to the second operation command on the target file.
Further, as a possible implementation manner, the apparatus may further include:
a fourth receiving unit configured to perform receiving a third operation command from a second client, wherein the second client logs in to the version management system using an administrator identification of the version management system, the third operation command indicates that the authority file is created under the target directory, and the target directory includes: a root target of the version management system;
a third control unit configured to perform creating the rights file and recording the at least one first account identifier in the rights file, wherein the at least one first account identifier includes: the administrator identification.
With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.
Fig. 3 is a block diagram illustrating an apparatus 300 for a rights management method for a version management system according to an example embodiment. The right management device 300 of the version management system corresponds to the server of the version management system mentioned in the above-mentioned embodiment.
The apparatus 300 may be provided as a server. Referring to FIG. 3, apparatus 300 includes a processing component 322 that further includes one or more processors and memory resources, represented by memory 332, for storing instructions, such as applications, that are executable by processing component 322. The application programs stored in memory 332 may include one or more modules that each correspond to a set of instructions. Further, the processing component 322 is configured to execute instructions to perform the method 100 described above.
The apparatus 300 may also include a power component 326 configured to perform power management of the apparatus 300, a wired or wireless network interface 350 configured to connect the apparatus 300 to a network, and an input/output (I/O) interface 358. The apparatus 300 may operate based on an operating system stored in the memory 332, such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, or the like.
In an exemplary embodiment, there is also provided a storage medium including instructions, for example, a memory including instructions executable by a processor of a rights management device of a version management system to perform a rights management method of the version management system. Alternatively, the storage medium may be a non-transitory computer readable storage medium, which may be, for example, a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
It should be noted that, since the rights management method of the version management system executed by the apparatus 300 in this embodiment has the same or corresponding technical features as or corresponding to the rights management method of the version management system in the foregoing embodiment 100, the detailed description of the rights management method of the version management system in this embodiment may refer to the description of the rights management method of the version management system in the foregoing embodiment 100, and the description of this embodiment is not repeated herein.
In an exemplary embodiment, a computer program product is also provided that includes at least one non-transitory computer readable medium storing instructions translatable by at least one processor for implementing the aforementioned method 100 of rights management for a version management system.
It should be noted that, since the rights management method of the version management system implemented by the computer program product in this embodiment has the same or corresponding technical features as the rights management method of the version management system in embodiment 100, the detailed description of the rights management method of the version management system in this embodiment may refer to the description of the rights management method of the version management system in embodiment 100, and the description of this embodiment is not repeated herein.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (10)
1. A rights management method of a version management system, comprising:
acquiring a permission file, wherein the permission file is positioned under a target directory, and at least one first account identifier with the control permission of the target directory is recorded in the permission file;
reading the at least one first account identifier in the permission file;
and updating the account identifier with the control authority of the target directory into the read at least one first account identifier in an authority configuration file of the version management system, so that the user of the at least one first account identifier has the control authority of the target directory.
2. The method of claim 1, further comprising:
receiving a first operation command for indicating control operation on the authority file, wherein the first operation command carries a second account identifier;
and searching the second account identifier in the permission configuration file, and if the second account identifier is searched and the second account identifier is recorded in the permission configuration file to have the control permission of the target directory, executing the control operation corresponding to the first operation command on the permission file.
3. The method of claim 2, wherein the control operation corresponding to the first operation command comprises: and adding or deleting at least one first account identifier in the authority file.
4. The method of claim 1,
before acquiring the rights file, the method further comprises: receiving an authority updating command;
before reading the first account identification in the rights file, the method further comprises:
and judging whether the information recorded in the current authority file is the same as the information recorded in the authority file when the authority updating command is received last time, and if so, executing the step of reading the at least one first account identifier in the authority file.
5. The method according to any one of claims 1 to 4, wherein updating the account identifier having the control right of the target directory to the read at least one first account identifier in the rights configuration file of the version management system comprises:
generating a new authority configuration file, and recording the account identifier with the control authority of the target directory in the new authority configuration file as the read at least one first account identifier;
and replacing the current authority configuration file of the version management system with the new authority configuration file.
6. The method according to any one of claims 1 to 4, wherein after the updating of the account identifier having the control right of the target directory to the read at least one first account identifier, the method further comprises:
receiving a second operation command from a first client, wherein the first client logs in the version management system by using the first account identifier, the second operation command indicates that a control operation is performed on a target file, and the target file comprises: files under the target directory and/or files under subdirectories under the target directory;
and executing the control operation corresponding to the second operation command on the target file.
7. The method according to any one of claims 1 to 4, wherein before acquiring the rights file, the method further comprises:
receiving a third operation command from a second client, wherein the second client logs in the version management system by using an administrator identification of the version management system, the third operation command indicates that the authority file is created under the target directory, and the target directory comprises: a root target of the version management system;
creating the authority file and recording the at least one first account identifier in the authority file, wherein the at least one first account identifier comprises: the administrator identification.
8. A rights management apparatus of a version management system, comprising:
the acquisition unit is configured to execute acquisition of a permission file, wherein the permission file is located under a target directory, and at least one first account identifier with the control permission of the target directory is recorded in the permission file;
a reading unit configured to perform reading of the at least one first account identifier in the rights file;
and the updating unit is configured to update the account identifier with the control authority of the target directory into the read at least one first account identifier in the authority configuration file of the version management system, so that the user of the at least one first account identifier has the control authority of the target directory.
9. A management apparatus of a version management system, comprising:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement a rights management method of a version management system as claimed in any one of claims 1 to 7.
10. A storage medium in which instructions, when executed by a processor of a rights management device of a version management system, enable the rights management device of the version management system to perform a rights management method of the version management system as claimed in any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011051736.3A CN112181480A (en) | 2020-09-29 | 2020-09-29 | Authority management method and device of version management system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011051736.3A CN112181480A (en) | 2020-09-29 | 2020-09-29 | Authority management method and device of version management system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112181480A true CN112181480A (en) | 2021-01-05 |
Family
ID=73945975
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011051736.3A Pending CN112181480A (en) | 2020-09-29 | 2020-09-29 | Authority management method and device of version management system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112181480A (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107220558A (en) * | 2017-05-24 | 2017-09-29 | 郑州云海信息技术有限公司 | A kind of method of rights management, apparatus and system |
| US20170351511A1 (en) * | 2015-12-22 | 2017-12-07 | Opera Solutions Usa, Llc | System and Method for Code and Data Versioning in Computerized Data Modeling and Analysis |
| CN107517124A (en) * | 2017-07-18 | 2017-12-26 | 交控科技股份有限公司 | Method and device based on Transmission Control Protocol Remote configuration Version Management Software SVN authorities |
| CN108614976A (en) * | 2018-04-28 | 2018-10-02 | 苏州科达科技股份有限公司 | Authority configuring method, device and storage medium |
| CN109344650A (en) * | 2018-09-25 | 2019-02-15 | 郑州云海信息技术有限公司 | A kind of file permission management method, system and the relevant apparatus of file system |
| CN109656618A (en) * | 2018-12-13 | 2019-04-19 | 泰康保险集团股份有限公司 | Source code edition control method, configuration server, medium, electronic equipment |
| CN109829330A (en) * | 2018-12-28 | 2019-05-31 | 恒生电子股份有限公司 | A kind of svn authority setting method, device, system, electronic equipment |
| CN110489155A (en) * | 2019-08-26 | 2019-11-22 | 北京达佳互联信息技术有限公司 | Data file management method, apparatus, electronic equipment and medium |
| CN111291330A (en) * | 2020-02-17 | 2020-06-16 | 苏州亿歌网络科技有限公司 | SVN authority management method, SVN authority management device, computer equipment and storage medium |
| CN111857806A (en) * | 2020-07-29 | 2020-10-30 | 北京达佳互联信息技术有限公司 | Permission configuration file updating method and device, electronic equipment and storage medium |
-
2020
- 2020-09-29 CN CN202011051736.3A patent/CN112181480A/en active Pending
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170351511A1 (en) * | 2015-12-22 | 2017-12-07 | Opera Solutions Usa, Llc | System and Method for Code and Data Versioning in Computerized Data Modeling and Analysis |
| CN107220558A (en) * | 2017-05-24 | 2017-09-29 | 郑州云海信息技术有限公司 | A kind of method of rights management, apparatus and system |
| CN107517124A (en) * | 2017-07-18 | 2017-12-26 | 交控科技股份有限公司 | Method and device based on Transmission Control Protocol Remote configuration Version Management Software SVN authorities |
| CN108614976A (en) * | 2018-04-28 | 2018-10-02 | 苏州科达科技股份有限公司 | Authority configuring method, device and storage medium |
| CN109344650A (en) * | 2018-09-25 | 2019-02-15 | 郑州云海信息技术有限公司 | A kind of file permission management method, system and the relevant apparatus of file system |
| CN109656618A (en) * | 2018-12-13 | 2019-04-19 | 泰康保险集团股份有限公司 | Source code edition control method, configuration server, medium, electronic equipment |
| CN109829330A (en) * | 2018-12-28 | 2019-05-31 | 恒生电子股份有限公司 | A kind of svn authority setting method, device, system, electronic equipment |
| CN110489155A (en) * | 2019-08-26 | 2019-11-22 | 北京达佳互联信息技术有限公司 | Data file management method, apparatus, electronic equipment and medium |
| CN111291330A (en) * | 2020-02-17 | 2020-06-16 | 苏州亿歌网络科技有限公司 | SVN authority management method, SVN authority management device, computer equipment and storage medium |
| CN111857806A (en) * | 2020-07-29 | 2020-10-30 | 北京达佳互联信息技术有限公司 | Permission configuration file updating method and device, electronic equipment and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 胡晓锋;: "基于SVN的网络协同开发环境构建", 民营科技, no. 06 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP7044879B2 (en) | Local tree update for client synchronization service | |
| AU2021202623B2 (en) | System for synchronization of changes in edited websites and interactive applications | |
| US20230418790A1 (en) | System and method for selective synchronization | |
| US10540173B2 (en) | Version control of applications | |
| US10127243B2 (en) | Fast recovery using self-describing replica files in a distributed storage system | |
| US11645245B2 (en) | Container software discovery and cataloging | |
| US9934256B2 (en) | End of retention processing using a database manager scheduler | |
| US20210117391A1 (en) | External data repository file integration using a virtual file system | |
| US8214410B2 (en) | Conflict management in a versioned file system | |
| CN112181481A (en) | Authority updating method and device of version management system | |
| JP2006031608A (en) | Computer, storage system, file management method which computer performs, and program | |
| CN109947739B (en) | Data source management method and device | |
| US20150347402A1 (en) | System and method for enabling a client system to generate file system operations on a file system data set using a virtual namespace | |
| CN112181480A (en) | Authority management method and device of version management system | |
| TW201629797A (en) | Method for performing file synchronization control, and associated apparatus | |
| US9467452B2 (en) | Transferring services in a networked environment | |
| US20220342779A1 (en) | Self-healing for data protection systems using automatic macro recording and playback | |
| US11294892B2 (en) | Virtual archiving of database records | |
| US11789968B2 (en) | Structured-data analysis and visualization | |
| US11550760B1 (en) | Time-based partitioning to avoid in-place updates for data set copies | |
| US20230094648A1 (en) | Backup feature provided by bidirectional synchronized content management system | |
| WO2017023255A1 (en) | System and method for updating a local instance of a shared drive | |
| US20210073268A1 (en) | Restoring integrity of a social media thread from a social network export | |
| CN116136841A (en) | Relational data migration method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |