CN116841563A - Product release method, device, equipment, storage medium and product - Google Patents

Product release method, device, equipment, storage medium and product Download PDF

Info

Publication number
CN116841563A
CN116841563A CN202310883686.2A CN202310883686A CN116841563A CN 116841563 A CN116841563 A CN 116841563A CN 202310883686 A CN202310883686 A CN 202310883686A CN 116841563 A CN116841563 A CN 116841563A
Authority
CN
China
Prior art keywords
product
template
product release
filled
release
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202310883686.2A
Other languages
Chinese (zh)
Inventor
张晓爽
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Construction Bank Corp
CCB Finetech Co Ltd
Original Assignee
China Construction Bank Corp
CCB Finetech Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China Construction Bank Corp, CCB Finetech Co Ltd filed Critical China Construction Bank Corp
Priority to CN202310883686.2A priority Critical patent/CN116841563A/en
Publication of CN116841563A publication Critical patent/CN116841563A/en
Pending legal-status Critical Current

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/40Transformation of program code
    • G06F8/41Compilation
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management
    • G06F8/71Version control; Configuration management

Abstract

The application provides a product release method, a device, equipment, a storage medium and a product, which can be used in the financial field. The product release template of the method comprises the following steps: the corresponding relation between each product identifier and the code engineering identifier; adding the product release information corresponding to the product to be released in the completed product release template into a release and production list template to generate a target release and production list; and sending the target release and production list to the operation and maintenance terminal so as to enable the operation and maintenance terminal to release the product to be released according to the product release information corresponding to the product to be released in the release and production list. The product to be released and the production information thereof are determined through selection in the product release template, and a production list is automatically generated according to the filled product release template, so that the situation of incorrect production information of product release is avoided, the probability of incorrect production or failure of product release is reduced, and the production release and production efficiency is improved.

Description

Product release method, device, equipment, storage medium and product
Technical Field
The present application relates to the field of finance, and in particular, to a method, apparatus, device, storage medium, and product for product release.
Background
Because of the diversity of financial products or government products, development, implementation, test, configuration and operation are required in the product release and production process to confirm the product release and production information, and release operation can be performed on the product to be released after the product release and production information is confirmed.
Because in the product development process, multiple product names may exist in the same product, such as product abbreviations and product names, repeated confirmation may be needed in the process of developing, implementing, testing, configuring and operating and maintaining to confirm the product release and production information, the efficiency is low, and the situation of incorrect product release and production information may also occur, so that the product release and production is incorrect or failed.
Disclosure of Invention
The application provides a product release method, a device, equipment, a storage medium and a product, which are used for solving the problems that the product release and production efficiency is low and the product release and production is incorrect or fails due to the fact that each flow confirms the product release and production information.
In a first aspect, the present application provides a product release method, applied to an electronic device, including:
receiving a product release template which is sent by an implementation terminal and is filled once; the product release template comprises the following steps: the corresponding relation between each product identifier and the code engineering identifier; the one-time filled product release template comprises the following steps: a product identifier to be issued and a corresponding target code engineering identifier;
The method comprises the steps of sending a product release template which is filled once to a development terminal to obtain a product release template which is filled twice; the secondarily filled product release template comprises content information to be released corresponding to the target code engineering identifier; the content information to be published comprises: object code version and compiling parameters;
the product release template which is filled in for the second time is sent to a configuration terminal so as to obtain a filled-in product release template; the filled product release template comprises the acquisition mode of a target product release package corresponding to the product to be released;
adding the product release information corresponding to the product to be released in the completed product release template into a release and production list template to generate a target release and production list; the product release information corresponding to the product to be released comprises: the acquisition mode of the target product release package, the target code version and the compiling parameters;
and sending the target release and production list to an operation and maintenance terminal so as to prompt the operation and maintenance terminal to release the product to be released according to the product release information corresponding to the product to be released in the release and production list.
In a second aspect, the present application provides a product release method, applied to an implementation terminal, including:
Obtaining a product release template; the product release template comprises the corresponding relation between each product identifier and the code engineering identifier;
determining corresponding target code engineering identifiers based on product identifiers to be distributed and corresponding relations between the product identifiers and the code engineering identifiers, which are determined in a product distribution template by an implementation personnel, and filling the target code engineering identifiers into corresponding records of the products to be distributed so as to generate a product distribution template which comprises the corresponding records of the products to be distributed and is filled once;
and sending the one-time filled product release template to the electronic equipment so that the electronic equipment forwards the one-time filled product release template to the development terminal.
In a third aspect, the present application provides a product issue device, applied to an electronic apparatus, including:
the receiving module is used for receiving the once filled product release template sent by the implementation terminal; the product release template comprises the following steps: the corresponding relation between each product identifier and the code engineering identifier; the one-time filled product release template comprises the following steps: a product identifier to be issued and a corresponding target code engineering identifier;
the forwarding module is used for sending the product release template which is filled once to the development terminal so as to obtain the product release template which is filled twice; the secondarily filled product release template comprises content information to be released corresponding to the target code engineering identifier; the content information to be published comprises: object code version and compiling parameters;
The forwarding module is also used for sending the secondarily filled product release template to the configuration terminal so as to obtain a filled product release template; the filled product release template comprises the acquisition mode of a target product release package corresponding to the product to be released;
the generating module is used for adding the product release information corresponding to the product to be released in the completed product release template into the release and production list template so as to generate a target release and production list; the product release information corresponding to the product to be released comprises: the acquisition mode of the target product release package, the target code version and the compiling parameters;
and the forwarding module is also used for sending the target release and production schedule to the operation and maintenance terminal so as to prompt the operation and maintenance terminal to release the product to be released according to the product release information corresponding to the product to be released in the release and production schedule.
In a fourth aspect, the present application provides a product issue device, applied to an implementation terminal, including:
the acquisition module is used for acquiring a product release template; the product release template comprises the corresponding relation between each product identifier and the code engineering identifier;
the determining module is used for determining corresponding target code engineering identifiers based on product identifiers to be distributed and corresponding relations between the product identifiers and the code engineering identifiers, which are determined in the product distribution template by an implementer, and filling the target code engineering identifiers into corresponding records of the product to be distributed so as to generate a product distribution template which comprises the corresponding records of the product to be distributed and is filled at one time;
And the sending module is used for sending the product release template which is filled once to the electronic equipment so that the electronic equipment forwards the product release template which is filled once to the development terminal.
In a fifth aspect, the present application provides an electronic device, comprising: a processor, and a memory and transceiver communicatively coupled to the processor;
the memory stores computer-executable instructions; the transceiver is used for receiving and transmitting data;
the processor executes the computer-executable instructions stored in the memory to implement the product release method described in the first aspect.
In a sixth aspect, the present application provides an implementation terminal, including: a processor, and a memory and transceiver communicatively coupled to the processor;
the memory stores computer-executable instructions; the transceiver is used for receiving and transmitting data;
the processor executes the computer-executable instructions stored in the memory to implement the product release method according to the second aspect.
In a seventh aspect, the present application provides a computer-readable storage medium having stored therein computer-executable instructions which, when executed by a processor, are configured to implement the product issue method according to the first or second aspect.
In an eighth aspect, the present application provides a computer program product comprising computer-executable instructions which, when executed by a processor, implement the product release method according to the first or second aspect.
The product release method, the device, the equipment, the storage medium and the product provided by the application receive the product release template which is sent by the implementation terminal and is filled once; the product release template comprises: the corresponding relation between each product identifier and the code engineering identifier; the method comprises the steps of sending a product release template which is filled once to a development terminal to obtain a product release template which is filled twice; the product release template which is filled in for the second time is sent to a configuration terminal so as to obtain a filled-in product release template; adding the product release information corresponding to the product to be released in the completed product release template into a release and production list template to generate a target release and production list; the product release information corresponding to the product to be released comprises: the acquisition mode of the target product release package, the target code version and the compiling parameters; and sending the target release and production list to the operation and maintenance terminal so as to enable the operation and maintenance terminal to release the product to be released according to the product release information corresponding to the product to be released in the release and production list. The product to be released and the production information thereof are determined through selection in the product release template, and a production list is automatically generated according to the filled product release template, so that the product to be released corresponds to only one product name in the whole production release process, and one product name corresponds to a fixed code project, the situation that the production release information is wrong is avoided, the probability of incorrect or failed production release is reduced, and the production release efficiency is improved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.
FIG. 1 is a flowchart of a product release method according to an embodiment of the present application;
FIG. 2 is a flowchart of a product release method according to a second embodiment of the present application;
FIG. 3 is a product release signaling diagram provided by an embodiment of the present application;
fig. 4 is a schematic structural diagram of a product issue device according to a fourth embodiment of the present application;
fig. 5 is a schematic structural diagram of a product issue device according to a fifth embodiment of the present application;
fig. 6 is a schematic structural diagram of an electronic device according to a sixth embodiment of the present application;
fig. 7 is a schematic structural diagram of an implementation terminal according to a sixth embodiment of the present application.
Specific embodiments of the present application have been shown by way of the above drawings and will be described in more detail below. The drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but rather to illustrate the inventive concepts to those skilled in the art by reference to the specific embodiments.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying claims.
The terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. In the following description of the embodiments, the meaning of "a plurality" is two or more, unless explicitly defined otherwise.
First, the prior art to which the present application relates will be described in detail and analyzed.
The existing product release and production process is that a developer fills out production information such as product names, code projects and the like, then the production information of each product is sequentially sent to a tester by implementation summarization, a configurator confirms the production information by the configurator and then arranges the production information into a production list and sends the production list to an operation and maintenance person, and the operation and maintenance person carries out production according to the information in the production list. In the process, the problem of non-uniform product names easily occurs, so that a responsible person needs to be found again for confirmation every time of confirmation of the production information, and a great deal of time and labor are wasted.
The inventor finds out in the study that the product names, code projects and other production information are manually arranged according to production mail information, and the production list is easy to write by mistake when the production names and package names are manually arranged, so that trouble is brought to operation and maintenance checking of the production list, therefore, the inventor finds out in the study that the information such as the product names and the corresponding code projects can be input in advance in a product release template, development, implementation, test, configuration, operation and maintenance and other personnel can determine the products to be released and the production information thereof through selection in the product release template, and can automatically generate the production list according to the filled product release template, so that the products to be released only correspond to one product name in the whole production release process, one product name corresponds to the fixed code projects, the situation that the production release information is wrong can be avoided, the probability that the product release is incorrect or failed can be reduced, and the efficiency of the product release and the production release can be improved. The application provides a product release method, wherein the product release template comprises the following steps: the corresponding relation between each product identifier and the code engineering identifier; the one-time filled product release template comprises the following steps: a product identifier to be issued and a corresponding target code engineering identifier; after receiving the once filled product release template sent by the implementation terminal; the method comprises the steps of sending a product release template which is filled once to a development terminal to obtain a product release template which is filled twice; the product release template which is filled in for the second time is sent to a configuration terminal so as to obtain a filled-in product release template; adding the product release information corresponding to the product to be released in the completed product release template into a release and production list template to generate a target release and production list; the product release information corresponding to the product to be released comprises: the acquisition mode of the target product release package, the target code version and the compiling parameters; and sending the target release and production list to the operation and maintenance terminal so as to enable the operation and maintenance terminal to release the product to be released according to the product release information corresponding to the product to be released in the release and production list.
It should be noted that, the user information (including but not limited to user equipment information, user personal information, etc.) and the data (including but not limited to data for analysis, stored data, presented data, etc.) related to the present application are information and data authorized by the user or fully authorized by each party, and the collection, use and processing of the related data need to comply with related laws and regulations and standards, and provide corresponding operation entries for the user to select authorization or rejection.
It should be noted that the product issuing method, device, equipment and storage medium of the present application can be used in the financial field, and can also be used in any field other than the financial field, and the application fields of the product issuing method, device, equipment, storage medium and product of the present application are not limited.
The following describes the technical scheme of the present application and how the technical scheme of the present application solves the above technical problems in detail with specific embodiments. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.
Example 1
Fig. 1 is a flowchart of a product release method provided by an embodiment of the present application, which provides a product release method for solving the problems that repeated confirmation may be required in the process of confirming product release and production information, the efficiency is low, and the product release and production information may be wrong, resulting in incorrect or failed product release and production. The method in the embodiment is applied to a product release device, and the product release device can be located in an electronic device. Wherein the electronic device may be a digital computer representing various forms. Such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers.
As shown in fig. 1, the method specifically comprises the following steps:
step S101, receiving a product release template which is sent by an implementation terminal and is filled in once.
Wherein, include in the product release template: the corresponding relation between each product identifier and the code engineering identifier; the one-time filled product release template comprises the following steps: the product identifier to be issued and the corresponding object code engineering identifier.
The product release template in the embodiment of the application is preconfigured with each product identifier and the code engineering identifier corresponding to each product identifier. After the implementation terminal acquires the product release template, an implementation personnel can select a product identifier to be released in the product information label page to be released, and the implementation terminal can automatically fill the code engineering identifier corresponding to the product identifier to be released into the corresponding record of the product to be released in the product information label page to be released.
Specifically, after selecting a product identifier to be published in the product publishing template and determining a corresponding target code engineering identifier, an implementer can send the product publishing template which is filled once to the electronic equipment; after the electronic equipment receives the once filled product release template, the once filled product release template can be sent to a development terminal so as to prompt a developer to fill in the content information to be released and form a twice filled product release template.
Step S102, the product release template which is filled once is sent to a development terminal so as to obtain the product release template which is filled twice.
The product release template which is filled in for the second time comprises content information to be released corresponding to the target code engineering identifier; the content information to be published includes: object code version and compiling parameters.
Specifically, after the product release template which has been filled in once is sent to the development terminal, the developer fills in the content information to be released to generate the product release template which has been filled in twice, and the development terminal sends the product release template which has been filled in twice to the electronic device.
Step S103, the secondarily filled product release template is sent to a configuration terminal to obtain the filled product release template.
The filled product release template comprises a target product release package acquisition mode corresponding to the product to be released.
Specifically, after the secondarily filled product release template is sent to the configuration terminal, the configuration terminal compiles the target code based on the content information to be released in the secondarily filled product release template to generate a target product release package, and fills the acquisition mode of the target product release package into the secondarily filled product release template to form a filled product release template.
It should be understood that the embodiment of the application does not limit the acquisition mode of the filled target product release package. The obtaining manner of the target product release package may be a storage address of the target product release package, or may be information such as an identifier of the target product release package.
Step S104, adding the product release information corresponding to the product to be released in the completed product release template into the release and production list template to generate a target release and production list.
The product release information corresponding to the product to be released comprises: the acquisition mode of the target product release package, the target code version and the compiling parameters. The target release and production list comprises product release information corresponding to the product to be released.
It should be understood that the product release information may include part of the information in the completed product release template, or may include all of the information in the completed product release template, which is not limited in the embodiment of the present application.
In the embodiment of the application, the production list can comprise fields such as an acquisition mode, a code version, a compiling parameter and the like of the product release package, and the product release information corresponding to the product to be released in each filled product release template can be added into the release production list template.
Optionally, product release information corresponding to the product to be released in the filled release delivery list template can be filled in, and product release information corresponding to the product to be released in the filled release delivery list template can be added in; and the release and production list template of the unfilled product release information can be obtained, and the product release information corresponding to the product to be released is added into the release and production list template to form a target release and production list.
Step 105, the target release and production list is sent to the operation and maintenance terminal, so that the operation and maintenance terminal can perform release operation on the product to be released according to the product release information corresponding to the product to be released in the release and production list.
In the embodiment of the application, the product release information corresponding to the product to be released is added into the release and production list template to generate, and the target release and production list is sent to the operation and maintenance terminal. After receiving the target release and production clearance, the operation and maintenance terminal can check the product release information in the target release and production clearance, and after the check is passed, the operation and maintenance terminal can acquire the target product release package and release the target product release package in an acquisition mode of the target product release package, so that the release operation of the product to be released is performed.
The product release method provided by the embodiment of the application receives the product release template which is sent by the implementation terminal and is filled once; the product release template comprises: the corresponding relation between each product identifier and the code engineering identifier; the method comprises the steps of sending a product release template which is filled once to a development terminal to obtain a product release template which is filled twice; the product release template which is filled in for the second time is sent to a configuration terminal so as to obtain a filled-in product release template; adding the product release information corresponding to the product to be released in the completed product release template into a release and production list template to generate a target release and production list; the product release information corresponding to the product to be released comprises: the acquisition mode of the target product release package, the target code version and the compiling parameters; and sending the target release and production list to the operation and maintenance terminal so as to enable the operation and maintenance terminal to release the product to be released according to the product release information corresponding to the product to be released in the release and production list. The product to be released and the production information thereof are determined through selection in the product release template, and a production list is automatically generated according to the filled product release template, so that the product to be released corresponds to only one product name in the whole production release process, and one product name corresponds to a fixed code project, the situation that the production release information is wrong is avoided, the probability of incorrect or failed production release is reduced, and the production release efficiency is improved.
The product release method provided by the above embodiment is described below with reference to a specific example, and specifically includes the following steps:
step S201, a product release template is sent to an implementation terminal in response to a received template acquisition request, so that an implementation personnel selects a product identifier to be released in the product release template, and accordingly a corresponding target code engineering identifier is determined and a product release template which is filled in at one time is formed.
Specifically, the product release template can be stored in a certain storage space, and after the fact that the product needs to be released is determined, a template acquisition request can be sent to the electronic equipment at the implementation terminal; after receiving the template acquisition request, the electronic equipment can acquire a product release template from the storage space and send the product release template to the implementation terminal; the implementation personnel can select the product identifier to be released from the product release template, so that the implementation terminal determines the corresponding target code engineering identifier and forms the product release template which is filled once.
According to the product release method provided by the embodiment of the application, the received template acquisition request is responded, and the product release template is sent to the implementation terminal, so that an implementation personnel selects the product identifier to be released in the product release template, and the corresponding target code engineering identifier is determined and the product release template which is filled once is formed. The product release template can be conveniently updated uniformly without being stored in each implementation terminal
Step S202, receiving a product release template which is transmitted by an implementation terminal and is filled in once, and acquiring an object code engineering identifier from the product release template which is filled in once.
And step 203, determining a corresponding development terminal based on the target code engineering identifier and the code engineering personnel information table, and transmitting the once filled product release template to the corresponding development terminal.
In the embodiment of the application, the developer corresponding to each code project is prestored in the code project personnel information table. After receiving the product release template which is filled in once, the electronic equipment can acquire the target code engineering identifier from the product release template which is filled in once, and determine the corresponding developer based on the target code engineering identifier and the code engineering personnel information table, so as to determine the corresponding development terminal based on the corresponding developer. After the corresponding development terminal is determined, the product release template which is filled once is used for enabling the corresponding developer to fill in the content information to be released corresponding to the target code engineering mark in the product release template which is filled once, so that the product release template which is filled twice is formed.
And step S204, receiving the secondarily filled product release template sent by the development terminal.
The product release method provided by the embodiment of the application receives the product release template which is sent by the implementation terminal and is filled once; acquiring an object code engineering identifier from the product release template which is filled once; determining a corresponding development terminal based on the target code engineering identifier and the code engineering personnel information table, and transmitting the once filled product release template to the corresponding development terminal so that the corresponding developer fills in the content information to be released corresponding to the target code engineering identifier in the once filled product release template to form a twice filled product release template; and receiving the secondarily filled product release template sent by the development terminal. The automatic forwarding of the product release templates filled once is realized through the code engineering personnel information table, and the product release efficiency is improved.
And step S205, transmitting the secondarily filled product release template to the corresponding test terminal based on the target code engineering identifier and the code engineering personnel information table.
In the embodiment of the application, the code engineering personnel information table can also store the testers corresponding to each code engineering in advance. In the embodiment of the present application, the secondarily filled product release template is sent to the corresponding test terminal based on the object code engineering identifier and the code engineering personnel information table, which is similar to step S203 and will not be described in detail herein.
In the embodiment of the application, after the test terminal corresponding to the target code engineering identifier is determined, the secondarily filled product release template is sent to the corresponding test terminal, so that the corresponding test terminal determines whether the test of the code corresponding to the target code version in the target code engineering is passed or not, and whether the release operation of the product to be released can be performed or not is determined. If the publishable determination information sent by the test terminal is received, step S206 is executed to send the secondarily filled product publication template to the configuration terminal.
Optionally, if the product non-issuable information sent by the test terminal is received, the product non-issuable information is sent to the implementation terminal. The method and the device can enable the implementation personnel to know that the product to be released can not be released, and promote the release of the product to be released.
Wherein, the non-publishable information of the product may include: the reason why the product is not issuable. The reason that the product is not issuable may be that no test is performed or that the test is passed.
And step S206, responding to the issuable determination information sent by the test terminal, and sending the secondarily filled product release template to the configuration terminal so as to obtain the filled product release template.
According to the product release method provided by the embodiment of the application, before the secondarily filled product release template is sent to the configuration terminal for configuration, the secondarily filled product release template is sent to the corresponding test terminal, so that the corresponding test terminal determines whether the test of the code corresponding to the target code version in the target code project is passed or not, the configuration and release operation can be carried out after the test of the code corresponding to the target code version in the target code project is passed, and the probability of product release errors can be reduced.
Specifically, the secondarily filled product release template is sent to the configuration terminal, so that the configuration terminal generates a target product release package according to the secondarily filled product release template, and the secondarily filled product release template is filled with the acquisition mode of the target product release package to form a filled product release template.
Step S207, receiving the filled product release template sent by the configuration terminal.
In the embodiment of the application, the configuration terminal can generate the target product release package according to the secondarily filled product release template, and after the secondarily filled product release template is obtained, the secondarily filled product release template can be sent to the configuration terminal, and the filled product release template sent by the configuration terminal is received.
Example two
Fig. 2 is a flowchart of a product release method provided by a second embodiment of the present application, which provides a product release method for solving the problems that in the process of confirming product release and production information, repeated confirmation may be required, the efficiency is low, and the product release and production information may be wrong, resulting in incorrect or failed product release and production. The method in this embodiment is applied to a product issue device, which may be located in an implementation terminal. The implementation terminal may be a digital computer or a mobile terminal representing various forms. Such as smartphones, laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other suitable computers.
As shown in fig. 2, the method specifically comprises the following steps:
step S301, obtaining a product release template.
The product release template comprises corresponding relations between each product identifier and code engineering identifiers.
The embodiment of the application does not limit the mode of acquiring the product release template. The product release template may be obtained by sending a template obtaining request to the electronic device, or may be obtained from a local storage space.
Step S302, determining corresponding target code engineering identifiers based on product identifiers to be distributed and corresponding relations between the product identifiers and the code engineering identifiers, which are determined in the product distribution templates by implementation personnel, and filling the target code engineering identifiers into corresponding records of the products to be distributed so as to generate a product distribution template which comprises the corresponding records of the products to be distributed and is filled at one time.
Specifically, an implementer selects a product identifier to be released in a product identifier selection column in a product release template to form a corresponding record of the product to be released; the product release template can fill the target code engineering identifier into the corresponding record of the product to be released based on the corresponding relation between each product identifier and the code engineering identifier so as to generate the product release template which comprises the corresponding record of the product to be released and is filled in once.
Step S303, the product release template which is filled once is sent to the electronic equipment, so that the electronic equipment forwards the product release template which is filled once to the development terminal.
Specifically, in response to the Chen Fasong operation of the implementer, the once filled product release template is transmitted to the electronic device, so that the electronic device forwards the once filled product release template to the development terminal.
The product release method provided by the embodiment of the application obtains the product release template; the product release template comprises the corresponding relation between each product identifier and the code engineering identifier; determining corresponding target code engineering identifiers based on product identifiers to be distributed and corresponding relations between the product identifiers and the code engineering identifiers, which are determined in a product distribution template by an implementation personnel, and filling the target code engineering identifiers into corresponding records of the products to be distributed so as to generate a product distribution template which comprises the corresponding records of the products to be distributed and is filled once; and sending the product release template which is filled once to the electronic equipment so that the electronic equipment forwards the product release template which is filled once to the development terminal. The product to be released and the production information thereof are determined through selection in the product release template, and a production list is automatically generated according to the filled product release template, so that the product to be released corresponds to only one product name in the whole production release process, and one product name corresponds to a fixed code project, the situation that the production release information is wrong is avoided, the probability of incorrect or failed production release is reduced, and the production release efficiency is improved.
Optionally, the product release template may be in excel format, and step S302 may include, based on the product identifier to be released and the correspondence between each product identifier and the code engineering identifier determined by the user in the product release template, determining a corresponding target code engineering identifier, and filling the target code engineering identifier into a record corresponding to the product to be released, where the implementation manner includes:
and determining an object code engineering identifier corresponding to the product identifier to be issued by adopting an excel built-in function LOOKUP function and a CELL function, and filling the object code engineering identifier into a record corresponding to the product to be issued.
Specifically, the LOOKUP function is used for searching using a function array syntax, and a search formula=lookup (array). The login_value is a product identifier which is input by an implementer in a fuzzy manner in a product release template, and an accurately released product identifier corresponding to the fuzzy input product identifier can be inquired. The array is a table range of pre-written product identifiers and code engineering identifiers. The CELL function can return the value of the last edited CELL of the CELL, and the SEARCH function can SEARCH the corresponding target code engineering identifier according to the returned position of the parameter name after the product identifier to be issued is selected by the pull-down.
In the embodiment of the application, the built-in function LOOKUP function of excel is used in the pull-down selection part of the production list module to be matched with the CELL function to carry out fuzzy query on the product, so that the problems of inaccuracy and non-uniqueness caused by manual input are avoided.
Fig. 3 is a product release signaling diagram provided by the embodiment of the present application, as shown in fig. 3, including the following steps:
step S401, the implementation terminal acquires a product release template, and generates a product release template which comprises a corresponding record of a product to be released and is filled in at one time based on a user.
And step S402, the implementation terminal sends the product release template which is filled in at one time to the electronic equipment.
Step S403, the electronic equipment sends the product release template which is filled in at one time to the development terminal.
And step S404, filling content information to be released corresponding to the target code engineering identifier by the development terminal to form a product release template which is filled in for the second time.
And step 405, the development terminal sends the secondarily filled product release template to the electronic equipment.
And step S406, the electronic equipment sends the secondarily filled product release template to the test terminal.
Step S407, the test terminal determines whether the test of the code corresponding to the target code version in the target code engineering is passed.
And step S408, the test terminal determines that the test is passed and then issues determination information to the sending electronic equipment.
And step S409, the electronic equipment sends the secondarily filled product release template to the configuration terminal.
Step S410, the configuration terminal generates a target product release package according to the secondarily filled product release template, and fills the obtaining mode of the target product release package in the secondarily filled product release template to form a filled product release template.
The filled product release template can comprise information such as a product identifier to be released, a target code engineering identifier, a production region, a deployment unit, a production type and the like determined by an implementation personnel; the method also comprises target code versions and compiling parameters filled in by the developer. The production type corresponding table comprises a conventional version daily production type, a rapid emergency production type, an emergency production, a agile conventional production and agile emergency production.
And step S411, the configuration terminal sends the filled product release template to the electronic equipment.
Step S412, the electronic equipment generates a target release and production list based on the filled product release template. The production schedule may include: whether transaction registration exists, whether database change exists, whether other production information such as interface encryption and decryption exists, and the like.
And step 413, the electronic equipment sends the target release and production list to the operation and maintenance terminal.
And step S414, the operation and maintenance terminal performs release operation on the product to be released according to the product release information corresponding to the product to be released in the release and production list.
Example IV
Fig. 4 is a schematic structural diagram of a product issue device according to a fourth embodiment of the present application. The product release device provided by the embodiment of the application can execute the processing flow provided by the first embodiment of the product release method. As shown in fig. 4, the product issuing apparatus 50 includes: a receiving module 501, a forwarding module 502, and a generating module 503.
Specifically, the receiving module 501 is configured to receive a product release template that is sent by an implementation terminal and is filled in once; the product release template comprises: the corresponding relation between each product identifier and the code engineering identifier; the one-time filled product release template comprises the following steps: a product identifier to be issued and a corresponding target code engineering identifier;
the forwarding module 502 is configured to send the product release template that has been filled in once to a development terminal, so as to obtain a product release template that has been filled in twice; the secondarily filled product release template comprises content information to be released corresponding to the target code engineering identifier; the content information to be published includes: object code version and compiling parameters;
The forwarding module 502 is further configured to send the secondarily filled product release template to a configuration terminal, so as to obtain a filled product release template; filling in an acquisition mode of a target product release package corresponding to a product to be released in a finished product release template;
a generating module 503, configured to add product release information corresponding to a product to be released in the completed product release template to the release and delivery list template, so as to generate a target release and delivery list; the product release information corresponding to the product to be released comprises: the acquisition mode of the target product release package, the target code version and the compiling parameters;
the forwarding module 502 is further configured to send the target release delivery list to the operation and maintenance terminal, so that the operation and maintenance terminal performs release operation on the product to be released according to the product release information corresponding to the product to be released in the release delivery list.
The apparatus provided in the embodiment of the present application may be specifically used to perform the method embodiment provided in the first embodiment, and specific functions are not described herein.
Optionally, before the receiving module 501 receives the product release template that is sent by the implementation terminal and is filled in at one time, the sending module 502 is further configured to: and responding to the received template acquisition request, and sending the product release template to the implementation terminal so that an implementation personnel selects a product identifier to be released in the product release template, thereby determining a corresponding target code engineering identifier and forming a product release template which is filled once.
Optionally, the forwarding module 502 sends the product release template that has been filled in once to the development terminal, so as to be specifically used when obtaining the product release template that has been filled in twice:
receiving a product release template which is sent by an implementation terminal and is filled once; acquiring an object code engineering identifier from the product release template which is filled once; determining a corresponding development terminal based on the target code engineering identifier and the code engineering personnel information table, and transmitting the once filled product release template to the corresponding development terminal so that the corresponding developer fills in the content information to be released corresponding to the target code engineering identifier in the once filled product release template to form a twice filled product release template; and receiving the secondarily filled product release template sent by the development terminal.
Optionally, the forwarding module 502 sends the product release template that has been filled in twice to the configuration terminal, so as to specifically be used when obtaining the product release template that has been filled in:
the method comprises the steps of sending a secondarily filled product release template to a configuration terminal, enabling the configuration terminal to generate a target product release package according to the secondarily filled product release template, and filling an acquisition mode of the target product release package in the secondarily filled product release template to form a filled product release template; and receiving the filled product release template sent by the configuration terminal.
Optionally, before the forwarding module 502 sends the product release template that has been filled in twice to the configuration terminal to obtain the product release template that has been filled in, the forwarding module is further configured to: based on the target code engineering identifier and the code engineering personnel information table, sending the secondarily filled product release template to a corresponding test terminal, so that the corresponding test terminal determines whether the test of the code corresponding to the target code version in the target code engineering is passed or not, and further determines whether the release operation of the product to be released can be performed or not; the forwarding module 502 sends the product release template that has been filled in twice to the configuration terminal, so as to obtain the product release template that has been filled in, which is specifically used when: and responding to the issuable determining information sent by the test terminal, and sending the secondarily filled product release template to the configuration terminal so as to obtain the filled product release template.
Optionally, after the forwarding module 502 sends the product release template that has been filled in twice to the test terminal, the forwarding module is further configured to: and receiving the product non-issuable information sent by the test terminal, and sending the product non-issuable information to the implementation terminal.
The apparatus provided in the embodiment of the present application may be specifically used to execute the above method embodiment, and specific functions are not described herein.
Example five
Fig. 5 is a schematic structural diagram of a product issue device according to a fifth embodiment of the present application. The product release device provided by the embodiment of the application can execute the processing flow provided by the second embodiment of the product release method. As shown in fig. 5, the product issuing apparatus 60 includes: the module for acquiring 601, the module for determining 602 and the module for sending 603.
Specifically, an obtaining module 601 is configured to obtain a product release template; the product release template comprises the corresponding relation between each product identifier and the code engineering identifier;
the determining module 602 is configured to determine a corresponding target code engineering identifier based on a product identifier to be distributed and a corresponding relationship between each product identifier and the code engineering identifier, which are determined by an implementer in the product distribution template, and fill the target code engineering identifier into a corresponding record of the product to be distributed, so as to generate a product distribution template that includes a corresponding record of the product to be distributed and is filled in once;
and the sending module 603 is configured to send the product release template that has been filled in at one time to the electronic device, so that the electronic device forwards the product release template that has been filled in at one time to the development terminal.
The apparatus provided in the embodiment of the present application may be specifically used to execute the method embodiment provided in the second embodiment, and specific functions are not described herein.
Optionally, the product release template is in excel format: the determining module 602 determines a corresponding target code engineering identifier based on the product identifier to be issued and the corresponding relation between each product identifier and the code engineering identifier, which are determined by the user in the product issuing template, and is specifically configured to:
and determining an object code engineering identifier corresponding to the product identifier to be issued by adopting an excel built-in function LOOKUP function and a CELL function, and filling the object code engineering identifier into a record corresponding to the product to be issued.
The apparatus provided in the embodiment of the present application may be specifically used to execute the above method embodiment, and specific functions are not described herein.
Example six
Fig. 6 is a schematic structural diagram of an electronic device according to a sixth embodiment of the present application, and as shown in fig. 6, the present application further provides an electronic device 70, including: a processor 701, and a memory 702 and a transceiver 703 communicatively coupled to the processor 701. Wherein the memory 702 stores computer-executable instructions; the transceiver 703 is used for receiving and transmitting data; the processor 701 executes computer-executable instructions stored in the memory 702 to implement the method provided by any of the embodiments of the present application.
In particular, the program may include program code including computer-executable instructions. The memory 702 may comprise high-speed RAM memory or may further comprise non-volatile memory (non-volatile memory), such as at least one disk memory. Wherein computer-executable instructions are stored in memory 702 and are configured to be executed by processor 701 to implement the methods provided by any of the embodiments of the present application. The related descriptions and effects corresponding to the steps in the drawings can be understood correspondingly, and are not repeated here.
In the embodiment of the present application, the memory 702 and the processor 701 are connected through a bus. The bus may be an industry standard architecture (Industry Standard Architecture, abbreviated ISA) bus, an external device interconnect (Peripheral Component Interconnect, abbreviated PCI) bus, or an extended industry standard architecture (Extended Industry Standard Architecture, abbreviated EISA) bus, among others. The buses may be divided into address buses, data buses, control buses, etc. For ease of illustration, only one thick line is shown in fig. 6, but not only one bus or one type of bus.
Fig. 7 is a schematic structural diagram of an implementation terminal according to a sixth embodiment of the present application, and as shown in fig. 7, the present application further provides an implementation terminal 80, including: a processor 801, and a memory 802 and a transceiver 803 communicatively coupled to the processor 801. Wherein the memory 802 stores computer-executable instructions; the transceiver 803 is used for receiving and transmitting data; processor 801 executes computer-executable instructions stored in memory 802 to implement the methods provided by any of the embodiments of the present application.
In particular, the program may include program code including computer-executable instructions. Memory 802 may comprise high-speed RAM memory or may also include non-volatile memory (non-volatile memory), such as at least one disk memory. Wherein computer-executable instructions are stored in memory 802 and are configured to be executed by processor 801 to implement the methods provided by any of the embodiments of the present application. The related descriptions and effects corresponding to the steps in the drawings can be understood correspondingly, and are not repeated here.
In the embodiment of the present application, the memory 802 and the processor 801 are connected through a bus. The bus may be an industry standard architecture (Industry Standard Architecture, abbreviated ISA) bus, an external device interconnect (Peripheral Component Interconnect, abbreviated PCI) bus, or an extended industry standard architecture (Extended Industry Standard Architecture, abbreviated EISA) bus, among others. The buses may be divided into address buses, data buses, control buses, etc. For ease of illustration, only one thick line is shown in fig. 7, but not only one bus or one type of bus.
The embodiment of the application also provides a computer readable storage medium, wherein computer executable instructions are stored in the computer readable storage medium, and the computer executable instructions are used for realizing the method provided by the first or second embodiment of the application when being executed by a processor.
The embodiment of the application also provides a computer program product, which comprises computer execution instructions, and the computer execution instructions realize the method provided by the first or second embodiment of the application when being executed by a processor.
In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of modules is merely a logical function division, and there may be additional divisions of actual implementation, e.g., multiple modules or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or modules, which may be in electrical, mechanical, or other forms.
The modules illustrated as separate components may or may not be physically separate, and components shown as modules may or may not be physical modules, i.e., may be located in one place, or may be distributed over a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional module in each embodiment of the present application may be integrated into one processing module, or each module may exist alone physically, or two or more modules may be integrated into one module. The integrated modules may be implemented in hardware or in hardware plus software functional modules.
Program code for carrying out methods of the present application may be written in any combination of one or more programming languages. These program code may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable full path trace fusion apparatus, such that the program code, when executed by the processor or controller, causes the functions/operations specified in the flowchart and/or block diagram block or blocks to be implemented. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of the present application, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
Moreover, although operations are depicted in a particular order, this should be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of the application. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single implementation. Conversely, various features that are described in the context of a single implementation can also be implemented in multiple implementations separately or in any suitable subcombination.
Other embodiments of the application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It is to be understood that the application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims (14)

1. A product release method, applied to an electronic device, comprising:
receiving a product release template which is sent by an implementation terminal and is filled once; the product release template comprises the following steps: the corresponding relation between each product identifier and the code engineering identifier; the one-time filled product release template comprises the following steps: a product identifier to be issued and a corresponding target code engineering identifier;
The method comprises the steps of sending a product release template which is filled once to a development terminal to obtain a product release template which is filled twice; the secondarily filled product release template comprises content information to be released corresponding to the target code engineering identifier; the content information to be published comprises: object code version and compiling parameters;
the product release template which is filled in for the second time is sent to a configuration terminal so as to obtain a filled-in product release template; the filled product release template comprises the acquisition mode of a target product release package corresponding to the product to be released;
adding the product release information corresponding to the product to be released in the completed product release template into a release and production list template to generate a target release and production list; the product release information corresponding to the product to be released comprises: the acquisition mode of the target product release package, the target code version and the compiling parameters;
and sending the target release and production list to an operation and maintenance terminal so as to prompt the operation and maintenance terminal to release the product to be released according to the product release information corresponding to the product to be released in the release and production list.
2. The method according to claim 1, wherein before receiving the one-time-filled product release template transmitted by the implementation terminal, the method comprises:
And responding to the received template acquisition request, sending the product release template to an implementation terminal so that an implementation personnel selects a product identifier to be released in the product release template, thereby determining a corresponding target code engineering identifier and forming a product release template which is filled in once.
3. The method of claim 1, wherein the transmitting the one-time filled-in product release template to the development terminal to obtain the two-time filled-in product release template comprises:
receiving a product release template which is sent by an implementation terminal and is filled once;
acquiring an object code engineering identifier from the one-time filled product release template;
determining a corresponding development terminal based on the target code engineering identifier and the code engineering personnel information table, and transmitting the once filled product release template to the corresponding development terminal so that the corresponding developer fills in the content information to be released corresponding to the target code engineering identifier in the once filled product release template to form a twice filled product release template;
and receiving the secondarily filled product release template sent by the development terminal.
4. A method according to claim 3, wherein said sending the twice filled product release template to the configuration terminal to obtain a filled product release template comprises:
The secondarily filled product release template is sent to a configuration terminal, so that the configuration terminal generates a target product release package according to the secondarily filled product release template, and the secondarily filled product release template is filled with the acquisition mode of the target product release package to form a filled product release template;
and receiving the filled product release template sent by the configuration terminal.
5. The method of claim 3, wherein before sending the twice filled product release template to the configuration terminal to obtain the filled product release template, further comprising:
based on the target code engineering identifier and the code engineering personnel information table, the secondarily filled product release template is sent to a corresponding test terminal, so that the corresponding test terminal determines whether the test of the code corresponding to the target code version in the target code engineering is passed or not, and whether the release operation of the product to be released can be performed or not is determined;
the step of sending the secondarily filled product release template to a configuration terminal to obtain a filled product release template, which comprises the following steps:
and responding to the issuable determining information sent by the test terminal, and sending the secondarily filled product release template to the configuration terminal so as to obtain the filled product release template.
6. The method of claim 5, wherein after the sending the twice-filled product release template to a test terminal, further comprising:
and receiving the product non-issuable information sent by the test terminal, and sending the product non-issuable information to the implementation terminal.
7. The product release method is characterized by being applied to an implementation terminal and comprising the following steps of:
obtaining a product release template; the product release template comprises the corresponding relation between each product identifier and the code engineering identifier;
determining corresponding target code engineering identifiers based on product identifiers to be distributed and corresponding relations between the product identifiers and the code engineering identifiers, which are determined in a product distribution template by an implementation personnel, and filling the target code engineering identifiers into corresponding records of the products to be distributed so as to generate a product distribution template which comprises the corresponding records of the products to be distributed and is filled once;
and sending the one-time filled product release template to the electronic equipment so that the electronic equipment forwards the one-time filled product release template to the development terminal.
8. The method of claim 7, wherein the product release template is in excel format: the determining the corresponding target code engineering identifier based on the product identifier to be distributed and the corresponding relation between each product identifier and the code engineering identifier, which are determined by the user in the product distribution template, and filling the target code engineering identifier into the corresponding record of the product to be distributed comprises the following steps:
And determining an object code engineering identifier corresponding to the product identifier to be issued by adopting an excel built-in function LOOKUP function and a CELL function, and filling the object code engineering identifier into a record corresponding to the product to be issued.
9. A product release apparatus, characterized by being applied to an electronic device, comprising:
the receiving module is used for receiving the once filled product release template sent by the implementation terminal; the product release template comprises the following steps: the corresponding relation between each product identifier and the code engineering identifier; the one-time filled product release template comprises the following steps: a product identifier to be issued and a corresponding target code engineering identifier;
the forwarding module is used for sending the product release template which is filled once to the development terminal so as to obtain the product release template which is filled twice; the secondarily filled product release template comprises content information to be released corresponding to the target code engineering identifier; the content information to be published comprises: object code version and compiling parameters;
the forwarding module is also used for sending the secondarily filled product release template to the configuration terminal so as to obtain a filled product release template; the filled product release template comprises the acquisition mode of a target product release package corresponding to the product to be released;
The generating module is used for adding the product release information corresponding to the product to be released in the completed product release template into the release and production list template so as to generate a target release and production list; the product release information corresponding to the product to be released comprises: the acquisition mode of the target product release package, the target code version and the compiling parameters;
and the forwarding module is also used for sending the target release and production schedule to the operation and maintenance terminal so as to prompt the operation and maintenance terminal to release the product to be released according to the product release information corresponding to the product to be released in the release and production schedule.
10. A product release device, characterized by being applied to an implementation terminal, comprising:
the acquisition module is used for acquiring a product release template; the product release template comprises the corresponding relation between each product identifier and the code engineering identifier;
the determining module is used for determining corresponding target code engineering identifiers based on product identifiers to be distributed and corresponding relations between the product identifiers and the code engineering identifiers, which are determined in the product distribution template by an implementer, and filling the target code engineering identifiers into corresponding records of the product to be distributed so as to generate a product distribution template which comprises the corresponding records of the product to be distributed and is filled at one time;
And the sending module is used for sending the product release template which is filled once to the electronic equipment so that the electronic equipment forwards the product release template which is filled once to the development terminal.
11. An electronic device, comprising: a processor, and a memory and transceiver communicatively coupled to the processor;
the memory stores computer-executable instructions; the transceiver is used for receiving and transmitting data;
the processor executes computer-executable instructions stored in the memory to implement the method of any one of claims 1-6.
12. An implementation terminal, comprising: a processor, and a memory and transceiver communicatively coupled to the processor;
the memory stores computer-executable instructions; the transceiver is used for receiving and transmitting data;
the processor executes computer-executable instructions stored in the memory to implement the method of any one of claims 7 or 8.
13. A computer readable storage medium having stored therein computer executable instructions which when executed by a processor are adapted to carry out the method of any one of claims 1-6 or any one of claims 7 or 8.
14. A computer program product comprising computer-executable instructions which, when executed by a processor, implement the method of any one of claims 1-6, or any one of claims 7 or 8.
CN202310883686.2A 2023-07-18 2023-07-18 Product release method, device, equipment, storage medium and product Pending CN116841563A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310883686.2A CN116841563A (en) 2023-07-18 2023-07-18 Product release method, device, equipment, storage medium and product

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310883686.2A CN116841563A (en) 2023-07-18 2023-07-18 Product release method, device, equipment, storage medium and product

Publications (1)

Publication Number Publication Date
CN116841563A true CN116841563A (en) 2023-10-03

Family

ID=88174198

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310883686.2A Pending CN116841563A (en) 2023-07-18 2023-07-18 Product release method, device, equipment, storage medium and product

Country Status (1)

Country Link
CN (1) CN116841563A (en)

Similar Documents

Publication Publication Date Title
CN109408375B (en) Method and device for generating interface document
CN104111885A (en) Method and device for verifying interface test results
CN105138461A (en) Interface testing method and device for application program
CN110058998B (en) Software testing method and device
CN111506358B (en) Method and device for updating container configuration
CN112181854A (en) Method, device, equipment and storage medium for generating flow automation script
CN111338869B (en) Configuration parameter management method, device, equipment and storage medium
CN111522741A (en) Interface test code generation method and device, electronic equipment and readable storage medium
CN110750434A (en) Interface testing method and device, electronic equipment and computer readable storage medium
CN111597069A (en) Program processing method, program processing apparatus, electronic device, and storage medium
US5745389A (en) System and mechanism for assigning pre-established electronic addresses to printed circuit boards
CN107450909A (en) The treating method and apparatus of validity check is integrated for SDK
CN111522881B (en) Service data processing method, device, server and storage medium
CN116841563A (en) Product release method, device, equipment, storage medium and product
CN112685077A (en) Data modification method, system, computer device and computer readable storage medium
CN115934129A (en) Software project updating method and device, computer equipment and storage medium
CN114253642B (en) System information processing method, device, electronic equipment and medium
CN115544950A (en) Constraint file importing method, device, equipment and storage medium
CN112541750B (en) Data processing method, device, equipment and computer readable storage medium
CN113190465B (en) Test information processing method, device, equipment and storage medium
CN113220595B (en) Test method and test equipment
CN116954510A (en) Data migration method, device, equipment and medium
CN116974928A (en) Dynamic test method, device, terminal equipment and medium based on data migration
KR102016606B1 (en) Method and Engine for common cause failure simulated information representation
CN115718697A (en) Version matching method of software module and optical ranging system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination