Jenkinsfile-based user-defined compiling and deploying method and system

Abstract

The invention provides a jenkinsfile-based user-defined compiling and deploying method and system, and the method comprises the steps: M1, introducing a jenkinsfile dependence package into a project,and completing the configuration of a basic module and a service module; M2, based on the jenkinsfile dependency package, identifying a modified source code in the project through a code identification module; M3, compiling the modified source code according to a preset coding strategy in a compiling strategy module to obtain a corresponding mirror image, and storing the corresponding mirror imagein a mirror image warehouse; and M4, deploying the mirror image in the mirror image warehouse to various environments based on a preset deployment strategy, and completing output of the source code service. By adopting the compiling deployment process capture module, the log capture and display problems in the compiling process are solved, and an unattended compiling deployment whole process canbe realized.

Description

technical field [0001] The present invention relates to the field of block chain technology, in particular to a method and system for self-defining compilation and deployment based on jenkinsfile. Background technique [0002] Typical compilation and deployment tools are git and jenkins, and a traditional scenario from source code to deployment is to submit the source code to the git warehouse before compiling, and then use jenkins to build all modules of the source code to generate related packages, and then use jenkins Deploying these packages to different environments, there are two problems in this scenario. One is the compatibility of different environments. The second is that it takes a long time to fully compile the source code, resulting in a very low efficiency of compilation and deployment. The tools used in a containerized compilation and deployment are still git and jenkins. Due to the introduction of the mirror warehouse, compilation can be compiled without comp...

AI Technical Summary

Problems solved by technology

[0002] Typical compilation and deployment tools are git and jenkins, and a traditional scenario from source code to deployment is to submit the source code to the git warehouse before compiling, and then use jenkins to build all modules of the source code to generate related packages, and then use jenkins Deploying these packages to different environments, there are two problems in this scenario. One is the compatibility of different environments. The second is that it takes a long time to fully compile the source code, resulting in a very low efficiency of compilation and deployment.

The tools used in a containerized compilation and deployment are still git and jenkins. Due to the introduction of the mirror warehouse, compilation can be compiled without compiling in each environment, which greatly shortens the compilation time. Containerization solves the problem of compatibility caused by inconsistencies in the environment problem, so the efficiency of compilation and deployment has been improved to a certain extent, and a system has basic modules and application modules, and the basic module is the basis of the application module, which only needs to be compiled without generating a mirror image, but traditional jenkins cannot specify the required compilation modules, resulting in mirror images for both basic modules and business modules, and every time the code is modified, no matter whether the business modules are modified or not, it needs to be recompiled to generate a new mirror image, resulting in very low compilation efficiency. There is a problem with the image being too large

Secondly, using jenkins is a closed system in the compilation and deployment process. The compilation log and deployment log cannot be connected with other automation tools, and the follow-up automatic processing after compilation and deployment failure cannot be done. Only manual intervention

Images