CN111679832B - Tool assembly integration method and device based on DevOps platform - Google Patents
Tool assembly integration method and device based on DevOps platform Download PDFInfo
- Publication number
- CN111679832B CN111679832B CN202010494413.5A CN202010494413A CN111679832B CN 111679832 B CN111679832 B CN 111679832B CN 202010494413 A CN202010494413 A CN 202010494413A CN 111679832 B CN111679832 B CN 111679832B
- Authority
- CN
- China
- Prior art keywords
- tool
- integrated
- tool component
- information
- devops platform
- 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.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application discloses a tool component integration method and device based on a DevOps platform, wherein the method comprises the following steps: receiving configuration information of tool components to be integrated through a unified interface provided by a DevOps platform, wherein the unified interface is used for calling different tool components; calling the tool component to be integrated according to the configuration information of the tool component to be integrated; and reading log data generated in the calling process of the tool component to be integrated. The application has simple operation, high operation efficiency and strong expandability.
Description
Technical Field
The application relates to the technical field of computers, in particular to a tool assembly integration method and device based on a DevOps platform.
Background
In the current digital age, the introduction of the DevOps can have profound effects on product delivery, testing, function development and maintenance, wherein the DevOps is a collective term for a set of processes, methods and systems, and is used for promoting communication, collaboration and integration among development (application/software engineering), technical operation and Quality Assurance (QA) departments. Because different products have different tool components in links of compiling, constructing, testing, code review, deployment and the like. In particular, in banking industry, there are many development lines with COBOL, CSPS, PLSQL and other features, many tools are developed autonomously, which results in failure to integrate all tool components on one platform completely, and each time one tool component is added, a version of the platform needs to be modified, which is complex in operation, low in operation efficiency, and lacks in scalability.
Disclosure of Invention
The embodiment of the application provides a tool component integration method based on a DevOps platform, which has the advantages of simple operation, high operation efficiency and strong expandability, and comprises the following steps:
receiving configuration information of tool components to be integrated through a unified interface provided by a DevOps platform, wherein the unified interface is used for calling different tool components;
calling the tool component to be integrated according to the configuration information of the tool component to be integrated;
reading log data generated in the calling process of the tool component to be integrated;
further comprises:
receiving an externally input query instruction;
feeding back the operation information of the tool component to be integrated according to the query instruction; and inquiring a quality index generated by the operation of the tool component to be integrated, and judging whether the quality index meets the quality requirement.
Optionally, the method further comprises:
and analyzing the log data and formatting and outputting the log data.
Optionally, the configuration information includes: tool component name information, tool component source information, and log structure information.
The embodiment of the application also provides a tool component integration device based on the DevOps platform, which has the advantages of simple operation, high operation efficiency and strong expandability, and comprises:
the configuration information receiving module is used for receiving configuration information of the tool components to be integrated through a unified interface provided by the DevOps platform, and the unified interface is used for calling different tool components;
the tool component calling module is used for calling the tool component to be integrated according to the configuration information of the tool component to be integrated;
the log data reading module is used for reading log data generated in the calling process of the tool component to be integrated;
further comprises:
the instruction receiving module is used for receiving an externally input query instruction;
the information feedback module is used for feeding back the operation information of the tool component to be integrated according to the query instruction; and inquiring a quality index generated by the operation of the tool component to be integrated, and judging whether the quality index meets the quality requirement.
Optionally, the apparatus further includes:
and the data analysis module is used for analyzing the log data and formatting and outputting the log data.
Optionally, the configuration information includes: tool component name information, tool component source information, and log structure information.
The embodiment of the application also provides computer equipment, which comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor realizes the method when executing the computer program.
Embodiments of the present application also provide a computer-readable storage medium storing a computer program for executing the above method.
In the embodiment of the application, the configuration information of the tool component to be integrated is received through the unified interface provided by the DevOps platform, the tool component to be integrated is called according to the configuration information of the tool component to be integrated, the log data generated in the calling process of the tool component to be integrated is read, and the calling of the tool component to be integrated on the DevOps platform is realized while the quick integration of different tool components to be integrated on the DevOps platform is realized.
Drawings
In order to more clearly illustrate the embodiments of the application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art. In the drawings:
FIG. 1 is a flow chart of a method for integrating tool components based on a DevOps platform in an embodiment of the application;
FIG. 2 is a flow chart of a method for integrating tool components based on a DevOps platform according to an embodiment of the present application;
FIG. 3 is a flowchart of a query for running information of a tool component to be integrated according to an embodiment of the present application;
FIG. 4 is a schematic diagram of a tool component integration apparatus based on a DevOps platform according to an embodiment of the present application;
FIG. 5 is a schematic diagram of another embodiment of a tool assembly integrated device based on a DevOps platform;
fig. 6 is a schematic structural diagram of a device for querying running information of a tool component to be integrated according to an embodiment of the present application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the embodiments of the present application will be described in further detail with reference to the accompanying drawings. The exemplary embodiments of the present application and their descriptions herein are for the purpose of explaining the present application, but are not to be construed as limiting the application.
In the description of the present specification, the terms "comprising," "including," "having," "containing," and the like are open-ended terms, meaning including, but not limited to. The description of the reference terms "one embodiment," "a particular embodiment," "some embodiments," "for example," etc., means that a particular feature, structure, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiments or examples. Furthermore, the particular features, structures, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. The order of steps involved in the embodiments is illustrative of the practice of the application, and is not limited and may be suitably modified as desired.
Fig. 1 is a flowchart of a tool component integration method based on a DevOps platform according to an embodiment of the application, where, as shown in fig. 1, the method includes:
step 101, receiving configuration information of tool components to be integrated through a unified interface provided by a DevOps platform, wherein the unified interface is used for calling different tool components.
Because the unified interface is configured, different tool components to be integrated can be called, and meanwhile, the data after execution can be read, and when the unified interface is implemented, the input parameters of the unified interface can be tool component name information and tool component source information, the output parameters can be log structure information and return code information.
In the implementation, when a certain tool component is required to be integrated on the DevOps platform, the tool component is only required to be integrated on the DevOps platform through the unified interface, and when the tool component is not required, the relevant parameters of the tool component are only required to be deleted on the DevOps platform.
Step 102, calling the tool component to be integrated according to the configuration information of the tool component to be integrated.
In this embodiment, the DevOps platform may perform tasks such as calling different tools and log parsing through the engine.
The configuration information includes: tool component name information, tool component source information, and log structure information.
In specific implementation, taking a component of a tool to be integrated as a code review tool as an example, the name of the code review tool, the source of the component, the front-end information Id (which is used for inquiring which configuration parameters are needed for the front end of the tool in a front-end information configuration table), the log structure Id (which is used for inquiring the structure of the running log of the tool in a log information configuration table so as to be analyzed by a platform), the returned result Id (which is used for configuring the returned information represented by the returned code and success or failure in the returned result table), and the quality index Id (which is used for inquiring the quality index generated by the running of the tool in a quality index configuration table so as to be controlled by the platform) are required to be configured.
Wherein, the code review tool assembly basic information configuration table is as follows in table 1:
TABLE 1
Component name | Component source | Front end information id | Log structure id | Returned result id | Quality index id |
Code review | Autonomous development | 101 | 101 | 101 | 101 |
Wherein, the front-end information configuration table is as follows in table 2:
TABLE 2
Front end information id | Parameter name | Type(s) | Value range |
101 | Development language | Enumeration of | Java,Cobol |
The DevOps platform can dynamically generate a front-end interface for the tool that requires input content at the front-end based on this table.
The log information configuration table is as follows table 3:
TABLE 3 Table 3
The DevOps platform can parse the log according to the table to display the running log of the tool for the user.
The returned result information configuration table is as follows in table 4:
TABLE 4 Table 4
Returned result id | Return code | Returning information | Whether or not to succeed |
101 | 0004 | ssh call failure | Whether or not |
The DevOps platform can query the running result of the tool according to the table and display the running result at the front end in time.
The returned result information configuration table is as follows in table 5:
TABLE 5
Quality index id | Index name | Type(s) | Range |
101 | Success rate of construction | Digital type | Less than 100% |
The DevOps platform can query the quality index generated by the tool according to the table so as to judge whether the quality index meets the quality requirement.
And step 103, reading log data generated in the calling process of the tool component to be integrated.
As can be seen from fig. 1, in the tool component integration method based on the DevOps platform provided by the embodiment of the application, the configuration information of the tool component to be integrated is received through the unified interface provided by the DevOps platform, the tool component to be integrated is called according to the configuration information of the tool component to be integrated, the log data generated in the calling process of the tool component to be integrated is read, and when different tool components to be integrated are rapidly integrated on the DevOps platform, the calling of the tool component to be integrated on the DevOps platform is realized, so that the whole process is simple to operate, the working efficiency is high, and the expandability is strong.
Fig. 2 is a further flowchart of a tool component integration method based on a DevOps platform according to an embodiment of the application, where, as shown in fig. 2, the method further includes:
and step 201, analyzing the log data and formatting and outputting the log data.
Because the user cannot directly read the meaning of the log data generated in the calling process of the tool component to be integrated, the log data is analyzed, formatted and output and displayed to the user, so that the user can conveniently track the problem of the use of the tool component to be integrated.
FIG. 3 is a flowchart of querying running information of a tool component to be integrated according to an embodiment of the present application, where, as shown in FIG. 3, the method further includes:
step 301, receiving an externally input query instruction.
Step 302, feeding back the operation information of the tool component to be integrated according to the query instruction.
In this embodiment, the "operation information" may be the operation result of the tool component to be integrated, i.e. the success or failure of its operation.
When the embodiment of the application is applied specifically, any tool component is accessed to the DevOps platform for a user to use, and only the following steps are needed:
encapsulating the tool assembly according to a unified interface issued by the DevOps platform;
uploading the tool assembly to a specified location;
selecting the tool component when the user creates the pipeline;
the platform calls the name of the tool assembly to inquire the parameters and types to be input at the front end of the tool assembly, and the parameters and types to be input are dynamically displayed at the front end so as to be used for inputting information by a user;
the scheduling engine of the DevOps platform calls the tool component to operate according to the interface, and meanwhile, operation log analysis is carried out according to log configuration of the tool component, and the operation log is displayed at the front end of the interface in real time;
after the operation is finished, the DevOps platform obtains a return code of the operation of the tool assembly, queries whether the operation result is successful or failed according to the configuration of the return result, and displays the operation result on the pipeline.
If the pipeline is configured with a quality access control, comparing and analyzing the quality index operated by the tool component with an access control value so as to determine whether the pipeline can still continue to operate.
Wherein, the pipeline refers to: and (3) connecting the process tasks of construction, deployment, testing, code review, safety scanning and the like in series in the operation process of the DevOps platform.
The quality gate inhibition refers to: and if the threshold value of the quality index is not reached, stopping the pipeline operation.
Based on the same inventive concept, the embodiment of the application also provides a tool assembly integration device based on the DevOps platform, as described in the following embodiment. Since the principle of solving the problem of the tool assembly integration device based on the DevOps platform is similar to that of the tool assembly integration method based on the DevOps platform, the implementation of the tool assembly integration device based on the DevOps platform can be referred to the implementation of the tool assembly integration method based on the DevOps platform, and the repetition is omitted. As used below, the term "unit" or "module" may be a combination of software and/or hardware that implements the intended function. While the means described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and contemplated.
Fig. 4 is a schematic structural diagram of a tool assembly integrated device based on a DevOps platform according to an embodiment of the application, and as shown in fig. 4, the device includes:
the configuration information receiving module 401 is configured to receive configuration information of a tool component to be integrated through a unified interface provided by the DevOps platform, where the unified interface is used to call different tool components.
And the tool component calling module 402 is configured to call the tool component to be integrated according to the configuration information of the tool component to be integrated.
And the log data reading module 403 is configured to read log data generated in the calling process of the tool component to be integrated.
Fig. 5 is a schematic structural diagram of a tool assembly integrated device based on a DevOps platform according to an embodiment of the application, where, as shown in fig. 5, the device further includes:
the data parsing module 501 is configured to parse the log data and format the log data for output.
In an embodiment of the present application, the configuration information includes: tool component name information, tool component source information, and log structure information.
Fig. 6 is a schematic structural diagram of a device for querying running information of a tool assembly to be integrated according to an embodiment of the present application, as shown in fig. 6, where the device further includes:
the instruction receiving module 601 is configured to receive an externally input query instruction.
And the information feedback module 602 is configured to feed back the operation information of the tool component to be integrated according to the query instruction.
The embodiment of the application also provides computer equipment, which comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor realizes the method when executing the computer program.
Embodiments of the present application also provide a computer-readable storage medium storing a computer program for executing the above method.
In summary, in the tool component integration method based on the DevOps platform provided by the embodiment of the application, the configuration information of the tool component to be integrated is received through the unified interface provided by the DevOps platform, the tool component to be integrated is called according to the configuration information of the tool component to be integrated, the log data generated in the calling process of the tool component to be integrated is read, and when different tool components to be integrated are rapidly integrated on the DevOps platform, the calling of the tool component to be integrated on the DevOps platform is realized.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The foregoing description of the embodiments has been provided for the purpose of illustrating the general principles of the application, and is not meant to limit the scope of the application, but to limit the application to the particular embodiments, and any modifications, equivalents, improvements, etc. that fall within the spirit and principles of the application are intended to be included within the scope of the application.
Claims (8)
1. A method for integrating tool components based on a DevOps platform, comprising:
receiving configuration information of tool components to be integrated through a unified interface provided by a DevOps platform, wherein the unified interface is used for calling different tool components;
calling the tool component to be integrated according to the configuration information of the tool component to be integrated;
reading log data generated in the calling process of the tool component to be integrated;
further comprises:
receiving an externally input query instruction;
feeding back the operation information of the tool component to be integrated according to the query instruction; after the operation is finished, the DevOps platform obtains a return code of the operation of the tool assembly, and inquires whether the operation result is successful or failed according to the configuration of the return result, and displays the result on the operation result of the assembly line; if the assembly line is provided with the quality gate inhibition, comparing the quality index operated by the tool assembly with the quality gate inhibition to determine whether the assembly line can still continue to operate; wherein, the pipeline refers to: executable jobs that connect tasks of construction, deployment, testing, code review, and security scan in series during the operation of the DevOps platform; the quality gate inhibition refers to: and if the threshold value of the quality index is not reached, stopping the pipeline operation.
2. The method as recited in claim 1, further comprising:
and analyzing the log data and formatting and outputting the log data.
3. The method of claim 1, wherein the configuration information comprises: tool component name information, tool component source information, and log structure information.
4. A DevOps platform-based tool assembly integration apparatus, comprising:
the configuration information receiving module is used for receiving configuration information of the tool components to be integrated through a unified interface provided by the DevOps platform, and the unified interface is used for calling different tool components;
the tool component calling module is used for calling the tool component to be integrated according to the configuration information of the tool component to be integrated;
the log data reading module is used for reading log data generated in the calling process of the tool component to be integrated;
further comprises:
the instruction receiving module is used for receiving an externally input query instruction;
the information feedback module is used for feeding back the operation information of the tool component to be integrated according to the query instruction;
the module is used for acquiring a return code of the tool assembly operation by the DevOps platform after the operation is finished, inquiring whether the operation result is successful or failed according to the configuration of the return result, and displaying the operation result on the operation result of the assembly line;
the module is used for comparing the quality index operated by the tool assembly with the quality access control if the assembly line is configured with the quality access control, and determining whether the assembly line can still operate continuously;
wherein, the pipeline refers to: executable jobs that connect tasks of construction, deployment, testing, code review, and security scan in series during the operation of the DevOps platform; the quality gate inhibition refers to: and if the threshold value of the quality index is not reached, stopping the pipeline operation.
5. The apparatus as recited in claim 4, further comprising:
and the data analysis module is used for analyzing the log data and formatting and outputting the log data.
6. The apparatus of claim 4, wherein the configuration information comprises: tool component name information, tool component source information, and log structure information.
7. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method of any of claims 1 to 3 when executing the computer program.
8. A computer readable storage medium, characterized in that it stores a computer program which, when executed by a processor, implements the method of any one of claims 1 to 3.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202010494413.5A CN111679832B (en) | 2020-06-03 | 2020-06-03 | Tool assembly integration method and device based on DevOps platform |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202010494413.5A CN111679832B (en) | 2020-06-03 | 2020-06-03 | Tool assembly integration method and device based on DevOps platform |
Publications (2)
Publication Number | Publication Date |
---|---|
CN111679832A CN111679832A (en) | 2020-09-18 |
CN111679832B true CN111679832B (en) | 2023-10-24 |
Family
ID=72434613
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202010494413.5A Active CN111679832B (en) | 2020-06-03 | 2020-06-03 | Tool assembly integration method and device based on DevOps platform |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN111679832B (en) |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN114615176B (en) * | 2022-03-07 | 2024-05-24 | 中银金融科技有限公司 | Message testing method and device and electronic equipment |
CN114625451A (en) * | 2022-03-28 | 2022-06-14 | 深圳市金蝶天燕云计算股份有限公司 | Component access method and device of DevOps system |
CN114968191A (en) * | 2022-05-03 | 2022-08-30 | 远光软件股份有限公司 | Research and development project and tool docking method, device, electronic equipment and storage medium |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6598037B1 (en) * | 1999-07-26 | 2003-07-22 | Microsoft Corporation | Data table object interface for datastore |
CN106126679A (en) * | 2016-06-29 | 2016-11-16 | 江苏电力信息技术有限公司 | A kind of exploitation O&M application process of cloud service-oriented |
CN110347575A (en) * | 2018-04-04 | 2019-10-18 | 中移(杭州)信息技术有限公司 | A kind of adjustment method based on big data component, device, terminal device and medium |
CN111221591A (en) * | 2019-12-27 | 2020-06-02 | 中国建设银行股份有限公司 | Method, system and medium for detecting availability of micro-service deployed based on Kubernetes |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3511834B1 (en) * | 2018-01-10 | 2020-10-21 | Tata Consultancy Services Limited | System and method for tool chain data capture through parser for empirical data analysis |
-
2020
- 2020-06-03 CN CN202010494413.5A patent/CN111679832B/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6598037B1 (en) * | 1999-07-26 | 2003-07-22 | Microsoft Corporation | Data table object interface for datastore |
CN106126679A (en) * | 2016-06-29 | 2016-11-16 | 江苏电力信息技术有限公司 | A kind of exploitation O&M application process of cloud service-oriented |
CN110347575A (en) * | 2018-04-04 | 2019-10-18 | 中移(杭州)信息技术有限公司 | A kind of adjustment method based on big data component, device, terminal device and medium |
CN111221591A (en) * | 2019-12-27 | 2020-06-02 | 中国建设银行股份有限公司 | Method, system and medium for detecting availability of micro-service deployed based on Kubernetes |
Also Published As
Publication number | Publication date |
---|---|
CN111679832A (en) | 2020-09-18 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN111679832B (en) | Tool assembly integration method and device based on DevOps platform | |
CN113961332B (en) | Workflow engine implementation method and device, electronic equipment and storage medium | |
US20030131342A1 (en) | Debugger with activity alert | |
CN108228173B (en) | Visual data interface development system and method | |
CN110334097B (en) | Table structure modification method, device, equipment, and computer-readable storage medium | |
CN111966597B (en) | Test data generation method and device | |
CN108959508B (en) | SQL data generation method and device | |
US9336247B2 (en) | Control data driven modifications and generation of new schema during runtime operations | |
CN117785920A (en) | Intelligent data analysis processing method, device, equipment and medium | |
CN112559339B (en) | Automatic test verification method and test system based on data template engine | |
CN111651470A (en) | Unified SQL execution and query method and system | |
CN111427784B (en) | Data acquisition method, device, equipment and storage medium | |
US20050204339A1 (en) | Standard application development template | |
CN113495723B (en) | Method, device and storage medium for calling functional component | |
CN113297081B (en) | Execution method and device of continuous integrated pipeline | |
US6993749B2 (en) | Conditional debug monitors | |
CN117435513B (en) | Test case generation method, terminal equipment and computer readable storage medium | |
CN118503105A (en) | Automatic test method, device, equipment, medium and product | |
CN116661758B (en) | Method, device, electronic equipment and medium for optimizing log framework configuration | |
CN110209565A (en) | A kind of metadata schema adjustment method and its device | |
US6983454B2 (en) | Extended “run to” function | |
CN108763474B (en) | Method, device and storage medium for acquiring transaction correlation and executing regression test | |
CN111160403A (en) | Method and device for multiplexing and discovering API (application program interface) | |
CN111026719A (en) | Data processing apparatus and control method thereof | |
CN112650683B (en) | Program testing method, device and storage medium |
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 | ||
GR01 | Patent grant | ||
GR01 | Patent grant |