System and method for realizing CI / CD function in integrated development environment

Abstract

The invention discloses a system and a method for realizing a CI / CD function in an integrated development environment. The system includes an integrated development environment (IDE) in which an engineering guide plug-in, a pipeline design plug-in, a communication plug-in, a code editing plug-in, a build state plug-in, and a Git plug-in are integrated. Through cooperative work of the plug-ins, a user can efficiently create projects, write codes, manage the codes and automatically construct and deploy the processes in an IDE in a one-stop mode. The method comprises the steps of project creation, CI / CD assembly line design, code writing and modification, construction task triggering, construction log receiving, fault processing, construction process repeating, continuous delivery completion, construction record viewing and the like. Through the steps, a user can efficiently carry out software development in the IDE, CI / CD is realized, and the development efficiency and the software quality are remarkably improved.

Description

Technical Field

[0001] The present invention belongs to the technical field of computer software development, and in particular to a system and method for realizing CI / CD functions in an integrated development environment. Background Art

[0002] In the modern software development process, continuous integration (CI) and continuous delivery (CD) have become key means to improve development efficiency and software quality. Domestic developers usually use a series of tools to implement CI / CD, such as:

[0003] Integrated Development Environment (IDE): such as Eclipse, IntelliJ IDEA, Visual Studio, QtCreator, etc., for code writing and management.

[0004] Version control system: such as Git, SVN, etc., used for code version control and team collaboration.

[0005] Continuous integration servers: Jenkins, GitLab CI, Travis CI, etc., for automated building, testing, and deployment.

[0006] However, these tools are independent of each other, and developers need to frequently switch between different tools, which makes the development process complicated and inefficient. For example:

[0007] Tool switching: Developers need to switch back and forth between IDE, version control system, and continuous integration server, which increases operational complexity.

[0008] Environment configuration: Different tools need to be configured separately, which increases the cost of environment construction and maintenance.

[0009] Information silos: Information between different tools cannot be shared, making it difficult for developers to obtain a complete view of the development process. Summary of the invention

[0010] The purpose of the present invention is to provide a system and method for implementing CI / CD functions in an integrated development environment to address the problems of tool fragmentation, complex processes, and low efficiency in the prior art, and to integrate continuous integration and continuous delivery (CI / CD) functions in an IDE. Through the present invention, users can efficiently create projects, write code, manage code, and automate the build and deployment process in an IDE in one stop.

[0011] The technical solution to achieve the purpose of the present invention is as follows: on the one hand, a system for implementing CI / CD functions in an integrated development environment is provided, the system comprising an integrated development environment IDE, wherein an engineering wizard plug-in, a pipeline design plug-in, a communication plug-in, a code editing plug-in, a build status plug-in and a Git plug-in are integrated;

[0012] The project wizard plug-in is used to create a project and generate corresponding project files;

[0013] The pipeline design plug-in is used to design the pipeline of the CI / CD process, define each step, and generate the corresponding JenkinsFile file;

[0014] The communication plug-in is used to receive instructions from the engineering wizard plug-in, call the APIs of GitLab and Jenkins, and manage and configure GitLab repositories and Jenkins pipeline tasks;

[0015] The build status plug-in is used to display the build log information of the Jenkins pipeline task and locate error information;

[0016] The code editing plug-in is used to write and modify the code;

[0017] The Git plug-in is used to update project files.

[0018] Furthermore, the project wizard plug-in is connected with the Git plug-in when the project is created to create a local branch of the project file.

[0019] Furthermore, the project wizard plug-in is connected to the communication plug-in at the same time when the project is created, and a remote warehouse is created in GitLab, and the warehouse contains remote branches of the project files.

[0020] Furthermore, the project wizard plug-in is also connected to the communication plug-in when the project is created, and a pipeline task is created in Jenkins. The JenkinsFile file source of the pipeline is configured as the warehouse address of GitLab, and the Jenkins task is integrated with the GitLab warehouse address to automatically trigger the Jenkins pipeline build when the version in the GitLab warehouse is updated.

[0021] Furthermore, while receiving the instruction from the engineering wizard plug-in, the communication plug-in is also used to obtain the build log of the Jenkins pipeline task and send it to the build status plug-in.

[0022] Furthermore, the build status plug-in is also used to call the code editing plug-in and the pipeline design plug-in to perform error correction according to the fault type.

[0023] Furthermore, the Git plug-in is connected to GitLab to associate the local branch with the remote branch of GitLab; when the local project file version is updated, the Git plug-in automatically triggers the update of the remote project file in GitLab.

[0024] On the other hand, a method for implementing CI / CD functions in an integrated development environment is provided, the method comprising the following steps:

[0025] Step 1, create a project, including: start the project wizard, generate project files, create a local branch, create a remote repository, create a pipeline task in Jenkins, and configure the source of JenkinsFile to the repository address of GitLab;

[0026] Step 2: Design the CI / CD pipeline, including: defining the steps of the CI / CD pipeline in the IDE, generating the JenkinsFile file, submitting the changes of the JenkinsFile to the local Git repository, and triggering synchronization with GitLab;

[0027] Step 3, code writing and modification, including: code writing and modification in the IDE, the Git plug-in automatically monitors changes in local branches, submits changes to the local Git repository, and triggers synchronization with GitLab;

[0028] Step 4, triggering the build task, including: when the code changes are pushed to GitLab, GitLab automatically triggers the Jenkins build task, Jenkins pulls the JenkinsFile and source code from the GitLab repository, and executes the CI / CD pipeline pre-defined in the JenkinsFile;

[0029] Step 5, receiving the build log, including: the build status plug-in receives and displays the Jenkins build log in real time;

[0030] Step 6: Perform troubleshooting, including: if the build error is caused by a source code bug, the build status plug-in will automatically jump to the error line number corresponding to the source code; if the build error is caused by the pipeline configuration, the build status plug-in will automatically jump to the error line number corresponding to the JenkinsFile;

[0031] Step 7, repeating the building process, including: after the user completes the repair in the IDE, repeating steps 3 to 7 until the pipeline is successfully built;

[0032] Step 8, complete continuous delivery, including: when the pipeline is built successfully, the build status plug-in will notify the user, mark the build as successful, and Jenkins will push the build product to the predetermined deployment environment to complete continuous delivery.

[0033] Furthermore, in step 5, if an error occurs during the build process, click the error message display line, and the build status plug-in will automatically jump to the location.

[0034] Furthermore, the method further comprises:

[0035] Step 9, view the build records, including: view the historical build records and logs through the IDE's build status plug-in for subsequent maintenance and optimization.

[0036] Compared with the prior art, the present invention has the following significant advantages:

[0037] (1) Simplify the development process: Developers can complete code writing, version control, building, testing, and deployment in one stop in the IDE without having to switch between different tools;

[0038] (2) Improve development efficiency: Automated construction, testing, and deployment reduce manual operations and improve development efficiency;

[0039] (3) Improve software quality: Continuous integration and continuous delivery to detect and fix problems as early as possible and improve software quality;

[0040] (4) Reduce learning costs: No need to learn new platforms and tools, reducing learning costs.

[0041] The present invention is further described in detail below in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Figure 1 The overall architecture of a system for implementing CI / CD functions in an integrated development environment of the present invention in one embodiment.

[0043] Figure 2 The present invention is a flowchart of using an integrated development environment to perform code version management, pipeline design, and automatic pipeline construction in one embodiment. DETAILED DESCRIPTION

[0044] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0045] In response to the problems existing in the prior art, the present invention provides a system and method for realizing CI / CD functions in an integrated development environment, integrating CI / CD functions into IDE, realizing a one-stop development experience, reducing tool switching and environment configuration, and simplifying the development process; reducing manual operations and improving development efficiency through automated building, testing, and deployment; and discovering and fixing problems as early as possible and improving software quality through continuous integration and continuous delivery.

[0046] In one embodiment, in combination Figure 1, provides a system for implementing CI / CD functions in an integrated development environment, the system comprising an integrated development environment IDE, wherein an engineering wizard plug-in, a pipeline design plug-in, a communication plug-in, a code editing plug-in, a build status plug-in and a Git plug-in are integrated;

[0047] The project wizard plug-in is used to create a project and generate corresponding project files;

[0048] The pipeline design plug-in is used to design the pipeline of the CI / CD process, define each step, and generate the corresponding JenkinsFile file;

[0049] The communication plug-in is used to receive instructions from the engineering wizard plug-in, call the APIs of GitLab and Jenkins, and manage and configure GitLab repositories and Jenkins pipeline tasks;

[0050] The build status plug-in is used to display the build log information of the Jenkins pipeline task and locate error information;

[0051] The code editing plug-in is used to write and modify the code;

[0052] The Git plug-in is used to update project files.

[0053] Furthermore, in one of the embodiments, the project wizard plug-in is connected to the Git plug-in when the project is created to create a local branch of the project file.

[0054] Furthermore, in one of the embodiments, the project wizard plug-in is simultaneously connected to the communication plug-in when the project is created, and a remote repository is created in GitLab, and the repository contains a remote branch of the project file.

[0055] Furthermore, in one of the embodiments, the project wizard plug-in is also connected to the communication plug-in when the project is created, and a pipeline task is created in Jenkins. The JenkinsFile file source of the pipeline is configured as the warehouse address of GitLab, and the Jenkins task is integrated with the GitLab warehouse address to automatically trigger the Jenkins pipeline build when the version in the GitLab warehouse is updated.

[0056] Furthermore, in one of the embodiments, while receiving instructions from the engineering wizard plug-in, the communication plug-in is also used to obtain the build log of the Jenkins pipeline task and send it to the build status plug-in.

[0057] Furthermore, in one of the embodiments, the build status plug-in is also used to call the code editing plug-in and the pipeline design plug-in to perform error correction according to the fault type.

[0058] Furthermore, in one of the embodiments, the Git plug-in is connected to GitLab to associate local branches with remote branches of GitLab; when the local project file version is updated, the Git plug-in automatically triggers the update of the remote project file in GitLab.

[0059] In one embodiment, in combination Figure 2 , provides a method for implementing CI / CD functions in an integrated development environment, the method comprising the following steps:

[0060] Step 1, create a project, including: start the project wizard, generate project files, create a local branch, create a remote repository, create a pipeline task in Jenkins, and configure the source of JenkinsFile to the repository address of GitLab;

[0061] Specifically include:

[0062] 1.1, the programmer (user) starts the new project creation wizard through the project wizard plug-in.

[0063] 1.2, the project wizard plug-in generates a project file containing project management files, source code and JenkinsFile.

[0064] 1.3. The Project Wizard plug-in is connected to the Git plug-in to automatically create a local branch of the project file.

[0065] 1.4, the Project Wizard plug-in creates a corresponding remote repository in GitLab through the communication plug-in to achieve the mapping association between local branches and remote branches.

[0066] 1.5, the Project Wizard plugin creates the corresponding pipeline task in Jenkins and configures the source of JenkinsFile to the repository address of GitLab.

[0067] 1.6, the Project Wizard plugin configures the Jenkins task integration address in the GitLab remote repository to ensure that it is automatically triggered when the GitLab remote repository changes.

[0068] Step 2, designing the CI / CD pipeline, including: defining the steps of the CI / CD pipeline in the IDE, generating the JenkinsFile file, submitting changes to the JenkinsFile to the local Git repository, and triggering synchronization with GitLab; specifically including:

[0069] 2.1. Programmers use the pipeline design plug-in to define the various steps of the CI / CD pipeline in the IDE, including code compilation, unit testing, static checking, packaging and deployment, and configure corresponding parameters, scripts and other content for each step.

[0070] 2.2, the pipeline design plug-in generates the corresponding JenkinsFile file.

[0071] 2.3, the Git plugin automatically commits changes to JenkinsFile to the local Git repository, triggers synchronization with GitLab, and pushes updates to the remote branch.

[0072] Step 3, code writing and modification, includes: code writing and modification in the IDE, the Git plug-in automatically monitors changes in local branches, submits changes to the local Git repository, and triggers synchronization with GitLab; specifically includes:

[0073] 3.1, Programmers write and modify code in IDE.

[0074] 3.2, Git plug-in automatically monitors changes in local branches.

[0075] 3.3, when an update is detected, the Git plugin will automatically commit the changes to the local Git repository and trigger synchronization with GitLab to push the updates to the remote branch.

[0076] Step 4, triggering the build task, including: when the code changes are pushed to GitLab, GitLab automatically triggers the Jenkins build task, Jenkins pulls the JenkinsFile and source code from the GitLab repository, and executes the CI / CD pipeline pre-defined in the JenkinsFile; specifically, it includes:

[0077] 4.1, when the code changes are pushed to GitLab, GitLab automatically triggers the Jenkins build task.

[0078] 4.2, Jenkins pulls JenkinsFile and source code from the GitLab repository.

[0079] 4.3, Jenkins executes the CI / CD pipeline pre-defined in JenkinsFile, performing steps such as code compilation, unit test packaging and deployment.

[0080] Step 5, receiving the build log, including: the build status plug-in receives and displays the Jenkins build log in real time; specifically including:

[0081] 5.1, the build status plug-in receives and displays Jenkins build logs in real time.

[0082] 5.2. If an error occurs during the build process, the programmer clicks the error message display line, and the build status plug-in will automatically jump to the location.

[0083] Step 6, troubleshooting, including: if the build error is caused by a source code bug, the build status plug-in will automatically jump to the error line number corresponding to the source code; if the build error is caused by the pipeline configuration, the build status plug-in will automatically jump to the error line number corresponding to the JenkinsFile; specifically including:

[0084] 6.1. If the build error is caused by a bug in the source code, the build status plug-in will automatically jump to the error line number corresponding to the source code, helping programmers quickly locate and fix the problem in the code.

[0085] 6.2. If the pipeline fails and causes a build error, the build status plug-in will automatically jump to the error line number corresponding to the JenkinsFile, helping programmers quickly locate and fix problems in the pipeline configuration.

[0086] Step 7, repeating the building process, including: after the user completes the repair in the IDE, repeating steps 3 to 7 until the pipeline is successfully built;

[0087] Step 8: Complete continuous delivery, including: When the pipeline is successfully built, the build status plug-in will notify the user and mark the build as successful. Jenkins will push the build product to the predetermined deployment environment to complete continuous delivery, including:

[0088] 8.1, when the pipeline is built successfully, the build status plugin will notify the programmer and mark the build as successful;

[0089] 8.2, Jenkins pushes the build product to the predetermined deployment environment to complete continuous delivery.

[0090] Furthermore, in one of the embodiments, in step 5, if an error occurs during the building process, the building status plug-in will automatically jump to the location by clicking the error message display line.

[0091] Furthermore, in one embodiment, the method further comprises:

[0092] Step 9, view the build records, including: view the historical build records and logs through the IDE's build status plug-in for subsequent maintenance and optimization.

[0093] As a specific example, in one of the embodiments, the present invention is further verified and explained in detail.

[0094] Based on the QtCreator integrated development environment (IDE), a system and method for implementing CI / CD functions is developed through C / C++ language, specifically including:

[0095] 1. System architecture design

[0096] This system integrates the project wizard plug-in, pipeline design plug-in, communication plug-in, build status plug-in and Git plug-in in QtCreator to achieve the integration of CI / CD functions.

[0097] 1.1, Integrated Development Environment (QtCreator)

[0098] QtCreator is an open source cross-platform integrated development environment that supports C / C++ language development. The present invention expands on this basis and integrates CI / CD functions.

[0099] 1.2, Plugin Architecture

[0100] Project Wizard Plugin: Responsible for creating projects, generating project files, and connecting with the Git plugin and communication plugin.

[0101] Pipeline design plug-in: used to design CI / CD pipelines and generate JenkinsFile files.

[0102] Communication plug-in: responsible for API communication with GitLab and Jenkins, managing warehouses and pipeline tasks.

[0103] Build Status Plugin: Displays Jenkins build logs and locates error messages.

[0104] Git plugin: connects to GitLab to manage the synchronization of local and remote branches.

[0105] 2. Project Wizard Plugin Implementation

[0106] 2.1, Create a project

[0107] a) Start the project wizard:

[0108] In QtCreator, programmers start the project wizard plug-in through the menu or shortcut keys.

[0109] The Project Wizard plug-in pops up a dialog box, prompting you to enter project name, path and other information.

[0110] b) Generate project files:

[0111] The project wizard plug-in generates project files based on the input information, including project management files (such as .pro files), source code files, and JenkinsFile files.

[0112] c) Create a local branch:

[0113] The Project Wizard plug-in calls the Git plug-in to create a local branch of the project file in the local Git repository.

[0114] d) Create a remote repository:

[0115] The Project Wizard plugin calls the GitLab API through the communication plugin, creates a remote repository in GitLab, and associates the local branch with the remote branch.

[0116] e) Create a Jenkins pipeline task:

[0117] The project wizard plug-in calls the Jenkins API through the communication plug-in, creates a pipeline task in Jenkins, and configures the source of the JenkinsFile to the GitLab warehouse address.

[0118] The Project Wizard plugin configures the Jenkins task integration address in the GitLab remote repository to ensure that the Jenkins build task is automatically triggered when the GitLab remote repository changes.

[0119] 3. Pipeline design plug-in implementation

[0120] 3.1. Design CI / CD pipeline

[0121] a) Define pipeline steps:

[0122] Programmers open the pipeline design plug-in in QtCreator and define the various steps of the CI / CD pipeline, such as code compilation, unit testing, static checking, packaging and deployment. The pipeline design plug-in provides a graphical interface that allows programmers to configure the parameters, scripts and other content of each step.

[0123] b) Generate JenkinsFile:

[0124] The pipeline design plug-in generates a JenkinsFile file based on the defined pipeline steps. The JenkinsFile file describes the detailed configuration of the CI / CD pipeline.

[0125] c) Submit JenkinsFile:

[0126] The Git plugin automatically monitors changes to JenkinsFile and submits them to the local Git repository. At the same time, the Git plugin triggers synchronization with GitLab and pushes updates to the remote branch.

[0127] 4. Code writing and modification

[0128] 4.1, Code Writing

[0129] a) Write code:

[0130] Programmers write and modify code in QtCreator.

[0131] b) Automatically submit changes:

[0132] The Git plugin automatically monitors changes in local branches. When an update is detected, the Git plugin automatically commits the change to the local Git repository and triggers synchronization with GitLab to push the update to the remote branch.

[0133] 5. Trigger the build task

[0134] 5.1, Automatically trigger the build

[0135] a) Push to GitLab:

[0136] When code changes are pushed to GitLab, GitLab automatically triggers the Jenkins build task.

[0137] b)Jenkins pulls the code:

[0138] Jenkins pulls the JenkinsFile and source code from the GitLab repository.

[0139] c) Execution pipeline:

[0140] Jenkins executes the CI / CD pipeline pre-defined in JenkinsFile to perform steps such as code compilation, unit testing, packaging, and deployment.

[0141] 6. Receive build logs

[0142] 6.1, Display build log

[0143] a) Real-time receiving logs:

[0144] The Build Status plugin receives and displays Jenkins build logs in real time.

[0145] b) Positioning error information:

[0146] If an error occurs during the build process, the programmer clicks the error message display line, and the build status plug-in will automatically jump to the location.

[0147] 7. Troubleshooting

[0148] 7.1, Source code bug handling

[0149] a) Jump to the error line:

[0150] If a build error is caused by a bug in the source code, the build status plug-in will automatically jump to the error line number corresponding to the source code, helping programmers quickly locate and fix the problem in the code.

[0151] 7.2, Pipeline Configuration Error Handling

[0152] a) Jump to JenkinsFile:

[0153] If the build error is caused by the pipeline configuration, the build status plug-in will automatically jump to the error line number corresponding to the JenkinsFile, helping programmers quickly locate and fix problems in the pipeline configuration.

[0154] 8. Repeat the build process

[0155] 8.1, Repeat the build

[0156] a) Rebuild after repair:

[0157] After the programmer completes the repair in QtCreator, repeat steps 3 to 7 until the pipeline is built successfully.

[0158] 9. Complete Continuous Delivery

[0159] 9.1, Build Success Notification

[0160] a) Notify the programmer:

[0161] When the pipeline build succeeds, the build status plugin notifies the programmer and marks the build as successful.

[0162] b) Push to the deployment environment:

[0163] Jenkins pushes the build products to the predetermined deployment environment to complete continuous delivery.

[0164] 10. View build records

[0165] 10.1, View History

[0166] a) View the build log:

[0167] Programmers can view historical build records and logs through QtCreator's build status plug-in for subsequent maintenance and optimization.

[0168] The present invention can simplify the development process, improve development efficiency, reduce development costs, shorten product launch time, and has significant economic benefits.

[0169] The above shows and describes the basic principles, main features and advantages of the present invention. Those skilled in the art should understand that the present invention is not limited by the above embodiments, and the above embodiments and descriptions are only for explaining the principles of the present invention. Without departing from the spirit and scope of the present invention, any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A system for implementing CI / CD functions in an integrated development environment, characterized in that: The system includes an integrated development environment IDE, which integrates an engineering wizard plug-in, a pipeline design plug-in, a communication plug-in, a code editing plug-in, a build status plug-in and a Git plug-in; The project wizard plug-in is used to create a project and generate corresponding project files; The pipeline design plug-in is used to design the pipeline of the CI / CD process, define each step, and generate the corresponding JenkinsFile file; The communication plug-in is used to receive instructions from the engineering wizard plug-in, call the APIs of GitLab and Jenkins, and manage and configure GitLab repositories and Jenkins pipeline tasks; The build status plug-in is used to display the build log information of the Jenkins pipeline task and locate error information; The code editing plug-in is used to write and modify the code; The Git plug-in is used to update project files.

2. The system for implementing CI / CD functions in an integrated development environment according to claim 1, characterized in that: The project wizard plug-in is connected with the Git plug-in when the project is created to create a local branch of the project file.

3. The system for implementing CI / CD functions in an integrated development environment according to claim 2, characterized in that: The project wizard plug-in is connected to the communication plug-in at the same time when the project is created, and a remote warehouse is created in GitLab, and the warehouse contains remote branches of the project files.

4. The system for implementing CI / CD functions in an integrated development environment according to claim 1, characterized in that: The project wizard plug-in is also connected to the communication plug-in when the project is created, and a pipeline task is created in Jenkins. The JenkinsFile file source of the pipeline is configured as the warehouse address of GitLab, and the Jenkins task is integrated with the GitLab warehouse address to automatically trigger the Jenkins pipeline build when the version in the GitLab warehouse is updated.

5. The system for implementing CI / CD functions in an integrated development environment according to claim 1, characterized in that: While receiving instructions from the engineering wizard plug-in, the communication plug-in is also used to obtain the build log of the Jenkins pipeline task and send it to the build status plug-in.

6. The system for implementing CI / CD functions in an integrated development environment according to claim 1, characterized in that: The build status plug-in is also used to call the code editing plug-in and the pipeline design plug-in respectively to perform error correction according to the fault type.

7. The system for implementing CI / CD functions in an integrated development environment according to claim 1 or 3, characterized in that: The Git plug-in is connected to GitLab to associate local branches with GitLab's remote branches; when the local project file version is updated, the Git plug-in automatically triggers the update of the remote project file in GitLab.

8. A method for implementing CI / CD functions in an integrated development environment based on the system according to any one of claims 1 to 7, characterized in that: The method comprises the following steps: Step 1, create a project, including: start the project wizard, generate project files, create a local branch, create a remote repository, create a pipeline task in Jenkins, and configure the source of JenkinsFile to the repository address of GitLab; Step 2: Design the CI / CD pipeline, including: defining the steps of the CI / CD pipeline in the IDE, generating the JenkinsFile file, submitting the changes of the JenkinsFile to the local Git repository, and triggering synchronization with GitLab; Step 3, code writing and modification, including: code writing and modification in the IDE, the Git plug-in automatically monitors changes in local branches, submits changes to the local Git repository, and triggers synchronization with GitLab; Step 4, triggering the build task, including: when the code changes are pushed to GitLab, GitLab automatically triggers the Jenkins build task, Jenkins pulls the JenkinsFile and source code from the GitLab repository, and executes the CI / CD pipeline pre-defined in the JenkinsFile; Step 5, receiving the build log, including: the build status plug-in receives and displays the Jenkins build log in real time; Step 6, troubleshooting, including: if the build error is caused by a source code bug, the build status plug-in will automatically jump to the error line number corresponding to the source code; if the build error is caused by the pipeline configuration, the build status plug-in will automatically jump to the error line number corresponding to the JenkinsFile; Step 7, repeating the building process, including: after the user completes the repair in the IDE, repeating steps 3 to 7 until the pipeline is successfully built; Step 8, complete continuous delivery, including: when the pipeline is built successfully, the build status plug-in will notify the user, mark the build as successful, and Jenkins will push the build product to the predetermined deployment environment to complete continuous delivery.

9. The method for implementing CI / CD function in an integrated development environment according to claim 8, characterized in that: In step 5, if an error occurs during the build process, click the error message display line and the build status plug-in will automatically jump to the location.

10. The method for implementing CI / CD function in an integrated development environment according to claim 8, characterized in that: The method further comprises: Step 9, view the build records, including: view the historical build records and logs through the IDE's build status plug-in for subsequent maintenance and optimization.

Images