CN111857861B - Jenkins task management method, system, terminal and storage medium - Google Patents
Jenkins task management method, system, terminal and storage medium Download PDFInfo
- Publication number
- CN111857861B CN111857861B CN202010063197.9A CN202010063197A CN111857861B CN 111857861 B CN111857861 B CN 111857861B CN 202010063197 A CN202010063197 A CN 202010063197A CN 111857861 B CN111857861 B CN 111857861B
- Authority
- CN
- China
- Prior art keywords
- jenkins
- task
- pipeline
- node
- environment
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000007726 management method Methods 0.000 title claims abstract description 19
- 238000003860 storage Methods 0.000 title claims abstract description 16
- 230000003044 adaptive effect Effects 0.000 claims abstract description 48
- 238000004891 communication Methods 0.000 claims abstract description 13
- 238000000034 method Methods 0.000 claims description 23
- 238000012360 testing method Methods 0.000 claims description 16
- 238000004140 cleaning Methods 0.000 claims description 15
- 238000004590 computer program Methods 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 6
- 230000008569 process Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000006467 substitution reaction Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 2
- 238000005259 measurement Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 238000005201 scrubbing Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
- G06F9/4451—User profiles; Roaming
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5061—Partitioning or combining of resources
- G06F9/5066—Algorithms for mapping a plurality of inter-dependent sub-tasks onto a plurality of physical CPUs
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention provides a jenkins task management method, a system, a terminal and a storage medium, comprising the following steps: setting a plurality of operating environments and deploying a plurality of jenkins nodes in each operating environment, wherein the operating environments establish communication in clusters with different ports; generating a pipeline task and matching an adaptive operating environment of the pipeline task; acquiring jenkins node resource information of the assembly line task under the adaptive operation environment, and judging whether idle jenkins nodes exist under the adaptive operation environment of the assembly line task: if so, issuing the pipeline task to the idle jenkins node; and if not, the pipeline task is issued to jenkins nodes of other operating environments. The invention greatly improves the task execution efficiency and avoids the condition that jenkins tasks are unevenly distributed.
Description
Technical Field
The invention relates to the technical field of jenkins, in particular to a jenkins task management method, a jenkins task management system, a jenkins task management terminal and a storage medium.
Background
jenkins is a service delivery widely used in the continuously constructed visual web tool industry, and is an "automated" compilation, packaging, distribution deployment of various items. Automated deployment has many advantages, such as reduced cost, increased productivity, high availability, greater reliability, performance optimization, etc., and the use of pipeline tasks to implement this process is widely used in k8s service deployment.
Taking a Devops module in a Langchao ICKS system as an example, firstly binding code warehouse information and establishing a pipeline task depending on code source information; and defining a pipeline task, wherein a complete pipeline task comprises the steps of pulling, constructing and releasing the code. The Jenkins multi-plug-in mode perfectly adapts to various language environments, including java/go/python and other languages used by developers. At present, a task pod is started by adopting a slave node corresponding to an agent in an ICKS jenkins task running mode, the pod exists along with a pipeline task, and the task is ended and can be automatically destroyed no matter success or failure occurs. At present, a deployment strategy for jenkins in a system is that one operation environment corresponds to one jenkins deployment, namely, no matter how many pipeline tasks are defined in the system, how many tasks need to be simultaneously operated by a user, the tasks need to be operated in one jenkins node, and a large-scale and repeated task request has an impact on the operation capacity of jenkins. On one hand, the task bearing capacity of the jenkins slave node is limited, one pipeline task starts one built executer at a time, and if the task capacity is increased, jenkins deployed in the k8s cluster are overloaded and are likely to be killed; on the other hand, the build queue of the task is too much accumulated, the measurement cannot be executed on time when the measurement is determined according to the definition, and the working efficiency of the devices module is seriously influenced; in addition, jenkins needs space for running tasks, including cache of execution records and the like, and the pipeline task fails due to insufficient memory possibly in the running process.
Disclosure of Invention
In view of the above-mentioned deficiencies of the prior art, the present invention provides a jenkins task management method, system, terminal and storage medium, so as to solve the above-mentioned technical problems.
In a first aspect, the present invention provides a jenkins task management method, including:
setting a plurality of operating environments and deploying a plurality of jenkins nodes in each operating environment, wherein the operating environments establish communication in clusters with different ports;
generating a pipeline task and matching the adaptive running environment of the pipeline task;
acquiring jenkins node resource information of the assembly line task under the adaptive operation environment, and judging whether idle jenkins nodes exist under the adaptive operation environment of the assembly line task:
if so, issuing the pipeline task to the idle jenkins node;
and if not, the pipeline task is issued to jenkins nodes of other operating environments.
Further, collecting jenkins node resource information under the adaptive operation environment of the pipeline task and judging whether idle jenkins nodes exist under the adaptive operation environment of the pipeline task includes:
collecting the number of compilers of jenkins nodes under the adaptive operation environment;
judging whether the number of compilers of the jenkins nodes reaches the rated number of compilers:
if not, judging that the jenkins node is an idle node.
Further, the generating a pipeline task and matching an adaptive operating environment of the pipeline task includes:
setting the triggering time and the testing scheme of the pipeline task;
matching available running environments of the pipeline tasks according to the test scheme, and selecting a running environment with the lowest resource utilization rate from the available running environments as an adaptive running environment;
and sending the pipeline task to the selected jenkins node at fixed time according to the trigger time.
Further, the method further comprises:
setting a pod cleaning period;
and periodically cleaning the cache data in the pod of the jenkins node according to the cleaning period.
In a second aspect, the present invention provides a jenkins task management system, including:
the node deployment unit is configured to set a plurality of operating environments and deploy a plurality of jenkins nodes in each operating environment, and the operating environments establish communication in clusters with different ports;
the task generation unit is configured for generating a pipeline task and matching an adaptive running environment of the pipeline task;
the information acquisition unit is configured to acquire jenkins node resource information of the pipeline task in the adaptive operation environment and judge whether idle jenkins nodes exist in the adaptive operation environment of the pipeline task;
the first issuing unit is configured to issue the pipeline task to an idle jenkins node if the idle jenkins node exists in the adaptive operating environment of the pipeline task;
and the second issuing unit is configured to issue the pipeline task to jenkins nodes of other operating environments if no idle jenkins node exists in the adaptive operating environment of the pipeline task.
Further, the information collecting unit includes:
the quantity acquisition module is configured for acquiring the quantity of compilers of jenkins nodes under the adaptive operation environment;
the quantity comparison module is configured for judging whether the quantity of the compilers of the jenkins nodes reaches the rated compiler quantity or not;
and the result judging module is configured to judge that the jenkins node is an idle node if the number of the compilers of the jenkins node does not reach the rated number of the compilers.
Further, the task generating unit includes:
the task setting module is used for setting the triggering time and the test scheme of the pipeline task;
the environment matching module is configured for matching available running environments of the pipeline tasks according to the test scheme, and selecting a running environment with the lowest resource utilization rate from the available running environments as an adaptive running environment;
and the task triggering module is configured to issue the pipeline task to the selected jenkins node at regular time according to the triggering time.
Further, the system further comprises:
a cycle setting unit configured to set a pod cleaning cycle;
and the data cleaning unit is configured to periodically clean the cache data in the pod of the jenkins node according to the cleaning period.
In a third aspect, a terminal is provided, including:
a processor, a memory, wherein,
the memory is used for storing a computer program which,
the processor is configured to call and run the computer program from the memory, so that the terminal performs the method of the terminal described above.
In a fourth aspect, a computer storage medium is provided having stored therein instructions that, when executed on a computer, cause the computer to perform the method of the above aspects.
The beneficial effect of the invention is that,
according to the jenkins task management method, the system, the terminal and the storage medium, jenkins under multiple operation environments are managed in a centralized mode, the assembly line tasks are automatically matched and adapted to the operation environments, a strategy of deploying a plurality of jenkins in one operation environment is adopted, and the task quantity is distributed reasonably according to the use conditions of the jenkins. The invention greatly improves the task execution efficiency and avoids the condition that jenkins tasks are unevenly distributed.
In addition, the invention has reliable design principle, simple structure and very wide application prospect.
Drawings
In order to more clearly illustrate the embodiments or technical solutions in the prior art of the present invention, the drawings used in the description of the embodiments or prior art will be briefly described below, and it is obvious for those skilled in the art that other drawings can be obtained based on these drawings without creative efforts.
FIG. 1 is a schematic flow diagram of a method of one embodiment of the invention.
FIG. 2 is a schematic flow diagram of a method of one embodiment of the invention.
FIG. 3 is a schematic block diagram of a system of one embodiment of the present invention.
Fig. 4 is a schematic structural diagram of a terminal according to an embodiment of the present invention.
Detailed Description
In order to make those skilled in the art better understand the technical solutions of the present invention, 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.
FIG. 1 is a schematic flow diagram of a method of one embodiment of the invention. The execution subject in fig. 1 may be a jenkins task management system.
As shown in fig. 1, the method 100 includes:
and 150, if not, issuing the pipeline task to jenkins nodes of other operating environments.
In order to facilitate understanding of the present invention, the jenkins task management method provided by the present invention is further described below by using the principle of the jenkins task management method of the present invention and combining the process of managing jenkins tasks in the embodiments.
Referring to fig. 2, specifically, the jenkins task management method includes:
s1, setting a plurality of operating environments and deploying a plurality of jenkins nodes in each operating environment, wherein the operating environments establish communication in clusters with different ports.
In order to implement centralized management on jenkins in multiple operating environments, it is necessary that each multiple operating environment can communicate in a cluster with different ports. And each operating environment does not expose an access port thereof, namely, a user cannot access the jenkins native interface and can only see the pipeline execution result through the revops module. Jenkins is a tool for running tasks and is not bound to a system one by one. For example, the dehaps module in runtime environment 1 may call jenkins in runtime environment 2 to execute the pipeline task. And a strategy of deploying a plurality of jenkins in one operating environment is adopted, and the task amount is reasonably distributed according to the use condition of the jenkins.
And S2, generating a pipeline task and matching the adaptive running environment of the pipeline task.
Setting the triggering time and the testing scheme of the pipeline task, automatically matching and adapting to the running environment according to the testing scheme of the task, wherein one running environment corresponds to a plurality of testing schemes, storing the mapping relation between the running environment and the type of the testing scheme, and automatically matching the running environment according to the type of the generated testing scheme of the task. A test scheme can be executed on various operation environments, the operation environments need to be further selected, and available operation environments with low CPU and low memory utilization rate are preferentially selected as adaptive operation environments of pipeline tasks.
And judging whether the triggering time of the pipeline task is reached, and if the triggering time is reached, issuing the pipeline task to the selected jenkins node at regular time.
S3, collecting jenkins node resource information of the pipeline task under the adaptive operation environment, and judging whether idle jenkins nodes exist under the adaptive operation environment of the pipeline task: if yes, the assembly line task is issued to the idle jenkins node; and if not, the assembly line task is issued to jenkins nodes of other operating environments.
Adapting to different jenkins in an operating environment, mainly seeing the pipeline task which is operated by the jenkins and the memory condition of the jenkins, and corresponding to a compiler based on one pipeline task, so that idle jenkins nodes with the number of compilers not reaching the number of rated compilers are selected.
And if the adaptive operating environment does not have idle jenkins, distributing the pipeline task to idle jenkins of other operating environments.
And connecting the selected jenkins node, and running the pipeline task on the selected jenkins node.
If the same jenkins task is constructed for multiple times, the execution records of the task are cached in a pod memory of jenkins, and if the pod memory is full, the task is failed to be constructed, so that the cache is cleaned up by regularly or even setting a strategy. The user may specify a cache scrubbing policy.
As shown in fig. 2, the system 200 includes:
a node deployment unit 210 configured to set a plurality of operating environments and deploy a plurality of jenkins nodes in each operating environment, where the plurality of operating environments establish communication in clusters with different ports;
a task generating unit 220 configured to generate a pipeline task and match an adaptive operating environment of the pipeline task;
the information acquisition unit 230 is configured to acquire jenkins node resource information of the pipeline task in the adaptive operation environment and judge whether an idle jenkins node exists in the adaptive operation environment of the pipeline task;
the first issuing unit 240 is configured to issue the pipeline task to an idle jenkins node if the idle jenkins node exists in the adaptive operating environment of the pipeline task;
and the second issuing unit 250 is configured to issue the pipeline task to jenkins nodes of other operating environments if an idle jenkins node does not exist in the adaptive operating environment of the pipeline task.
Optionally, as an embodiment of the present invention, the information collecting unit includes:
the quantity acquisition module is configured for acquiring the quantity of compilers of jenkins nodes under the adaptive operation environment;
the quantity comparison module is configured for judging whether the quantity of the compilers of the jenkins nodes reaches the rated compiler quantity or not;
and the result judging module is configured to judge that the jenkins node is an idle node if the number of the compilers of the jenkins node does not reach the rated number of the compilers.
Optionally, as an embodiment of the present invention, the task generating unit includes:
the task setting module is used for setting the triggering time and the test scheme of the pipeline task;
the environment matching module is configured for matching available running environments of the pipeline tasks according to the test scheme, and selecting a running environment with the lowest resource utilization rate from the available running environments as an adaptive running environment;
and the task triggering module is configured to issue the pipeline task to the selected jenkins node at regular time according to the triggering time.
Optionally, as an embodiment of the present invention, the system further includes:
a cycle setting unit configured to set a pod cleaning cycle;
and the data cleaning unit is configured to periodically clean the cache data in the pod of the jenkins node according to the cleaning period.
Fig. 4 is a schematic structural diagram of a terminal system 400 according to an embodiment of the present invention, where the terminal system 400 may be used to execute the jenkins task management method according to the embodiment of the present invention.
The terminal system 400 may include: a processor 410, a memory 420, and a communication unit 430. The components communicate via one or more buses, and those skilled in the art will appreciate that the architecture of the servers shown in the figures is not intended to be limiting, and may be a bus architecture, a star architecture, a combination of more or less components than those shown, or a different arrangement of components.
The memory 420 may be used for storing instructions executed by the processor 410, and the memory 420 may be implemented by any type of volatile or non-volatile storage terminal or combination thereof, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The executable instructions in memory 420, when executed by processor 410, enable terminal 400 to perform some or all of the steps in the method embodiments described below.
The processor 410 is a control center of the storage terminal, connects various parts of the entire electronic terminal using various interfaces and lines, and performs various functions of the electronic terminal and/or processes data by operating or executing software programs and/or modules stored in the memory 420 and calling data stored in the memory. The processor may be composed of an Integrated Circuit (IC), for example, a single packaged IC, or a plurality of packaged ICs connected with the same or different functions. For example, the processor 410 may include only a Central Processing Unit (CPU). In the embodiment of the present invention, the CPU may be a single operation core, or may include multiple operation cores.
A communication unit 430, configured to establish a communication channel so that the storage terminal can communicate with other terminals. And receiving user data sent by other terminals or sending the user data to other terminals.
The present invention also provides a computer storage medium, wherein the computer storage medium may store a program, and the program may include some or all of the steps in the embodiments provided by the present invention when executed. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM) or a Random Access Memory (RAM).
Therefore, the method carries out centralized management on jenkins under multiple operation environments, automatically adapts to the operation environment for pipeline task matching, adopts a strategy of deploying a plurality of jenkins in one operation environment, and reasonably distributes the task amount according to the use condition of the jenkins. The invention greatly improves the task execution efficiency, avoids the condition that jenkins tasks are distributed unevenly, and the technical effect achieved by the embodiment can be referred to the description above, and is not described again here.
Those skilled in the art will readily appreciate that the techniques of the embodiments of the present invention may be implemented as software plus a required general purpose hardware platform. Based on such understanding, the technical solutions in the embodiments of the present invention may be embodied in the form of a software product, where the computer software product is stored in a storage medium, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and the like, and the storage medium can store program codes, and includes instructions for enabling a computer terminal (which may be a personal computer, a server, or a second terminal, a network terminal, and the like) to perform all or part of the steps of the method in the embodiments of the present invention.
The same and similar parts among the various embodiments in this specification may be referred to each other. Especially, for the terminal embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant points can be referred to the description in the method embodiment.
In the embodiments provided in the present invention, it should be understood that the disclosed system and method can be implemented in other ways. For example, the above-described system embodiments are merely illustrative, and for example, the division of the units is only one logical functional division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, systems or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
Although the present invention has been described in detail by referring to the drawings in connection with the preferred embodiments, the present invention is not limited thereto. Various equivalent modifications or substitutions can be made on the embodiments of the present invention by those skilled in the art without departing from the spirit and scope of the present invention, and these modifications or substitutions are within the scope of the present invention/any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (10)
1. A jenkins task management method is characterized by comprising the following steps:
setting a plurality of operating environments and deploying a plurality of jenkins nodes in each operating environment; the multiple operating environments establish communication in the clusters with different ports, and each operating environment does not expose an access port of the operating environment to the outside, so that a user cannot access a jenkins native interface and can only see a pipeline execution result through the revops module; jenkins are used as a tool for task operation and are not in a one-to-one binding relationship with system nodes, so that a devops module in one operation environment can call Jenkins in another operation environment to execute a pipeline task;
generating a pipeline task and matching the adaptive running environment of the pipeline task;
acquiring jenkins node resource information of the assembly line task under the adaptive operation environment, and judging whether idle jenkins nodes exist under the adaptive operation environment of the assembly line task:
if so, issuing the pipeline task to the idle jenkins node;
and if not, the pipeline task is issued to jenkins nodes of other operating environments.
2. The method according to claim 1, wherein the collecting jenkins node resource information in the adaptive operating environment of the pipeline task and determining whether there is an idle jenkins node in the adaptive operating environment of the pipeline task comprises:
collecting the number of compilers of jenkins nodes under the adaptive operation environment;
judging whether the number of compilers of the jenkins node reaches the rated number of compilers:
if not, judging that the jenkins node is an idle node.
3. The method of claim 1, wherein generating the pipeline task and matching the adaptive execution environment of the pipeline task comprises:
setting the triggering time and the testing scheme of the pipeline task;
matching available running environments of the pipeline tasks according to the test scheme, and selecting a running environment with the lowest resource utilization rate from the available running environments as an adaptive running environment;
and sending the pipeline task to the selected jenkins node at fixed time according to the trigger time.
4. The method of claim 1, further comprising:
setting a pod cleaning period;
and periodically cleaning the cache data in the pod of the jenkins node according to the cleaning period.
5. A jenkins task management system, comprising:
the node deployment unit is configured to set a plurality of operating environments and deploy a plurality of jenkins nodes in each operating environment; the multiple operating environments establish communication in the clusters with different ports, and each operating environment does not expose an access port of the operating environment to the outside, so that a user cannot access a jenkins native interface and can only see a pipeline execution result through the revops module; jenkins are used as a tool for task operation and are not in a one-to-one binding relationship with system nodes, so that a devops module in one operation environment can call Jenkins in another operation environment to execute a pipeline task;
the task generation unit is configured for generating a pipeline task and matching an adaptive running environment of the pipeline task;
the information acquisition unit is configured to acquire jenkins node resource information of the pipeline task in the adaptive operation environment and judge whether idle jenkins nodes exist in the adaptive operation environment of the pipeline task;
the first issuing unit is configured to issue the pipeline task to an idle jenkins node if the idle jenkins node exists in the adaptive operating environment of the pipeline task;
and the second issuing unit is configured to issue the pipeline task to jenkins nodes of other operating environments if no idle jenkins node exists in the adaptive operating environment of the pipeline task.
6. The system of claim 5, wherein the information collection unit comprises:
the quantity acquisition module is configured for acquiring the quantity of compilers of jenkins nodes under the adaptive operation environment;
the quantity comparison module is configured for judging whether the quantity of the compilers of the jenkins nodes reaches the rated compiler quantity or not;
and the result judging module is configured to judge that the jenkins node is an idle node if the number of the compilers of the jenkins node does not reach the rated number of the compilers.
7. The system of claim 5, wherein the task generation unit comprises:
the task setting module is used for setting the triggering time and the test scheme of the pipeline task;
the environment matching module is configured for matching available running environments of the pipeline tasks according to the test scheme, and selecting a running environment with the lowest resource utilization rate from the available running environments as an adaptive running environment;
and the task triggering module is configured to issue the pipeline task to the selected jenkins node at regular time according to the triggering time.
8. The system of claim 5, further comprising:
a cycle setting unit configured to set a pod cleaning cycle;
and the data cleaning unit is configured to periodically clean the cache data in the pod of the jenkins node according to the cleaning period.
9. A terminal, comprising:
a processor;
a memory for storing instructions for execution by the processor;
wherein the processor is configured to perform the method of any one of claims 1-4.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010063197.9A CN111857861B (en) | 2020-01-19 | 2020-01-19 | Jenkins task management method, system, terminal and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010063197.9A CN111857861B (en) | 2020-01-19 | 2020-01-19 | Jenkins task management method, system, terminal and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111857861A CN111857861A (en) | 2020-10-30 |
| CN111857861B true CN111857861B (en) | 2022-07-08 |
Family
ID=72984868
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010063197.9A Active CN111857861B (en) | 2020-01-19 | 2020-01-19 | Jenkins task management method, system, terminal and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111857861B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112559022A (en) * | 2020-12-16 | 2021-03-26 | 同盾控股有限公司 | Jenkins high-availability system and method |
| CN112860438A (en) * | 2021-02-23 | 2021-05-28 | 浪潮云信息技术股份公司 | Distributed DevOps operation method based on cloud platform |
| CN114172904B (en) * | 2021-12-02 | 2024-02-13 | 上海众源网络有限公司 | Jenkins information processing method and device, electronic equipment and storage medium |
| CN118092943A (en) * | 2024-04-26 | 2024-05-28 | 杭州数云信息技术有限公司 | Application release method and device, computer readable storage medium and terminal |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160028672A1 (en) * | 2014-07-22 | 2016-01-28 | Polycom, Inc. | Message Controlled Application and Operating System Image Development and Deployment |
| CN105335210A (en) * | 2014-07-30 | 2016-02-17 | 小米科技有限责任公司 | Task distribution method and device |
| CN106339260A (en) * | 2016-08-19 | 2017-01-18 | 北京小米移动软件有限公司 | Task allocation method and device for Jenkins platform |
| CN110471831A (en) * | 2019-06-21 | 2019-11-19 | 南京壹进制信息科技有限公司 | A kind of automatic method and device of compatibility test |
-
2020
- 2020-01-19 CN CN202010063197.9A patent/CN111857861B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160028672A1 (en) * | 2014-07-22 | 2016-01-28 | Polycom, Inc. | Message Controlled Application and Operating System Image Development and Deployment |
| CN105335210A (en) * | 2014-07-30 | 2016-02-17 | 小米科技有限责任公司 | Task distribution method and device |
| CN106339260A (en) * | 2016-08-19 | 2017-01-18 | 北京小米移动软件有限公司 | Task allocation method and device for Jenkins platform |
| CN110471831A (en) * | 2019-06-21 | 2019-11-19 | 南京壹进制信息科技有限公司 | A kind of automatic method and device of compatibility test |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111857861A (en) | 2020-10-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111857861B (en) | Jenkins task management method, system, terminal and storage medium | |
| CN112272203B (en) | Cluster service node selection method, system, terminal and storage medium | |
| CN101707399A (en) | Method and system for acquiring electric energy information | |
| CN110389843B (en) | Service scheduling method, device, equipment and readable storage medium | |
| CN105580007A (en) | Monitoring a computing network | |
| CN112230847B (en) | Method, system, terminal and storage medium for monitoring K8s storage volume | |
| CN114416200A (en) | System and method for monitoring, acquiring, configuring and dynamically managing and loading configuration of declarative cloud platform | |
| CN105404530B (en) | It is a kind of to realize easy deployment and the system and method using private clound | |
| CN107368419A (en) | Automatic test approach and system, service terminal, memory under distributed environment | |
| CN111262753B (en) | Method, system, terminal and storage medium for automatically configuring number of NUMA nodes | |
| CN109873714A (en) | Cloud computing node configures update method and terminal device | |
| CN111506331A (en) | Server BMC refreshing method, system, terminal and storage medium | |
| CN112565416B (en) | Cloud-native-based large-scale edge android equipment nanotube system and nanotube method thereof | |
| CN112463195B (en) | Method, system, terminal and storage medium for cluster grouping online upgrade | |
| CN113296795A (en) | Application deployment method, device, equipment, storage medium and program product | |
| CN115530699B (en) | Cleaning control method and device for floor cleaning machine, computer equipment and storage medium | |
| CN109257256A (en) | Apparatus monitoring method, device, computer equipment and storage medium | |
| CN114968286A (en) | Micro-service issuing method, device, storage medium and electronic equipment | |
| CN103677994A (en) | Distributed data processing system, device and method | |
| CN1251086C (en) | Method and device for machine group system node dynamic configuration | |
| CN111124854A (en) | Method, system, terminal and storage medium for distributing smoking test cases | |
| CN113076111A (en) | Customized cluster configuration method, system, terminal and storage medium | |
| CN112860379A (en) | Method for installing and deploying high availability of redis on cloud platform | |
| CN109995617A (en) | Automated testing method, device, equipment and the storage medium of Host Administration characteristic | |
| CN111061562B (en) | Software collaborative packaging method, system, terminal and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |