A software product release method

Abstract

The embodiment of the specification discloses a software product publishing method, comprising: when a software product is specified to be published, configuration information corresponding to the specified software product is determined, the configuration information comprising version definition, publishing strategy configuration, product publishing unit definition, source code repository configuration in the product publishing unit, publishing context, publishing action configuration, publishing action and publishing strategy relationship configuration, product publishing record, and publishing parameter configuration; the product publishing unit definition is used to define a publishing unit of the specified software product; the source code repository configuration in the product publishing unit is used to define a position of a source code repository in the publishing unit of the specified software product; the publishing context is used to record publishing related information of the publishing unit; the publishing action configuration is used to configure related information of a publishing action; the publishing action and publishing strategy relationship configuration is used to determine a publishing action corresponding to a publishing strategy and an execution sequence of the publishing action; and the configuration information is used to realize publishing of the specified software product.

Description

Technical Field

[0001] This specification relates to the field of computer technology, and in particular to a method for releasing a software product. Background Technology

[0002] With the development of enterprise digital transformation, higher demands are being placed on business collaboration. It is no longer just about collaboration between internal departments, but also about business collaboration between enterprises. This requires a large software product to not only have an intranet part to handle internal business, but also a public network Software-as-a-Service (SaaS) part. These two parts have significantly different requirements for software product release. In addition, a large software product usually has multiple business domains, each business domain has multiple modules, and each module has multiple business object units. Therefore, a software product has multiple business object units. If the source code repository is defined at the granularity of business object units, there will be multiple repositories. The pre-release checks, release documentation preparation, branch migration, compilation and construction, and tagging of these repositories will bring a huge amount of repetitive work to the release process. Summary of the Invention

[0003] This specification provides one or more embodiments of a software product release method to solve the technical problems mentioned in the background art.

[0004] One or more embodiments of this specification employ the following technical solutions:

[0005] This specification provides a method for releasing a software product according to one or more embodiments, including:

[0006] When releasing a specific software product, the configuration information corresponding to that software product is determined. This configuration information includes version definition, release strategy configuration, product release unit definition, source code repository configuration within the product release unit, release context, release action configuration, relationship configuration between release actions and release strategies, product release records, and release parameter configuration, wherein:

[0007] The version definition is used to define the release version information of the specified software product;

[0008] The release strategy configuration is used to define the release strategy for the specified software product;

[0009] The product release unit definition is used to define the release unit of the specified software product;

[0010] The source code repository configuration within the product release unit is used to define the location of the source code repository within the release unit of the specified software product.

[0011] The release context is used to record release-related information of the release unit;

[0012] The release action configuration is used to configure relevant information for the release action;

[0013] The configuration of the relationship between release actions and release strategies is used to determine the release actions corresponding to the release strategies, and the execution order of the release actions;

[0014] The product release record is used to determine whether a specified version of a product release unit has been released and the release time.

[0015] The release parameter configuration is used to record the configuration of the release action;

[0016] The specified software product is released based on the configuration information.

[0017] The above-described at least one technical solution adopted in the embodiments of this specification can achieve the following beneficial effects:

[0018] This specification's embodiments define corresponding configuration information for a specified software product. This configuration information defines the attributes and operations required for the release of the specified software product, thereby enabling the release of product release units that conform to interface standards based on the configuration information. This method can reduce a large amount of repetitive manual work in the release of specified software products and improve the automation level of software product release. Attached Figure Description

[0019] To more clearly illustrate the technical solutions in the embodiments or prior art of this specification, the drawings used in the description of the embodiments or prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. In the drawings:

[0020] Figure 1 This is a flowchart illustrating a method for releasing a software product according to one or more embodiments of this specification. Detailed Implementation

[0021] This specification provides an embodiment of a method for releasing a software product.

[0022] To enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this specification, and not all embodiments. Based on the embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this specification.

[0023] Figure 1 This diagram illustrates a software product release method according to one or more embodiments of this specification. This process can be executed by a software product release system. Certain input parameters or intermediate results in the process can be manually adjusted to help improve accuracy.

[0024] The method flow steps of the embodiments in this specification are as follows:

[0025] S102, when a specified software product is released, the configuration information corresponding to the specified software product is determined. The configuration information includes version definition, release strategy configuration, product release unit definition, source code repository configuration within the product release unit, release context, release action configuration, relationship configuration between release action and release strategy, product release record, and release parameter configuration.

[0026] In the embodiments of this specification, version definition can be used to define the release version information of the specified software product; release strategy configuration can be used to define the release strategy of the specified software product; product release unit definition can be used to define the release unit of the specified software product; source code repository configuration within the product release unit can be used to define the location of the source code repository within the release unit of the specified software product; release context can be used to record release-related information of the release unit; release action configuration can be used to configure relevant information of the release action; release action and release strategy relationship configuration can be used to determine the release action corresponding to the release strategy, and the execution order of the release actions; product release record can be used to determine whether a specified version of the product release unit has been released and the release time; release parameter configuration can be used to record the configuration of the release action.

[0027] The following explains each part of the configuration information:

[0028] The version definition includes a version identifier, version name, planned release date, and version tag; the version identifier can be used to uniquely identify the version; the version tag is used to mark the source code repository with a release label when the specified software product is released.

[0029] The release strategy configuration includes a release strategy identifier and a release strategy name; wherein, the release strategy identifier is used to identify the release strategy of different parts of the specified software product; and the release strategy name is used to determine the release strategy name of different parts of the specified software product.

[0030] The product release unit definition includes attributes such as product release unit identifier, product identifier, key application identifier, service unit identifier, and release strategy identifier. The operations included in the product release unit definition are obtaining a list of product release units and obtaining the release strategy for each unit. Specifically, the product release unit identifier is used to identify the basic product release unit during product release; when multiple product lines exist, the product identifier is used to distinguish the software products to which different product release units belong; the key application identifier is used to determine the domain to which the product release unit belongs; the service unit identifier is used to determine the module to which the product release unit belongs; and the release strategy identifier is used to determine the identifier of the product release unit's release strategy. Obtaining the product release unit list involves: when a product is released, a list of product release units needs to be obtained, where each product release unit includes a product identifier, a key application identifier, and a service unit identifier; when the entire product is released, the product identifier needs to be passed, and all product release units for the current product are returned; when releasing based on a key application, both the product identifier and the key application identifier need to be passed, and a list of all product release units under the current key application domain is returned. Obtaining the release unit release strategy involves: obtaining the product release strategy based on the product release unit identifier; the parameters of the product release unit include the product release unit identifier, and the release strategy identifier matching the current product release unit is returned.

[0031] The source code repository configuration within a product release unit includes attributes such as source code repository identifier, product release unit identifier, business object identifier, and source code path. The operation included in the source code repository configuration within the product release unit is to obtain the source code repository list of the product release unit; wherein, obtaining the source code repository list of the product release unit is used to obtain the relevant source code repositories.

[0032] The release context includes the release unit identifier, product identifier, key application identifier, service unit identifier, release strategy identifier, version identifier, and version release tag.

[0033] The release action configuration includes attributes such as release action identifier, action name, release action type, applicable release level, and full name of the release action implementation class. The release action configuration includes the operation of obtaining release action details. The obtaining release action details is used to obtain detailed information of the action to be initiated based on the input release action identifier. The detailed information of the action to be initiated includes release action type, release action level, and full name of the release action implementation class.

[0034] The configuration of the relationship between release actions and release strategies includes attributes such as the relationship identifier between release strategies and release actions, the release strategy identifier, the release action identifier, the processing timing of the release action, and the execution sequence number. The operation included in the configuration of the relationship between release actions and release strategies is obtaining a list of release actions.

[0035] The method of obtaining the release action list is used to return the corresponding release action list based on the input release strategy identifier. The returned release actions are sorted by processing time and execution sequence number so that a series of release actions can be executed in sequence.

[0036] The product release record includes the following attributes: version release record identifier, product identifier, key application identifier, service unit identifier, release version, whether it has been released, and release time. The product release record includes the operation of product release record processing. Among them, product release record processing is used to record whether a specified version has been released based on the product identifier, key application identifier, and service unit identifier, and if it has been released, record the release time.

[0037] The release parameter configuration includes attributes such as parameter identifier, parameter name, and parameter value. The release parameter configuration includes operations such as obtaining parameter value. The method of obtaining parameter value is used to obtain the parameter value of the specified parameter identifier.

[0038] S104, Release the specified software product according to the configuration information.

[0039] It should be noted that the purpose of the embodiments in this specification is to provide a method for releasing large-scale software products. This method defines a set of interface standards (configuration information) for the product release unit of the software product. These interface standards define the attributes and operations required for product release, thereby enabling the release of product release units that conform to these interface standards. This method reduces a significant amount of repetitive manual work in product release and improves the automation level of software product release.

[0040] The objectives of the embodiments in this specification can be achieved through the following specific technical solutions:

[0041] A method for releasing a large software product includes the following steps:

[0042] A. Define interface standards.

[0043] B. Runtime control.

[0044] In step A, to release the software product at its smallest product release unit, it is necessary to define the interface standard to be followed during the release. The interface standard includes the following components:

[0045] (1) Version definition

[0046] (2) Release strategy configuration

[0047] (3) Product Release Unit Definition

[0048] (4) Configuration of source code repository within product release unit

[0049] (5) Release context

[0050] (6) Release Action Interface.

[0051] (7) Release Action Configuration

[0052] (8) Configuration of the relationship between release actions and release strategies

[0053] (9) Product release history

[0054] (10) Release parameter configuration

[0055] Version definition is used to define the release version information of a product. The "Version Definition" includes five attributes: Version Identifier, Version Name, Planned Release Date, Version Tag, and Remarks, described in detail below:

[0056] Attribute Name meaning Version identifier Used to uniquely identify a version Version Name A meaningful version name. For example, 2204 means the April 2022 version. Planned release date Used to record the planned release date of a version, such as 2022-03-31 Version tag When a user releases a version, a unified release tag is assigned to the source code repository, such as v2204. Remark This is used to briefly explain the main improvements and key features of this edition.

[0057] The version definition includes an operation called "Get Version Information", which is described in detail below.

[0058]

[0059] Release strategy configuration is used to define the release strategy of a product. Different parts of the same product may have different delivery forms, and thus their release strategies and release actions will also be different.

[0060] The "Release Strategy Configuration" includes three attributes: Release Strategy Identifier, Release Strategy Name, and Remarks, which are described in detail below:

[0061] Attribute Name meaning Release strategy identifier Used to uniquely identify a release strategy Release Strategy Name Release strategy name, for example: SaaS release strategy Remark This is used to briefly explain the scenarios in which the release strategy applies and the applicable delivery methods.

[0062] Product release unit definition is used to define the release unit of a product. For large products, release can be done by product or by key application area. Different release units have different release strategies.

[0063] The "Product Release Unit Definition" includes five attributes: Product Release Unit Identifier, Product Identifier, Key Application Identifier, Service Unit Identifier, and Release Strategy Identifier, described in detail below:

[0064]

[0065]

[0066] The "Product Release Unit Definition" includes two operations: "Get Product Release Unit List" and "Get Release Unit Release Strategy". Details are as follows:

[0067]

[0068] The source code repository configuration within a product release unit is used to define the location of all source code repositories within that product release unit. For large products, the dimension for establishing source code repositories may be smaller than that of modules, that is, source code repositories are established based on business objects. A module may have multiple business objects, which means there are multiple source code repositories.

[0069] The "Source Code Repository Configuration within Product Release Unit" includes four attributes: Source Code Repository Identifier, Product Release Unit Identifier, Business Object Identifier, and Source Code Path, described in detail below:

[0070]

[0071] The "Source Code Repository Configuration within Product Release Unit" includes one operation: "Get the List of Source Code Repositories for Product Release Unit". The details are as follows:

[0072]

[0073] Release context is used to record basic release information for a release unit. It includes several attributes: release unit identifier, product identifier, key application identifier, service unit identifier, release strategy identifier, version identifier, and version release tag. A detailed description follows:

[0074]

[0075]

[0076] The release action interface is a common convention for all release actions, and it has a "processing" operation. A detailed description follows:

[0077]

[0078] Release action configuration is used to configure information related to release actions. It includes six attributes: release action identifier, action name, release action type, processing timing, applicable hierarchy for release work, and fully qualified name of the release action implementation class. A detailed description follows:

[0079]

[0080]

[0081] It includes an operation called "Get Release Action Details", which is described as follows:

[0082]

[0083] The configuration for the relationship between release actions and release strategies determines the release actions corresponding to the release strategies and their execution order. It includes the following attributes: identifier, release strategy identifier, release action identifier, processing timing, and execution sequence number, described in detail below:

[0084]

[0085]

[0086] The "Relationship Configuration between Release Actions and Release Strategies" includes an operation called "Get Release Action List". The specific description is as follows:

[0087]

[0088] Product release history is used to determine whether a specific version of a product release unit has been released and on what date. It includes the following attributes: Identifier, Product Identifier, Key Application Identifier, Service Unit Identifier, Release Version, Release Status, and Release Date. A detailed description follows:

[0089]

[0090] The "Product Release History" includes an operation called "Processing". The specific description is as follows:

[0091]

[0092] Release parameter configuration is used to record the configuration of release actions, such as the location of the defect repository and the location of the release document. It contains four attributes: identifier, parameter name, parameter value, and remarks, as described below:

[0093] Attribute Name meaning logo Parameter identifier Parameter name Parameter name Parameter value Parameter value Remark This is used to explain the function of the parameter.

[0094] The "Release Parameter Configuration" includes one operation: "Get Parameter Values". The details are as follows:

[0095]

[0096] In step B, during system operation, the release of specific product release units is achieved through the interface standards defined in step A. Step B can be implemented in the following scenarios:

[0097] Release by the product release unit.

[0098] In the product release unit release scenario, when releasing a product unit, the release personnel can first select the product, key application (optional), service unit (optional), and release version. The system user selects the product identifier, key application identifier, and service unit identifier, and calls the "Get Product Release Unit List" operation in "Product Release Unit Definition" to obtain the product release unit list. Different product release strategies are extracted from this list. Then, the "Get Release Action List" operation in "Relationship Configuration between Release Actions and Release Strategies" is called to obtain the release action list for different release strategies.

[0099] Based on the release version information selected by the user, the system invokes the "Get Version Information" operation within "Version Definition" to obtain detailed information for the specified version. The system then iterates through the aforementioned product release unit list. For each product release unit, the system combines the above information—product release unit identifier, product identifier, key application identifier, service unit identifier, release version identifier, release version tag, and release strategy identifier—to form a release context. That is, each product release unit has its own release context.

[0100] The system, based on the release unit identifier in the release context, calls the "Get Source Code Repository List of Product Release Unit" operation in the "Source Code Repository Configuration within Product Release Unit" to obtain information on all source code repositories within this release unit. The system then obtains a list of release actions based on the release strategy, ordered by execution timing and order. Iterating through this list, for each release action identifier, the system calls the "Get Release Action Details" operation in the "Release Action Configuration" to obtain detailed configuration information for the release action. Using reflection, the system creates an instance of the release action based on the "Fully Named Implementation Class of Release Work," and then calls the "Process" operation in the "Release Interface." The processing operation requires not only the "Release Context" information but also other parameter information, such as a list of source code repositories. The implementation class may also call the "Get Parameter Value" operation in the "Release Parameter Configuration" to retrieve the parameters for that release action.

[0101] After each release action is completed, the system will call the "Process" operation of "Product Release Record" to record the current version of the current product release unit, the current product, and the current key application, indicating that the release has been completed; iterate to the next product release unit and execute the above operation until all product release units have completed the release.

[0102] The following example uses a real-world implementation scenario, which can be divided into two phases: the development phase and the operation phase.

[0103] During the development phase, the system pre-configured two release strategies: SaaS delivery release strategy and local delivery release strategy.

[0104] 1. SaaS delivery and release strategy

[0105] Attribute Name value Release strategy identifier SaaS Release Strategy Name SaaS delivery and release strategy Remark Strategies for releasing software products delivered as SaaS

[0106] Local delivery release strategy

[0107] Attribute Name value Release strategy identifier Local Release Strategy Name Local delivery release strategy Remark Strategies for releasing software products in a local delivery format

[0108] A standard interface for initiating actions has been pre-defined: IPublishAction. This interface contains an action.

[0109] operate deal with Dealwith(release context)

[0110] Three pre-made release actions are provided.

[0111]

[0112] The system has pre-configured the relationship between release actions and release strategies.

[0113] logo Release strategy identifier Release Action Marker Timing of handling Execution sequence number 1 SaaS 1 Before release 1 2 SaaS 2 Release in progress 1 3 Local 1 Before release 1 4 Local 2 Release in progress 2 5 Local 3 After release 3

[0114] Assuming the release version information is

[0115] Version identifier Version Name Planned release date Version tag Remark 10 V2204 2022-03-31 V2204

[0116] Assuming the product release unit information is

[0117]

[0118] Assume the "Source Code Repository Configuration within Product Release Unit" information is as follows:

[0119]

[0120] During runtime, in the "Product Release Unit Release" scenario, when releasing a product unit, the release personnel first select the product, key application (optional), service unit (optional), and release version. The system user selects the product identifier ERP and the key application identifier Scm. Then, the "Get Product Release Unit List" operation in "Product Release Unit Definition" is invoked to obtain the product release unit list.

[0121] Release Unit Identifier Product Identification Key application identifiers Service Unit Identifier Release strategy identifier 100 ERP Scm PO Local 200 ERP Scm Supplier Saas

[0122] Extract different product release strategies from this list: Local and SaaS.

[0123] Then call the "Get Release Action List" operation in "Release Action and Release Strategy Relationship Configuration" to get the release action list for different release strategies;

[0124] The action list corresponding to the Local release strategy is:

[0125]

[0126] The action list corresponding to the SaaS release strategy

[0127] logo Release strategy identifier Release Action Marker Timing of handling Execution sequence number 1 SaaS 1 Before release 1 2 SaaS 2 Release in progress 1

[0128] Based on the release version information selected by the user, i.e. version identifier 10, the system calls the "Get Version Information" operation in "Version Definition" to obtain detailed information about the specified version;

[0129] Version identifier Version Name Planned release date Version tag Remark 10 V2204 2022-03-31 V2204

[0130] The system iterates through the above product release unit list. For each product release unit, such as release unit identifier 100, the system combines the following information to form a release context: product release unit identifier 100, product identifier ERP, key application identifier SCM, service unit identifier PO, release version identifier 10, release version tag: v2204, and release strategy identifier Local. That is, each product release unit has one release context.

[0131] Attribute Name value Release Unit Identifier 100 Product Identification ERP Key application identifiers Scm Service Unit Identifier PO Release strategy identifier Local Version identifier 10 Version release tag V2204

[0132] Based on the release unit identifier in the release context, the system invokes the "Get Source Code Repository List of Product Release Unit" operation under "Source Code Repository Configuration within Product Release Unit" to obtain information on all source code repositories within this release unit.

[0133]

[0134] The system obtains a list of release actions based on the release strategy. This list is sorted by execution timing and order. The system iterates through the release action list.

[0135]

[0136]

[0137] For each release action identifier, the system calls the "Get Release Action Details" operation in "Release Action Configuration" to obtain detailed configuration information for the release action. The system uses reflection technology to create an instance of the release action based on the "fully qualified name of the implementation class of the release task," and then calls the "Process" operation in the "Release Interface." In addition to the "Release Context" context information, the processing operation may also require other parameter information, such as a list of source code repositories. Its implementation class may also call the "Get Parameter Value" operation in "Release Parameter Configuration" to obtain the parameters of the release action.

[0138] After each release action is completed, the system will call the "Process" operation of "Product Release Record" to record the current version of the current product release unit, the current product, and the current key application, indicating that the release has been completed.

[0139] logo 1 Product Identification ERP Key application identifiers Scm Service Unit Identifier PO Version identifier 10 Has it been released yet? yes Release date 2022-08-16

[0140] Iterate through the next product release unit and perform the above operations until all product release units have completed their releases.

[0141] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the embodiments of apparatus, devices, and non-volatile computer storage media are basically similar to the method embodiments, so the descriptions are relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0142] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0143] The above description is merely one or more embodiments of this specification and is not intended to limit this specification. Various modifications and variations can be made to the one or more embodiments of this specification by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principle of one or more embodiments of this specification should be included within the scope of the claims of this specification.

Claims

1. A method for releasing a software product, characterized in that, The method includes: When releasing a specified software product, the configuration information corresponding to the specified software product is determined. This configuration information includes version definition, release strategy configuration, product release unit definition, source code repository configuration within the product release unit, release context, release action configuration, relationship configuration between release actions and release strategies, product release records, and release parameter configuration, wherein: The version definition is used to define the release version information of the specified software product; The release strategy configuration is used to define the release strategy for the specified software product; The product release unit definition is used to define the release unit of the specified software product; The source code repository configuration within the product release unit is used to define the location of the source code repository within the release unit of the specified software product. The release context is used to record release-related information of the release unit; The release action configuration is used to configure relevant information for the release action; The configuration of the relationship between release actions and release strategies is used to determine the release actions corresponding to the release strategies, and the execution order of the release actions; The product release record is used to determine whether a specified version of a product release unit has been released and the release time. The release parameter configuration is used to record the configuration of the release action; The specified software product is released based on the configuration information. The source code repository configuration within the product release unit includes attributes such as source code repository identifier, product release unit identifier, business object identifier, and source code path. The operation included in the source code repository configuration within the product release unit is to obtain a list of source code repositories for the product release unit. The source code repository list for obtaining the product release unit is used to obtain the relevant source code repositories.

2. The method according to claim 1, characterized in that, The version definition includes a version identifier, version name, planned release date, and version tag; wherein... The version identifier is used to uniquely identify the version; The version tag is a release tag used to mark the source code repository when the specified software product is released.

3. The method according to claim 1, characterized in that, The release strategy configuration includes a release strategy identifier and a release strategy name; wherein... The release strategy identifier is used to identify the release strategies of different parts of the specified software product; The release strategy name is used to determine the release strategy name for different parts of the specified software product.

4. The method according to claim 1, characterized in that, The product release unit definition includes attributes such as product release unit identifier, product identifier, key application identifier, service unit identifier, and release strategy identifier. The operations included in the product release unit definition are obtaining a list of product release units and obtaining the release strategy for each release unit. The product release unit identifier is used to identify the basic product release unit during product release; When there are multiple product lines, the product identifier is used to distinguish the software products to which different product release units belong; The key application identifier is used to determine the domain to which the product release unit belongs; The service unit identifier is used to determine the module to which the product release unit belongs; The release strategy identifier is used to identify the release strategy of the product release unit; The process of obtaining the product release unit list is as follows: When a product is released, a list of product release units needs to be obtained. The product release unit includes a product identifier, a key application identifier, and a service unit identifier. When the entire product is released, the product identifier needs to be transmitted, and all product release units of the current product are returned. When a product is released based on a key application, the product identifier and the key application identifier need to be transmitted, and a list of all product release units under the current key application domain is returned. The release strategy of the release unit is obtained as follows: the product release strategy is obtained based on the product release unit identifier; the parameters of the product release unit include the product release unit identifier, and the release strategy identifier that matches the current product release unit is returned.

5. The method according to claim 1, characterized in that, The release context includes release unit identifier, product identifier, key application identifier, service unit identifier, release strategy identifier, version identifier, and version release tag.

6. The method according to claim 1, characterized in that, The release action configuration includes attributes such as release action identifier, action name, release action type, applicable release level, and fully qualified name of the release action implementation class. The release action configuration also includes the operation of retrieving release action details. The process of obtaining release action details is used to obtain detailed information about the action based on the input release action identifier. The detailed information about the action includes the release action type, the release action level, and the full name of the release action implementation class.

7. The method according to claim 1, characterized in that, The configuration of the relationship between release actions and release strategies includes attributes such as the relationship identifier between release strategies and release actions, the release strategy identifier, the release action identifier, the processing timing and execution sequence number of the release action, and the operation of the configuration of the relationship between release actions and release strategies is to obtain a list of release actions; wherein, The method of obtaining the release action list is used to return the corresponding release action list based on the input release strategy identifier. The returned release actions are sorted in ascending order by processing time and execution sequence number so that a series of release actions can be executed in sequence.

8. The method according to claim 1, characterized in that, The product release record includes the following attributes: version release record identifier, product identifier, key application identifier, service unit identifier, release version, whether it has been released, and release time. The operation included in the product release record is product release record processing. Product release record processing is used to record whether a specified version has been released based on the product identifier, key application identifier, and service unit identifier. If a version has been released, the release time is recorded.

9. The method according to claim 1, characterized in that, The release parameter configuration includes attributes such as parameter identifier, parameter name, and parameter value, and the operation of the release parameter configuration includes retrieving the parameter value; wherein, The parameter value acquisition method is used to acquire the parameter value of the specified parameter identifier.

Images