CN113590485B - Multi-management system integration method and computer readable storage medium - Google Patents
Multi-management system integration method and computer readable storage medium Download PDFInfo
- Publication number
- CN113590485B CN113590485B CN202110881164.XA CN202110881164A CN113590485B CN 113590485 B CN113590485 B CN 113590485B CN 202110881164 A CN202110881164 A CN 202110881164A CN 113590485 B CN113590485 B CN 113590485B
- Authority
- CN
- China
- Prior art keywords
- management system
- interface
- buddhist
- gitlab
- executed
- 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
- 238000000034 method Methods 0.000 title claims abstract description 30
- 230000010354 integration Effects 0.000 title claims abstract description 25
- 230000006870 function Effects 0.000 claims abstract description 42
- 238000012360 testing method Methods 0.000 claims description 17
- 238000004590 computer program Methods 0.000 claims description 4
- 230000000391 smoking effect Effects 0.000 claims description 4
- 238000013507 mapping Methods 0.000 claims description 3
- 238000004806 packaging method and process Methods 0.000 claims description 3
- 238000012545 processing Methods 0.000 claims description 3
- 239000000758 substrate Substances 0.000 claims 2
- 230000008439 repair process Effects 0.000 description 4
- 230000001960 triggered effect Effects 0.000 description 4
- 230000008901 benefit Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 238000012856 packing Methods 0.000 description 3
- 230000009471 action Effects 0.000 description 1
- 238000007792 addition Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 239000000779 smoke Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3664—Environments for testing or debugging software
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a multi-management system integration method and a computer readable storage medium, wherein a first interface, a second interface and a calling module are preset, then the calling module calls the functions of a Buddhist management system through the first interface and the functions of the GitLab management system through the second interface, and finally the operation required by the current task to be executed is finished, so that the continuous integration of the Buddhist management system and the GitLab management system is realized, and a user can call the Buddhist and GitLab simultaneously, thereby greatly improving the user experience.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method for integrating multiple management systems and a computer readable storage medium.
Background
Buddhist channel (zentao) is an open source software research and development project management system, which can manage requirements, tasks, bug and test cases, and the like at the same time, and many companies select Buddhist channel for project management. GitLab is an open source code management system that is very widely used, especially for information security reasons, where it is desirable to isolate the development network from the internet, most of which are selected for use in intranet deployment GitLab for code management.
However, the integration of Buddhist and GitLab cannot be achieved, so that when a company uses Buddhist and GitLab for project management and code management at the same time, no continuous integration scheme which is very compatible with the two operating systems is available, which causes great trouble to users.
Disclosure of Invention
The invention provides a multi-management system integration method and a computer readable storage medium, which are used for solving the problem that Buddhist channels and GitLab cannot be well integrated in the prior art.
In a first aspect, the present invention provides a method for integrating a management system, the management system including a Buddhist management system and GitLab management system, the method including: presetting a first interface, a second interface and a calling module, wherein the first interface is an interface for calling the Buddhist management system function, and the second interface module is an interface for calling the GitLab management system function; based on the current task to be executed, the calling module calls the Buddhist management system function through the first interface and calls the GitLab management system function through the second interface to complete the operation required by the current task to be executed, so that the Buddhist management system and the GitLab management system are continuously integrated.
Optionally, the method further comprises: all tasks are managed through a preset code branch management specification.
Optionally, the code branch management specification is to perform corresponding naming management on the codes of the tasks according to the trunks, functions and repairs of the codes, and set corresponding trigger links one by one.
Optionally, the calling module calls the Buddhist canal management system function through the first interface and calls the GitLab management system function through the second interface, so as to complete the operation required by the task to be executed currently, including:
The calling module calls a triggering link of a corresponding functional branch or a repairing branch based on a current task to be executed, and configures the triggering link to the Buddhist management system or the GitLab management system, so that the triggering link calls the Buddhist management system function through the first interface and calls the GitLab management system function through the second interface to complete the operation required by the current task to be executed.
Optionally, the trigger links are obtained according to the use requirement of the task to be executed currently, and one or more trigger links are provided.
Optionally, the tasks include: downloading project codes to a compiling test environment, packaging and archiving the projects, smoking the projects, regression testing the projects, and synchronizing code information submitted to a GitLab management system to a Buddhist management system.
Optionally, the calling module is set up based on Jenkins.
Optionally, the first interface and the second interface are both created through a Groovy scripting language, and the first interface is disposed on the Buddhist management system, and the second interface is disposed on the GitLab management system.
Optionally, the calling module calls the Buddhist canal management system function through the first interface and the GitLab management system function through the second interface, and after completing the operation required by the task to be currently executed, the method further includes:
and carrying out subsequent processing operation according to the execution result and the current task to be executed through the calling module.
In a second aspect, the present invention provides a computer readable storage medium storing a computer program for signal mapping, which when executed by at least one processor, implements any of the above-described methods of multi-management system integration.
The invention has the following beneficial effects:
The invention presets the first interface, the second interface and the calling module, then the calling module calls the Buddhist channel management system function through the first interface and calls the GitLab management system function through the second interface, and finally the operation required by the current task to be executed is completed, so that the continuous integration of the Buddhist channel management system and the GitLab management system is realized, the user can call the Buddhist channel and the GitLab at the same time, and the user experience is greatly improved.
The foregoing description is only an overview of the present invention, and is intended to be implemented in accordance with the teachings of the present invention in order that the same may be more clearly understood and to make the same and other objects, features and advantages of the present invention more readily apparent.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to designate like parts throughout the figures. In the drawings:
FIG. 1 is a schematic flow chart of a method for integrating a multi-management system according to a first embodiment of the present invention;
fig. 2 is a schematic diagram of functional modules of a Buddhist channel according to a first embodiment of the present invention;
FIG. 3 is a schematic diagram of functional modules of GitLab provided by the first embodiment of the present invention;
Fig. 4 is a schematic diagram of functional modules of Jenkins according to the first embodiment of the present invention.
Detailed Description
Aiming at the problem that integration of Buddhist channels and GitLab cannot be really realized in the prior art, the embodiment of the invention respectively creates an interface for the Jenkins to call on the Buddhist channels and GitLab by using a Groovy script language, the Jenkins configures a triggering link carrying a corresponding Jenkins task to the Buddhist channels and GitLab by calling the interfaces, triggers the Buddhist channels and GitLab to execute operations corresponding to the Jenkins task and feeds back execution results to the Jenkins, and the Jenkins carries out other subsequent operations based on the Jenkins task and specific execution results, so that continuous integration of the Buddhist channels, gitLab and the Jenkins is realized, and different use requirements of users are met. The present invention will be described in further detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.
A first embodiment of the present invention provides a method for integrating a management system, referring to fig. 1, the management system including a Buddhist management system and GitLab management system, the method including:
S101, presetting a first interface, a second interface and a calling module, wherein the first interface is an interface for calling the Buddhist channel management system function, and the second interface module is an interface for calling the GitLab management system function;
The calling module of the embodiment of the invention is built based on Jenkins. In addition, in the embodiment of the present invention, the first interface and the second interface are both created through a Groovy scripting language, and the first interface is disposed on the Buddhist management system, and the second interface is disposed on the GitLab management system.
It is well known that Jenkins is an open-source and very popular continuous integration tool, and that there are also a large number and abundance of plug-ins that can be used in combination to implement a wide variety of automated processes.
It should be noted that, the continuous integration in the embodiment of the present invention is an idea of compiling and testing the software under development through short period and high frequency, so as to achieve fast feedback quality and improve development efficiency. The invention provides a continuous integration scheme of two tools, namely a complete and very compatible Buddhist channel and GitLab, through Jenkins.
S102, based on the current task to be executed, the calling module calls the Buddhist management system function through the first interface and calls the GitLab management system function through the second interface, and the operation required by the current task to be executed is completed, so that the Buddhist management system and the GitLab management system are continuously integrated.
That is, the embodiment of the invention combines the characteristics of Buddhist channels and GitLab, introduces Jenkins to provide a practical and complete continuous integration scheme, and practice proves that the method of the embodiment of the invention can be used for holding each link of continuous integration to be integrated into daily operations on Buddhist channels and GitLab without additionally doing some work to execute continuous integration flow.
In specific implementation, the embodiment of the invention manages all tasks through a preset code branch management specification, wherein the code branch management specification carries out corresponding naming management on the codes of the tasks according to the trunk, the functions and the restoration of the codes respectively, and sets corresponding trigger links one by one.
That is, in the embodiment of the present invention, all tasks are classified, and corresponding trigger links are set for each task, so that the calling module can call the functions on Buddha channels or GitLab according to the trigger links corresponding to the specific task. That is, in the embodiment of the present invention, the trigger links are obtained according to the use requirement of the task to be executed currently, and according to the requirement of different tasks, one or more trigger links are provided.
Specifically, the calling module in the embodiment of the present invention calls the trigger link of the corresponding functional branch or repair branch based on the current task to be executed, and configures the trigger link to the Buddhist management system or GitLab management system, so that the trigger link calls the Buddhist management system function through the first interface and calls the GitLab management system function through the second interface, thereby completing the operation required by the current task to be executed.
In specific implementation, the tasks in the embodiment of the invention include: downloading project codes to a compiling test environment, packaging and archiving the projects, smoking the projects, regression testing the projects, and synchronizing code information submitted to a GitLab management system to a Buddhist management system.
For example, the smoke test is automatically triggered when the merge request is created at GtiLab, the code information is automatically synchronized to the Buddhist canal when the merge request is received at GitLab, the packing task is automatically triggered when the version is created on the Buddhist canal, the regression test is automatically triggered when the test ticket is created on the Buddhist canal, and the like, and the specific person skilled in the art can perform any setting according to actual needs, so that the invention does not enumerate one by one here.
Namely, in the embodiment of the invention, the Jenkins task is managed through a preset code branch management specification, the code branch management specification is used for carrying out corresponding naming management on the code of the Jenkins task according to the trunk, the function and the restoration of the code respectively, the corresponding function branch or the restoration branch is called based on specific use requirements, and then the calling module is used for triggering the trigger link of the called branch to be configured into the Buddhist channel and GitLab through the first functional module and the second functional module, so that the Buddhist channel and GitLab can execute corresponding operation based on the received trigger, thereby realizing continuous integration of the Buddhist channel, gitLab and Jenkins and meeting different use requirements of users.
In a specific implementation, the calling module of the embodiment of the present invention calls the Buddhist channel management system function through the first interface and calls the GitLab management system function through the second interface, and after completing the operation required by the task to be executed currently, the method further includes: and carrying out subsequent processing operation according to the execution result and the current task to be executed through the calling module.
That is, the invention aims at carrying out overall control on the task through the calling module and improving the user experience by completing the task as the final purpose.
According to the embodiment of the invention, tasks of all links of the continuous integration are held by means of webhook automatic triggering and are integrated into daily Buddhist channels and GitLab and operation types, so that related operators can access the continuous integration flow without knowing and operating extra work, and user experience is greatly improved.
The method according to the invention will be explained and illustrated in detail below by means of a specific example in connection with fig. 2-4:
Step 1: the embodiment of the invention uses a Groovy script language (which can run in Jenkins) to realize a functional module ZenTao.groovy capable of calling a Buddhist channel interface to operate the Buddhist channel, and the functional module ZenTao.groovy comprises a plurality of functional functions shown in figure 2;
Step 2: a functional module gitlab. Groovy, which can invoke GitLab interface operations GitLab, is implemented using the Groovy scripting language (which can run in Jenkins), containing several functional functions as shown in fig. 3;
Step 3: a Jenkins task is created that contains a script (Jenkinsfile) of the task, including several functions as shown in fig. 4.
Step 4: formulating a code branch management specification:
The method is divided into three branch types of a trunk (master/develop), a function (feature) and a repair (fix);
the trunk name is fixed;
one functional branch corresponds to one requirement on the Buddhist canal, and the naming format is feature-STORYID, STORYID which is the ID of the requirement on the Buddhist canal, such as feature-1584;
One repair branch corresponds to one bug on the Buddhist canal, and the named format is fix-BUGID, and BUGID is the ID of the bug on the Buddhist canal, such as fix-998;
Step 5: trigger links for Jenkins tasks are configured to webhook of Buddhist and GitLab, and events configuring Buddhist triggers webhook are "create version" and "create test order", and events configuring GitLab triggers webhook are "create merge request" and "accept merge request". The tasks triggered by each event are as follows:
creating a merge request on GtiLab: triggering Jenkins to carry out smoking test on the source branch of the merging request;
GitLab accept the merge request: triggering Jenkins to fill the combination request information into corresponding requirements or bugs on the Buddhist channel;
creating versions on Buddhist channels: triggering Jenkins to execute a packing task and backfilling a packing download address to Buddhist channel version details;
creating a test sheet on the Buddhist channel: triggering Jenkins to execute a regression test and backfilling the test result on the Buddhist channel test sheet;
that is, in the embodiment of the present invention, a Groovy scripting language is used to create an interface on the Buddha channel and GitLab for Jenkins to call, jenkins configures the triggering link carrying the corresponding Jenkins task to the Buddha channel and GitLab by calling the interface, triggers the Buddha channel and GitLab to execute the operation corresponding to the Jenkins task and feed back the execution result to the Jenkins, and the Jenkins performs other subsequent operations based on the Jenkins task and the specific execution result, so as to realize continuous integration of the Buddha channel, gitLab and Jenkins, and satisfy different use requirements of users.
Therefore, the embodiment of the invention repeatedly combines the characteristics of Buddhist channels and GitLab on the whole, realizes a complete set of continuous integration scheme, and integrates the triggering action into the daily related operations of Buddhist channels and GitLab, thereby reducing the difficulty of continuous integration of project access and improving the convenience.
A second embodiment of the present invention provides a computer-readable storage medium storing a computer program of signal mapping, which when executed by at least one processor, implements the multi-management system integration method according to any one of the first embodiments of the present invention.
The relevant content of the embodiments of the present invention can be understood with reference to the first embodiment of the present invention, and will not be discussed in detail herein.
Although the preferred embodiments of the present invention have been disclosed for illustrative purposes, those skilled in the art will appreciate that various modifications, additions and substitutions are possible, and accordingly the scope of the invention is not limited to the embodiments described above.
Claims (8)
1. A method of integrating a plurality of management systems, wherein the management systems include a Buddhist management system and GitLab management system, the method comprising:
presetting a first interface, a second interface and a calling module, wherein the first interface is an interface for calling the Buddhist management system function, and the second interface module is an interface for calling the GitLab management system function;
Based on the current task to be executed, the calling module calls the Buddhist management system function through the first interface and calls the GitLab management system function through the second interface to complete the operation required by the current task to be executed so as to enable the Buddhist management system and the GitLab management system to be continuously integrated;
Wherein the method further comprises:
all tasks are managed through a preset code branch management specification;
The code branch management specifications are used for carrying out corresponding naming management on the codes of the tasks according to the trunks, functions and restoration of the codes respectively, and setting corresponding trigger links one by one.
2. The method according to claim 1, wherein the calling module calls the Buddhist management system function through the first interface and the GitLab management system function through the second interface, completing the operations required by the currently to-be-performed task, comprising:
The calling module calls a triggering link of a corresponding functional branch or a repairing branch based on a current task to be executed, and configures the triggering link to the Buddhist management system or the GitLab management system, so that the triggering link calls the Buddhist management system function through the first interface and calls the GitLab management system function through the second interface to complete the operation required by the current task to be executed.
3. The method of claim 1, wherein the step of determining the position of the substrate comprises,
The trigger links are obtained according to the use requirement of the task to be executed currently, and one or more trigger links are provided.
4. The method of claim 1, wherein the step of determining the position of the substrate comprises,
The tasks include: downloading project codes to a compiling test environment, packaging and archiving the projects, smoking the projects, regression testing the projects, and synchronizing code information submitted to a GitLab management system to a Buddhist management system.
5. The method according to any one of claims 1 to 4, wherein,
The calling module is built based on Jenkins.
6. The method according to any one of claims 1 to 4, wherein,
The first interface and the second interface are both created through a Groovy scripting language, the first interface is arranged on the Buddhist channel management system, and the second interface is arranged on the GitLab management system.
7. The method according to any one of claims 1 to 4, wherein the calling module calls the Buddhist management system function through the first interface and the GitLab management system function through the second interface, and after completing the operation required by the task currently to be performed, the method further comprises:
and carrying out subsequent processing operation according to the execution result and the current task to be executed through the calling module.
8. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program of signal mapping, which computer program, when being executed by at least one processor, implements the multi-management system integration method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110881164.XA CN113590485B (en) | 2021-08-02 | 2021-08-02 | Multi-management system integration method and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110881164.XA CN113590485B (en) | 2021-08-02 | 2021-08-02 | Multi-management system integration method and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113590485A CN113590485A (en) | 2021-11-02 |
| CN113590485B true CN113590485B (en) | 2024-06-25 |
Family
ID=78253738
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110881164.XA Active CN113590485B (en) | 2021-08-02 | 2021-08-02 | Multi-management system integration method and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113590485B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116843308A (en) * | 2023-07-05 | 2023-10-03 | 舟谱数据技术南京有限公司 | Automatic card punching method, device, equipment and system |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109542769A (en) * | 2018-10-25 | 2019-03-29 | 武汉精立电子技术有限公司 | A kind of automated testing method of continuous integrating |
| CN109583839A (en) * | 2018-12-03 | 2019-04-05 | 广东鸭梨科技集团股份有限公司 | A kind of research and development management system and method based on DevOps |
| CN109597751A (en) * | 2018-10-16 | 2019-04-09 | 成都颠峰科创信息技术有限公司 | A method of Bug is submitted automatically based on integrated test tools |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109558147A (en) * | 2018-11-29 | 2019-04-02 | 上海新炬网络技术有限公司 | A kind of continuous integrating platform construction method based on Jenkins and Gitlab |
| CN109766269A (en) * | 2018-12-18 | 2019-05-17 | 微梦创科网络科技（中国）有限公司 | Continuous integrating automated testing method, device, equipment and medium |
| CN111078274B (en) * | 2019-12-09 | 2023-05-16 | 北京五八信息技术有限公司 | Code development method, device, electronic equipment and computer storage medium |
| CA3102809A1 (en) * | 2019-12-16 | 2021-06-16 | Bce Inc. | System and method for managing data object creation |
| CN112527382B (en) * | 2020-12-14 | 2023-12-12 | 携程旅游网络技术（上海）有限公司 | Method for deploying pipeline engine system, and method and device for continuous integration |
-
2021
- 2021-08-02 CN CN202110881164.XA patent/CN113590485B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109597751A (en) * | 2018-10-16 | 2019-04-09 | 成都颠峰科创信息技术有限公司 | A method of Bug is submitted automatically based on integrated test tools |
| CN109542769A (en) * | 2018-10-25 | 2019-03-29 | 武汉精立电子技术有限公司 | A kind of automated testing method of continuous integrating |
| CN109583839A (en) * | 2018-12-03 | 2019-04-05 | 广东鸭梨科技集团股份有限公司 | A kind of research and development management system and method based on DevOps |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113590485A (en) | 2021-11-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101311903B (en) | Method and device for reusing component of software system based on component | |
| US20050044531A1 (en) | Methods and systems for deploying computer source code | |
| CN110543328B (en) | Cross-platform component management method, system, terminal and storage medium based on Ambari | |
| CN112882700A (en) | iOS application program construction method and device, electronic equipment and storage medium | |
| CN104615462B (en) | Cross-platform Mobile solution generation service end and system | |
| CN114064213B (en) | Quick arranging service method and system based on Kubernets container environment | |
| CN105468427A (en) | Implementation method and system of automatic compilation and release | |
| CN113590485B (en) | Multi-management system integration method and computer readable storage medium | |
| US20090249312A1 (en) | Process Generation Approach and System for an Integrated Telecom Platform | |
| CN107301041A (en) | A kind of method and system of custom-built system function | |
| CN103984769A (en) | Use-case data management and storage method | |
| CN116149747A (en) | Interface arrangement method, device, electronic equipment and computer readable storage medium | |
| CN102622550A (en) | Safe online patch check system facing terminal computers | |
| CN102117219A (en) | Method for generating clients, system and terminal equipment | |
| CN102609357A (en) | Method for dynamically building test cases for automatic testing meeting AUTOSAR (automotive open system architecture) standards | |
| CN109634734A (en) | Automatic compiling dissemination method, device and computer readable storage medium | |
| CN115185489B (en) | Time sequence data algorithm configuration system and method | |
| CN111580853A (en) | Universal generation method for multi-channel software installation package | |
| KR20210039714A (en) | Method and apparatus for constructing test environment | |
| CN116302380A (en) | Resource calling method and system based on experimental resource comprehensive integration | |
| CN112579470B (en) | Compiling and linking method and system for debugging dynamic software library | |
| CN114003486A (en) | Plug-in debugging method, client, server and storage medium | |
| CN114564385A (en) | Software testing method and device, computer equipment and storage medium | |
| CN104123168A (en) | Application upgrading method and device | |
| CN112650669A (en) | Automatic appium testing method based on block chain |
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 |