CN115964191A - Operation and maintenance control system based on DevOps platform - Google Patents
Operation and maintenance control system based on DevOps platform Download PDFInfo
- Publication number
- CN115964191A CN115964191A CN202211586512.1A CN202211586512A CN115964191A CN 115964191 A CN115964191 A CN 115964191A CN 202211586512 A CN202211586512 A CN 202211586512A CN 115964191 A CN115964191 A CN 115964191A
- Authority
- CN
- China
- Prior art keywords
- platform
- task
- devops
- module
- pipeline
- 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
Links
Images
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y04—INFORMATION OR COMMUNICATION TECHNOLOGIES HAVING AN IMPACT ON OTHER TECHNOLOGY AREAS
- Y04S—SYSTEMS INTEGRATING TECHNOLOGIES RELATED TO POWER NETWORK OPERATION, COMMUNICATION OR INFORMATION TECHNOLOGIES FOR IMPROVING THE ELECTRICAL POWER GENERATION, TRANSMISSION, DISTRIBUTION, MANAGEMENT OR USAGE, i.e. SMART GRIDS
- Y04S10/00—Systems supporting electrical power generation, transmission or distribution
- Y04S10/50—Systems or methods supporting the power network operation or management, involving a certain degree of interaction with the load-side end user applications
Landscapes
- Stored Programmes (AREA)
Abstract
The invention discloses an operation and maintenance control system based on a DevOps platform. The system comprises: a DevOps platform, an integrated management platform and a business service platform; the DevOps platform comprises a plurality of software components, and each software component executes a calling task under the condition of being called; the integrated management platform comprises a packaging module corresponding to each software component in the DevOps platform and forms an integrated interface corresponding to the DevOps platform; calling a software component in the DevOps platform through an access request of the service platform; and the service platform receives an access request to the software component in the DevOps platform through the integrated interface. According to the invention, the independent software components are packaged through the integrated management platform, so that the learning cost caused by inconsistent different functions and interfaces of a plurality of independent software components is avoided, the operation and maintenance difficulty caused by jump among the software components and data transmission during project execution is avoided, and the research, development, operation and maintenance efficiency of the operation and maintenance control system is improved.
Description
Technical Field
The invention relates to the technical field of research and development control, in particular to an operation and maintenance control system based on a DevOps platform.
Background
With the continuous development of services, the requirements of services taking the internet + as a main form on research, development, operation and maintenance support are gradually increased, and more service requirements need to be continuously integrated and continuously delivered.
At present, the efficiency can be improved only in the field of specific research and development links by introducing department-level tool support, and the whole delivery level cannot be improved, so that the research, development, operation and maintenance efficiency of the current research and development management platform is lower.
Disclosure of Invention
The invention provides an operation and maintenance control system based on a DevOps platform, which aims to solve the problem of low research, development, operation and maintenance efficiency of the current research and development management platform.
According to an aspect of the present invention, there is provided an operation and maintenance control system based on a DevOps platform, characterized in that, the DevOps platform, an integrated management platform and a service platform; wherein the content of the first and second substances,
the DevOps platform comprises a plurality of software components, and each software component executes a calling task under the condition of being called;
the integrated management platform comprises a packaging module corresponding to each software component in the DevOps platform, and an integrated interface corresponding to the DevOps platform is formed; calling a software component in the DevOps platform through an access request of the service platform;
and the business service platform receives an access request to a software component in the DevOps platform through the integrated interface.
Optionally, the integrated management platform performs data interaction with the plurality of software components of the DevOps platform through an HTTPS Restful Call interface.
Optionally, the operation and maintenance control system further includes a resource platform, and the resource platform is connected to the DevOps platform and the integrated management platform respectively;
the resource platform comprises a micro-service function module and a cloud cluster function module, wherein the micro-service function module encapsulates each software component in the DevOps platform to form an encapsulation module, and sends the encapsulation module to the integrated management platform;
and the cloud cluster function module is used for issuing the development success data of the integrated management platform to the cloud cluster and operating in the cloud cluster.
Optionally, the integrated management platform is connected to the resource platform through an external interface.
Optionally, the integrated management platform further includes a management control module, and the management control module is configured to perform life cycle management on the target project.
Optionally, the management control module includes: the system comprises a requirement acquisition sub-module, a task creation sub-module, a code management sub-module and an application deployment sub-module;
the requirement acquisition submodule is used for acquiring project requirement information of a target project and sending the project requirement information to the task creation submodule;
the task creating submodule is used for constructing at least one compiling task according to the project requirement information, issuing the compiling task to a corresponding execution terminal and receiving a compiling code sent back by the execution terminal;
the code management submodule is used for managing the compiled code corresponding to the target project;
and the application deployment submodule is used for generating an application release task of the target project and releasing the compiled code corresponding to the target project in a corresponding service cluster in an application mode.
Optionally, the integrated management platform further includes a test function module, configured to execute a test task on the target code data, where the test task includes one or more of the following: an automation unit test task, an automation UI test task, an API interface test task and a performance test task.
Optionally, the integrated management platform further includes a pipeline function module, configured to create a task pipeline, call a corresponding function module to the task pipeline, and execute a task to be executed in the task pipeline
Optionally, the task pipeline includes multiple tasks to be executed; the task pipeline comprises serial execution tasks to be executed and/or parallel execution tasks, and the tasks to be executed comprise one or more of the following items: code detection task, compiling task, testing task and deployment task.
Optionally, the pipeline function module creates pipeline nodes, each pipeline node is hung with a corresponding task to be executed, and the pipeline nodes perform data interaction with the DevOps platform.
According to the technical scheme of the embodiment of the invention, the independent software components are packaged by the integrated management platform, and the service is provided by the integrated interface, so that the research and development process can be managed in a standardized manner, the learning cost caused by inconsistent functions and interfaces of a plurality of independent software components is avoided, the operation and maintenance difficulty caused by skip among the software components and data transmission during project execution is avoided, the problem of low research, development, operation and maintenance efficiency of the current research and development management platform is solved, and the research, development, operation and maintenance efficiency of the operation and maintenance control system is improved.
It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present invention, nor do they necessarily limit the scope of the invention. Other features of the present invention will become apparent from the following description.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic structural diagram of an operation and maintenance control system based on a DevOps platform according to an embodiment of the present invention.
Detailed Description
In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
Fig. 1 is a schematic structural diagram of an operation and maintenance control system based on a DevOps platform according to an embodiment of the present invention, which is applicable to a case where a plurality of packaged software components of the DevOps platform are called through a unified user interface, where the system may be built on the DevOps platform or a system associated with the DevOps platform; the DevOps platform is a set of solution scheme formed by combining various software products, and each software runs independently. As shown in fig. 1, the system includes: a DevOps platform 110, an integrated management platform 120 and a business service platform 130; wherein, the first and the second end of the pipe are connected with each other,
the DevOps platform 110 includes a plurality of software components therein, each of which performs a calling task if called.
The software components refer to software components constituting the DevOps platform 110, and specifically, the software components of the DevOps platform 110 include, but are not limited to, a GitLab (code warehouse), a SonarQube (code quality analysis), a NexusOSS (workpiece warehouse), a Maven (compilation and build), a Harbor (Docker mirror warehouse), a Selenium (automation test), a Jenkins (DevOps pipeline), a JMeter (performance test), and Redmine (development and collaboration), which are not limited herein. In this embodiment, in the process of project development, the project requirement is realized by calling each software component in the DevOps platform 110 to execute the corresponding calling task, so as to obtain the corresponding development result.
It can be understood that, there are problems of non-uniform software interface, non-uniform user interface design and non-uniform operation method of each product in each software component in the DevOps platform, and to master the using method of the DevOps platform, each software component on the platform needs to be learned separately. The complex scheme design and high cost learning threshold prevent DevOps from popularizing and applying to a certain extent and the deep application of development team on DevOps. In order to realize research, development, operation and maintenance management, complex functions of different software can be packaged into a simple and easy-to-use user interface, and a user can master the use of the platform without learning various specialties of the DevOps platform.
An integrated management platform 120 including a packaging module corresponding to each of the software components in the DevOps platform 110, forming an integrated interface corresponding to the DevOps platform 110; and, making calls to software components in the DevOps platform 110 through access requests of the business services platform 130.
The encapsulation module is obtained by encapsulating each software component in the DevOps platform 110. In this embodiment, the integrated management platform 120 encapsulates each software component in the DevOps platform 110 through the micro service resource management function, and micro-services each software component to form an integrated interface corresponding to the DevOps platform 110; the integrated interface is a unified user interface of each software component in the DevOps platform 110, and the integrated interface includes, but is not limited to, an integrated interface UI, an integrated access logic, a normalized data interface, and the like, which is not limited herein. By packaging each software component in the DevOps platform 110 to form an integrated interface, the difference and complexity of the use methods of each different software are shielded, thereby improving the efficiency of developing, operating and maintaining.
In this embodiment, the integrated management platform 120 may also call a software component in the DevOps platform 110 through an access request of the service platform 130, so as to execute a corresponding call task, implement a project requirement, and obtain a corresponding development result.
In some embodiments, the unified management platform 120 is further configured to implement full lifecycle management of the data of each package module.
The business service platform 130 receives an access request to the software component in the DevOps platform 110 through the unified interface.
In this embodiment, during development, the business service platform 130 may receive an access request for a software component in the DevOps platform 110 through the integrated user interface, and call the corresponding software component based on the access request, thereby completing a software development project. The business service platform 130 is a plurality of development platforms providing access services for users, the users can be program developers, research and development personnel can directly call functions through an integrated interface without acquiring operation methods of all software, operation and maintenance difficulties caused by jumping among software components and data transmission during project execution are avoided, and research and development operation and maintenance efficiency is improved.
According to the technical scheme, the independent software components are packaged through the integrated management platform, services are provided through the integrated interface, the research and development process can be managed in a standardized mode, the learning cost caused by inconsistent increase of different functions and interfaces of a plurality of independent software components is avoided, the operation and maintenance difficulty caused by skip among the software components and data transmission when projects are executed is avoided, the problem that the research, development, operation and maintenance efficiency of the current research and development management platform is low is solved, and the research, development, operation and maintenance efficiency of the operation and maintenance control system is improved.
On the basis of the above embodiment, optionally, the unified management platform 120 performs data interaction with the plurality of software components of the DevOps platform 110 through the HTTPS Restful Call interface.
In this embodiment, the integrated management platform 120 may perform data interaction with each software component of the DevOps platform 110 through the HTTPS Restful Call interface, so as to realize the integration of each software component and the Call to each software component.
On the basis of the above embodiment, optionally, the operation and maintenance control system further includes a resource platform, and the resource platform is respectively connected to the DevOps platform 110 and the integrated management platform 120; the resource platform comprises a micro service function module and a cloud cluster function module, wherein the micro service function module encapsulates each software component in the DevOps platform 110 to form an encapsulation module, and sends the encapsulation module to the integrated management platform 120; the cloud cluster function module is configured to issue the development success data of the integrated management platform 120 to the cloud cluster, and operate in the cloud cluster.
In this embodiment, the micro service function module is used to support the integrated management platform 120 to encapsulate each software component in the DevOps platform 110, form a corresponding encapsulated module, and send the encapsulated module to the integrated management platform 120; specifically, the micro service function module may deeply interface the integrated management platform 120 and the DevOps platform 110, complete interfacing of software such as gillab, sonarQube, jenkins and the like in the DevOps platform 110, and the DevOps platform 110 completes support of a DevOps full flow for developing a project in a "interfacing + enhancing" manner.
It should be noted that micro-servization is a methodology for developing and supporting an application with a series of small services, and the services interact independently in their own process through a lightweight communication mechanism.
In this embodiment, the cloud cluster function module may be configured to access the integrated management platform 120 to the cloud cluster, issue the development success data of the integrated management platform 120 to the cloud cluster, and operate in the cloud cluster. The development success data refers to data related to a development result of a development project, and specifically, the development success data may be an application, a program, or other information that may be published in a cloud cluster. In the embodiment, the integrated management platform is accessed to the cloud cluster, so that the efficiency of successful development data release can be improved, and the full life cycle management of successful development data is realized.
On the basis of the above embodiment, optionally, the integrated management platform 120 is connected to the resource platform through an external interface.
In this embodiment, the integrated management platform 120 further includes a docking management module, the docking management module includes an external interface, and the integrated management platform can dock with the resource platform through the external interface.
On the basis of the foregoing embodiment, optionally, the integrated management platform 120 further includes a management control module, and the management control module is configured to perform life cycle management on the target item.
The target project refers to a project being developed in the system. In this embodiment, the management control module is configured to perform lifecycle management from a demand to an application release on a target item in the system.
On the basis of the foregoing embodiment, optionally, the management control module includes: the system comprises a requirement acquisition sub-module, a task creation sub-module, a code management sub-module and an application deployment sub-module; the requirement acquisition submodule is used for acquiring project requirement information of a target project and sending the project requirement information to the task creation submodule; the task creating submodule is used for constructing at least one compiling task according to the project requirement information, issuing the compiling task to a corresponding execution terminal and receiving a compiling code sent back by the execution terminal; the code management submodule is used for managing the compiled codes corresponding to the target projects; and the application deployment sub-module is used for generating an application release task of the target project and releasing the compiled codes corresponding to the target project in a corresponding service cluster in an application mode.
In the embodiment, in the development process of the target project, the requirement acquisition sub-module receives the task trigger instruction, analyzes the task trigger instruction to obtain project requirement information in the task trigger instruction, and sends the project requirement information to the task creation sub-module; after receiving the project requirement, the task creating sub-module carries out information splitting on the received project requirement information to obtain a plurality of task information, respectively constructs corresponding compiling tasks based on the task information, issues the compiling tasks to corresponding execution terminals, and receives task results sent back by the execution terminals; the code management submodule is used for creating a code warehouse of the target project and managing the compiled codes of the target project based on the code warehouse; and the application deployment submodule creates an application release task of the target project through the template file and releases the compiled code corresponding to the target project in the service cluster in an application form.
On the basis of the foregoing embodiment, optionally, the unified management platform 120 further includes a test function module, configured to execute a test task on the target code data, where the test task includes one or more of the following: an automation unit test task, an automation UI test task, an API interface test task, and a performance test task.
The object code data refers to a compiled code of the object item. In this embodiment, the test function module may execute a unit test task on the compiled code of the target project, track an execution state of the compiled code of the target project, and display a test result of the compiled code of each test case on the target project. After the test script is executed, the integrated management platform 120 automatically updates the test case list and displays the final test execution result (non-execution, successful execution, and failed execution). It should be noted that, in the process of executing the test case, the operation and maintenance control system may synchronously display the detailed log of executing the test case.
In this embodiment, the test function module may also be configured to execute an automated UI test task on the compiled code of the target project, track an execution state of the automated UI test task, and display, for the executed task, a test result of each UI test case through the integrated interface by the integrated management platform 120. It should be noted that the automated UI test is performed based on an integrated interface of the mainstream UI test framework.
In this embodiment, the test function module may also be configured to execute an API interface test task on the compiled code of the target project, track an execution state of the API interface test task, and display, for the executed task, a test result of each API interface test case through the integrated interface by the integrated management platform 120. It should be noted that the API interface testing task is performed based on an integrated interface of the mainstream API interface testing framework.
In this embodiment, the test function module is further configured to execute a performance test task on the compiled code of the target project, track an execution state of the performance test task, and display, for the executed task, a test result of each performance test case through the integrated interface by the integrated management platform 120. It should be noted that the performance test is performed based on an integrated interface of the mainstream performance test framework.
On the basis of the foregoing embodiment, optionally, the integrated management platform 120 further includes a pipeline function module, configured to create a task pipeline, call a corresponding function module to the task pipeline, and execute a task to be executed in the task pipeline.
The task pipeline refers to a pipeline for executing tasks to be executed in the process of project development and application release. In this embodiment, the pipeline function module creates a task pipeline, calls the function module corresponding to each task to be executed in the task pipeline according to the task pipeline, and executes the task to be executed in the pipeline based on the function module.
It can be understood that the pipeline function of the pipeline function module is realized through an integrated interface on the basis of Jenkins software.
On the basis of the above embodiment, optionally, the task pipeline includes a plurality of tasks to be executed; the task pipeline comprises serially executed tasks to be executed and/or parallelly executed tasks, and the tasks to be executed comprise one or more of the following items: code detection task, compiling task, testing task and deployment task.
In this embodiment, in the process of project development, the multiple tasks to be executed may be managed in association as required according to the multiple tasks to be executed in the execution task pipeline in which the task pipeline is created in parallel, or the multiple tasks to be executed in the execution task pipeline in series, so as to improve the delivery efficiency.
On the basis of the above embodiment, optionally, the pipeline function module creates pipeline nodes, each of which is hung with a corresponding task to be executed, and the pipeline nodes perform data interaction with the DevOps platform 110.
The pipeline nodes refer to task nodes of each task to be executed, and each pipeline node in the task pipeline corresponds to one task to be executed. In this embodiment, the pipeline function module creates pipeline nodes, and each pipeline node is hung with a corresponding task to be executed; the pipeline functional module realizes data interaction between the pipeline node and the DevOps platform 110 by calling the functional module corresponding to the pipeline node and executing the corresponding task to be executed in serial or parallel based on the called functional module.
Illustratively, taking a functional module corresponding to a pipeline node as a test functional module as an example, each software component in the test functional module is integrated with the pipeline functional module through a Plug-in interface, and the pipeline functional module calls the test functional module in a DevOps pipeline node manner and executes a corresponding test task. The test class component includes: selenium (automated testing), JMeter (performance testing), API Test, unit Test.
It should be understood that various forms of the flows shown above, reordering, adding or deleting steps, may be used. For example, the steps described in the present invention may be executed in parallel, sequentially, or in different orders, and are not limited herein as long as the desired result of the technical solution of the present invention can be achieved.
The above-described embodiments should not be construed as limiting the scope of the invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. An operation and maintenance control system based on a DevOps platform is characterized by comprising the DevOps platform, an integrated management platform and a service platform; wherein the content of the first and second substances,
the DevOps platform comprises a plurality of software components, and each software component executes a calling task under the condition of being called;
the integrated management platform comprises a packaging module corresponding to each software component in the DevOps platform, and an integrated interface corresponding to the DevOps platform is formed; calling a software component in the DevOps platform through an access request of the service platform;
and the business service platform receives an access request to a software component in the DevOps platform through the integrated interface.
2. The operation and maintenance control system according to claim 1, wherein the unified management platform performs data interaction with the plurality of software components of the DevOps platform through an HTTPS Restful Call interface.
3. The operation and maintenance control system according to claim 1, further comprising a resource platform connected with the DevOps platform and the integrated management platform, respectively;
the resource platform comprises a micro-service function module and a cloud cluster function module, wherein the micro-service function module encapsulates each software component in the DevOps platform to form an encapsulation module, and sends the encapsulation module to the integrated management platform;
and the cloud cluster function module is used for issuing the development success data of the integrated management platform to a cloud cluster and operating in the cloud cluster.
4. The operation and maintenance control system according to claim 3, wherein the integrated management platform is connected with the resource platform through an external interface.
5. The operation and maintenance control system according to claim 1, wherein the integrated management platform further comprises a management control module, and the management control module is configured to perform lifecycle management on the target project.
6. The operation and maintenance control system according to claim 5, wherein the management control module comprises: the system comprises a requirement acquisition sub-module, a task creation sub-module, a code management sub-module and an application deployment sub-module;
the requirement acquisition submodule is used for acquiring project requirement information of a target project and sending the project requirement information to the task creation submodule;
the task creating submodule is used for constructing at least one compiling task according to the project requirement information, issuing the compiling task to a corresponding execution terminal and receiving a compiling code sent back by the execution terminal;
the code management submodule is used for managing the compiled code corresponding to the target project;
and the application deployment sub-module is used for generating an application release task of the target project and releasing the compiled codes corresponding to the target project in a corresponding service cluster in an application mode.
7. The operation and maintenance control system according to claim 1, wherein the integrated management platform further comprises a test function module, configured to execute a test task on the target code data, where the test task includes one or more of the following: an automation unit test task, an automation UI test task, an API interface test task, and a performance test task.
8. The operation and maintenance control system according to claim 1, wherein the integrated management platform further comprises a pipeline function module, configured to create a task pipeline, and call a corresponding function module to the task pipeline to execute a task to be executed in the task pipeline.
9. The operation and maintenance control system according to claim 8, wherein the task pipeline comprises a plurality of tasks to be executed; the task pipeline comprises serially executed tasks to be executed and/or parallelly executed tasks, and the tasks to be executed comprise one or more of the following items: code detection task, compiling task, testing task and deployment task.
10. The operation and maintenance control system according to claim 9, wherein the pipeline function module creates pipeline nodes, each pipeline node is hung with a corresponding task to be executed, and the pipeline nodes perform data interaction with the DevOps platform.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211586512.1A CN115964191A (en) | 2022-12-09 | 2022-12-09 | Operation and maintenance control system based on DevOps platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211586512.1A CN115964191A (en) | 2022-12-09 | 2022-12-09 | Operation and maintenance control system based on DevOps platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115964191A true CN115964191A (en) | 2023-04-14 |
Family
ID=87351920
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211586512.1A Pending CN115964191A (en) | 2022-12-09 | 2022-12-09 | Operation and maintenance control system based on DevOps platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115964191A (en) |
-
2022
- 2022-12-09 CN CN202211586512.1A patent/CN115964191A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109933522B (en) | Test method, test system and storage medium for automatic case | |
| CN107590186B (en) | Method for managing and executing data processing policy and policy engine system | |
| CN103198009B (en) | A kind of universal testing method, system and related device | |
| CN105843684B (en) | Managing task execution | |
| CN109683899A (en) | A kind of software integrating method and device | |
| US20050044532A1 (en) | System and method for testing and/or debugging runtime sytems for solving mes manufacturing execution system problems | |
| CN108519952A (en) | A kind of distributed WEB automatization test systems and method | |
| CN113268319A (en) | Business process customization and distributed process scheduling method based on micro-service architecture | |
| CN110399119A (en) | A kind of modularization construction method, device, electronic equipment and storage medium | |
| US20210133091A1 (en) | System and method for implementing mainframe continuous integration continuous development | |
| CN105975351A (en) | User behavior message reporting method and apparatus | |
| CN110620815A (en) | Distributed micro-service system based on side car mode | |
| CN109656528A (en) | Measured modularization software development methodology | |
| CN114816375A (en) | Service arranging method, device, equipment and storage medium | |
| Riccobene et al. | A modeling and executable language for designing and prototyping service-oriented applications | |
| CN114579469A (en) | Full link interface test method and device, electronic equipment and storage medium | |
| CN111104181A (en) | Webpage data filling system for visually editing task flow | |
| CN110262782A (en) | The interface comparison method and device of software systems | |
| CN115964191A (en) | Operation and maintenance control system based on DevOps platform | |
| CN115056234B (en) | RPA controller scheduling method and system based on event-driven and infinite state machine | |
| CN112328225A (en) | Page operation method and operation system thereof | |
| US20100058198A1 (en) | Collaborative realtime planning using a model driven architecture and iterative planning tools | |
| CN116974716A (en) | Scheduling task issuing method and device, electronic equipment and storage medium | |
| Liu et al. | New model of SaaS: SaaS with tenancy agency | |
| CN114115821A (en) | Application development method and platform, application deployment method and node, system and equipment |
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 |