A code integration management method and system based on Jenkins
By monitoring code submission events during the code integration process and triggering Jenkins remote construction tasks, the problem of easy contamination of the code and inconsistent construction environment is solved, and the code is safely integrated and unified.
CN113626036BActive Publication Date: 2025-03-18BEIJING WODONG TIANJUN INFORMATION TECH CO LTD
2 Cites 0 Cited by
Patent Information
- Application Number
- CN202110914845.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-08-10
- Publication Date
- 2025-03-18
- Estimated Expiration
- 2041-08-10
AI Technical Summary
Technical Problem
In the process of code integration, the existing technology has the problem that code is easily contaminated and cannot achieve a unified construction of an integrated environment.
Method used
By monitoring the code submission event, the client runs to trigger the Jenkins remote build task, perform defect detection, and poll the Jenkins monitoring plug-in to obtain the build status. If successful, the code will be pushed to the code repository.
Benefits of technology
It realizes the process of code submission interception, differential code application to the server, and a unified server-side construction, solving the problems of code pollution and inconsistent construction environment.
✦ Generated by Eureka AI based on patent content.
Abstract
The present invention discloses a code integration management method and system based on Jenkins, and relates to the field of computer technology. A specific implementation of the method includes: after monitoring and intercepting a code submission event, triggering the client to run, so as to trigger a Jenkins remote build task through the client; polling the monitoring plug-in in Jenkins to obtain the latest build status of each task; if all tasks are successfully built, the code is pushed to the code warehouse through the client, otherwise a push failure message is returned. On the one hand, this implementation can ensure that a continuous integration build check can be performed before the code is submitted to the code warehouse, so as to avoid the code in the code warehouse from being contaminated; on the other hand, the entire build environment is built in Jenkins, and each user does not need to repeatedly build the environment locally, while also ensuring the uniformity of the continuous integration environment.
Need to check novelty before this filing date? Find Prior Art