CN115291928A - Task automatic integration method and device of multiple technology stacks and electronic equipment - Google Patents
Task automatic integration method and device of multiple technology stacks and electronic equipment Download PDFInfo
- Publication number
- CN115291928A CN115291928A CN202210756797.2A CN202210756797A CN115291928A CN 115291928 A CN115291928 A CN 115291928A CN 202210756797 A CN202210756797 A CN 202210756797A CN 115291928 A CN115291928 A CN 115291928A
- Authority
- CN
- China
- Prior art keywords
- task
- acquiring
- configuration
- request
- tasks
- 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
- 238000005516 engineering process Methods 0.000 title claims abstract description 74
- 238000000034 method Methods 0.000 title claims abstract description 63
- 230000010354 integration Effects 0.000 title claims abstract description 42
- 238000012360 testing method Methods 0.000 claims description 10
- 238000004590 computer program Methods 0.000 claims description 3
- 238000012423 maintenance Methods 0.000 abstract description 6
- 238000010586 diagram Methods 0.000 description 20
- 238000010276 construction Methods 0.000 description 16
- 238000012545 processing Methods 0.000 description 8
- 238000013515 script Methods 0.000 description 7
- 238000004422 calculation algorithm Methods 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 238000011161 development Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 238000009430 construction management Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 230000002085 persistent effect Effects 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 230000000007 visual effect Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000007613 environmental effect Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 239000010979 ruby Substances 0.000 description 1
- 229910001750 ruby Inorganic materials 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3664—Environments for testing or debugging software
Abstract
The application relates to a method and a device for automatically integrating tasks of multiple technology stacks, electronic equipment and a computer readable medium. The method comprises the following steps: acquiring task requests from a plurality of technology stacks; acquiring task configuration from a distributed file system according to the type of the task in the task request; acquiring an execution parameter based on the identification of the task in the task request; and integrating the tasks according to the task configuration and the execution parameters to generate a task integration result. The method, the device, the electronic equipment and the computer readable medium for automatically integrating the tasks of the multiple technology stacks can automatically and uniformly process data from different technology stacks, improve user operation experience and reduce task access cost and management maintenance cost.
Description
Technical Field
The application relates to the field of computer information processing, in particular to a method and a device for automatically integrating tasks of multiple technology stacks, electronic equipment and a computer readable medium.
Background
Persistent integration services (CI services) are the process of automatically completing the compilation and testing of software code. Most developers do this manually. Some or even none. The CI server may automatically perform the compilation and testing process according to a set frequency. The CI server can continue and automatically compile processes, which can help software development teams reduce project risks and improve work efficiency and software product quality.
However, in the case of a widely used micro service architecture, as a business scene is complicated and developed, various tasks are generally constructed by a plurality of teams through splitting. And different technical stacks are adopted among the teams according to the characteristics of the field of the teams to complete business cooperation so as to ensure stable and efficient completion of the business. The cooperation mode causes the coexistence phenomenon of various technical stacks such as Java, go, python, node, C + + and the like. How to simply and efficiently implement persistent integration services in a multi-technology stack scenario is a current problem to be solved.
Jenkins is an open source software project, is a continuous integration tool based on Java development, and is used for monitoring continuous repeated work and integrating an operating system in a traditional mode to carry out task construction, and in the prior art, jenkins has some problems, such as: the environmental variables required for the task need to be configured in advance, the operator needs to be familiar with the Shell/Groovy script, the Jenkins parameter configuration and use are known, each task needs to be configured separately, and the like, so that the method is not friendly to the use of developers, and the learning and use cost is high.
Therefore, there is a need for a new method, apparatus, electronic device, and computer readable medium for automatic task integration of multiple technology stacks.
The above information disclosed in this background section is only for enhancement of understanding of the background of the application and therefore it may contain information that does not constitute prior art that is already known to a person of ordinary skill in the art.
Disclosure of Invention
In view of this, the present application provides a method and an apparatus for automatically integrating tasks in multiple technology stacks, an electronic device, and a computer readable medium, which can automatically and uniformly process data from different technology stacks, improve user operation experience, and reduce task access cost and maintenance cost of management.
Other features and advantages of the present application will be apparent from the following detailed description, or may be learned by practice of the application.
According to one aspect of the application, a method for automatically integrating tasks of multiple technology stacks is provided, and the method comprises the following steps: acquiring task requests from a plurality of technology stacks; acquiring task configuration from a distributed file system according to the type of the task in the task request; acquiring an execution parameter based on the identification of the task in the task request; and integrating the tasks according to the task configuration and the execution parameters to generate a task integration result.
Optionally, the task request from the multiple technology stacks is obtained, including: and acquiring task requests from various technology stacks one by one through a message queue.
Optionally, obtaining task configuration from the distributed file system according to the category of the task in the task request includes: judging whether the task in the task request exists in a task list or not; when the task is stored in the task list, acquiring task configuration from a distributed file system according to the type of the task in the task request; and when the task does not exist in the task list, creating the task.
Optionally, obtaining an execution parameter based on an identifier of a task in the task request, further includes: and dynamically storing the execution parameters corresponding to the tasks in a key value pair mode in the UI according to the user operation.
Optionally, integrating the task according to the task configuration and the execution parameter includes: acquiring a node label from the task request; determining a target proxy server according to the node label; and sending the task configuration and the execution parameters to the target proxy server to integrate the task.
Optionally, generating a task integration result comprises: compiling and testing the task automatically to generate a test result; and pushing the test result to a user side.
Optionally, creating the task comprises: acquiring the technology type of a technology stack corresponding to the task; extracting a template according to the technology type to create the task.
Optionally, extracting a template according to the technology type to create the task includes: extracting a template according to the technology type; generating a creation message according to the template; the background server acquires the creation message in the form of consumption message; and creating the task according to the creation message.
Optionally, creating the task according to the creation message includes: acquiring configuration data from a distributed file system according to the template in the creating message; creating task configuration corresponding to the task according to the directory level in the configuration data; and after the creation is finished, updating the task list.
According to an aspect of the present application, an apparatus for automatically integrating tasks of multiple technology stacks is provided, the apparatus comprising: the request module is used for acquiring task requests from various technical stacks; the configuration module is used for acquiring task configuration from the distributed file system according to the type of the task in the task request; the parameter module is used for acquiring execution parameters based on the task identifier in the task request; and the integration module is used for integrating the tasks according to the task configuration and the execution parameters to generate a task integration result.
According to an aspect of the present application, an electronic device is provided, the electronic device including: one or more processors; storage means for storing one or more programs; when executed by one or more processors, cause the one or more processors to implement a method as above.
According to an aspect of the application, a computer-readable medium is proposed, on which a computer program is stored, which program, when being executed by a processor, carries out the method as above.
According to the method, the device, the electronic equipment and the computer readable medium for automatically integrating tasks of multiple technology stacks, the task requests from the multiple technology stacks are obtained; acquiring task configuration from a distributed file system according to the category of the task in the task request; acquiring an execution parameter based on the identification of the task in the task request; the task is integrated according to the task configuration and the execution parameters to generate a task integration result, data from different technical stacks can be automatically and uniformly processed, user operation experience is improved, and task access cost and management maintenance cost are reduced.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
The above and other objects, features and advantages of the present application will become more apparent by describing in detail exemplary embodiments thereof with reference to the attached drawings. The drawings described below are only some embodiments of the present application, and other drawings may be derived from those drawings by those skilled in the art without inventive effort.
Fig. 1 is a system block diagram illustrating a method and apparatus for automatic task integration of multiple technology stacks in accordance with an exemplary embodiment.
FIG. 2 is a schematic diagram illustrating automatic integration of tasks of a multi-technology stack in accordance with an exemplary embodiment.
FIG. 3 is a flow diagram illustrating a method for automatic integration of tasks of a multi-technology stack in accordance with an exemplary embodiment.
FIG. 4 is a flow diagram illustrating a method for automatic integration of tasks of a multiple technology stack in accordance with another exemplary embodiment.
FIG. 5 is a flow diagram illustrating a method for automatic integration of tasks of a multiple technology stack in accordance with another exemplary embodiment.
FIG. 6 is a schematic diagram illustrating a method for automatic integration of tasks of a multiple technology stack, according to another exemplary embodiment.
FIG. 7 is a block diagram illustrating an apparatus for task auto-integration of a multiple technology stack in accordance with an exemplary embodiment.
FIG. 8 is a block diagram of an electronic device shown in accordance with an example embodiment.
FIG. 9 is a block diagram illustrating a computer-readable medium in accordance with an example embodiment.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The same reference numerals denote the same or similar parts in the drawings, and thus, a repetitive description thereof will be omitted.
Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the application. One skilled in the relevant art will recognize, however, that the subject matter of the present application can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and so forth. In other instances, well-known methods, devices, implementations, or operations have not been shown or described in detail to avoid obscuring aspects of the application.
The block diagrams shown in the figures are functional entities only and do not necessarily correspond to physically separate entities. I.e. these functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor means and/or microcontroller means.
The flow charts shown in the drawings are merely illustrative and do not necessarily include all of the contents and operations/steps, nor do they necessarily have to be performed in the order described. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the actual execution sequence may be changed according to the actual situation.
It will be understood that, although the terms first, second, third, etc. may be used herein to describe various components, these components should not be limited by these terms. These terms are used to distinguish one element from another. Thus, a first component discussed below may be termed a second component without departing from the teachings of the present concepts. As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items.
It should be understood by those skilled in the art that the drawings are merely schematic representations of exemplary embodiments, and that the blocks or flowchart illustrations in the drawings are not necessarily required to practice the present application and, therefore, should not be considered to limit the scope of the present application.
Fig. 1 is a system block diagram illustrating a method and apparatus for automatic task integration of multiple technology stacks in accordance with an exemplary embodiment.
As shown in fig. 1, the system architecture 10 may include service stacks 101, 102, 103, a network 104, and a server 105. Network 104 is the medium used to provide communication links between service stacks 101, 102, 103 and server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
The service stacks 101, 102, 103 interact with a server 105 over a network 104 to receive or send task requests and the like. The service stacks 101, 102, 103 may have software processing class applications installed thereon, such as Java, go, python, node, C + +, and the like.
The server 105 may be a server providing various services, such as a backend management server automatically integrating software tasks performed by the service stacks 101, 102, 103. The backend management server may process the received task request and feed back the processing results (e.g., task integration results) to the administrator of the internet service website and/or to the service stacks 101, 102, 103.
The server 105 may for example fetch task requests from the service stacks 101, 102, 103; the server 105 may obtain task configuration from the distributed file system, for example, according to the category of the task in the task request; the server 105 may obtain execution parameters, e.g., based on the identification of the task in the task request; the server 105 may integrate the task, for example, according to the task configuration and the execution parameters, and generate a task integration result.
The server 105 and the service stacks 101, 102, and 103 may each be a single entity server, or may be composed of multiple servers, for example, it should be noted that the method for automatically integrating tasks of multiple technology stacks provided in the embodiment of the present application may be executed by the server 105, and accordingly, a device for automatically integrating tasks of multiple technology stacks may be disposed in the server 105.
FIG. 2 is a schematic diagram illustrating automatic integration of tasks of a multi-technology stack in accordance with an exemplary embodiment. In the system framework of the method for automatically integrating the tasks of the multiple technology stacks, a set of visual interface UI is provided, a user is guided to select tasks of different technology stack types to construct through the visual interface, the construction process result is transmitted to the UI system in real time through an API mode, and the user can visually check the construction process result in real time.
In a specific implementation process, the Jenkins bottom layer is isolated by the automatic task integration method of the multiple technology stacks, so that the user operation experience is improved, and the use cost is reduced. The background abstracts the data into a general standard file according to different technical stack construction types (Java, node, go, python, ruby, self-definition and the like), and creates, updates, executes and archives task tasks in a directory mode by using the standard file. The task tasks are classified and stored according to the type directory, and in order to ensure the single-point problem of the task files, the task scripts are stored in a GFS (distributed file system), so that the task scripts are stored orderly and are convenient to manage. This reduces the task access cost and the maintenance cost of Jenkins management to a large extent.
The present application will be described in detail with reference to specific examples.
FIG. 3 is a flow diagram illustrating a method for automatic integration of tasks of a multi-technology stack in accordance with an exemplary embodiment. The method 30 for automatic integration of tasks of a plurality of technology stacks comprises at least steps S302 to S308.
As shown in fig. 3, in S302, task requests from multiple technology stacks are obtained. Task requests from multiple technology stacks may be fetched one by one, for example, through a message queue.
In S304, task configuration is obtained from the distributed file system according to the type of the task in the task request.
In one embodiment, determining whether a task in the task request exists in a task list; when the task is stored in the task list, acquiring task configuration from a distributed file system according to the type of the task in the task request; and when the task does not exist in the task list, creating the task.
The specific contents of "creating the task" will be described in detail in the embodiment corresponding to fig. 4.
In S306, an execution parameter is obtained according to the identifier of the task in the task request. And dynamically storing the execution parameters corresponding to the tasks in a key value pair mode in the UI according to the user operation.
In a specific embodiment, the execution parameters input by the user may be acquired through the UI interface, the names of the execution parameters and specific values may be stored in a < key, value > key-value pair mode, and specific task names corresponding to the execution parameters may be further configured to be automatically invoked.
In S308, the tasks are integrated according to the task configuration and the execution parameters, and a task integration result is generated. The node label can be obtained from the task request, for example; determining a target proxy server according to the node label; and sending the task configuration and the execution parameters to the target proxy server to integrate the task.
In one embodiment, the task may also be compiled and tested automatically, for example, to generate a test result; and pushing the test result to a user side.
Details of "sending the task configuration and the execution parameters to the target proxy server to integrate the task" will be described in detail in the embodiment corresponding to fig. 6.
According to the method for automatically integrating the tasks of the multiple technology stacks, the task requests from the multiple technology stacks are obtained; acquiring task configuration from a distributed file system according to the type of the task in the task request; acquiring an execution parameter according to the identification of the task in the task request; the task is integrated according to the task configuration and the execution parameters to generate a task integration result, so that data from different technology stacks can be automatically and uniformly processed, user operation experience is improved, and task access cost and management maintenance cost are reduced.
It should be clearly understood that this application describes how to make and use particular examples, but the principles of this application are not limited to any details of these examples. Rather, these principles can be applied to many other embodiments based on the teachings of the present disclosure.
FIG. 4 is a schematic diagram illustrating a method for automatic integration of tasks of a multiple technology stack, according to another exemplary embodiment. The schematic diagram shown in fig. 4 is a detailed description of "create the task" of S204 in the flow shown in fig. 2. The task is detected whether the task exists before running, and if the task does not exist, the template file is automatically loaded and created according to the technical stack type of the current task.
In one embodiment, creating the task includes: acquiring the technology type of a technology stack corresponding to the task; extracting a template according to the technology type to create the task.
In one embodiment, extracting templates to create the tasks according to the technology type includes: extracting a template according to the technology type; generating a creation message according to the template; the background server acquires the creation message in a consumption message form; and creating the task according to the creation message.
In one embodiment, creating the task from the create message includes: acquiring configuration data from a distributed file system according to the template in the establishment message; creating task configuration corresponding to the task according to the directory level in the configuration data; and after the creation is finished, updating the task list.
FIG. 5 is a schematic diagram illustrating a method for automatic integration of tasks of a multiple technology stack, according to another exemplary embodiment. The schematic diagram shown in fig. 5 is a detailed description of the flow shown in fig. 2. During task execution, configuration convention is carried out according to the definition content of the template, for example: starting a container construction execution environment, and ensuring the normal execution of task construction due to the fact that the loading construction time is overtime and the like.
In one embodiment, a Message Queue (MQ) can be used to obtain the task request, and the task request is controlled through the message queue, so that a single point of failure can be avoided, and data security is ensured.
In one embodiment, the self-research plug-in can dynamically pull the relevant task configuration in the GFS, so that the script configuration and the construction are decoupled, and the batch construction management of the script is realized.
It should be noted that, in order to facilitate the technician to obtain the task structure, the task naming rule may be: prefix name + configuration name of standard file prefix type.
The template is based on Jenkins DSL language specification, service customization development is carried out on the stack type in the prior art, and a task standard file meeting the specification is generated.
After the task execution is finished, the execution result can be actively reported, and the result is sent to the administrator through various information channels.
FIG. 6 is a schematic diagram of a method for automatic integration of tasks of a multi-technology stack shown in accordance with another exemplary embodiment. The flow 50 shown in fig. 6 is a detailed description of "sending the task configuration and the execution parameters to the target proxy server to integrate the task".
In the Jenkins technology, different tasks are executed in different node machines by tagging nodes and designating agents in pipelines through tags. This scenario has satisfied most task needs. With the development of company services, usage scenarios are increasingly complex, more and more tasks are required in the construction of pipelines, and the construction of a large number of tasks cannot be supported by the conventional Jenkins disk configuration.
In the application, tasks are sent to background servers corresponding to different labels based on application name hash values, each application is built in a fixed server node every time, and necessary data of the application, such as a dependency package of java application and a dependency package of vue, can be cached in the server nodes, so that the application building speed is effectively increased, the cache data of each original server node is reduced to a single server node cache, and the disk space is effectively saved.
And when the server node fails, the master node can drop the corresponding slave node, and the failure transfer is automatically carried out to the normal server node based on the hash algorithm routing.
The scheduling algorithm may be as follows:
(s[0]*31 (n-1) +s[1]*31 (n-2) +...+s[n-1])％count
s is a character string char array;
n is the length of a character string char array;
count is the number of server nodes;
as shown in fig. 6, a user creates a task through a master node, and the master node dynamically calculates a label name based on a hash algorithm according to a name parameter in the task, so that the label name is routed to a fixed slave node, and it is ensured that the same name parameter is constructed in the same slave node, thereby reducing the occupation of the whole disk space of a cache, reusing the disk cache, and increasing the construction rate.
Case (2): under a Jenkins cluster (1 master node +4 slave nodes), a task named demo is being executed and is scheduled to a specific slave node through the master node, and the scheduling algorithm is as follows:
(100*31 3 +101*31 2 +109*31 1 +111*31 0 )％4＝3；
that is, the task is scheduled to run by the Node3 Node.
According to the method for automatically integrating the tasks of the multiple technology stacks, the following advantages are achieved:
1) And dynamically pulling related task configuration in the GFS, decoupling script configuration and construction, and realizing batch construction management of scripts.
2) And a kind of task application is managed by adopting a standardized file, so that the management is convenient. Aiming at the requirements of special tasks, an extensible interface is provided, and the support is strong. The concept of gray release is integrated into the design, and gray modification of a single task is supported.
3) By optimizing a Jenkins routing scheduling strategy and starting a new Hash scheduling algorithm, the occupied space of the whole cache disk is reduced, the disk cache is repeatedly utilized, and the construction speed is improved.
Through the implementation of the scheme, the number of the accessed construction projects is larger than 600 at present, and through actual measurement, the construction efficiency of the projects is improved by about 30%.
Those skilled in the art will appreciate that all or part of the steps implementing the above embodiments are implemented as computer programs executed by a CPU. When executed by the CPU, performs the functions defined by the methods provided herein. The program may be stored in a computer readable storage medium, which may be a read-only memory, a magnetic or optical disk, or the like.
Furthermore, it should be noted that the above-mentioned figures are only schematic illustrations of the processes involved in the method according to exemplary embodiments of the present application and are not intended to be limiting. It will be readily understood that the processes shown in the above figures are not intended to indicate or limit the chronological order of the processes. In addition, it is also readily understood that these processes may be performed, for example, synchronously or asynchronously in multiple modules.
The following are embodiments of the apparatus of the present application that may be used to perform embodiments of the method of the present application. For details which are not disclosed in the embodiments of the apparatus of the present application, reference is made to the embodiments of the method of the present application.
FIG. 7 is a block diagram of a task auto-integration apparatus showing a multi-technology stack in accordance with an example embodiment. As shown in fig. 7, the task automatic integration apparatus 70 of the various technology stacks includes: a request module 702, a configuration module 704, a parameter module 706, an integration module 708, and a creation module 710.
The request module 702 is used for acquiring task requests from a plurality of technology stacks; the request module 702 is also configured to retrieve task requests from multiple technology stacks one by one through a message queue.
The configuration module 704 is configured to obtain task configuration from the distributed file system according to the type of the task in the task request; the configuration module 704 is further configured to determine whether a task in the task request exists in a task list; when the task is stored in the task list, acquiring task configuration from a distributed file system according to the type of the task in the task request;
the parameter module 706 is configured to obtain an execution parameter based on an identifier of a task in the task request; the parameter module 706 is further configured to dynamically store the execution parameters corresponding to the task in the UI interface in a key-value pair manner according to the user operation.
The integration module 708 is configured to integrate the task according to the task configuration and the execution parameter, and generate a task integration result. The integration module 708 is further configured to obtain a node tag from the task request; determining a target proxy server according to the node label; and sending the task configuration and the execution parameters to the target proxy server to integrate the task.
The creating module 710 is configured to create the task when the task does not exist in the task list. The creating module 710 is further configured to obtain a technology type of a technology stack corresponding to the task; extracting a template according to the technology type to create the task.
According to the automatic task integration device of the multiple technology stacks, the task requests from the multiple technology stacks are obtained; acquiring task configuration from a distributed file system according to the type of the task in the task request; acquiring an execution parameter based on the identification of the task in the task request; the task is integrated according to the task configuration and the execution parameters to generate a task integration result, data from different technical stacks can be automatically and uniformly processed, user operation experience is improved, and task access cost and management maintenance cost are reduced.
FIG. 8 is a block diagram illustrating an electronic device in accordance with an example embodiment.
An electronic device 800 according to this embodiment of the application is described below with reference to fig. 8. The electronic device 800 shown in fig. 8 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.
As shown in fig. 8, electronic device 800 is in the form of a general purpose computing device. The components of the electronic device 800 may include, but are not limited to: at least one processing unit 810, at least one memory unit 820, a bus 830 connecting the various system components (including the memory unit 820 and the processing unit 810), a display unit 840, and the like.
Wherein the storage unit stores program code that can be executed by the processing unit 810, such that the processing unit 810 performs the steps according to various exemplary embodiments of the present application in the present specification. For example, the processing unit 810 may perform the steps as shown in fig. 3, 4, 5.
The memory unit 820 may include readable media in the form of volatile memory units such as a random access memory unit (RAM) 8201 and/or a cache memory unit 8202, and may further include a read only memory unit (ROM) 8203.
The memory unit 820 may also include a program/utility 8204 having a set (at least one) of program modules 8205, such program modules 8205 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.
The electronic device 800 may also communicate with one or more external devices 800' (e.g., keyboard, pointing device, bluetooth device, etc.) such that a user can communicate with devices with which the electronic device 800 interacts, and/or any devices (e.g., router, modem, etc.) with which the electronic device 800 can communicate with one or more other computing devices. Such communication may occur via input/output (I/O) interfaces 850. Also, the electronic device 800 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network such as the internet) via the network adapter 860. The network adapter 860 may communicate with other modules of the electronic device 800 via the bus 830. It should be appreciated that although not shown, other hardware and/or software modules may be used in conjunction with the electronic device 800, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, as shown in fig. 9, the technical solution according to the embodiment of the present application may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, or a network device, etc.) to execute the above method according to the embodiment of the present application.
The software product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, 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.
The computer readable storage medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable storage medium may be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations of the present application may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).
The computer readable medium carries one or more programs which, when executed by a device, cause the computer readable medium to perform the functions of: acquiring task requests from a plurality of technology stacks; acquiring task configuration from a distributed file system according to the type of the task in the task request; acquiring an execution parameter based on the identification of the task in the task request; and integrating the tasks according to the task configuration and the execution parameters to generate a task integration result.
Those skilled in the art will appreciate that the modules described above may be distributed in the apparatus according to the description of the embodiments, or may be modified accordingly in one or more apparatuses unique from the embodiments. The modules of the above embodiments may be combined into one module, or further split into multiple sub-modules.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiment of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the embodiment of the present application.
Exemplary embodiments of the present application are specifically illustrated and described above. It is to be understood that the application is not limited to the details of construction, arrangement or method of operation set forth herein; on the contrary, the intention is to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.
Claims (12)
1. A method for automatically integrating tasks of multiple technology stacks is characterized by comprising the following steps:
acquiring task requests from a plurality of technology stacks;
acquiring task configuration from a distributed file system according to the category of the task in the task request;
acquiring an execution parameter based on the identification of the task in the task request;
and integrating the tasks according to the task configuration and the execution parameters to generate a task integration result.
2. The method of claim 1, wherein obtaining task requests from a plurality of technology stacks comprises:
and acquiring task requests from various technology stacks one by one through a message queue.
3. The method of claim 1, wherein obtaining task configurations from a distributed file system based on the category of the task in the task request comprises:
judging whether the task in the task request exists in a task list or not;
when the task is stored in the task list, acquiring task configuration from a distributed file system according to the type of the task in the task request;
and when the task does not exist in the task list, creating the task.
4. The method of claim 1, wherein obtaining execution parameters based on an identification of a task in the task request further comprises:
and dynamically storing the execution parameters corresponding to the tasks in a key value pair mode in the U I interface according to the user operation.
5. The method of claim 1, wherein integrating the task according to the task configuration and the execution parameters comprises:
acquiring a node label from the task request;
determining a target proxy server according to the node label;
and sending the task configuration and the execution parameters to the target proxy server to integrate the task.
6. The method of claim 1, wherein generating a task integration result comprises:
compiling and testing the task automatically to generate a test result;
and pushing the test result to a user side.
7. The method of claim 3, wherein creating the task comprises:
acquiring the technology type of a technology stack corresponding to the task;
extracting a template according to the technology type to create the task.
8. The method of claim 7, wherein extracting a template to create the task according to the technology type comprises:
extracting a template according to the technology type;
generating a creation message according to the template;
the background server acquires the creation message in the form of consumption message;
and creating the task according to the creation message.
9. The method of claim 8, wherein creating the task from the create message comprises:
acquiring configuration data from a distributed file system according to the template in the establishment message;
creating task configuration corresponding to the task according to the directory level in the configuration data;
and after the creation is finished, updating the task list.
10. An apparatus for automatically integrating tasks of a plurality of technology stacks, comprising:
the request module is used for acquiring task requests from various technical stacks;
the configuration module is used for acquiring task configuration from the distributed file system according to the type of the task in the task request;
the parameter module is used for acquiring execution parameters based on the task identifier in the task request;
and the integration module is used for integrating the tasks according to the task configuration and the execution parameters to generate a task integration result.
11. An electronic device, comprising:
one or more processors;
storage means for storing one or more programs;
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-9.
12. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-9.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210756797.2A CN115291928A (en) | 2022-06-29 | 2022-06-29 | Task automatic integration method and device of multiple technology stacks and electronic equipment |
| PCT/CN2023/077881 WO2024001240A1 (en) | 2022-06-29 | 2023-02-23 | Task integration method and apparatus for multiple technology stacks |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210756797.2A CN115291928A (en) | 2022-06-29 | 2022-06-29 | Task automatic integration method and device of multiple technology stacks and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115291928A true CN115291928A (en) | 2022-11-04 |
Family
ID=83821505
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210756797.2A Pending CN115291928A (en) | 2022-06-29 | 2022-06-29 | Task automatic integration method and device of multiple technology stacks and electronic equipment |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN115291928A (en) |
| WO (1) | WO2024001240A1 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2024001240A1 (en) * | 2022-06-29 | 2024-01-04 | 上海淇玥信息技术有限公司 | Task integration method and apparatus for multiple technology stacks |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160275123A1 (en) * | 2015-03-18 | 2016-09-22 | Hitachi, Ltd. | Pipeline execution of multiple map-reduce jobs |
| CN110069329A (en) * | 2019-04-15 | 2019-07-30 | 北京达佳互联信息技术有限公司 | A kind of task processing method, device, server and storage medium |
| CN110781007B (en) * | 2019-10-31 | 2023-12-26 | 广州市网星信息技术有限公司 | Task processing method, device, server, client, system and storage medium |
| CN113760302B (en) * | 2021-09-09 | 2023-04-07 | 四川虹美智能科技有限公司 | Jenkins-based UI package deployment method and system |
| CN115291928A (en) * | 2022-06-29 | 2022-11-04 | 上海淇玥信息技术有限公司 | Task automatic integration method and device of multiple technology stacks and electronic equipment |
-
2022
- 2022-06-29 CN CN202210756797.2A patent/CN115291928A/en active Pending
-
2023
- 2023-02-23 WO PCT/CN2023/077881 patent/WO2024001240A1/en unknown
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2024001240A1 (en) * | 2022-06-29 | 2024-01-04 | 上海淇玥信息技术有限公司 | Task integration method and apparatus for multiple technology stacks |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2024001240A1 (en) | 2024-01-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10481884B2 (en) | Systems and methods for dynamically replacing code objects for code pushdown | |
| US8671222B2 (en) | Systems and methods for dynamically deploying an application transformation tool over a network | |
| US8572566B2 (en) | Systems and methods for analyzing changes in application code from a previous instance of the application code | |
| US8898627B2 (en) | Systems and methods for applying rules to transform objects of an application | |
| CN109062563B (en) | Method and device for generating page | |
| US10169222B2 (en) | Apparatus and method for expanding the scope of systems management applications by runtime independence | |
| US11934287B2 (en) | Method, electronic device and computer program product for processing data | |
| US11061739B2 (en) | Dynamic infrastructure management and processing | |
| CN105094857B (en) | Method and system for application load | |
| CN111309621A (en) | Interface test method, system, equipment and storage medium | |
| WO2024001240A1 (en) | Task integration method and apparatus for multiple technology stacks | |
| CN113377342B (en) | Project construction method and device, electronic equipment and storage medium | |
| US9154380B2 (en) | Rules based fetching of operating platform status | |
| US10705824B2 (en) | Intention-based command optimization | |
| CN112286802B (en) | Method and device for testing program performance and electronic equipment | |
| CN111158645B (en) | System and method for providing an integrated development environment | |
| CN113032004A (en) | Method, apparatus and program product for managing development jobs in a development environment | |
| CN113141407B (en) | Page resource loading method and device and electronic equipment | |
| CN113342633B (en) | Performance test method and device | |
| CN112988528B (en) | Log processing method, device and container group | |
| CN113760229A (en) | Front-end project generation method and system, electronic equipment and storage medium | |
| CN116755758A (en) | Data processing method, device, electronic equipment and computer readable medium | |
| CN112445850A (en) | Data conversion method and device, electronic equipment and readable medium | |
| CN114816672A (en) | Virtual machine creation method and device, electronic equipment and storage medium | |
| CN116594630A (en) | File generation method, device, medium and electronic 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 | ||
| CB02 | Change of applicant information |
Country or region after: Zhong Guo Address after: Room 1109, No. 4, Lane 800, Tongpu Road, Putuo District, Shanghai, 200062 Applicant after: Shanghai Qiyue Information Technology Co.,Ltd. Address before: Room a2-8914, 58 Fumin Branch Road, Hengsha Township, Chongming District, Shanghai, 201500 Applicant before: Shanghai Qiyue Information Technology Co.,Ltd. Country or region before: Zhong Guo |
|
| CB02 | Change of applicant information |