Project management method, device, equipment, medium and program product

Abstract

The invention relates to the technical field of financial science and technology, and discloses a project management method, device and equipment, a medium and a program product. The method comprises the steps of obtaining a to-be-tested item and a corresponding to-be-tested version label; according to the to-be-tested version tag and a preset tag format, obtaining a to-be-tested service interface identifier, and according to the to-be-tested service interface identifier, searching to obtain a target item associated with the to-be-tested item and a target version tag corresponding to the target item; and according to the target item and the corresponding target version tag, testing a to-be-tested version corresponding to the to-be-tested version tag, and obtaining a test result. According to the scheme of the embodiment, by setting the unified label system, the synchronization problem in public dependence and upstream and downstream relations in the multi-version warehouse process can be solved, different projects can be submitted according to respective version plans, and the operation and maintenance cost can be reduced.

Description

Technical Field

[0001] The present invention relates to the field of financial technology, and in particular to a project management method, device, equipment, medium and program product. Background Art

[0002] At present, distributed source code management is generally used to develop large projects. However, as the scale of projects becomes larger and larger, using a single repository to manage projects will be accompanied by a large number of conflicts and modifications; and using a single repository to manage projects also violates the "single responsibility" principle. To solve this problem, a multi-version repository method is often used to manage numerous projects and services, and these projects will eventually be built separately as needed, and then aggregated into a complete large project.

[0003] When using a multi-version repository for project management, each service can use its own iteration cycle, and submission permissions can be managed in a way that minimizes authorization. However, there is a problem of service version asynchrony between the services after this split. For example, when the interface parameter list provided by a service changes, if the caller or user does not make adjustments in time, it will cause downstream applications or services to report errors. Similarly, when publishing related modifications, the amount of modification to the application that cooperates with the modification is often less than the amount of modification to the called party. In the process of continuous integration, if the downstream application completes the modification first, and the service interface has not yet released a new version, the calling process will be interrupted. Summary of the invention

[0004] The present invention provides a project management method, device, equipment, medium and program product, which can solve the synchronization problems in common dependencies and upstream and downstream relationships in a multi-version warehouse process. Different projects can be submitted according to their respective version plans, which can reduce operation and maintenance costs.

[0005] According to one aspect of the present invention, there is provided a project management method, comprising:

[0006] Get the project to be tested and the corresponding version label to be tested;

[0007] According to the version tag to be tested and the preset tag format, the service interface identifier to be tested is obtained, and according to the service interface identifier to be tested, a target project associated with the project to be tested and a target version tag corresponding to the target project are searched and obtained;

[0008] According to the target project and the corresponding target version tag, the version to be tested corresponding to the version to be tested tag is tested to obtain a test result.

[0009] According to another aspect of the present invention, there is provided a project management device, comprising:

[0010] The module for obtaining the tag of the version to be tested is used to obtain the item to be tested and the corresponding tag of the version to be tested;

[0011] A target version label search module is used to obtain the service interface identifier to be tested according to the version label to be tested and a preset label format, and to search for a target project associated with the project to be tested and a target version label corresponding to the target project according to the service interface identifier to be tested;

[0012] The version testing module is used to test the version to be tested corresponding to the version tag to be tested according to the target project and the corresponding target version tag, and obtain the test result.

[0013] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0014] at least one processor; and

[0015] a memory communicatively connected to the at least one processor; wherein,

[0016] The memory stores a computer program that can be executed by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the project management method described in any embodiment of the present invention.

[0017] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program, and the computer program is used to enable a processor to implement the project management method described in any embodiment of the present invention when executed.

[0018] According to another aspect of the present invention, a computer program product is provided, comprising a computer program, wherein when the computer program is executed by a processor, the project management method according to any embodiment of the present invention is implemented.

[0019] The technical solution of the embodiment of the present invention obtains the project to be tested and the corresponding version label to be tested; obtains the service interface identifier to be tested according to the version label to be tested and the preset label format, and searches for the target project associated with the project to be tested and the target version label corresponding to the target project according to the service interface identifier to be tested; tests the version to be tested corresponding to the version label to be tested according to the target project and the corresponding target version label to obtain the test result; by setting a unified label system, the synchronization problem in the common dependency and upstream and downstream relationship in the multi-version warehouse process can be solved, different projects can be submitted according to their respective version plans, and the operation and maintenance cost can be reduced.

[0020] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0022] Figure 1 is a flowchart of a project management method provided according to Embodiment 1 of the present invention;

[0023] Figure 2 is a structural diagram of a project management device provided according to Embodiment 2 of the present invention;

[0024] Figure 3 It is a structural schematic diagram of an electronic device for implementing the project management method according to an embodiment of the present invention. DETAILED DESCRIPTION

[0025] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0026] It should be noted that the terms "first", "second", "target", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0027] Embodiment 1

[0028] Figure 1A flowchart of a project management method is provided for the first embodiment of the present invention. This embodiment is applicable to the situation of managing project versions during project development. The method can be executed by a project management device. The project management device can be implemented in the form of hardware and / or software. Typically, the project management device can be configured in an electronic device, such as a computer device or a server. Figure 1 As shown, the method includes:

[0029] S110: Obtain the project to be tested and the corresponding version label to be tested.

[0030] In this embodiment, a unified build label can be established for the project version, and a complete label system can be established for the project of the multi-version warehouse. For example, the version label is 1.2.4, and 1.2 represents the unaffected version of the entire project, that is, the version of all services, which means that in the upstream and downstream relationship, version 1.2 is a common service version, that is, it will not publish content that affects the call relationship. When the interface or service has a new external interface, it is represented as 1.3. 1.2.4 represents a small version of each warehouse, which only means that the modified content has no impact on the upstream and downstream services. It can be an internal adjustment, transformation, etc. By using this build label, related services can be released without affecting the progress of their respective version plans.

[0031] Specifically, the version to be tested corresponding to the project to be tested uploaded by the user and the version to be tested label corresponding to the version to be tested can be directly obtained on the relevant system page. Alternatively, the version to be tested label corresponding to the version to be tested of the project to be tested can be automatically generated according to the project test configuration information uploaded by the user and the preset label generation rules. Among them, the project version can be the current project program file, and the version label can be the version number of the project version generated based on the unified label format, and the project version corresponds to the version label one by one.

[0032] S120: Obtain a service interface identifier to be tested according to the version tag to be tested and a preset tag format, and search for a target project associated with the project to be tested and a target version tag corresponding to the target project according to the service interface identifier to be tested.

[0033] Specifically, after obtaining the version tag to be tested, the content of the version tag to be tested can be parsed based on the preset tag format to extract the service interface identifier to be tested contained therein. The preset tag format defines the number of tag bits contained in the version tag and the data type represented by each tag bit. For example, in the preset tag format, the number of tag bits is 3, and each bit is separated by the character ".", and the second bit can represent the service interface identifier. Then, in the existing version tags corresponding to each existing project, the target existing version tag with the same service interface identifier to be tested as the version tag to be tested can be found, and based on the target existing version tag, the target project associated with the project to be tested and the corresponding target version tag can be determined.

[0034] S130: According to the target project and the corresponding target version tag, test the version to be tested corresponding to the version to be tested tag to obtain a test result.

[0035] In this embodiment, the target project and the project to be tested have the same service interface identifier, indicating that the two projects jointly provide an external service interface. Therefore, when the version to be tested needs to be tested, the service interface of the project version corresponding to the target version label needs to be used. Specifically, the project version corresponding to the target version label can be used as an auxiliary file of the version to be tested, and the project version test can be carried out in conjunction with it to obtain the test results. This embodiment does not specifically limit the method of project version testing.

[0036] Optionally, testing the version to be tested corresponding to the version to be tested tag according to the target project and the corresponding target version tag, and obtaining the test result may include:

[0037] According to the target project and the corresponding target version tag, the target version corresponding to the target project is obtained, and based on the target version, the version to be tested corresponding to the version to be tested tag is tested to obtain a test result.

[0038] Specifically, after determining the target project and target version tag, the corresponding target version file can be found and the service interface provided by the target version file can be used to assist in testing the version to be tested and obtain the test results. The test results may include whether the test passed, error code, error description information, etc.

[0039] The advantage of the above settings is that it can solve the synchronization problems in public dependencies and upstream and downstream relationships in the multi-version repository process, allowing different projects to be developed in different iteration cycles, and ensuring that the test environment of different projects is always available.

[0040] In this embodiment, by establishing service version labels and planning for a multi-version repository, when upstream and downstream services are not fully released, they can be deployed according to the old version, and the released services can enter the integration test phase in advance; when the upstream and downstream applications have completed the version release, the corresponding containers are automatically built, and the services that have entered the integration test are replaced according to the corresponding versions to ensure that all services and functions are available during the entire testing process.

[0041] The technical solution of the embodiment of the present invention obtains the project to be tested and the corresponding version label to be tested; obtains the service interface identifier to be tested according to the version label to be tested and the preset label format, and searches for the target project associated with the project to be tested and the target version label corresponding to the target project according to the service interface identifier to be tested; tests the version to be tested corresponding to the version label to be tested according to the target project and the corresponding target version label to obtain the test result; by setting a unified label system, the synchronization problem in the common dependency and upstream and downstream relationship in the multi-version warehouse process can be solved, different projects can be submitted according to their respective version plans, and the operation and maintenance cost can be reduced.

[0042] In an optional implementation of this embodiment, obtaining the to-be-tested item and the corresponding to-be-tested version label may include:

[0043] According to the project test configuration request, the project test configuration information is obtained, and according to the project test configuration information, the project to be tested and the corresponding version to be tested, as well as the update type and historical version label corresponding to the version to be tested are obtained;

[0044] The historical version tag is updated according to the update type, and the version tag to be tested corresponding to the version to be tested is obtained.

[0045] In this embodiment, the relationship between the previous and next items of the project version label and the highest and lowest labels can be established, so as to use the build label to clearly display a linear development progress. When the project version test is required, the label value of the corresponding label position can be modified according to the current update type to obtain the label of the version to be tested corresponding to the current version to be tested.

[0046] The update type may include internal modification update, external service interface update and / or complete demand chain update. In this embodiment, a correspondence between the update type and the tag bit of the version tag can be established in advance, so that when the version tag is updated, only the tag value of the tag bit corresponding to the update type needs to be updated to obtain the updated version tag.

[0047] The advantage of the above settings is that the label system can be applied to different types of project updates, covering all scenarios of project development.

[0048] Specifically, first, the project test configuration information entered by the user in the system page can be obtained, and the contents of each field of the project test configuration information can be extracted to obtain the identification of the project to be tested, the version file to be tested, the update type and the historical version tag. Among them, the historical version tag can be the version tag corresponding to the previous project version of the version to be tested. Then, the tag value of the tag bit corresponding to the current update type in the historical version tag can be upgraded, and the updated historical version tag can be used as the version tag to be tested.

[0049] The advantage of the above settings is that it can clearly display the progress of project development and intuitively display the content of each version update.

[0050] Optionally, updating the historical version tag according to the update type to obtain the version tag to be tested corresponding to the version to be tested may include:

[0051] According to the update type, a target tag bit is obtained, and in the historical version tag, a historical tag value corresponding to the target tag bit is extracted;

[0052] An updated label value corresponding to the historical label value is obtained, and the historical label value corresponding to the target label position in the historical version label is replaced with the updated label value to obtain the version label to be tested.

[0053] In a specific example, in the preset label format, the number of label bits is 3. If the update type is an internal modification update, the label value of the third label bit is modified; if the update type is an external service interface update, the label value of the second label bit is modified; if the update type is a complete demand chain update, the label value of the first label bit is modified. When the label value of the second label bit is the same, it means that the interface between the projects is still a usable relationship. For example, x.2.x means finding a matching service interface, and 1.x.2 means the updated iterative version of the project.

[0054] Secondly, when updating the label value, the historical label value can be increased by 1 to obtain the updated label value. For example, if the update type is external service interface update, the target label is the second label, and the historical version label is 1.2.3, then the historical label value corresponding to the target label is 2, the updated label value is 3, and the version label to be tested is 1.3.3.

[0055] The advantage of the above settings is that the relationship between the previous and next items of the version tags can be established, and the establishment of a continuous integration deployment pipeline can be realized.

[0056] Optionally, in production and test environments, the labeling scheme of this embodiment can be used to build a continuous integration pipeline. For example, the development build label is 2, and the service interface labels of all version repositories are 3 and 4. At this time, the version on the deployment pipeline of the entire test environment is 2.3.{max}. Similarly, it can be confirmed that the version of the production environment is 1.3.{max}.

[0057] In this embodiment, multiple versions of applications can be easily built by deploying the pipeline, and the cost of version rollback and grayscale testing can be reduced by comparing tags.

[0058] In another optional implementation of this embodiment, searching for a target project associated with the project to be tested and a target version tag corresponding to the target project according to the service interface identifier to be tested may include:

[0059] Obtain each existing project and the corresponding existing version tag, and extract the existing service interface identifier corresponding to each existing version tag according to a preset tag format;

[0060] The service interface identifier to be tested is matched and detected with each of the existing service interface identifiers to obtain a target existing service interface identifier that matches the service interface identifier to be tested, and the existing version label and existing project corresponding to the target existing service interface identifier are used as the target version label and target project, respectively.

[0061] In this embodiment, when there are two or more projects that jointly provide an external service interface, a matching test of the service interface identifier can be performed to find an existing project that matches the project to be tested and an existing version that matches the version to be tested. If it is detected that the service interface identifiers of two version labels are the same, it can be determined that the two version labels match.

[0062] In a specific example, there are two projects, A and B, which jointly provide an external service interface. The production version tag of project A is 1.2.7, and the test version tags are 2.2.9 and 2.3.11. The production version tags of project B are 1.2.8 and 1.3.8, and the test version tags are 2.3.10 and 2.4.10. The production build versions of A and B are 1.2.7 and 1.2.8 respectively, and the build versions of the test environment are 2.2.9 and 2.3.10 respectively.

[0063] At this time, the iteration cycle of Project B is faster than that of Project A. Project A needs to use the service interface of Project B's version x.2.y to test its own version 2.2.9. At the same time, versions 2.3.11 and 2.3.10 are also included in the parallel test versions. When version 2.2.9 of Project A is put into production, the production build versions are 2.2.9 and 1.2.8 respectively. At this time, the two projects can be developed in different iteration cycles. Even if the version of Project B is much higher than that of Project A, the test environment of Project A can be guaranteed to be always available.

[0064] Secondly, when projects A and B need to release production patches, they also iterate their current versions separately without considering the corresponding relationship. When project B needs to release a new service interface that affects project A, the defined build tag is version x.3.0. As for project A, the modification related to project B has not been completed, so its version tag is the previous version x.2.y. At this time, in the build pipeline, when packaging the completed projects, you only need to find the minimum tag, and then obtain the latest version of all projects based on the tag value of the second tag position.

[0065] The benefit of the above settings is that they can help testers establish a minimal test scope, and if the modification has no impact on the periphery of the application, it can be delivered quickly.

[0066] In this embodiment, by establishing a unified labeling system, the scope of influence among the entire project can be known, and a single version repository can be used to reduce operation and maintenance costs; secondly, it can help developers quickly enter the next iteration cycle without worrying about the negative impact of functional modifications of other dependent projects on the development progress.

[0067] Embodiment 2

[0068] Figure 2 This is a schematic diagram of the structure of a project management device provided in Embodiment 2 of the present invention. Figure 2 As shown, the device includes: a to-be-tested version label acquisition module 210, a target version label search module 220 and a version test module 230; wherein,

[0069] The to-be-tested version label acquisition module 210 is used to acquire the to-be-tested item and the corresponding to-be-tested version label;

[0070] The target version label search module 220 is used to obtain the service interface identifier to be tested according to the version label to be tested and the preset label format, and to search for the target project associated with the project to be tested and the target version label corresponding to the target project according to the service interface identifier to be tested;

[0071] The version testing module 230 is used to test the version to be tested corresponding to the version tag to be tested according to the target project and the corresponding target version tag, and obtain the test result.

[0072] The technical solution of the embodiment of the present invention obtains the project to be tested and the corresponding version label to be tested; obtains the service interface identifier to be tested according to the version label to be tested and the preset label format, and searches for the target project associated with the project to be tested and the target version label corresponding to the target project according to the service interface identifier to be tested; tests the version to be tested corresponding to the version label to be tested according to the target project and the corresponding target version label to obtain the test result; by setting a unified label system, the synchronization problem in the common dependency and upstream and downstream relationship in the multi-version warehouse process can be solved, different projects can be submitted according to their respective version plans, and the operation and maintenance cost can be reduced.

[0073] Optionally, the to-be-tested version label acquisition module 210 is specifically used to acquire project test configuration information according to the project test configuration request, and acquire the to-be-tested project and the corresponding to-be-tested version, as well as the update type and historical version label corresponding to the to-be-tested version according to the project test configuration information;

[0074] The historical version tag is updated according to the update type, and the version tag to be tested corresponding to the version to be tested is obtained.

[0075] Optionally, the to-be-tested version tag acquisition module 210 is specifically configured to acquire a target tag bit according to the update type, and extract a historical tag value corresponding to the target tag bit from the historical version tag;

[0076] An updated label value corresponding to the historical label value is obtained, and the historical label value corresponding to the target label position in the historical version label is replaced with the updated label value to obtain the version label to be tested.

[0077] Optionally, update types include internal modification updates, external service interface updates, and / or complete demand chain updates.

[0078] Optionally, the target version tag search module 220 is specifically used to obtain each existing project and the corresponding existing version tag, and extract the existing service interface identifier corresponding to each existing version tag according to a preset tag format;

[0079] The service interface identifier to be tested is matched and detected with each of the existing service interface identifiers to obtain a target existing service interface identifier that matches the service interface identifier to be tested, and the existing version label and existing project corresponding to the target existing service interface identifier are used as the target version label and target project, respectively.

[0080] Optionally, the version testing module 230 is specifically used to obtain the target version corresponding to the target project according to the target project and the corresponding target version tag, and test the version to be tested corresponding to the version to be tested tag based on the target version to obtain the test result.

[0081] The project management device provided in the embodiment of the present invention can execute the project management method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0082] In the technical solution of the present disclosure, the collection, storage, use, processing, transmission, provision and disclosure of user personal information involved are in compliance with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0083] Embodiment 3

[0084] Figure 3 A schematic diagram of the structure of an electronic device 30 that can be used to implement an embodiment of the present invention is shown. The electronic device 30 is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device 30 can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.

[0085] like Figure 3 As shown, the electronic device 30 includes at least one processor 31, and a memory connected to the at least one processor 31, such as a read-only memory (ROM) 32, a random access memory (RAM) 33, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 31 can perform various appropriate actions and processes according to the computer program stored in the read-only memory 32 or the computer program loaded from the storage unit 38 to the random access memory 33. In the RAM 33, various programs and data required for the operation of the electronic device 30 can also be stored. The processor 31, the ROM 32 and the RAM 33 are connected to each other through a bus 34. The input / output (I / O) interface 35 is also connected to the bus 34.

[0086] A number of components in the electronic device 30 are connected to the I / O interface 35, including: an input unit 36, such as a keyboard, a mouse, etc.; an output unit 37, such as various types of displays, speakers, etc.; a storage unit 38, such as a disk, an optical disk, etc.; and a communication unit 39, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 39 allows the electronic device 30 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0087] The processor 31 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 31 include, but are not limited to, a central processing unit, a graphics processing unit, various special artificial intelligence computing chips, various processors running machine learning model algorithms, digital signal processors, and any appropriate processors, controllers, microcontrollers, etc. The processor 31 executes the various methods and processes described above, such as the project management method.

[0088] In some embodiments, the project management method may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 38. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 30 via the ROM 32 and / or the communication unit 39. When the computer program is loaded into the RAM 33 and executed by the processor 31, one or more steps of the project management method described above may be performed. Alternatively, in other embodiments, the processor 31 may be configured to perform the project management method in any other suitable manner (e.g., by means of firmware).

[0089] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays, application specific integrated circuits, application specific standard products, systems on a chip, load programmable logic devices, computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0090] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0091] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, device, or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory, a read-only memory, an erasable programmable read-only memory, an optical fiber, a portable compact disk read-only memory, an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0092] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device 30 having: a display device (e.g., a cathode ray tube or a liquid crystal display) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or a trackball) through which the user can provide input to the electronic device 30. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0093] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local area networks, wide area networks, blockchain networks, and the Internet.

[0094] A computing system may include clients and servers. Clients and servers are generally remote from each other and typically interact through a communication network. The relationship of client and server is generated by computer programs running on respective computers and having a client-server relationship to each other. The server may be a cloud server.

[0095] This embodiment may also include a computer program product, which includes a computer program. When the computer program is executed by a processor, it implements the project management method provided by any embodiment of the present invention.

[0096] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0097] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A project management method, characterized in that: include: Get the project to be tested and the corresponding version label to be tested; According to the version tag to be tested and the preset tag format, the service interface identifier to be tested is obtained, and according to the service interface identifier to be tested, a target project associated with the project to be tested and a target version tag corresponding to the target project are searched and obtained; According to the target project and the corresponding target version tag, the version to be tested corresponding to the version to be tested tag is tested to obtain a test result.

2. The method according to claim 1, characterized in that: Get the project to be tested and the corresponding version tag to be tested, including: According to the project test configuration request, the project test configuration information is obtained, and according to the project test configuration information, the project to be tested and the corresponding version to be tested, as well as the update type and historical version label corresponding to the version to be tested are obtained; The historical version tag is updated according to the update type, and the version tag to be tested corresponding to the version to be tested is obtained.

3. The method according to claim 2, characterized in that According to the update type, the historical version tag is updated to obtain the version tag to be tested corresponding to the version to be tested, including: According to the update type, a target tag bit is obtained, and in the historical version tag, a historical tag value corresponding to the target tag bit is extracted; An updated label value corresponding to the historical label value is obtained, and the historical label value corresponding to the target label position in the historical version label is replaced with the updated label value to obtain the version label to be tested.

4. The method according to claim 2 or 3, characterized in that: Update types include internal modification updates, external service interface updates, and / or complete demand chain updates.

5. The method according to claim 1, characterized in that According to the service interface identifier to be tested, a target project associated with the project to be tested and a target version tag corresponding to the target project are searched and obtained, including: Obtain each existing project and the corresponding existing version tag, and extract the existing service interface identifier corresponding to each existing version tag according to a preset tag format; The service interface identifier to be tested is matched and detected with each of the existing service interface identifiers to obtain a target existing service interface identifier that matches the service interface identifier to be tested, and the existing version label and existing project corresponding to the target existing service interface identifier are used as the target version label and target project, respectively.

6. The method according to claim 1, characterized in that According to the target project and the corresponding target version tag, testing the version to be tested corresponding to the version to be tested tag to obtain the test result includes: According to the target project and the corresponding target version tag, the target version corresponding to the target project is obtained, and based on the target version, the version to be tested corresponding to the version to be tested tag is tested to obtain a test result.

7. A project management device, characterized in that: include: The module for obtaining the tag of the version to be tested is used to obtain the item to be tested and the corresponding tag of the version to be tested; A target version label search module is used to obtain the service interface identifier to be tested according to the version label to be tested and a preset label format, and to search for a target project associated with the project to be tested and a target version label corresponding to the target project according to the service interface identifier to be tested; The version testing module is used to test the version to be tested corresponding to the version tag to be tested according to the target project and the corresponding target version tag, and obtain the test result.

8. An electronic device, characterized in that: The electronic device comprises: at least one processor, and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the project management method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and the computer program is used to enable a processor to implement the project management method according to any one of claims 1 to 6 when executed.

10. A computer program product, characterized in that The invention comprises a computer program, which implements the project management method according to any one of claims 1 to 6 when executed by a processor.

Images