A method for managing the quality of publication based on multi-platform interaction

Abstract

The application discloses an IT system development technical field and discloses a release quality management method based on multi-platform interaction, which comprises the following steps: S1: Jira webhook sends BBFB work order "creation / update message" to CICD platform, obtains various data in application research and development test process, and automatically fills or completes work order fields; S2: CICD platform verifies application release check items; S3: a release plan is created through the CICD platform, when the release check items fail in one place, the "release plan input" is in a gray state and cannot be clicked, the CICD automatically marks that the release work order check item fails, the system will automatically intercept, the button is in a gray state, at this time, the release work order personnel corrects and releases again; S4: on the basis of supporting manual creation of a release plan, when all release check items pass, the CICD platform calls a YOPS platform interface to generate a release plan, compile a basic package, inject a configuration, and release successfully, so that risks can be effectively avoided, and work efficiency is improved.

Description

Technical Field

[0001] This invention relates to the field of IT system development technology, specifically to a release quality management method based on multi-platform interaction. Background Technology

[0002] During routine system deployments, it's crucial to ensure deployment quality and stability. The traditional deployment method involved manual review and deployment. However, manual review is prone to omissions or misjudgments, leading to unnecessary malfunctions and causing numerous drawbacks to the workflow.

[0003] Based on this, the present invention designs a release quality management method based on multi-platform interaction to solve the above problems. Summary of the Invention

[0004] The purpose of this invention is to provide a release quality management method based on multi-platform interaction to solve the problems mentioned in the background art.

[0005] To achieve the above objectives, the present invention provides the following technical solution: a release quality management method based on multi-platform interaction, comprising the following steps:

[0006] S1: Jira webhook sends BBFB ticket "creation / update message" to the CICD platform to obtain various data in the application development and testing process, and automatically fills or completes the ticket fields;

[0007] S2: CICD platform verification of application release checks;

[0008] S3: The release plan is created through the CICD platform. When any release check item fails, the "Enter Release Plan" button will be grayed out and cannot be clicked. CICD will automatically mark this release work order as failing the check item, and the system will automatically block it. The button will then be grayed out. At this time, the person releasing the work order will correct the error and re-release it.

[0009] S4: With support for manually creating release plans, and all release checks passing, the CICD platform calls the YOPS platform interface to generate a release plan, compile the base package, inject configuration, and release successfully.

[0010] Preferably, in S2, the release check items include BBFB work order approval status, requirement work order completion status, configuration work order completion status, quality inspection results, test completion status, release permissions, and release time.

[0011] Preferably, in S2, the action is initiated by receiving a Jira webhook message or by manually clicking.

[0012] Preferably, in S3, after all publications have been approved, the button displays a green status, and after successful publication, the "Enter Publication Plan" button displays a gray status.

[0013] Preferably, in S1, the real-time nature of work order data in the CICD platform is maintained through Jira webhook.

[0014] Preferably, S2 includes a function that automatically performs release verification when a work order is updated, in addition to supporting manual release verification.

[0015] Preferably, the CICD platform verification in S2 adopts a queue form, that is, only the latest work order data is published and verified within 5 seconds.

[0016] Preferably, the data in S1 includes the release version, release time, release window, and release permissions.

[0017] Compared with the prior art, the beneficial effects of the present invention are:

[0018] Jira webhook sends a BBFB ticket "Create / Update Message" to the CICD platform. The CICD platform verifies the application's release checklist (by receiving the Jira webhook message or clicking manually), including BBFB ticket approval status, requirement ticket completion status, configuration ticket completion status, quality inspection results, test completion status, release permissions, and release time. If all release checklists pass, the CICD platform calls the YOPS platform interface to generate a release plan, compile the base package, inject configuration, and release successfully. This effectively mitigates risks and improves work efficiency. The release plan is created through the CICD platform. If any release checklist fails, CICD automatically marks that release ticket checklist as failed, and the system will automatically block it, with the button turning gray. At this point, the release ticket personnel correct the error and re-release.

[0019] Of course, any product implementing this invention does not necessarily need to achieve all of the advantages described above at the same time. Attached Figure Description

[0020] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 This is a schematic diagram of the overall structure of the present invention;

[0022] Figure 2This is an interface diagram of the modification and amendment application for this invention;

[0023] Figure 3 This is an interface diagram for viewing inspection items according to the present invention;

[0024] Figure 4 This is an interface diagram of the input and release plan for this invention;

[0025] Figure 5 This is an overview diagram of the release status of the present invention;

[0026] Figure 6 This is an overview diagram of the release status results of the present invention. Detailed Implementation

[0027] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0028] Example 1

[0029] Please see Figures 1 to 6 This invention provides a technical solution for a release quality management method based on multi-platform interaction: a release quality management method based on multi-platform interaction, comprising the following steps:

[0030] S1: Jira webhook sends BBFB ticket "Creation / Update Message" to the CICD platform. By easily creating tickets, it obtains various data in the application development and testing process, such as release version, release time, release window, release permissions, etc., and automatically fills or completes the ticket fields, improving the efficiency and accuracy of creating release tickets.

[0031] S2: CICD platform verification of application release check items, received from Jira webhook messages or manually clicked, including BBFB work order approval status, requirement work order completion status, configuration work order completion status, quality inspection results, test completion status, release permissions, and release time. Jira webhook is used to maintain the real-time status of work order data in the CICD platform, avoiding the need for the CICD platform to call the Jira interface to obtain work order data for each release verification, which can reduce the pressure on Jira.

[0032] S3: Release plans are created through the CICD platform. In addition to supporting manual release verification, it automatically performs release verification when work orders are updated, reducing manual costs and increasing the timeliness of release verification. Figure 4As shown, when any check item fails, the "Enter Release Plan" button will be grayed out and unclickable. The CICD will automatically mark this release order as failing, and the system will automatically block it, with the button remaining grayed out. At this point, the person releasing the work order must correct the error and re-release it. Figure 5 As shown, once all checks are completed, the button will display a green status, indicating a successful release. Therefore, the "Enter Release Plan" button will be grayed out. To avoid frequent updates to work orders within a short period and the need for multiple release verifications, a queuing system is used. This means that only the most recent work order data is verified for release within 5 seconds, reducing the pressure on the Jira and CICD platforms.

[0033] S4: If all release checks pass, the CICD platform calls the YOPS platform interface to generate a release plan, compile the base package, inject configuration, and the release is successful. Figure 6 As shown in the overview diagram, it presents which items were successfully published and which were not.

[0034] One specific application of this embodiment is as follows: Jira webhook sends a BBFB ticket "Create / Update Message" to the CICD platform; the CICD platform verifies the application's release check items (by receiving the Jira webhook message or clicking manually), including BBFB ticket approval status, requirement ticket completion status, configuration ticket completion status, quality inspection results, test completion status, release permissions, release time, etc.; if all release check items pass, the CICD platform calls the YOPS platform interface to generate a release plan, compile the basic package, inject configuration, and release successfully.

[0035] The existing technology effectively mitigates risks and improves work efficiency. The release plan is created through the CICD platform. When any release check item fails, CICD automatically marks the release work order as failing, and the system will automatically block it, with the button turning gray. At this point, the person releasing the work order can correct the error and re-release it.

[0036] In the description of this specification, references to terms such as "an embodiment," "example," "specific example," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the invention. In this specification, illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0037] The preferred embodiments of the present invention disclosed above are merely illustrative of the invention. These preferred embodiments do not exhaustively describe all details, nor do they limit the invention to the specific implementations described. Clearly, many modifications and variations can be made based on the content of this specification. This specification selects and specifically describes these embodiments to better explain the principles and practical applications of the invention, thereby enabling those skilled in the art to better understand and utilize the invention. The invention is limited only by the claims and their full scope and equivalents.

Claims

1. A release quality management method based on multi-platform interaction, characterized in that, Includes the following steps: S1: Jirawebhook sends a BBFB ticket "Create / Update Message" to the CICD platform, retrieves various data from the application development and testing process, and automatically fills in or completes the ticket fields; S2: The CICD platform verifies the application release checklist; S3: The release plan is created through the CICD platform. When any release checklist fails, the "Enter Release Plan" button is grayed out and cannot be clicked. CICD automatically marks this release ticket checklist as failed, and the system will automatically block it. At this point, the release ticket personnel correct the issue and re-release; S4: Based on the support for manually creating release plans... Based on this, if all release checks pass, the CICD platform calls the YOPS platform interface to generate a release plan, compiles and injects the basic package configuration, and finally completes the release successfully. The release checks in S2 include BBFB work order approval status, requirement work order completion status, configuration work order completion status, quality inspection results, test completion status, release permissions, and release time. In S3, after all releases pass, the button displays a green status; after a successful release, the "Enter Release Plan" button displays a gray status. The data in S1 includes the release version, release time, release window, and release permissions.

2. The release quality management method based on multi-platform interaction according to claim 1, characterized in that: The CICD platform verification application release check item in S2 is triggered by receiving a Jira webhook message or by manually clicking.

3. The release quality management method based on multi-platform interaction according to claim 1, characterized in that: In S1, the real-time nature of work order data in the CICD platform is maintained through Jira webhook.

4. The release quality management method based on multi-platform interaction according to claim 1, characterized in that: The S2 has the function of automatically performing release verification when the work order is updated, in addition to supporting manual release verification.

5. The release quality management method based on multi-platform interaction according to claim 1, characterized in that: The CICD platform verification in S2 adopts a queue format, meaning that only the latest work order data is published and verified within 5 seconds.

Images