Version baseline management method, system, device and storage medium for composite products

Abstract

The embodiments of the present invention disclose a version baseline management method, system, device and storage medium for composite products, including: obtaining version baseline management requirements and drawing workflows, creating new products, services and versions according to the requirements, performing product integration on the newly created products and submitting the integrated products for review, detecting whether the product needs to be upgraded after approval, and if it needs to be upgraded, performing product upgrade and recording the upgraded product address; storing the upgraded product address in the product library, generating version description information in json format and continuing to circulate the workflow; exporting the complete version package after receiving the version export signal. The embodiments of the present invention propose to manage the application version throughout its life cycle with the application as the core and the attachments as the products, and to create end-to-end continuous delivery capabilities, thereby realizing automated baseline version management of composite products, improving iterative release efficiency, ensuring that iterative versions are controllable and traceable, and ensuring the reliability and stability of version products.

Description

Technical Field

[0001] Embodiments of the present invention relate to the technical field of performance management, and in particular to a version baseline management method, system, device and storage medium for a composite product. Background Art

[0002] Baseline is a term in configuration management, which refers to a set of document or source code versions at a specific stage of a project. These versions have been formally reviewed and approved to become a stable reference point in the project. Baselines are often used to ensure the reproducibility, traceability, and reporting capabilities of a project.

[0003] Currently, there is a lack of a unified version management platform for version management on the market, which makes it impossible to integrate requirements, defects, documents, codes, builds, and products. There is a lack of end-to-end version services, and there is a gap in the definition and management of each version, which makes it impossible to better review and trace the version.

[0004] Currently, more and more companies are beginning to apply the ToB delivery model. With the continuous iteration within the company and the increase in customer needs, the number of product versions continues to increase, the version baseline is becoming increasingly difficult to control, the R&D team is difficult to collaborate, and the delivery model becomes chaotic. Summary of the invention

[0005] To this end, embodiments of the present invention provide a version baseline management method, system, device and storage medium for composite products to solve the technical problems of high application integration complexity, chaotic configuration management and lack of tools for project integration.

[0006] In order to achieve the above purpose, the embodiment of the present invention provides the following technical solutions:

[0007] According to a first aspect of an embodiment of the present invention, a method for managing version baselines of a composite product is provided, the method comprising:

[0008] S1. Obtain the version baseline management requirements and draw a workflow, create new products, services and versions according to the version baseline management requirements, perform product integration on the newly created products and submit the integrated products for review to check whether they have been approved;

[0009] S2. If the product is approved, check whether it needs to be upgraded. If it needs to be upgraded, upgrade the product and record the upgraded product address.

[0010] S3. Store the upgraded product address in the product library, generate version description information in JSON format, and continue the workflow;

[0011] S4, detecting whether a version export signal is received, and if so, exporting a complete version package;

[0012] The product integration includes uploading products or automatically filling products into the version through the pipeline.

[0013] Furthermore, obtaining version baseline management requirements and drawing workflows also includes: customizing approval and promotion configurations.

[0014] Furthermore, new products, services and versions are created according to the version baseline management requirements, including:

[0015] Newly created products, services, and releases have features associated with them, code, and documentation.

[0016] Further, executing product upgrade and recording the upgraded product address includes:

[0017] Automatically identify product promotion warehouses and configure promotion strategies;

[0018] Real-time detection of whether the promotion is completed, and triggering the webhook if the promotion is completed;

[0019] The address of the product after the upgrade is completed is obtained and the address of the product is persisted.

[0020] Furthermore, executing product upgrade and recording the upgraded product address also includes:

[0021] Get an artifact from the development environment, push it into the version set through the pipeline, and store it in the development library;

[0022] Read the artifacts that need to be upgraded from the development library, perform the first upgrade, and write them to the procedural version library;

[0023] The version set includes the product line version set corresponding to each product.

[0024] Furthermore, executing product upgrade and recording the upgraded product address also includes:

[0025] Extract a product version from the procedural version library, deploy it through the pipeline, and then input it into the test environment for testing;

[0026] After passing the test, the product version is upgraded and stored in the pass version library;

[0027] Among them, the procedural version library and the pass version library together constitute the controlled library.

[0028] Further, executing product upgrade and recording the upgraded product address includes:

[0029] Get the required artifact version from the passable version library and write it to the production library;

[0030] Obtain the required artifact version from the production library, record the artifact address, and deploy the production environment through the pipeline.

[0031] According to a second aspect of an embodiment of the present invention, a version baseline management system for a composite product is provided, the system comprising:

[0032] The workflow drawing module is used to obtain the version baseline management requirements and draw the workflow, create new products, services and versions according to the version baseline management requirements, perform product integration on the newly created products and submit the integrated products for review to check whether they have been approved;

[0033] The upgrade module is used to detect whether the product needs to be upgraded if it is approved. If it needs to be upgraded, it will perform the upgrade and record the address of the upgraded product;

[0034] The storage module is used to store the upgraded product address in the product library, generate JSON-formatted version description information, and continue the workflow;

[0035] The export module is used to detect whether a version export signal is received, and if so, to export the complete version package;

[0036] The product integration includes uploading products or automatically filling products into the version through the pipeline.

[0037] According to a third aspect of an embodiment of the present invention, there is provided a version baseline management device for a composite product, the device comprising: a processor and a memory;

[0038] The memory is used to store one or more program instructions;

[0039] The processor is used to run one or more program instructions to execute the steps of a version baseline management method for a composite product as described in any one of the above items.

[0040] According to a fourth aspect of an embodiment of the present invention, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps of a version baseline management method for a composite product as described in any of the above items are implemented.

[0041] The embodiments of the present invention have the following advantages:

[0042] The embodiment of the present invention proposes to manage the application version throughout its life cycle with the application as the core and the attachments as the products, build end-to-end continuous delivery capabilities, and comprehensively upgrade the pipeline capabilities to form the best practices for B2B application integration under large-scale continuous delivery, solving the problems of high complexity of application integration, chaotic configuration management, and lack of tools for project integration. Products are promoted through intelligent algorithms, thereby achieving automated baseline version management of composite products, improving iterative release efficiency, better managing product version baselines, ensuring that iterative versions are controllable and traceable, and ensuring the reliability and stability of version products. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the implementation methods of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for the implementation methods or the description of the prior art. Obviously, the drawings in the following description are only exemplary, and for ordinary technicians in this field, other implementation drawings can be derived from the provided drawings without creative work.

[0044] The structures, proportions, sizes, etc. illustrated in this specification are only used to match the contents disclosed in the specification so as to facilitate understanding and reading by persons familiar with the technology. They are not used to limit the conditions under which the present invention can be implemented, and therefore have no substantial technical significance. Any structural modification, change in proportion or adjustment of size shall still fall within the scope of the technical contents disclosed in the present invention without affecting the effects and purposes that can be achieved by the present invention.

[0045] Figure 1 A schematic diagram of the logical structure of a version baseline management system for a composite product provided by an embodiment of the present invention;

[0046] Figure 2 A schematic diagram of a process flow of a composite product version baseline management method provided by an embodiment of the present invention;

[0047] Figure 3 A schematic diagram of a version management process of a version baseline management method for a composite product provided by an embodiment of the present invention;

[0048] Figure 4 A schematic diagram of the process of product promotion in a version baseline management method of a composite product provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0049] The following is a description of the implementation of the present invention by specific embodiments. People familiar with the art can easily understand other advantages and effects of the present invention from the contents disclosed in this specification. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0050] Currently, there is a lack of a unified version management platform for version management on the market, which makes it impossible to integrate requirements, defects, documents, codes, builds, and products. There is a lack of end-to-end version services, and there is a gap in the definition and management of each version, which makes it impossible to better review and trace the version.

[0051] Currently, more and more companies are beginning to apply the ToB delivery model. With the continuous iteration within the company and the increase in customer needs, the number of product versions continues to increase, the version baseline is becoming increasingly difficult to control, the R&D team is difficult to collaborate, and the delivery model becomes chaotic.

[0052] In order to solve the above-mentioned technical problems of high application integration complexity, chaotic configuration management, and lack of tools for project integration.

[0053] refer to Figure 1 The embodiment of the present invention discloses a version baseline management system for a composite product, the system comprising: a workflow drawing module 1; a promotion module 2; a storage module 3; and an export module 4.

[0054] This system proposes to manage the application version throughout its life cycle with the application as the core and the attachments as the products. The version flow workflow can be customized, and approval, promotion and other functions can be configured in the workflow. It supports multiple approval modes: single signature, joint signature, custom signature, etc., to achieve refined approval; it supports multiple approval types: designated person, designated role, etc., supports related matters, documents, codes, etc. In the version flow process, according to the intelligent algorithm, it automatically identifies the warehouse that needs to be promoted and automatically configures it. The product promotion process is fully automated to ensure a single trusted source. The promotion is automatically called back after completion, and the address of the upgraded product is recorded and traceable. It supports one-click export of the complete version offline package, and supports exporting the full information of the current version in json format.

[0055] Corresponding to the above disclosed composite product version baseline management system, the embodiment of the present invention further discloses a composite product version baseline management method. The following describes in detail the composite product version baseline management method disclosed in the embodiment of the present invention in combination with the above described composite product version baseline management system.

[0056] refer to Figure 2 and Figure 3The present invention discloses a version baseline management method for a composite product, the method comprising: S1, obtaining version baseline management requirements and drawing a workflow, creating new products, services and versions according to the version baseline management requirements, performing product integration on the newly created products and submitting the integrated products for review, and detecting whether the approval is passed; S2, if the approval is passed, detecting whether the product needs to be upgraded, if it needs to be upgraded, performing product upgrade and recording the upgraded product address; S3, storing the upgraded product address in the product library, generating json formatted version description information and continuing the workflow; S4, detecting whether a version export signal is received, and if the version export signal is received, exporting the complete version package.

[0057] The product integration includes uploading products or automatically filling products into the version through the pipeline.

[0058] The embodiment of the present invention can generate version description information in JSON format, and can also export the complete version package with one click.

[0059] Furthermore, obtaining version baseline management requirements and drawing workflows also includes: customizing approval and promotion configurations.

[0060] Furthermore, new products, services and versions are created according to the version baseline management requirements, including: the new products, services and versions have the functions of associating matters, codes and documents.

[0061] Furthermore, product promotion is executed and the product address after promotion is recorded, including: automatically identifying the product promotion warehouse and configuring the promotion strategy; real-time detection of whether the promotion is completed, and triggering the webhook if the promotion is completed; obtaining the product address after the promotion is completed and persisting the product address.

[0062] For further information, see Figure 4 , executing product promotion and recording the address of the upgraded product, also includes: obtaining a product through the development environment, pushing the product into the version set through the pipeline and storing it in the development library; reading the product that needs to be promoted from the development library and performing the first promotion and writing it into the procedural version library.

[0063] The version set includes the product line version set corresponding to each product.

[0064] Furthermore, executing product promotion and recording the address of the upgraded product also includes: extracting a product version from the procedural version library, deploying it through the pipeline, and inputting it into the test environment for testing; after passing the test, the product version is promoted and stored in the pass version library; wherein the procedural version library and the pass version library together constitute a controlled library.

[0065] In the embodiment of the present invention, the pass version library is also called a quasi-production library.

[0066] Furthermore, executing product promotion and recording the address of the upgraded product includes: obtaining the required product version from the pass version library and writing it into the production library; obtaining the required product version from the production library, recording the product address and deploying the production environment through the pipeline.

[0067] The embodiments of the present invention have the following advantages:

[0068] 1) Innovative software delivery model, defining a new version baseline management method;

[0069] 2) With applications as the core and upgrades as the core process, we ensure a single trusted source for products;

[0070] 3) Realize refined permission control based on the configured approval mode;

[0071] 4) Automatically configure various product warehouses based on intelligent algorithms to achieve fully automated product promotion;

[0072] 5) Webhook message sending, which can connect with various platforms and send message notifications.

[0073] In addition, an embodiment of the present invention also provides a version baseline management device for a composite product, the device comprising: a processor and a memory; the memory is used to store one or more program instructions; the processor is used to run one or more program instructions to execute the steps of a version baseline management method for a composite product as described in any of the above items.

[0074] In addition, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of a version baseline management method for a composite product as described in any of the above items are implemented.

[0075] In the embodiment of the present invention, the processor may be an integrated circuit chip having the signal processing capability. The processor may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0076] The methods, steps and logic block diagrams disclosed in the embodiments of the present invention can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiments of the present invention can be directly embodied as a hardware decoding processor for execution, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The processor reads the information in the storage medium and completes the steps of the above method in combination with its hardware.

[0077] The storage medium may be a memory, which may be, for example, a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memory.

[0078] Among them, the non-volatile memory can be a read-only memory (ROM), a programmable ROM (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory.

[0079] The volatile memory may be a random access memory (RAM) which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM).

[0080] The storage media described in the embodiments of the present invention are intended to include, but are not limited to, these and any other suitable types of memory.

[0081] Those skilled in the art will appreciate that in one or more of the above examples, the functions described in the present invention can be implemented using a combination of hardware and software. When software is used, the corresponding functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any media that facilitates the transmission of computer programs from one place to another. Storage media can be any available media that can be accessed by general or special-purpose computers.

[0082] Although the present invention has been described in detail above by general description and specific embodiments, it is obvious to those skilled in the art that some modifications or improvements can be made to the present invention. Therefore, these modifications or improvements made without departing from the spirit of the present invention all belong to the scope of protection claimed by the present invention.

Claims

1. A method for managing version baselines of composite products, characterized in that: The method comprises: S1. Obtain the version baseline management requirements and draw a workflow, create new products, services and versions according to the version baseline management requirements, perform product integration on the newly created products and submit the integrated products for review to check whether they have been approved; S2. If the product is approved, check whether it needs to be upgraded. If it needs to be upgraded, upgrade the product and record the upgraded product address. S3. Store the upgraded product address in the product library, generate version description information in JSON format, and continue the workflow; S4, detecting whether a version export signal is received, and if so, exporting a complete version package; The product integration includes uploading products or automatically filling products into the version through the pipeline; Execute product upgrades and record the upgraded product addresses, including: Automatically identify product promotion warehouses and configure promotion strategies; Real-time detection of whether the promotion is completed, and triggering the webhook if the promotion is completed; Obtain the address of the product after the upgrade is completed and persist the address of the product; Execute product upgrade and record the upgraded product address, including: Get an artifact from the development environment, push it into the version set through the pipeline, and store it in the development library; Read the artifacts that need to be upgraded from the development library, perform the first upgrade, and write them to the procedural version library; The version set includes the product line version set corresponding to each product; Execute product upgrade and record the upgraded product address, including: Extract a product version from the procedural version library, deploy it through the pipeline, and then input it into the test environment for testing; After passing the test, the product version is upgraded and stored in the pass version library; Among them, the procedural version library and the pass version library together constitute the controlled library; Execute product upgrades and record the upgraded product addresses, including: Get the required artifact version from the passable version library and write it to the production library; Obtain the required artifact version from the production library, record the artifact address, and deploy the production environment through the pipeline.

2. A method for managing version baselines of a composite product according to claim 1, characterized in that: Obtain version baseline management requirements and draw workflows, including: custom approval and promotion configurations.

3. A method for managing version baselines of a composite product as claimed in claim 2, characterized in that: Create new products, services, and versions based on the version baseline management requirements, including: Newly created products, services, and releases have features associated with them, code, and documentation.

4. A version baseline management system for composite products, characterized in that: The system comprises: The workflow drawing module is used to obtain the version baseline management requirements and draw the workflow, create new products, services and versions according to the version baseline management requirements, perform product integration on the newly created products and submit the integrated products for review to check whether they have been approved; The upgrade module is used to detect whether the product needs to be upgraded if it is approved. If it needs to be upgraded, it will perform the upgrade and record the address of the upgraded product; The storage module is used to store the upgraded product address in the product library, generate JSON-formatted version description information, and continue the workflow; The export module is used to detect whether a version export signal is received, and if so, to export the complete version package; The product integration includes uploading products or automatically filling products into the version through the pipeline; Execute product upgrades and record the upgraded product addresses, including: Automatically identify product promotion warehouses and configure promotion strategies; Real-time detection of whether the promotion is completed, and triggering the webhook if the promotion is completed; Obtain the address of the product after the upgrade is completed and persist the address of the product; Execute product upgrade and record the upgraded product address, including: Get an artifact from the development environment, push it into the version set through the pipeline, and store it in the development library; Read the artifacts that need to be upgraded from the development library, perform the first upgrade, and write them to the procedural version library; The version set includes the product line version set corresponding to each product; Execute product upgrade and record the upgraded product address, including: Extract a product version from the procedural version library, deploy it through the pipeline, and then input it into the test environment for testing; After passing the test, the product version is upgraded and stored in the pass version library; Among them, the procedural version library and the pass version library together constitute the controlled library; Execute product upgrades and record the upgraded product addresses, including: Get the required artifact version from the passable version library and write it to the production library; Obtain the required artifact version from the production library, record the artifact address, and deploy the production environment through the pipeline.

5. A version baseline management device for a composite product, characterized in that: The device comprises: a processor and a memory; The memory is used to store one or more program instructions; The processor is used to run one or more program instructions to execute the steps of the version baseline management method of a composite product as described in any one of claims 1 to 3.

6. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of a version baseline management method for a composite product as claimed in any one of claims 1 to 3.

Images