CN116382694A - Method for improving compiling speed of Maven engineering in container environment - Google Patents

Abstract

The embodiment of the present invention provides a method for improving the compilation speed of a Maven project in a container environment. First, by accessing a Web program containing a scheduling algorithm, submit a compilation task for a certain branch of the Gitlab warehouse; calculate the execution time corresponding to the Gitlab warehouse. The slave node and the corresponding Mave n local warehouse, and then store the corresponding relationship; submit the compilation task to the Jenkins master; the Jenk in master node creates a Jenkins job, and judges whether there is a Jenkins job. If the Jenkins job does not exist, then according to the slave label , and issue the instructions for compiling task execution to the slave node; the Jenkins slave node first pulls the specified branch code from the specified warehouse from Gitlab, and then pulls the image for compilation from Harbor; mounts the Maven local warehouse, and at the same time Change the code warehouse directory. A method for improving the compilation speed of a Maven project in a container environment proposed by this application improves the compilation speed and continuous integration efficiency of a Maven project in a container environment.

Description

A method to improve the compilation speed of Maven project in container environment

technical field

The invention relates to the technical field of virtual machine security, in particular to a method for improving the compilation speed of a Maven project in a container environment.

Background technique

In the traditional software development process, the important link of source code compilation is executed on the physical machine, but with the maturity and popularization of container technology, the advantages of container native, such as: unified and standardized environment, allowing source code to be compiled in the container environment Execution becomes a better option.

Software companies usually deploy Jenkins+Nexus+Gitlab as a continuous integration and delivery tool for Maven-based Java microservices. In the compilation phase, Jenkins pulls the Docker image with Maven and JDK installed, creates a container, executes compilation in the container environment, and destroys the container after the compilation is completed. Compiling code in a container environment has the advantages of containers such as security and unified environmental standards. However, because the container is destroyed when it is used up, the Maven local warehouse will also be destroyed, which leads to re-pulling from Nexus for each compilation. Packages and plug-ins in the pom (packages are used to refer to packages and plug-ins later in this patent), resulting in slow compilation speed and low continuous integration efficiency. This patent solves the problem of slow compilation speed of Maven projects in a container environment.

Contents of the invention

An embodiment of the present invention provides a method for improving the compilation speed of a Maven project in a container environment, aiming at solving or partially solving the above-mentioned technical problems.

In order to solve the problems of the technologies described above, the present invention is achieved in that:

In the first aspect of the present application, a method for improving the compilation speed of a Maven project in a container environment is provided. The method includes: accessing a Web program containing a scheduling algorithm, submitting a compilation task about a branch of a Gitlab warehouse; calculating the Gitlab warehouse The corresponding execution slave node and the corresponding Maven local warehouse, and then store the corresponding relationship; submit the compilation task to the Jenkins master; the Jenkin master node creates a Jenkins job, and judges whether there is a Jenkins job. If the Jenkins job does not exist, then According to the slave label, the instruction for compiling task execution is issued to the slave node; the Jenkins slave node first pulls the specified branch code from the specified warehouse from Gitlab, and then pulls the image for compilation from Harbor; mounts the Maven local warehouse , and at the same time add the code warehouse directory.

In some implementation manners, the method further includes: executing Maven commands in the container environment to compile and package.

In some implementation manners, the method further includes: cleaning up the workspace and destroying the container environment after the compilation is completed.

In some embodiments, the Jenkin master node creates a Jenkins job, and judges whether there is a Jenkins job. If the Jenkins job does not exist, then according to the slave label, the command for executing the compilation task is sent to the slave node, including: selecting At present, the slave node with the least Maven local warehouse, records the corresponding relationship between the Gitlab warehouse and the Maven local warehouse under the slave node; if there is no Maven local warehouse quota, an error message will be prompted to contact the administrator to expand the slave node.

In some embodiments, the Jenkin master node creates a Jenkins job, and judges whether there is a Jenkins job. If the Jenkins job does not exist, then according to the slave label, the instruction for executing the compilation task is sent to the slave node, which also includes: When the Maven project is recompiled, the node at the time of the first compilation is prioritized, and the corresponding Maven local warehouse is mounted; if the slave node is in an inactive state, the slave node with the least Maven local warehouse is selected again, and the Gitlab warehouse is recorded It corresponds to the Maven local warehouse under the slave node; if there is no Maven local warehouse quota, an error will be reported and the administrator will be prompted to expand the slave node.

In some implementation manners, it also includes: cleaning up Maven local warehouses corresponding to 30% of the Gitlab warehouses with the least number of compilations, so as to recycle Maven local warehouse resources.

In some implementations, the cleanup period of the cleanup compilation is one month.

In some embodiments, each slave has a uniquely identifiable label.

In some implementations, the Git server uses Gitlab.

In some implementations, the Maven private server uses Nexus.

In the second aspect, the present application provides a device for improving the compilation speed of Maven projects in a container environment, and the device includes:

The access module, the storytelling access module is used to access the web program containing the scheduling algorithm, and submit the compilation task of a certain branch of the Gitlab warehouse;

Computing module, described computing module is used for computing the slave node and the corresponding Maven local warehouse of the corresponding execution of this Gitlab warehouse, store correspondence afterwards;

A submission module, the submission module submits the compilation task to the Jenkins master;

Create a module, the creation module is used for the Jenkin master node to create a Jenkins job, and judge whether there is a Jenkins job, if there is no Jenkins job, then according to the slave label, the instruction for compiling task execution is sent to the slave node;

Pulling module, the pulling module is used for the Jenkins slave node to pull the specified branch code under the specified warehouse from Gitlab first, and then pull the image for compiling from Harbor;

The mounting module is used to mount the Maven local warehouse and the code warehouse directory at the same time.

In the third aspect of the embodiment of the present invention, an electronic device is provided, and the electronic device includes:

at least one processor; and,

memory communicatively coupled to at least one processor; wherein,

The memory stores instructions executable by at least one processor, and the instructions are executed by the at least one processor, so that the at least one processor can execute the method steps provided in the first aspect of the embodiments of the present invention.

A fourth aspect of the embodiments of the present invention provides a computer-readable storage medium storing a computer program, and when the computer program is executed by a processor, the method steps provided in the first aspect of the embodiments of the present invention are implemented.

The embodiment of the present invention provides a method for improving the compilation speed of a Maven project in a container environment. First, by accessing a Web program containing a scheduling algorithm, submit a compilation task about a certain branch of the Gitlab warehouse; calculate the execution time corresponding to the Gitlab warehouse. The slave node and the corresponding Mave n local warehouse, and then store the corresponding relationship; submit the compilation task to the Jenkins master; the Jenk in master node creates a Jenkins job, and judges whether there is a Jenkins job. If the Jenkins job does not exist, then according to the slave label, Send the instructions for compiling task execution to the slave node; the Jenkins slave node first pulls the specified branch code under the specified warehouse from Gitlab, and then pulls the image used for compilation from Harbor; mounts the Maven local warehouse, and at the same time Code repository directory. A method for improving the compilation speed of a Maven project in a container environment proposed by this application improves the compilation speed and continuous integration efficiency of a Maven project in a container environment.

1. Make full use of the Maven local warehouse. This solution will mount the host Maven local warehouse to the container every time the container used for compilation is pulled up.

2. Solved the problem of compiling stuck when updating the Maven local warehouse metafile in the container environment.

3. The compilation task uses an independent Maven local warehouse, and the number of Maven local warehouses is evenly distributed on the host machine. Static compilation tasks are evenly distributed on the Jenkins slave nodes.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only These are some embodiments of the present application. Those skilled in the art can also obtain other drawings based on these drawings without creative work.

FIG. 1 is a schematic structural diagram of an electronic device in a hardware operating environment involved in an embodiment of the present application;

Fig. 2 is a flow chart showing a method for improving Maven project compilation speed in a container environment according to an exemplary embodiment;

FIG. 3 is a flow chart of Maven pulling dependent packages in a method for improving the compilation speed of a Maven project in a container environment according to an exemplary embodiment;

Fig. 4 is a schematic diagram of Jenkins based on Kurbenetes deployment in a method for improving Maven project compilation speed in a container environment according to an exemplary embodiment;

5 is a schematic diagram of an improved Maven local warehouse mounting scheme in a method for improving the Maven project compilation speed in a container environment according to an exemplary embodiment;

Fig. 6 is a flow chart of resource allocation and task scheduling in a method for improving Maven project compilation speed in a container environment according to an exemplary embodiment;

FIG. 7 is a flow chart of resource recovery in a method for improving Maven project compilation speed in a container environment according to an exemplary embodiment;

Fig. 8 is a structural diagram of a method for improving the compilation speed of a Maven project in a container environment according to an exemplary embodiment.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of them. Based on the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of this application.

In the existing technology, the security domain is a technology that guides network service packets to pass through the security service node (Security Node) in sequence. It combines SDN (Software Defined Network, software-defined network) to realize business orchestration and guide network packets It is processed and forwarded through the security nodes in the required order. The security service node is a device that processes certain services in the network, and may be a physical device or an NFV (Network Function Virtualization, network function virtualization) device. There can be multiple service nodes on a security domain service chain. Each security service node processes the message according to the security service type specified in the security service list. The security service list is used to specify the service type and processing sequence. Currently, typical service types include nodes such as FW, ACG, DPI, and IPS.

When the container used for compilation is pulled up, the Maven local warehouse directory on the host machine where the container is located is mounted, so that the Maven local warehouse will not be destroyed with the destruction of the container, thereby achieving the purpose of improving the compilation speed. This solution can be found to be flawed in practice. When multiple Maven projects are assigned to the same Jenkins slave node for compilation at the same time, if you download the package of the same snapshot version at the same time during the compilation process, you will be stuck at the place where the metafile maven-metadata.xml is downloaded.

The principle of Maven project compiling and pulling dependent packages is an important basic technology in this patent. The prerequisites for Maven project compilation in this patent are as follows:

1. The configuration warehouse and plug-in addresses in the Maven project pom file are both the addresses of the Maven private server Nexus;

2. Maven project compilation command: mvn–U clean package-Dmaven.test.skip=true;

3. All the snapshot version packages that the Maven project depends on are self-developed by the user and published to the Maven private server Nexus;

4. The Maven remote warehouse in this patent only has Maven private server Nexus and Maven central warehouse, and there is no other official remote warehouse.

Maven dependency packages are divided into official version and snapshot version. The pull order of the dependent packages of these two versions is shown in the flowchart in Figure 1:

For the official version of the dependent package,

1. Check whether the Maven local warehouse exists, and end if it exists; otherwise

2. Check whether the Maven private server Nexus exists, and if it exists, pull it from the Nexus to the local Maven warehouse; otherwise

3. Check whether the Maven central warehouse exists. If it exists, pull it from the central warehouse to the Maven private server Nexus, and then pull it to the local Maven warehouse; if the package does not exist in the Maven central warehouse, the compilation will fail.

For snapshot version dependencies,

1. Pull the dependency package metadata file, check whether there is the latest snapshot version, and end if it does not exist, otherwise

2. Pull the latest snapshot version package from Nexus to the Maven local warehouse.

The reason for the above problem is the -U parameter in the compilation command, the specific command is mvn–U cle anpackage-Dmaven.test.skip=true. The -U parameter in this command means to forcibly refresh the official version package and all snapshot version packages missing from the local warehouse. For the snapshot version package, you need to compare the lastUpdated field in the maven-metadata.xml file on the Maven private server and the maven-meta data-snapshots.xml file in the Maven local warehouse. This field is a timestamp. If you decide whether to download the snapshot package, and update the maven-metadata-snapshots.xml file. When multiple processes modify the maven-metadata-snapshots.xml file at the same time, a deadlock is caused. The snapshots in the maven-metadata-snapshots.xml file name here is because the name of the snapshot version warehouse on the Maven private server Nexus is snapshots.

Based on this, the present application proposes a method for improving the compilation speed of a Maven project in a container environment, so as to improve the above problems.

Referring to FIG. 1 , FIG. 1 is a schematic structural diagram of an electronic device in a hardware operating environment involved in the solution of the embodiment of the present application.

As shown in FIG. 1 , the electronic device may include: a processor 1001 , such as a central processing unit (Central Processing Unit, CPU), a communication bus 1002 , a user interface 1003 , a network interface 1004 , and a memory 1005 . Wherein, the communication bus 1002 is used to realize connection and communication between these components. The user interface 1003 may include a display screen (Display), an input unit such as a keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a wireless interface. Optionally, the network interface 1004 may include a standard wired interface and a wireless interface (such as a wireless fidelity (WIreles-FIdelity, WI-FI) interface). The memory 1005 may be a high-speed random access memory (Random Access Memory, RAM) memory, or a stable non-volatile memory (Non-Volatile Memory, N virtual machine), such as a disk memory. Optionally, the memory 1005 may also be a storage device independent of the aforementioned processor 1001 .

Those skilled in the art can understand that the structure shown in FIG. 1 does not constitute a limitation on the electronic device, and may include more or less components than shown in the figure, or combine some components, or arrange different components.

As shown in FIG. 1 , the memory 1005 as a storage medium may include an operating device, a data storage module, a network communication module, a user interface module, and an electronic program.

In the electronic device shown in Figure 1, the network interface 1004 is mainly used for data communication with the network server; the user interface 1003 is mainly used for data interaction with the user; the processor 1001 and the memory 1005 in the electronic device of the present invention can be set in In the electronic device, the electronic device calls the electronic program stored in the memory 1005 through the processor 1001, and executes the method for improving the Maven project compilation speed in the container environment provided by the embodiment of the present application.

Referring to Fig. 2, based on the aforementioned hardware operating environment, embodiments of the present application provide a method for improving the Maven project compilation speed in a container environment, the method comprising:

S201: access the web program containing the scheduling algorithm, and submit a compilation task about a certain branch of the Gitlab warehouse;

S202: Calculate the corresponding execution slave node and the corresponding Maven local warehouse of the Gitlab warehouse, and then store the corresponding relationship;

S203: Submit the compilation task to the Jenkins master;

The Jenkin master node creates a Jenkins job, and judges whether there is a Jenkins job. If the Jenkins job does not exist, then according to the slave label, the command to execute the compilation task is sent to the slave node;

S204: The Jenkins slave node first pulls the specified branch code under the specified warehouse from Gitlab, and then pulls the image for compiling from Harbor;

S205: Mount the Maven local warehouse, and at the same time, the code warehouse directory.

Please also refer to FIG. 3 , FIG. 4 , FIG. 5 , FIG. 6 , FIG. 7 and FIG. 8 . Jenkins has a deployment method based on the Kurbenetes cluster. The compilation tasks in this deployment method are originally executed in the container environment. In Jenkins based on the Kurbenetes cluster, the master node and all slave nodes run on the k8s cluster. Among them, the Jenkins master node will persistently store some stateful data, while the Jenkins slave node is completely stateless. Whenever the Jenkins master node receives a compilation task request, it will automatically create a slave node and establish a connection with the master node. When the compilation task is completed, the slave node will be automatically destroyed. Because the slave node is stateless, the Maven local warehouse is also destroyed with the destruction of the slave node, so every time the compilation task is executed under the slave node, the dependency package needs to be pulled from the Maven private server Nexus again, which greatly reduces the Compilation speed and continuous integration efficiency.

The specific algorithm flow is as follows:

1. When the Gitlab warehouse Maven project is compiled for the first time, select the slave node with the least Maven local warehouse at present, and record the corresponding relationship between the Gitlab warehouse and the Maven local warehouse under the slave node; if there is no Maven local warehouse quota, an error message will be prompted to contact the administrator to proceed Slave node expansion.

2. When the Maven project is recompiled, it is first scheduled to the node at the time of the first compilation, and the corresponding Maven local warehouse is mounted; if the slave node is in an inactive state, execute 1 process;

3. Regularly clean up the Maven local warehouses corresponding to 30% of the Gitlab warehouses with the least compilation times at the end of each month to recycle Maven local warehouse resources.

It should be noted that the Maven local warehouse quota on each host machine, the duration in the cleanup rule, and the proportion of the Maven local warehouse cleanup are all configurable. The values of these specific parameters need to be configured according to specific situations in practice.

In some implementation manners, the method further includes: executing Maven commands in the container environment to compile and package.

In some implementation manners, the method further includes: cleaning up the workspace and destroying the container environment after the compilation is completed.

In some embodiments, the Jenkin master node creates a Jenkins job, and judges whether there is a Jenkins job. If the Jenkins job does not exist, then according to the slave label, the command for executing the compilation task is sent to the slave node, including: selecting At present, the slave node with the least Maven local warehouse, records the corresponding relationship between the Gitlab warehouse and the Maven local warehouse under the slave node; if there is no Maven local warehouse quota, an error message will be prompted to contact the administrator to expand the slave node.

In some embodiments, the Jenkin master node creates a Jenkins job, and judges whether there is a Jenkins job. If the Jenkins job does not exist, then according to the slave label, the instruction for executing the compilation task is sent to the slave node, which also includes: When the Maven project is recompiled, the node at the time of the first compilation is prioritized, and the corresponding Maven local warehouse is mounted; if the slave node is in an inactive state, the slave node with the least Maven local warehouse is selected again, and the Gitlab warehouse is recorded It corresponds to the Maven local warehouse under the slave node; if there is no Maven local warehouse quota, an error will be reported and the administrator will be prompted to expand the slave node.

Program is a self-developed Web program that includes methods to improve the compilation speed of Maven projects in a container environment; Jenkins uses the master-slave deployment method, the master is responsible for scheduling, and the slave is responsible for the execution of specific tasks. Each slave has a unique identifier label; the Git server uses Gitlab; the Maven private server uses Nexus, and Nexus can pull the packages from the Maven central warehouse out of the public network.

The overall execution process is as follows:

1. The user accesses the web program containing the scheduling algorithm and submits a compilation task for a certain branch of a certain Gitlab warehouse;

2. Calculate the execution slave node corresponding to the Gitlab warehouse and the corresponding Maven local warehouse according to the self-developed algorithm, store the corresponding relationship, and then submit the compilation task to the Jenkins master;

3. The Jenkin master node creates a Jenkins job. If the Jenkins job does not exist, then according to the slave label, the command to execute the compilation task is sent to the slave node;

4. The Jenkins slave node first pulls the code of the specified branch under the specified warehouse from Gitlab, and then pulls the image for compilation from Harbor. When creating the container, it mounts the allocated Maven local warehouse, and at the same time, the code warehouse directory, namely : The workspace directory of the job under the slave node is also mounted to the container, and finally execute the Maven command in the container environment to compile and package. After compilation, clean up the workspace and destroy the container environment.

In some implementation manners, it also includes: cleaning up Maven local warehouses corresponding to 30% of the Gitlab warehouses with the least number of compilations, so as to recycle Maven local warehouse resources.

In some implementations, the cleanup period of the cleanup compilation is one month.

In some embodiments, each slave has a uniquely identifiable label.

In some implementations, the Git server uses Gitlab.

In some implementations, the Maven private server uses Nexus.

The embodiment of the present invention provides a method for improving the compilation speed of a Maven project in a container environment. First, by accessing a Web program containing a scheduling algorithm, submit a compilation task about a certain branch of the Gitlab warehouse; calculate the execution time corresponding to the Gitlab warehouse. The slave node and the corresponding Mave n local warehouse, and then store the corresponding relationship; submit the compilation task to the Jenkins master; the Jenk in master node creates a Jenkins job, and judges whether there is a Jenkins job. If the Jenkins job does not exist, then according to the slave label, Send the instructions for compiling task execution to the slave node; the Jenkins slave node first pulls the specified branch code under the specified warehouse from Gitlab, and then pulls the image used for compilation from Harbor; mounts the Maven local warehouse, and at the same time Code repository directory. A method for improving the compilation speed of a Maven project in a container environment proposed by this application improves the compilation speed and continuous integration efficiency of a Maven project in a container environment.

In the second aspect, the present application provides a device for improving the compilation speed of Maven projects in a container environment, and the device includes:

The access module, the storytelling access module is used to access the web program containing the scheduling algorithm, and submit the compilation task of a certain branch of the Gitlab warehouse;

Computing module, described computing module is used for computing the slave node and the corresponding Maven local warehouse of the corresponding execution of this Gitlab warehouse, store correspondence afterwards;

A submission module, the submission module submits the compilation task to the Jenkins master;

Create a module, the creation module is used for the Jenkin master node to create a Jenkins job, and judge whether there is a Jenkins job, if there is no Jenkins job, then according to the slave label, the instruction for compiling task execution is sent to the slave node;

Pulling module, the pulling module is used for the Jenkins slave node to pull the specified branch code under the specified warehouse from Gitlab first, and then pull the image for compiling from Harbor;

The mounting module is used to mount the Maven local warehouse and the code warehouse directory at the same time.

In some implementations, the creation module is also used to: select the slave node with the least Maven local warehouse at present, record the corresponding relationship between the Gitlab warehouse and the Maven local warehouse under the slave node; if there is no Maven local warehouse quota, then report an error and prompt to contact the administrator , to expand the slave node.

In some implementations, the creation module is also used for the Jenkin master node to create a Jenkinsjob, and judge whether there is a Jenkins job, if there is no Jenkins job, then according to the slave label, the command to execute the compilation task is sent to The slave node also includes: when the Maven project is recompiled, the node at the time of the first compilation is prioritized, and the corresponding Maven local warehouse is mounted; if the slave node is inactive, the current Maven local warehouse with the least amount is selected again slave node, record the corresponding relationship between the Gitlab warehouse and the Maven local warehouse under the slave node; if there is no Maven local warehouse quota, an error message will be prompted to contact the administrator to expand the slave node.

Based on the same inventive concept, an embodiment of the present application also provides an electronic device, the electronic device includes:

at least one processor; and,

memory communicatively coupled to at least one processor; wherein,

The memory stores instructions executable by at least one processor, and the instructions are executed by at least one processor, so that the at least one processor can execute the above method.

Based on the same inventive concept, an embodiment of the present application further provides a computer-readable storage medium storing a computer program, and implementing the above method when the computer program is executed by a processor.

Based on the same inventive concept, an embodiment of the present application further provides a computer program product, which implements the above method when the computer program product is processed.

Those skilled in the art should understand that the embodiments of the present invention may be provided as methods, systems, or computer program products. Accordingly, embodiments of the invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, embodiments of the invention may take the form of a computer program product implemented on one or more computer-usable vehicles (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

Embodiments of the present invention are described with reference to flowcharts and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each procedure and/or block in the flowchart and/or block diagram, and a combination of procedures and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions may be provided to a general purpose computer, special purpose computer, embedded processor or processor of other programmable data processing terminal equipment to produce a machine such that instructions executed by the computer or processor of other programmable data processing terminal equipment Produce a system for realizing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing terminal to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising a system of instructions, the The instruction system realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions can also be loaded into a computer or other programmable data processing terminal equipment, so that a series of operational steps are performed on the computer or other programmable terminal equipment to produce computer-implemented processing, thereby The instructions executed above provide steps for implementing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

Finally, it should also be noted that in this text, relational terms such as first and second etc. are only used to distinguish one entity or operation from another, and do not necessarily require or imply that these entities or operations, any such actual relationship or order exists. "And/or" means that either one of the two can be selected, or both can be selected. Furthermore, the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article, or terminal equipment comprising a set of elements includes not only those elements, but also includes elements not expressly listed. other elements identified, or also include elements inherent in such a process, method, article, or terminal equipment. Without further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article or terminal device comprising said element.

The method for improving the Maven project compilation speed in the container environment provided by the present invention has been introduced in detail above. In this paper, specific examples are used to illustrate the principle and implementation of the present invention. The description of the above embodiments is only used to help Understand the method of the present invention and its core idea; at the same time, for those of ordinary skill in the art, according to the idea of the present invention, there will be changes in the specific implementation and scope of application. In summary, the content of this specification is not It should be understood as a limitation of the present invention.

Claims (10)

1. A method for improving the compiling speed of Maven engineering in a container environment, comprising the following steps:

accessing a Web program containing a scheduling algorithm, and submitting a compiling task related to a certain branch of the Gitlab warehouse;

calculating an executed slave node corresponding to the Gitlab warehouse and a corresponding Maven local warehouse, and then storing a corresponding relation;

submitting the compiling task to a Jenkins master;

the Jenkins master node creates Jenkins job, judges whether the Jenkins job exists or not, and if the Jenkins job does not exist, issues a command for executing a compiling task to a slave node according to a slave tag;

the Jenkins slave node firstly pulls the appointed branch codes under the appointed warehouse from the Gitlab, and then pulls the mirror image for compiling from the Harbor;

the Maven local warehouse is mounted while the code warehouse is catalogued.

2. The method for increasing the compiling speed of Maven project in a container environment according to claim 1, wherein the method further comprises:

the Maven command is executed in the container environment for compiling and packing.

3. The method for increasing the compiling speed of Maven project in a container environment according to claim 2, wherein the method further comprises:

after compiling is finished, cleaning up the workspace and destroying the container environment.

4. The method for improving the compiling speed of Maven engineering in a container environment according to claim 3, wherein the Jenkin master node creates Jenkins job, judges whether Jenkins job exists, and if not, issues a compiling task executing instruction to a slave node according to a slave tag, including:

selecting the slave node with the least current Maven local warehouse, and recording the corresponding relation between the Gitlab warehouse and the Maven local warehouse under the slave node; if the Maven local warehouse quota does not exist, the error prompt contacts an administrator to expand the capacity of the slave node.

5. The method for increasing the compiling speed of Maven engineering in a container environment according to claim 4, wherein the Jenkin master node creates Jenkins job, determines whether Jenkins job exists, if not, issues a compiling task executing instruction to the slave node according to the slave tag, and further comprises:

when the Maven project is compiled again, preferentially scheduling the nodes to the nodes at the first compiling time, and mounting the corresponding Maven local warehouse; if the slave node is in an inactive state, selecting the slave node with the least current Maven local warehouse again, and recording the corresponding relation between the Gitlab warehouse and the Maven local warehouse under the slave node; if the Maven local warehouse quota does not exist, the error prompt contacts an administrator to expand the capacity of the slave node.

6. The method for increasing the compiling speed of Maven project in a container environment according to claim 5, further comprising:

and cleaning the Maven local warehouse corresponding to the Gitlab warehouse with the minimum compiling frequency, and recovering the Maven local warehouse resources.

7. The method for improving compilation speed of Maven project in a container environment of claim 6 wherein the cleaning cycle of cleaning compilation is one month.

8. The method of claim 7, wherein each slave has a unique identifiable tag.

9. The method for improving compilation speed of Maven project in container environment according to claim 8, wherein the Git server uses Gitlab.

10. The method of claim 9, wherein the Maven private service uses Ne xus.

Images