Project management method and device for database

Abstract

The invention discloses a project management method and device for a database, and relates to the technical field of data processing. The method comprises the steps of determining a to-be-managed project in a database based on a user instruction, wherein the project is provided with a project identifier and a project version; the item identifier at least comprises one character; the project versions are set based on a preset format, and the project versions are used for distinguishing different batches of modified and / or updated projects; based on an operation demand determined by the user instruction, a corresponding baseline is constructed, and the baseline comprises a baseline category and a baseline configuration item; the baseline categories are used for distinguishing different baselines, and each baseline category at least comprises one baseline configuration item; and issuing the baseline to the GitLab system so as to call the GitLab system to execute corresponding operation behaviors on the to-be-managed items in the database. The method is used for realizing the project management function of the database.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a database project management method and device. Background Art

[0002] In the project management process, especially when managing project repositories involving code and documents, traditional configuration management methods have many shortcomings.

[0003] Specifically, in existing technologies, document management during project development often requires extensive manual effort. However, in practice, this approach not only consumes significant manpower but is also prone to errors. Especially during project changes and iterations, multiple documents or codes involved in a project may require collaborative processing by different personnel. When managing large projects, the complex document structure and frequent changes make manual processing extremely cumbersome and difficult, making it prone to errors. Summary of the Invention

[0004] The embodiments of the present application provide a database project management method and device, the main purpose of which is to implement a database project management method to solve the problem that the existing database project management method is cumbersome and difficult in the management process and is prone to errors.

[0005] To solve the above technical problems, the embodiments of the present application provide the following technical solutions:

[0006] In a first aspect, the present application provides a database project management method, the method comprising:

[0007] Determine a project to be managed in a database based on a user instruction, wherein the project is provided with a project identifier and a project version; wherein the project identifier comprises at least one character; and the project version is provided based on a preset format, and is used to distinguish between different batches of modified and / or updated projects;

[0008] Based on the operational requirements determined by the user instructions, a corresponding baseline is constructed, wherein the baseline includes a baseline category and baseline configuration items. The baseline category is used to distinguish different baselines, and each baseline category includes at least one baseline configuration item. The baseline configuration item is identifiable information of the connected GitLab system and is used to call the GitLab system to perform the operational behavior corresponding to the operational requirements.

[0009] The baseline is published to the GitLab system so as to call the GitLab system to perform corresponding operation behaviors on the projects to be managed in the database.

[0010] In a second aspect, the present application further provides a project management device for a database, comprising:

[0011] a determining unit, configured to determine a project to be managed in a database based on a user instruction, wherein the project is provided with a project identifier and a project version; wherein the project identifier comprises at least one character; and the project version is provided based on a preset format, and is used to distinguish between projects that have been modified and / or updated in different batches;

[0012] A construction unit is configured to construct a corresponding baseline based on the operation requirement determined by the user instruction, wherein the baseline includes a baseline category and baseline configuration items; the baseline category is used to distinguish different baselines, and each baseline category includes at least one baseline configuration item; the baseline configuration item is identifiable information of the connected GitLab system, and the baseline configuration item is used to call the GitLab system to perform the operation behavior corresponding to the operation requirement;

[0013] A publishing unit is used to publish the baseline to the GitLab system so as to call the GitLab system to perform corresponding operation behaviors on the projects to be managed in the database.

[0014] In a third aspect, an embodiment of the present application provides a storage medium, which includes a stored program, wherein when the program is running, the device where the storage medium is located is controlled to execute the project management method of the database of the terminal device described in the first aspect.

[0015] In a fourth aspect, an embodiment of the present application provides a project management device for a database, the device comprising a storage medium; and one or more processors, the storage medium being coupled to the processor, the processor being configured to execute program instructions stored in the storage medium; and the program instructions executing the project management method for a database of a terminal device described in the first aspect.

[0016] By means of the above technical solution, the technical solution provided by this application has at least the following advantages:

[0017] The present application provides a database project management method and device, which can first determine the project to be managed in the database based on user instructions, wherein the project is provided with a project identifier and a project version; wherein the project identifier contains at least one character; the project version is set based on a preset format, and the project version is used to distinguish between different batches of modified and / or updated projects; then, based on the operation requirements determined by the user instructions, a corresponding baseline is constructed, wherein the baseline includes a baseline category and a baseline configuration item; the baseline category is used to distinguish different baselines, and each baseline category includes at least one baseline configuration item; the baseline configuration item is identifiable information of the connected GitLab system, and the baseline configuration item is used to call the GitLab system to perform the operation behavior corresponding to the operation requirement; finally, the baseline is published to the GitLab system so as to call the GitLab system to perform the corresponding operation behavior on the project to be managed in the database, thereby realizing the project management function of the database. Compared with the prior art, since the method of the present application determines the project to be managed in the database by user instructions, it sets the baseline and publishes it to the GitLab system, thereby using the GitLab system to identify the baseline configuration items of the baseline and then automatically processes the project to be managed, reducing the need for manual operations in project identification, version management and baseline creation in the project management process, thereby reducing the workload and error probability, and solving the problem of complex and difficult operations and easy errors in the management of projects in the database by the prior art. At the same time, in the process of building the baseline, it is possible to support multiple baseline categories and configuration items, so as to ensure that when carrying out project management, it is possible to adapt to the needs and changes of different projects, making configuration management more flexible. In addition, in the process of carrying out management based on the baseline, the baseline configuration items are docked with the GitLab system, and the document management function of the GitLab system can be directly used to manage the project, without the need for additional compilation and setting of tools or scripts with document management, thereby saving the preparatory work before project management as a whole, and also saving the time and money of developing document management scripts or tools, and reducing the overall cost.

[0018] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The above and other objects, features and advantages of the exemplary embodiments of the present application will become readily understood by reading the detailed description below with reference to the accompanying drawings. In the accompanying drawings, several embodiments of the present application are shown in an exemplary and non-limiting manner, and the same or corresponding reference numerals represent the same or corresponding parts, wherein:

[0020] Figure 1 A flowchart of a database project management method provided by an embodiment of the present application is shown;

[0021] Figure 2 A flowchart of another database project management method provided by an embodiment of the present application is shown;

[0022] Figure 3 A block diagram showing the composition of another database project management device provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0023] The following describes exemplary embodiments of the present application in more detail with reference to the accompanying drawings. Although exemplary embodiments of the present application are shown in the accompanying drawings, it should be understood that the present application can be implemented in various forms and should not be limited by the embodiments described herein. Instead, these embodiments are provided to enable a more thorough understanding of the present application and to fully convey the scope of the present application to those skilled in the art.

[0024] It should be noted that, unless otherwise specified, the technical or scientific terms used in this application should have the common meanings understood by those skilled in the art to which this application belongs.

[0025] The present application provides a database project management method, specifically: Figure 1 As shown, the method includes:

[0026] 101. Determine an item to be managed in a database based on a user instruction.

[0027] The project settings include a project identifier and a project version. The project identifier contains at least one character; the project version is set based on a preset format and is used to distinguish between different batches of modified and / or updated projects.

[0028] In this embodiment, the database project management method described in this embodiment can be deployed in an independent server to form a separate management system, or it can be deployed in the database to become an independent subsystem in the database for managing database projects. Of course, the specific deployment method can be selected based on the needs of the user and is not limited here. For the convenience of subsequent description, the execution subject of this embodiment is explained in the form of this system.

[0029] Specifically, in this step, determining the items to be managed based on the user instructions can actually be carried out in the following steps:

[0030] First, during the user interface interaction process, users can enter or select the project to be managed through the configuration management system's user interface (UI). This can be achieved in a variety of ways, such as selecting the project from a drop-down menu or entering the project name or logo in a search box. The system provides a user-friendly interface to guide users in entering or selecting projects. The interface design should be concise and clear, allowing users to quickly find and select the desired project.

[0031] Then, during the project search process, after the system receives the user's selection or input, it searches the database for projects that match the user's input. Specifically, the database stores detailed information about all projects, including project IDs, project versions, and project descriptions. This system can quickly locate user-specified projects using SQL queries or other database query languages.

[0032] Finally, during the project information acquisition process, once a matching project is found, the system retrieves detailed information about the project, including its project ID and project version. The project ID consists of at least one character and uniquely identifies the project. The project version, based on a pre-set format, is used to distinguish between batches of modified and / or updated projects.

[0033] In this way, the system's automated processing based on user instructions reduces the manual work required of project managers in project identification and version management, reducing workload and the probability of error. Furthermore, this embodiment supports multiple project identification and version formats, adapting to the needs and changes of different projects and making configuration management more flexible. Furthermore, standardized management of project identification and version information facilitates subsequent review and tracing, ensuring project traceability and consistency.

[0034] 102. Build a corresponding baseline based on the operation requirements determined by the user instructions.

[0035] Among them, the baseline includes a baseline category and a baseline configuration item; the baseline category is used to distinguish different baselines, and each baseline category contains at least one baseline configuration item; the baseline configuration item is identifiable information of the connected GitLab system, and the baseline configuration item is used to call the GitLab system to perform the operation behavior corresponding to the operation requirement.

[0036] In this example, during the operation requirement determination process, users are generally required to specify the operation requirements through the interface, such as creating a new baseline, updating an existing baseline, deleting a baseline, etc. Here, the system will provide an operation requirement selection interface where users can select different operation types and enter relevant parameters.

[0037] After determining the operational requirements, the next step is to build a baseline. The system constructs a baseline consisting of baseline categories and baseline configuration items based on the operational requirements selected by the user. Specifically, baselines are divided into two important components: baseline classification, which is used to distinguish between different baselines, such as requirement baselines, design baselines, and test baselines; and baseline configuration items, where each baseline category contains at least one baseline configuration item. These baseline configuration items can be understood as identifiable information for the connected GitLab system, used to invoke the GitLab system to perform the corresponding operational behavior.

[0038] GitLab is an open-source Git-based code management platform, primarily used for code hosting, version control, continuous integration / continuous deployment (CI / CD), code review, security review, and project management during the software development process. It provides a unified DevOps lifecycle tool that covers all project phases, from planning, coding, building, to monitoring, significantly improving development efficiency and team transparency. GitLab supports unlimited private repositories and uses a Git-based version control system to effectively manage and track code change history, ensuring efficient collaboration among team members.

[0039] In this embodiment, the baseline configuration item can be a branch, label, commit ID, etc. in GitLab, which is not limited here and can be set based on the functions of the GitLab system.

[0040] Specifically, during the baseline information generation process, the system can generate a baseline identifier and a baseline configuration item identifier to ensure the uniqueness of each baseline and its configuration items. Specifically, the baseline identifier is generated based on the project identifier, project version, baseline type, and baseline version, while the baseline configuration item identifier can be generated based on the project identifier, project version, baseline configuration item, and baseline configuration item version.

[0041] Thus, in this step, the system automatically generates baselines based on user requirements determined by user instructions, reducing the manual work required of project managers in baseline creation and management, thereby lowering workload and the probability of error. Furthermore, the baseline construction process supports multiple baseline categories and configuration items, adapting to the needs and changes of different projects and making configuration management more flexible. Furthermore, the method based on this step standardizes the management of baseline and configuration item identification, facilitating subsequent review and traceability, and ensuring project traceability and consistency.

[0042] 103. Publish the baseline to the GitLab system so as to call the GitLab system to perform corresponding operations on the projects to be managed in the database.

[0043] When a baseline is released, the system can send the constructed baseline information to the connected GitLab system. During the specific release process, the system will call the GitLab interface program and send the relevant operation requirements represented by the baseline configuration items to the GitLab system. After receiving the baseline, the GitLab system will perform the corresponding operations based on the baseline configuration items.

[0044] For example, if the baseline configuration item is to filter a branch, the GitLab system will check out the code of that branch; if the baseline configuration item is to create a tag, the GitLab system will create the corresponding tag.

[0045] After GitLab executes an operation, it will feedback the results to the system. This allows users to know the status of the current project being managed, helping them quickly understand the management results. In addition, the system can also record the feedback results based on user needs for subsequent review and traceability.

[0046] The present application provides a project management method for a database, which can first determine a project to be managed in the database based on a user instruction, wherein the project is provided with a project identifier and a project version; wherein the project identifier contains at least one character; the project version is set based on a preset format, and the project version is used to distinguish between different batches of modified and / or updated projects; then, based on the operation requirements determined by the user instruction, a corresponding baseline is constructed, wherein the baseline includes a baseline category and a baseline configuration item; the baseline category is used to distinguish different baselines, and each baseline category includes at least one baseline configuration item; the baseline configuration item is identifiable information of the docked GitLab system, and the baseline configuration item is used to call the GitLab system to perform operation behaviors corresponding to the operation requirements; finally, the baseline is published to the GitLab system so as to call the GitLab system to perform corresponding operation behaviors on the project to be managed in the database, thereby realizing the project management function of the database. Compared with the prior art, since the method of the present application determines the project to be managed in the database by user instructions, it sets the baseline and publishes it to the GitLab system, thereby using the GitLab system to identify the baseline configuration items of the baseline and then automatically processes the project to be managed, reducing the need for manual operations in project identification, version management and baseline creation in the project management process, thereby reducing the workload and error probability, and solving the problem of complex and difficult operations and easy errors in the management of projects in the database by the prior art. At the same time, in the process of building the baseline, it is possible to support multiple baseline categories and configuration items, so as to ensure that when carrying out project management, it is possible to adapt to the needs and changes of different projects, making configuration management more flexible. In addition, in the process of carrying out management based on the baseline, the baseline configuration items are docked with the GitLab system, and the document management function of the GitLab system can be directly used to manage the project, without the need for additional compilation and setting of tools or scripts with document management, thereby saving the preparatory work before project management as a whole, and also saving the time and money of developing document management scripts or tools, and reducing the overall cost.

[0047] As a further description and refinement of the above embodiments, in some embodiments, the project identifier is set based on a project identifier setting rule; wherein the project identifier setting rule is used to indicate that the types of characters when the user sets the project identifier include numbers, English and underscores, and the first character of the project identifier is a non-numeric character.

[0048] In this embodiment, the specific process of setting the project identifier may be as follows:

[0049] First, during the system configuration phase, it's necessary to define project ID settings rules. These rules specify that project IDs must contain the following characters: numbers, English letters, and the underscore (_). Furthermore, the first character of a project ID must be non-numeric. These rules aim to ensure the standardization and uniqueness of project IDs, facilitating effective project identification and management, while also preventing potential errors and confusion caused by inconsistent ID formats.

[0050] Then, guidance is provided in the user interface. When a user creates a new project in the system's interface, the system will prompt the user to set the project ID according to established rules. For example, the system may provide an input box in the project creation form for the user to enter the project ID, and display formatting prompts next to the input box, such as "Project IDs can only contain numbers, English characters, and underscores, and cannot begin with a number." This interface guidance helps users correctly set project IDs when creating projects, reduces repeated modifications due to formatting errors, and improves subsequent project management efficiency.

[0051] Next, after the user enters the project ID, the system will validate the input. This validation process includes checking that the project ID consists only of permitted characters and that the first character must be non-numeric. If the project ID entered by the user does not meet the requirements, the system will immediately display an error message and require the user to re-enter the ID until it meets the requirements. This validation step ensures that only project IDs that meet the requirements are accepted and saved by the system, thereby ensuring the consistency and standardization of project IDs and promoting the standardization of overall project management.

[0052] After the user enters the project ID, the verified project ID will be saved by the system to the database, along with other project information (such as project name and description). During the saving process, the system may further process the project ID, such as converting it to a unified format or encoding it to facilitate subsequent query and management. In this way, the saved project ID will serve as a unique identifier for the project in the system, distinguishing different projects and allowing project managers to quickly locate and access specific projects in the system.

[0053] Throughout a project's lifecycle, project identification will be widely used in various scenarios, such as naming project documents, organizing folders, and assigning tasks. Due to the standardized nature of project identification, different project managers can easily identify and associate various project-related resources and activities, improving the efficiency and accuracy of project management. Furthermore, standardized project identification facilitates the system's automatic generation of project-related reports and statistical information, providing strong support for project decision-making and evaluation.

[0054] As a further description and refinement of the above embodiment, in some embodiments, before the above embodiment of “step 101, determining the items to be managed in the database based on the user instruction”, the method may further include:

[0055] When creating a new project in the project center of the database, fill in the basic information of the new project and set a project ID for the new project based on the project ID setting rules;

[0056] According to the preset format, a corresponding project version is set for the new project; wherein the format includes at least three fields, namely, a major version, a minor version, and a revision number; wherein the levels of the major version, the minor version, and the revision number decrease in sequence, and when the content of a higher-level field changes, the content of a lower-level field is cleared.

[0057] During the project version setting process, you can proceed as follows:

[0058] First, define the version format. When creating a project, the system requires users to set the project version according to a predefined format. This predefined format includes at least three fields: major version, minor version, and revision number. These fields are ranked in descending order, and when the content of a higher-level field is changed, the content of the lower-level field is cleared.

[0059] For example, the version format can be defined as "major.minor.revision", such as "1.0.0". The major version indicates an incompatible API modification, the minor version indicates a backward-compatible functional addition, and the revision number indicates a backward-compatible bug fix.

[0060] Next, the system guides users through the version setting process. The system provides guidance on version setting within the project creation interface, helping users understand the meaning of each field and the setting rules. Users can select an appropriate version number based on the project's specific circumstances and development plan. Specifically, the system may provide examples and instructions to help users better understand and apply version setting rules.

[0061] After the user sets the project version, the system can also verify the version number to ensure it conforms to the preset format. This verification includes checking whether the version number format is correct and whether the values ​​of each field comply with the rules for incrementing and clearing. If the version number set by the user does not meet the rules, the system will display an error message and require the user to reset it until the version number meets the rules.

[0062] Afterwards, the verified version number can be saved. Specifically, the verified project version number will be stored in the database by the system, along with the project identifier and other project information. The version number will serve as the basis for project version management, recording the different development stages and change history of the project.

[0063] In this way, during the subsequent project development process, the system will automatically manage the project version upgrades and changes according to the version number setting rules to ensure the continuity and traceability of the version.

[0064] Through the above method in this embodiment, it is ensured that during the project creation process, the settings of the project identification and project version comply with the specifications and rules, which not only helps to improve the efficiency of project management, but also provides a solid foundation for the smooth progress and successful delivery of the project, and also lays the foundation for accurate management of projects based on project identification and project version.

[0065] As a further description and refinement of the above embodiment, in some embodiments, the preset format further includes at least one of the following fields, including: extended version, patch version, customized version, and compilation serial number;

[0066] The major version is used to indicate that it is incremented when the user performs an incompatible modification; the major version content is an integer in the range of 1-99, and the minor version content and revision number content are cleared when incrementing;

[0067] The minor version is used to indicate that it is incremented when a user adds a new backward-compatible feature. The minor version value ranges from 0 to 99, and the revision number is reset to zero when incremented.

[0068] The revision number is used to indicate that it is incremented when the user performs a backward compatibility fix, and the revision number is an integer ranging from 0 to 99;

[0069] The extended version further specifically includes emergency hot patches, emergency cold patches, and cumulative upgrade patches, wherein the value range of the content of the emergency hot patches, the value range of the content of the emergency cold patches, and the value range of the content of the cumulative upgrade patches are all integers between 1 and 99;

[0070] The customized version further specifically includes a customer customization number and a number that identifies the upgrade number of the customized version; wherein the content that identifies the customer customization number begins with the character C; the content that identifies the customer customization number includes a character that begins with U and an integer in the range of 1-99;

[0071] The compilation sequence number is determined based on any one of the build number, the timestamp, and the Commit ID.

[0072] Based on the description of the above embodiment, it can be seen that the major version, minor version, and revision number are the three most basic version formats, which are used to record the different development stages and change history of the project. The major version represents incompatible modifications, the minor version represents the addition of backward-compatible functionality, and the revision number represents the correction of backward-compatible problems. In this embodiment, the preset format also involves other extended fields in addition to the major version, minor version, and revision number, namely, the extended version, patch version, customized version, and compilation number. Among them, the extended version: includes emergency hot patches (HPx), emergency cold patches (CPx), and cumulative upgrade patches (SPx), which are used to record specific types of updates; the patch version: is used to record smaller fixes or updates; the customized version: includes a customer customization number (Cx) and a number (Ux) that identifies the upgrade number of the customer customization version, which is used to record customer-specific customized content; the compilation number is determined based on the build number, timestamp, or Commit ID, and is used to record specific build information.

[0073] In this embodiment, the build number can be understood as a number used to identify a specific build in software code development. It is usually composed of a series of letters and numbers and is used to distinguish different build versions. It can help the development team track and manage different build versions of the software, ensuring that a specific build can be accurately identified and traced back during the release and testing process. For example, in Android development, the build number may use the format of PVBB.YYMMDD.bbb, where P represents the first letter of the platform version code, V represents the supported category, BB is the code branch identifier, YYMMDD is the date code, and bbb is the version sequence number.

[0074] In addition, a commit ID is a hash value used to uniquely identify each commit in the Git system. Each commit generates a unique commit ID, which is calculated based on information such as the commit content, author information, and commit time. For example, in real-world applications, you can use the gitlog command to view commit IDs in the commit history. These commit IDs can be used to track and manage code versions.

[0075] A timestamp is a numerical value representing a specific moment in time, typically expressed as the number of seconds or milliseconds since January 1, 1970, 00:00:00 UTC. It is used in software development to record the time when an event occurred. For example, in JavaScript, you can use new Date().getTime() to get the current timestamp.

[0076] Based on this, the process of determining the compilation sequence based on the build number, commit ID, and timestamp can be divided into the following methods:

[0077] 1. Use the build number directly. In some projects, the build number can be used directly as the compilation number. For example, in Android development, the build number already contains rich version information and can be used directly as the compilation number.

[0078] 2. Use the Commit ID directly. In the GitLab system, each commit ID is unique and can be used as a build sequence. For example, in a continuous integration / continuous deployment (CI / CD) process, each build is associated with a specific Commit ID, which can be used as the build sequence.

[0079] 3. Use timestamps directly. Timestamps can be accurate to milliseconds and can therefore be used as compilation numbers. For example, in an automated build system, the current timestamp is obtained during each build and used as the compilation number.

[0080] 4. Combined use. Specifically, you can combine the build number, commit ID, and timestamp to generate a compilation sequence number. For example, you can use the format of build number_timestamp_commitID. This format includes the build version, time information, and code commit information, making it easier to track and manage.

[0081] Based on the above description, you can choose the appropriate method for generating build numbers based on project requirements and development processes. Specifically, by combining the build number, commit ID, and timestamp, you can generate a unique and traceable build number, helping to improve project management and development efficiency.

[0082] When including the aforementioned extended fields, the version number setting process can be as follows: When creating a project, the user selects an appropriate version number based on the project's actual situation and development plan. This system provides guidance on version number setting to help users understand the meaning and setting rules of each field. The subsequent version number verification, storage, and application are consistent with the previous embodiment and are not further described here.

[0083] Furthermore, when setting the above fields specifically, you can do the following:

[0084] (1) Main version:

[0085] Definition: Incremented when the user performs an incompatible modification.

[0086] Value range: integer from 1 to 99.

[0087] Behavior when incrementing: Minor and revision numbers are cleared to zero.

[0088] (2) Minor version:

[0089] Definition: Incremented when the user adds a backward-compatible feature.

[0090] Value range: integer from 0 to 99.

[0091] Behavior when incrementing: The contents of the revision number are reset to zero.

[0092] (3) Revision number:

[0093] Definition: Incremented when the user performs a backward-compatible bug fix.

[0094] Value range: integer from 0 to 99.

[0095] (4) Extended version:

[0096] Definition: Includes emergency hot patches, emergency cold patches, and cumulative upgrade patches.

[0097] Value range: integer from 1 to 99.

[0098] (5) Customized version:

[0099] Definition: Includes the number that identifies the customer customization and the number that identifies the upgrade sequence of the customer customization version.

[0100] Value range: The customer customization number starts with C, and the upgrade number of the customer customization version starts with U. The value range is an integer from 1 to 99.

[0101] (6) Compilation number:

[0102] Definition: Determined based on build number, timestamp or CommitID.

[0103] Specifically, the actual operation examples are as follows:

[0104] Assume that the initial version of a project is 1.0.0:

[0105] Major version increment: When the project undergoes incompatible modifications, the major version is incremented from 1 to 2, and the minor version and revision numbers are cleared to 2.0.0.

[0106] Minor version increment: When the project adds backward-compatible functionality, the minor version increments from 0 to 1, and the revision number is reset to 1.1.0.

[0107] Revision number increment: When the project makes a backward-compatible fix, the revision number increments from 0 to 1, becoming 1.0.1.

[0108] Extended version application: When a project needs urgent repair, add the emergency hot patch HP1 and the version number becomes 1.0.0.HP1.

[0109] Customized version application: When a project is customized for a specific customer, the customer customization number C1 and upgrade number U1 are added, and the version number becomes 1.0.0.C1.U1.

[0110] Compile number application: When the project is built, the compile number is based on the build number 20240101, and the version number becomes 1.0.0.20240101.

[0111] The method of this embodiment ensures that project version settings and management comply with standards and regulations. This not only helps improve project management efficiency but also provides a solid foundation for the smooth progress and successful delivery of projects. Furthermore, standardized version number management ensures that every development stage and change history of a project can be accurately recorded and traced, providing strong support for long-term project maintenance and collaboration.

[0112] As a further description and refinement of the above embodiment, in some embodiments, the baseline further includes a baseline identifier, which is determined based on the project identifier, project version, baseline type, and baseline version; the baseline configuration item further includes a baseline configuration item identifier, which is determined based on the project identifier, project version, baseline configuration item, and baseline configuration item version;

[0113] In the aforementioned embodiment, “Step 102, constructing a corresponding baseline based on the operation requirement determined by the user instruction” may be performed as follows:

[0114] S1. Based on the project to be managed, obtain a project identifier and a project version;

[0115] S2. Determine a corresponding baseline configuration item based on the operation requirement, and determine a baseline type corresponding to the operation requirement based on a relationship between the baseline configuration item and the baseline category;

[0116] S3, obtaining the baseline type, setting the baseline version, and then generating the baseline identifier by combining the project identifier, project version, baseline type, and baseline version;

[0117] S4. Setting a baseline configuration item version for the baseline configuration item corresponding to the operation requirement, and generating the baseline configuration item identifier based on the project identifier, project version, baseline configuration item, and baseline configuration item version;

[0118] S4. Construct the baseline based on the baseline identifier and the baseline configuration item identifier.

[0119] In this embodiment, the above process from S1 to S4 is mainly divided into two parts: the first part is the process of determining the baseline identifier and the baseline configuration item identifier; the second part is the specific steps of building the baseline, which are as follows:

[0120] 1. The process of determining the baseline identifier and baseline configuration item identifier:

[0121] During the baseline identification generation process, the system first retrieves the project ID and project version information of the project to be managed from the database. This information is set and saved according to established rules when the project is created. Then, based on the user-specified operational requirements, the system determines the required baseline type. The baseline type distinguishes different baselines, and each baseline type contains at least one baseline configuration item. Examples include requirements baselines, design baselines, and test baselines. Next, the system sets a baseline version for the specified baseline type. This baseline version records baseline iterations and updates. Finally, the project ID, project version, baseline type, and baseline version are combined to create a unique baseline ID. For example, if the project ID is "ProjectA," the project version is "1.0.0," the baseline type is "Requirements," and the baseline version is "1," the baseline ID might be "ProjectA-1.0.0-Requirements-1." Of course, in practice, to facilitate machine recognition, the baseline type can be assigned the corresponding baseline code. For example, if the baseline code corresponding to the requirement is BL_RM, the baseline ID might be "ProjectA-1.0.0-BL_RM-1."

[0122] In the process of generating the baseline configuration item identifier, first, based on the user's operational requirements, the system can determine the required baseline configuration items. Since the baseline configuration item is information that can be identified by the GitLab system and is used to call the GitLab system to perform the corresponding operational behavior, the process of determining the baseline configuration item is the process of laying the foundation for the subsequent operational behaviors that can be executed by the GitLab system. Then, the system sets a version number for each baseline configuration item to record the iteration and update of the configuration item. After that, the system will combine the project identifier, project version, baseline configuration item, and baseline configuration item version into a unique baseline configuration item identifier. For example, if the project identifier is "ProjectA", the project version is "1.0.0", the baseline configuration item is "Original Requirement Record (Baseline Configuration Item Coded as RDM-ORM)", and the baseline configuration item version is "1", then the baseline configuration item identifier can be "ProjectA-1.0.0-RDM-ORM-1".

[0123] 2. The specific steps for building a baseline are as follows:

[0124] First, project information is obtained. Specifically, this system can obtain the project identifier and project version information of the project to be managed from the database. Next, baseline configuration items are determined. Specifically, this system can determine the required baseline configuration items based on user operational requirements. These configuration items can be documents, code, test cases, etc. Next, the baseline type is determined. At this time, the system determines the baseline type corresponding to the operational requirements based on the relationship between the baseline configuration items and the baseline category. Next, the system sets the baseline version for the determined baseline type and combines the project identifier, project version, baseline type, and baseline version into a unique baseline identifier. At the same time, this system also sets a version number for each baseline configuration item and then combines the project identifier, project version, baseline configuration item, and baseline configuration item version into a unique baseline configuration item identifier. Finally, a complete baseline is constructed based on the generated baseline identifier and baseline configuration item identifiers.

[0125] The following example illustrates the above process: Assume a project with the project ID "ProjectA" and the project version "1.0.0." The user needs to create a requirements baseline, which includes two configuration items: a requirements document and a design document. The specific process is as follows:

[0126] 1. Get project information: Project ID: ProjectA; Project version: 1.0.0

[0127] 2. Determine baseline configuration items: requirements documents; design documents

[0128] 3. Determine the baseline type: demand baseline

[0129] 4. Set baseline version: Baseline version: 1

[0130] 5. Generate baseline identification: Baseline identification: ProjectA-1.0.0-Requirement-1

[0131] 6. Set baseline configuration item version: Requirement document version: 1; Design document version: 1

[0132] 7. Generate baseline configuration item identification: Requirement document identification: ProjectA-1.0.0-Requirement document-1; Design document identification: ProjectA-1.0.0-Design document-1

[0133] 8. Build baseline: The baseline contains the baseline identifier "ProjectA-1.0.0-Requirement-1" and two baseline configuration item identifiers "ProjectA-1.0.0-Requirement Document-1" and "ProjectA-1.0.0-Design Document-1".

[0134] The method of this embodiment ensures that the setup and management of baselines and their configuration items comply with standards and regulations, helping to improve project management efficiency while also providing a solid foundation for smooth project progress and successful delivery. Furthermore, standardized management of baseline and configuration item identifiers ensures that every stage of a project's development and change history can be accurately recorded and traced, providing strong support for long-term project maintenance and collaboration.

[0135] As a further description and refinement of the above embodiment, in some embodiments, before the aforementioned embodiment of "step 103, publishing the baseline to the GitLab system so as to call the GitLab system to perform corresponding operations on the project to be managed in the database", the method further includes: calling an interface of the GitLab system using preset identity information to obtain a commit record of the project in the database, and obtaining address information corresponding to the project based on the database address, the commit identifier in the commit record, and the project identifier;

[0136] Based on this, the aforementioned embodiment "Step 103, publishing the baseline to the GitLab system so as to call the GitLab system to perform corresponding operations on the projects to be managed in the database" is specifically as follows during execution: publishing the baseline to the GitLab system so as to call the GitLab system to perform corresponding operations on the projects to be managed in the database through the address information.

[0137] In the process of calling the GitLab system interface to obtain the project's commit records using preset identity information, the specific execution method can be as follows:

[0138] A1. Generate a personal access token. To do this, log in to your GitLab account, go to the "User Settings" page, select "Access Tokens," and generate a new access token. Ensure that sufficient permissions (such as "api" permissions) are selected so that the GitLab system can access project information. Record the generated access token, which is the credential for calling the GitLab API.

[0139] A2. Call the GitLab system API to obtain project information. Specifically, you can use the curl command line tool or write code to call the GitLab API. For example, use curl to make an API call:

[0140] curl --header "PRIVATE-TOKEN:<your_access_token> "https: / / gitlab.cn / api / v4 / projects"

[0141] in,<your_access_token> The access token obtained in the previous step. This will return information about all your projects, including the address of each project.

[0142] A3. Parse the API response. The API response is usually in JSON format and contains various project information. Find the http_url_to_repo or ssh_url_to_repo field, which will display the project's HTTPS or SSH address.

[0143] For example:

[0144] {

[0145] "id":123,

[0146] "name":"example-project",

[0147] "http_url_to_repo":"https: / / gitlab.cn / username / example-project.git",

[0148] "ssh_url_to_repo":"git@gitlab.cn:username / example-project.git"

[0149] }

[0150] Extract the required project address from it.

[0151] A4. Get the project's commit history: Next, you can use the project ID or project path to call the GitLab API to get the project's commit history.

[0152] For example:

[0153] curl --header "PRIVATE-TOKEN:<your_access_token> ""https: / / gitlab.cn / api / v4 / projects / :project_id / repository / commits"

[0154] in,<your_access_token> The access token obtained in the previous step is project_id, which is the project ID.

[0155] A5. Parse the commit record. Specifically, parse the returned JSON data to obtain the commit ID and other related information for each commit.

[0156] A6. Get the address information corresponding to the project. The address information corresponding to the project is generated based on the database address, the commit ID in the commit record, and the project ID. For example, if the project ID is "ProjectA", the project version is "1.0.0", and the commit ID is "abc123", the project address information can be: https: / / gitlab.cn / ProjectA / 1.0.0.git?commit=abc123

[0157] After obtaining the address information in the above steps, the next step is to publish the baseline to the GitLab system. The GitLab system will perform corresponding operations on the managed project based on the address information. The specific execution steps are:

[0158] B1. Build baseline information. Specifically, complete baseline information can be built based on the generated baseline identifier and baseline configuration item identifier. Baseline information includes baseline identifier, baseline configuration item identifier, project address information, etc.

[0159] B2. Publish the baseline to GitLab. This process can be accomplished in a variety of ways, such as by creating a new branch, tag, or commit through the GitLab API. The project's address information is then used to ensure that GitLab can accurately locate and operate on the project.

[0160] B3. Call the GitLab system to perform operations. After receiving the baseline information, the GitLab system will perform corresponding operations based on the baseline configuration items. For example, if the baseline configuration item is a branch, the GitLab system will check out the code for that branch; if the baseline configuration item is a tag, the GitLab system will create the corresponding tag.

[0161] B4. Feedback on operation results. After GitLab executes an operation, it will feed back the results to the configuration management system. The system will also record the results for subsequent review and tracing.

[0162] The method in this example ensures that the entire baseline publishing process to the GitLab system complies with specifications and rules. This not only helps improve project management efficiency but also enables the GitLab system to accurately locate the project to be managed based on address information. Furthermore, standardized management of the baseline publishing process ensures that every development stage and change history of a project can be accurately recorded and traced, providing strong support for long-term project maintenance and collaboration.

[0163] As a further description and refinement of the above embodiment, in some embodiments, after the above embodiment of "step 103, publishing the baseline to the GitLab system", the method further includes:

[0164] 104. Create a baseline tag by calling the GitLab system. The content of the baseline tag is the baseline identifier of the published baseline, and the baseline tag is used to view baseline records and / or trace back the operation requirements corresponding to the baseline.

[0165] 105. When it is detected that the baseline has been changed, an update operation is performed on the published baseline based on the change behavior, and the update operation is used to increment the baseline version in the baseline identifier.

[0166] There are two execution processes for step 104 : one is to create a tag using the GitLab UI, and the other is to create a tag using the command line.

[0167] The process for creating a tag using the GitLab UI is as follows: 1. Log in to the GitLab system and go to the project page; 2. In the left navigation bar, select "Code" > "Tags"; 3. Click the "New Tag" button; 4. In the dialog box that pops up, enter the tag name (for example, the baseline identifier "ProjectA-1.0.0-Requirement-1"); 5. Select the commit to be tagged (usually the commit corresponding to the baseline); Optional: Add a tag description. 6. Click the "Create Tag" button.

[0168] The process of creating a tag using the command line can be: 1. Clone the project repository locally: git clonehttps: / / gitlab.cn / username / project.git; 2. Switch to the project directory: cd project; 3. Create a new tag: git tag-a "ProjectA-1.0.0-Requirement-1" -m "Create requirement baseline tag"; 4. Push the tag to the remote repository: git push origin–tags.

[0169] It should be noted that both of the above two methods of creating tags can be performed by pre-setting the relevant instruction set. That is to say, when the GitLab system detects that a tag needs to be created corresponding to the newly released baseline, it can automatically trigger the instruction set, thereby realizing the tag creation function of the above two methods.

[0170] In this way, by setting a baseline label for the baseline, you can view the label list through the GitLab UI or command line to understand the baseline history. The label description information and commit records meet the corresponding operational requirements for backtracking the baseline.

[0171] Furthermore, in step 105, when it is detected that the baseline has been changed, the published baseline can be updated based on the change behavior. The specific operation process is as follows:

[0172] (1) Detecting baseline changes: This system uses hooks or regular check mechanisms in version control systems (such as GitLab) to detect whether the baseline has changed. Changes may include code modifications, document updates, etc.

[0173] (2) Determine the change behavior. In this system, the specific content of the change will be analyzed in real time to determine the type and scope of the change. For example, whether it involves incompatible modifications, backward-compatible functional additions, or problem corrections.

[0174] (3) Update the baseline version. Based on the change behavior, the system will determine whether the baseline version needs to be incremented. For example, if the change involves an incompatible modification, the major version number is incremented; if it involves a backward-compatible functional addition, the minor version number is incremented; if it involves a bug fix, the revision number is incremented.

[0175] (4) Generate a new baseline identifier. When a new baseline version is determined, a new baseline identifier is generated based on this new baseline version. For example, if the original baseline identifier is "ProjectA-1.0.0-Requirement-1", the new baseline identifier may be "ProjectA-1.0.1-Requirement-1".

[0176] (5) Update baseline configuration items. For each baseline configuration item, update its version number according to the changed content and generate a new baseline configuration item identifier.

[0177] (6) Release the updated baseline. After determining the new baseline version and the versions of the baseline configuration items, the baseline can be updated. This involves sending the updated baseline information to the GitLab system, creating a new tag or updating an existing tag through the GitLab API, and recording the latest status of the baseline.

[0178] Practical examples

[0179] Assume a project named "ProjectA" with the project ID "ProjectA" and the project version "1.0.0". The user needs to publish a requirements baseline, which includes two configuration items: the requirements document and the design document.

[0180] The method used in this example ensures that the management and update process of baselines published to the GitLab system complies with standards and regulations. This not only helps improve project management efficiency but also provides a solid foundation for smooth project progress and successful delivery. Furthermore, the creation and management of baseline tags ensures that every development stage and change history of a project can be accurately recorded and traced, providing strong support for long-term project maintenance and collaboration.

[0181] Furthermore, as a response to the above Figure 1 In addition to the implementation of the methods shown in the other above embodiments, another embodiment of the present application also provides a project management device for a database. The project management device embodiment of the database corresponds to the above method embodiment. For ease of reading, the project management device embodiment of the database will no longer describe the details of the above method embodiment one by one, but it should be clear that the device in this embodiment can correspond to all the contents of the above method embodiment. Specifically, Figure 2 As shown, the project management device of the database includes:

[0182] The determining unit 21 may be configured to determine a project to be managed in the database based on a user instruction, wherein the project is provided with a project identifier and a project version; wherein the project identifier comprises at least one character; and the project version is set based on a preset format, and the project version may be used to distinguish between different batches of modified and / or updated projects.

[0183] The construction unit 22 may be configured to construct a corresponding baseline based on the operation requirement determined by the user instruction, wherein the baseline includes a baseline category and baseline configuration items. The baseline category may be used to distinguish different baselines, and each baseline category includes at least one baseline configuration item. The baseline configuration item is identifiable information of the connected GitLab system and may be used to invoke the GitLab system to perform the operation corresponding to the operation requirement.

[0184] The publishing unit 23 may be configured to publish the baseline constructed by the constructing unit 22 to the GitLab system, so as to call the GitLab system to perform corresponding operation actions on the project to be managed determined by the determining unit 21 in the database.

[0185] Further, such as Figure 3 As shown, the project identifier is set based on the project identifier setting rules; wherein, the project identifier setting rules can be used to indicate that the types of characters when the user sets the project identifier include numbers, English and underscores, and the first character of the project identifier is a non-numeric character.

[0186] Further, such as Figure 3 As shown, the device also includes:

[0187] The first setting unit 24 may be used to fill in basic information of the new project when creating a new project in the project center of the database, and to set a project identifier for the new project based on the project identifier setting rule;

[0188] The second setting unit 25 can be used to set the corresponding project version for the new project according to the preset format; wherein the format includes at least three fields, namely major version, minor version and revision number; wherein the levels of the major version, minor version and revision number decrease in sequence, and when the content of a higher-level field changes, the content of a lower-level field is cleared.

[0189] Further, such as Figure 3 As shown, the preset format further includes at least one of the following fields, including: extended version, patch version, customized version, and compilation serial number;

[0190] The major version can be used to indicate that it is incremented when the user performs an incompatible modification; the content of the major version is an integer in the range of 1-99, and the content of the minor version and the revision number are cleared when incrementing;

[0191] The minor version may be used to indicate that the revision number is incremented when a user adds a new backward-compatible feature. The minor version number is an integer ranging from 0 to 99, and the revision number is reset to zero when incremented.

[0192] The revision number may be used to indicate that it is incremented when a user performs a backward-compatible fix, and the revision number is an integer ranging from 0 to 99;

[0193] The extended version further specifically includes emergency hot patches, emergency cold patches, and cumulative upgrade patches, wherein the value range of the content of the emergency hot patches, the value range of the content of the emergency cold patches, and the value range of the content of the cumulative upgrade patches are all integers between 1 and 99;

[0194] The customized version further specifically includes a customer customization number and a number that identifies the upgrade number of the customized version; wherein the content that identifies the customer customization number begins with the character C; the content that identifies the customer customization number includes a character that begins with U and an integer in the range of 1-99;

[0195] The compilation sequence number is determined based on any one of the build number, the timestamp, and the Commit ID.

[0196] Further, such as Figure 3As shown, the baseline also includes a baseline identifier, which is determined based on the project identifier, project version, baseline type, and baseline version; the baseline configuration item also includes a baseline configuration item identifier, which is determined based on the project identifier, project version, baseline configuration item, and baseline configuration item version;

[0197] The construction unit 22 can be specifically used to obtain a project identifier and a project version based on the project to be managed; and, based on the operation requirements, determine the corresponding baseline configuration item, and based on the relationship between the baseline configuration item and the baseline category, determine the baseline type corresponding to the operation requirements; and, obtain the baseline type, set the baseline version, and then generate the baseline identifier by combining the project identifier, project version, baseline type, and baseline version; and, set a baseline configuration item version for the baseline configuration item corresponding to the operation requirement, and generate the baseline configuration item identifier based on the project identifier, project version, baseline configuration item, and baseline configuration item version; and, construct the baseline based on the baseline identifier and the baseline configuration item identifier.

[0198] Further, such as Figure 3 As shown, the device also includes:

[0199] The acquisition unit 26 may be configured to call the GitLab system interface using the preset identity information to obtain the commit record of the project in the database, and obtain the address information corresponding to the project based on the database address, the commit identifier in the commit record, and the project identifier;

[0200] The publishing unit 23 can also be specifically used to publish the baseline to the GitLab system so as to call the GitLab system and perform corresponding operation behaviors on the project to be managed in the database through the address information obtained by the obtaining unit 26.

[0201] Further, such as Figure 3 As shown, the device also includes:

[0202] The creation unit 27 can be used to create a baseline tag by calling the GitLab system, wherein the content of the baseline tag is the baseline identifier of the baseline published by the publishing unit 23, and the baseline tag can be used to view the baseline record and / or trace back the operation requirements corresponding to the baseline.

[0203] The updating unit 28 may be configured to, when detecting that the baseline published by the publishing unit 23 has been changed, perform an update operation on the published baseline based on the change behavior. The update operation may be configured to increment the baseline version in the baseline identifier.

[0204] An embodiment of the present application provides a database project management method and device. In the embodiment of the present application, the project to be managed in the database can be first determined based on user instructions, wherein the project is provided with a project identifier and a project version; wherein the project identifier contains at least one character; the project version is set based on a preset format, and the project version is used to distinguish between different batches of modified and / or updated projects; then, based on the operation requirements determined by the user instructions, a corresponding baseline is constructed, wherein the baseline includes a baseline category and a baseline configuration item; the baseline category is used to distinguish different baselines, and each baseline category includes at least one baseline configuration item; the baseline configuration item is identifiable information of the docked GitLab system, and the baseline configuration item is used to call the GitLab system to perform the operation behavior corresponding to the operation requirement; finally, the baseline is published to the GitLab system so as to call the GitLab system to perform the corresponding operation behavior on the project to be managed in the database, thereby realizing the project management function of the database. Compared with the prior art, since the method of the present application determines the project to be managed in the database by user instructions, it sets the baseline and publishes it to the GitLab system, thereby using the GitLab system to identify the baseline configuration items of the baseline and then automatically processes the project to be managed, reducing the need for manual operations in project identification, version management and baseline creation in the project management process, thereby reducing the workload and error probability, and solving the problem of complex and difficult operations and easy errors in the management of projects in the database by the prior art. At the same time, in the process of building the baseline, it is possible to support multiple baseline categories and configuration items, so as to ensure that when carrying out project management, it is possible to adapt to the needs and changes of different projects, making configuration management more flexible. In addition, in the process of carrying out management based on the baseline, the baseline configuration items are docked with the GitLab system, and the document management function of the GitLab system can be directly used to manage the project, without the need for additional compilation and setting of tools or scripts with document management, thereby saving the preparatory work before project management as a whole, and also saving the time and money of developing document management scripts or tools, and reducing the overall cost.

[0205] An embodiment of the present application provides a storage medium, which includes a stored program. When the program is running, the device where the storage medium is located is controlled to execute the above-mentioned database project management method.

[0206] The storage medium may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0207] An embodiment of the present application also provides a database project management device, which includes a storage medium; and one or more processors, wherein the storage medium is coupled to the processor, and the processor is configured to execute program instructions stored in the storage medium; when the program instructions are executed, the above-mentioned database project management method is executed.

[0208] An embodiment of the present application provides a device, which includes a processor, a memory, and a program stored in the memory and executable on the processor. When the processor executes the program, the following steps are implemented: determining a project to be managed in a database based on a user instruction, wherein the project is provided with a project identifier and a project version; wherein the project identifier includes at least one character; the project version is set based on a preset format, and the project version is used to distinguish between different batches of modified and / or updated projects; constructing a corresponding baseline based on the operational requirements determined by the user instruction, wherein the baseline includes a baseline category and a baseline configuration item; the baseline category is used to distinguish between different baselines, and each baseline category includes at least one baseline configuration item; the baseline configuration item is identifiable information of a connected GitLab system, and the baseline configuration item is used to call the GitLab system to perform operational behaviors corresponding to the operational requirements; publishing the baseline to the GitLab system so as to call the GitLab system to perform corresponding operational behaviors on the project to be managed in the database.

[0209] Furthermore, the project identifier is set based on a project identifier setting rule; wherein the project identifier setting rule is used to indicate that the types of characters when the user sets the project identifier include numbers, English and underscores, and the first character of the project identifier is a non-numeric character.

[0210] Furthermore, before determining the items to be managed in the database based on the user instruction, the method further includes:

[0211] When creating a new project in the project center of the database, fill in the basic information of the new project and set a project ID for the new project based on the project ID setting rules;

[0212] According to the preset format, a corresponding project version is set for the new project; wherein the format includes at least three fields, namely, a major version, a minor version, and a revision number; wherein the levels of the major version, the minor version, and the revision number decrease in sequence, and when the content of a higher-level field changes, the content of a lower-level field is cleared.

[0213] Furthermore, the preset format further includes at least one of the following fields, including: extended version, patch version, customized version, and compilation serial number;

[0214] The major version is used to indicate that it is incremented when the user performs an incompatible modification; the major version content is an integer in the range of 1-99, and the minor version content and revision number content are cleared when incrementing;

[0215] The minor version is used to indicate that it is incremented when a user adds a new backward-compatible feature. The minor version value ranges from 0 to 99, and the revision number is reset to zero when incremented.

[0216] The revision number is used to indicate that it is incremented when the user performs a backward compatibility fix, and the revision number is an integer ranging from 0 to 99;

[0217] The extended version further specifically includes emergency hot patches, emergency cold patches, and cumulative upgrade patches, wherein the value range of the content of the emergency hot patches, the value range of the content of the emergency cold patches, and the value range of the content of the cumulative upgrade patches are all integers between 1 and 99;

[0218] The customized version further specifically includes a customer customization number and a number that identifies the upgrade number of the customized version; wherein the content that identifies the customer customization number begins with the character C; the content that identifies the customer customization number includes a character that begins with U and an integer in the range of 1-99;

[0219] The compilation sequence number is determined based on any one of the build number, the timestamp, and the Commit ID.

[0220] Furthermore, the baseline further includes a baseline identifier, which is determined based on the project identifier, project version, baseline type, and baseline version; the baseline configuration item further includes a baseline configuration item identifier, which is determined based on the project identifier, project version, baseline configuration item, and baseline configuration item version;

[0221] The operation requirement determined based on the user instruction is used to construct a corresponding baseline, including:

[0222] Based on the project to be managed, obtaining a project identifier and a project version;

[0223] Determine a corresponding baseline configuration item based on the operation requirement, and determine a baseline type corresponding to the operation requirement based on a relationship between the baseline configuration item and the baseline category;

[0224] Obtain the baseline type, set the baseline version, and then generate the baseline identifier by combining the project identifier, project version, baseline type, and baseline version;

[0225] Setting a baseline configuration item version for the baseline configuration item corresponding to the operation requirement, and generating the baseline configuration item identifier based on the project identifier, project version, baseline configuration item, and baseline configuration item version;

[0226] The baseline is constructed based on the baseline identifier and the baseline configuration item identifier.

[0227] Furthermore, before publishing the baseline to the GitLab system so as to call the GitLab system to perform corresponding operations on the project to be managed in the database, the method further includes:

[0228] Call the GitLab system interface through the preset identity information to obtain the submission record of the project in the database, and obtain the address information corresponding to the project based on the database address, the submission identifier in the submission record, and the project identifier;

[0229] Publishing the baseline to the GitLab system so as to call the GitLab system to perform corresponding operations on the project to be managed in the database includes:

[0230] The baseline is published to the GitLab system so as to call the GitLab system and perform corresponding operation behaviors on the project to be managed in the database through the address information.

[0231] Furthermore, after publishing the baseline to the GitLab system, the method further includes:

[0232] A baseline tag is created by calling the GitLab system, wherein the content of the baseline tag is the baseline identifier of the published baseline, and the baseline tag is used to view baseline records and / or trace back the operation requirements corresponding to the baseline.

[0233] and / or,

[0234] When it is detected that the baseline has been changed, an update operation is performed on the published baseline based on the change behavior, and the update operation is used to increment the baseline version in the baseline identifier.

[0235] The present application also provides a computer program product, which, when executed on a data processing device, is suitable for executing program code that initializes the following method steps: determining a project to be managed in a database based on user instructions, wherein the project is provided with a project identifier and a project version; wherein the project identifier contains at least one character; the project version is set based on a preset format, and the project version is used to distinguish between different batches of modified and / or updated projects; based on the operation requirements determined by the user instructions, constructing a corresponding baseline, wherein the baseline includes a baseline category and a baseline configuration item; the baseline category is used to distinguish different baselines, and each baseline category includes at least one baseline configuration item; the baseline configuration item is identifiable information of the docked GitLab system, and the baseline configuration item is used to call the GitLab system to perform operation behaviors corresponding to the operation requirements; publishing the baseline to the GitLab system so as to call the GitLab system to perform corresponding operation behaviors on the project to be managed in the database.

[0236] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can 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 can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0237] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes 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 steps in the process. 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.

[0238] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work 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 The function specified in one or more boxes.

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

[0240] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0241] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0242] Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. The 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 disc read-only memory (CD-ROM), digital versatile disc (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 transitory computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0243] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

[0244] 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 take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the present application may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0245] The above are merely embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application should all be included within the scope of the claims of the present application.

Claims

1. A database project management method, characterized in that: include: Determining a project to be managed in a database based on a user instruction, wherein the project is provided with a project identifier and a project version; wherein the project identifier includes at least one character; and the project version is provided based on a preset format; Based on the operational requirements determined by the user instructions, a corresponding baseline is constructed, wherein the baseline includes a baseline category and baseline configuration items. The baseline category is used to distinguish different baselines, and each baseline category includes at least one baseline configuration item. The baseline configuration item is identifiable information of the connected GitLab system and is used to call the GitLab system to perform the operational behavior corresponding to the operational requirements. The baseline is published to the GitLab system so as to call the GitLab system to perform corresponding operation behaviors on the projects to be managed in the database.

2. The method according to claim 1, characterized in that The project identifier is set based on a project identifier setting rule; wherein the project identifier setting rule is used to instruct the user that the character types when setting the project identifier include numbers, English and underscores, and the first character of the project identifier is a non-numeric character.

3. The method according to claim 1, characterized in that Before determining the items to be managed in the database based on the user instruction, the method further includes: When creating a new project in the project center of the database, fill in the basic information of the new project and set a project ID for the new project based on the project ID setting rules; According to the preset format, a corresponding project version is set for the new project; wherein the format includes at least three fields, namely, a major version, a minor version, and a revision number; wherein the levels of the major version, the minor version, and the revision number decrease in sequence, and when the content of a higher-level field changes, the content of a lower-level field is cleared.

4. The method according to claim 3, characterized in that The preset format further includes at least one of the following fields, including: extended version, patch version, customized version, and compilation serial number; The major version is used to indicate that it is incremented when the user performs an incompatible modification; the major version content is an integer in the range of 1-99, and the minor version content and revision number content are cleared when incrementing; The minor version is used to indicate that it is incremented when a user adds a new backward-compatible feature. The minor version value ranges from 0 to 99, and the revision number is reset to zero when incremented. The revision number is used to indicate that it is incremented when the user performs a backward compatibility fix, and the revision number is an integer ranging from 0 to 99; The extended version further specifically includes emergency hot patches, emergency cold patches, and cumulative upgrade patches, wherein the value range of the content of the emergency hot patches, the value range of the content of the emergency cold patches, and the value range of the content of the cumulative upgrade patches are all integers between 1 and 99; The customized version further specifically includes a customer customization number and a number that identifies the upgrade number of the customized version; wherein the content that identifies the customer customization number begins with the character C; the content that identifies the customer customization number includes a character that begins with U and an integer in the range of 1-99; The compilation sequence number is determined based on any one of the build number, the timestamp, and the Commit ID.

5. The method according to claim 1, wherein The baseline also includes a baseline identifier, which is determined based on the project identifier, project version, baseline type, and baseline version; the baseline configuration item also includes a baseline configuration item identifier, which is determined based on the project identifier, project version, baseline configuration item, and baseline configuration item version; The operation requirement determined based on the user instruction is used to construct a corresponding baseline, including: Based on the project to be managed, obtaining a project identifier and a project version; Determine a corresponding baseline configuration item based on the operation requirement, and determine a baseline type corresponding to the operation requirement based on a relationship between the baseline configuration item and the baseline category; Obtain the baseline type, set the baseline version, and then generate the baseline identifier by combining the project identifier, project version, baseline type, and baseline version; Setting a baseline configuration item version for the baseline configuration item corresponding to the operation requirement, and generating the baseline configuration item identifier based on the project identifier, project version, baseline configuration item, and baseline configuration item version; The baseline is constructed based on the baseline identifier and the baseline configuration item identifier.

6. The method according to claim 1, characterized in that Before publishing the baseline to the GitLab system so as to call the GitLab system to perform corresponding operations on the project to be managed in the database, the method further includes: Call the GitLab system interface through the preset identity information to obtain the submission record of the project in the database, and obtain the address information corresponding to the project based on the database address, the submission identifier in the submission record, and the project identifier; Publishing the baseline to the GitLab system so as to call the GitLab system to perform corresponding operations on the project to be managed in the database includes: The baseline is published to the GitLab system so as to call the GitLab system and perform corresponding operation behaviors on the project to be managed in the database through the address information.

7. The method according to claim 6, characterized in that After publishing the baseline to the GitLab system, the method further includes: Create a baseline tag by calling the GitLab system, where the content of the baseline tag is the baseline identifier of the published baseline, and the baseline tag is used to view baseline records and / or backtrack to the corresponding operation requirements of the baseline; and / or, When it is detected that the baseline has been changed, an update operation is performed on the published baseline based on the change behavior, and the update operation is used to increment the baseline version in the baseline identifier.

8. A project management device for a database, characterized in that: include: A determining unit, configured to determine a project to be managed in a database based on a user instruction, wherein the project is provided with a project identifier and a project version; wherein the project identifier comprises at least one character; and the project version is provided based on a preset format; A construction unit is configured to construct a corresponding baseline based on the operation requirement determined by the user instruction, wherein the baseline includes a baseline category and baseline configuration items; the baseline category is used to distinguish different baselines, and each baseline category includes at least one baseline configuration item; the baseline configuration item is identifiable information of the connected GitLab system, and the baseline configuration item is used to call the GitLab system to perform the operation behavior corresponding to the operation requirement; A publishing unit is used to publish the baseline to the GitLab system so as to call the GitLab system to perform corresponding operation behaviors on the projects to be managed in the database.

9. A storage medium, characterized in that: The storage medium includes a stored program, wherein when the program is running, the device where the storage medium is located is controlled to execute the database project management method according to any one of claims 1 to 7.

10. A project management device for a database, characterized in that: The device includes a storage medium; and one or more processors, the storage medium is coupled to the processor, and the processor is configured to execute program instructions stored in the storage medium; when the program instructions are executed, the database project management method described in any one of claims 1 to 7 is executed.

Images