Service release management method, system, equipment and medium

Abstract

The invention discloses a service release management method, system and device and a medium. The method comprises the following steps: responding to a change instruction of a target service; a target interface needing to be changed is obtained from the change instruction, and the target interface is linked with a target service; determining the interface state of the target interface according to the release state of the target service; determining a target change level of the target service; and according to the change instruction and the target change level, the interface state of the target interface is adjusted, so that the service release efficiency and stability can be improved, the release failure or service interruption risk caused by improper change is further remarkably reduced, and powerful support is provided for continuous integration and continuous delivery of software development.

Description

Technical Field

[0001] This application relates to the technical field of software development, and in particular, to a management method, system, device and medium for service release. Background Art

[0002] In a software development environment, the pace of project maintenance and iteration is accelerating continuously. A software or project requires multiple developers from different departments to collaborate and jointly promote the continuous development of the same project or service. During this process, the project involves various configuration and middleware operation changes. These change interfaces are numerous and complex and need to be coordinated and managed. Moreover, when a developer makes a configuration change without notifying other team members, it will seriously interfere with the upcoming software release process, resulting in release failure and even posing a major threat to the stable operation of the service.

[0003] In the prior art, in order to achieve a smooth software release, developers are usually notified comprehensively to prohibit software changes. When a change is required, it is necessary to respond to each unit to confirm whether to suspend the release before a coordinated change can occur. The change efficiency is low and it is difficult to control other unstable factors during the change process, which may lead to risks of release failure or service interruption caused by improper configuration changes. Summary of the Invention

[0004] The following is an overview of the subject matter described in detail in this document. This overview is not intended to limit the scope of protection of the claims.

[0005] The main purpose of the embodiments of the present disclosure is to provide a management method, system, device and storage medium for service release, which can manage service release and realize changes according to service management development interfaces.

[0006] The first aspect of the embodiments of this application provides a management method for service release, which is used for a central controller. The method includes:

[0007] Respond to a change instruction for a target service;

[0008] Obtain a target interface that needs to be changed from the change instruction, and the target interface is linked to the target service;

[0009] Determine the interface status of the target interface according to the release status of the target service;

[0010] Determine the target change level of the target service;

[0011] Adjust the interface status of the target interface according to the change instruction and the target change level.

[0012] An embodiment of the present application provides a management method for service release. By responding to a change instruction of a target service; obtaining a target interface to be changed from the change instruction, where the target interface is linked to the target service; determining the interface status of the target interface according to the release status of the target service; determining the target change level of the target service; and adjusting the interface status of the target interface according to the change instruction and the target change level, it can improve the efficiency and stability of service release, and also significantly reduce the risk of release failure or service interruption caused by improper changes, providing strong support for continuous integration and continuous delivery of software development.

[0013] In some embodiments of the present application, the determining the target change level of the target service includes:

[0014] Determining the target change level of the target service from preset change level information, where the change level information includes the correspondence between services and change levels.

[0015] In some embodiments of the present application, the adjusting the interface status of the target interface according to the change instruction and the target change level includes:

[0016] When the target change level is less than or equal to a level threshold, adjusting the interface status of the target interface to a first preset status according to the change instruction.

[0017] In some embodiments of the present application, the adjusting the interface status of the target interface according to the change instruction and the target change level further includes:

[0018] When the target change level is greater than the level threshold, adjusting the interface status of the target interface to a second preset status according to the change instruction.

[0019] In some embodiments of the present application, after adjusting the interface status of the target interface to the second preset status according to the change instruction, the method further includes:

[0020] Responding to a re-change instruction;

[0021] Evaluating the re-change instruction to obtain an evaluation result of the re-change instruction;

[0022] Controlling a service change interface corresponding to the re-change instruction according to the evaluation result.

[0023] In some embodiments of the present application, after adjusting the interface status of the target interface according to the change instruction and the target change level, the method further includes:

[0024] Responding to a change end instruction;

[0025] From the change completion instruction, obtain the service change interface corresponding to the change completion instruction to adjust the interface status of the service change interface corresponding to the change completion instruction.

[0026] To achieve the above object, a second aspect of the embodiments of the present invention provides a service release management system, the system includes:

[0027] A response module, configured to respond to a change instruction of a target service;

[0028] An acquisition module, configured to obtain a target interface to be changed from the change instruction, and the target interface is linked to the target service;

[0029] A matching module, configured to determine the interface status of the target interface according to the release status of the target service;

[0030] A confirmation module, configured to determine the target change level of the target service;

[0031] An adjustment module, configured to adjust the interface status of the target interface according to the change instruction and the target change level.

[0032] To achieve the above object, a third aspect of the embodiments of the present invention provides an electronic device, including: at least one control processor and a memory for communicating with the at least one control processor; the memory stores instructions executable by the at least one control processor, and the instructions are executed by the at least one control processor so that the at least one control processor can execute the above-mentioned service release management method.

[0033] To achieve the above object, a fourth aspect of the embodiments of the present invention provides a computer-readable storage medium, the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to make a computer execute the above-mentioned service release management method.

[0034] To achieve the above object, a fifth aspect of the embodiments of the present invention provides a computer program product. When the instructions in the computer program product are executed by a processor of an electronic device, the electronic device executes the above-mentioned service release management method.

[0035] It can be understood that the beneficial effects of the above second aspect to fifth aspect compared with the related art are the same as those of the above first aspect compared with the related art. For the relevant descriptions, please refer to the relevant descriptions in the above first aspect and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] The above and / or additional aspects and advantages of the present application will become apparent and be readily understood from the description of the embodiments in conjunction with the following drawings, where:

[0037] Figure 1 is a schematic flowchart of a service release management method provided by an embodiment of the present application;

[0038] Figure 2 is an execution schematic diagram provided by an embodiment of the present application;

[0039] Figure 3 is a schematic structural diagram of a service release management training system provided by an embodiment of the present application;

[0040] Figure 4 is a schematic hardware structure diagram of an electronic device provided by an embodiment of the present application. Detailed Embodiments

[0041] The embodiments of the present application will be described in detail below. The examples of the embodiments are shown in the drawings, where the same or similar reference numerals denote the same or similar elements or elements with the same or similar functions throughout. The embodiments described below with reference to the drawings are exemplary and are only used to explain the present application, and should not be construed as a limitation of the present application.

[0042] In the description of the present application, if the first, second, etc. are described only for the purpose of distinguishing technical features, they should not be construed as indicating or implying relative importance or implicitly indicating the quantity of the indicated technical features or the sequence of the indicated technical features.

[0043] In the description of the present application, it should be understood that the orientation descriptions such as up, down, etc. indicate the orientation or positional relationship based on the orientation or positional relationship shown in the drawings, and are only for the convenience of describing the present application and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of the present application.

[0044] In the description of the present application, it should be noted that unless otherwise clearly defined, words such as setting, installation, connection, etc. should be understood in a broad sense, and those skilled in the art can reasonably determine the specific meanings of the above words in the present application in combination with the specific content of the technical solution.

[0045] First, several terms involved in the present application are analyzed:

[0046] Service release (software release): refers to the process of transitioning software from the development stage to the production environment for users to use or test.

[0047] In the software development environment, the pace of project maintenance and iteration is accelerating continuously. A software or project requires multiple developers from different departments to collaborate and jointly promote the continuous development of the same project or service. During this process, the project involves various configuration and middleware operation changes. These change interfaces are extremely complex and require coordination and management. Moreover, when a developer makes unauthorized configuration changes without notifying other team members, it seriously interferes with the upcoming software release process, resulting in release failures and even posing a major threat to the stable operation of the service.

[0048] In the prior art, software developers are usually fully notified to prohibit software changes to achieve a smooth software release. When changes are required, it is necessary to respond to each unit to confirm whether to suspend the release before making coordinated changes. The change efficiency is low and it is difficult to control other unstable factors during the change process, thus leading to the risk of release failures or service interruptions caused by improper configuration changes.

[0049] Based on this, the embodiments of the present application provide a service release management method, system, electronic device, and medium, aiming to manage service releases and achieve changes according to service management development interfaces.

[0050] The service release management method, system, electronic device, and medium provided by the embodiments of the present application are specifically described through the following embodiments. First, the service release management method in the embodiments of the present application is described.

[0051] The embodiments of the present application can acquire and process relevant data based on artificial intelligence technology. Among them, artificial intelligence (AI) is the theory, method, technology, and application system that uses digital computers or machines controlled by digital computers to simulate, extend, and expand human intelligence, perceive the environment, acquire knowledge, and use knowledge to obtain the best results.

[0052] Artificial intelligence basic technologies generally include technologies such as sensors, dedicated artificial intelligence chips, cloud computing, distributed storage, big data processing technology, operation / interaction systems, and mechatronics. Artificial intelligence software technologies mainly include several major directions such as computer vision technology, robotics, biometric technology, speech processing technology, natural language processing technology, and machine learning / deep learning.

[0053] The service release management method provided by the embodiments of the present application relates to the technical field of software development. The service release management method provided by the embodiments of the present application can be applied to a terminal, or to a server side, or can be software running on a terminal or a server side. In some embodiments, the terminal can be a smart phone, a tablet computer, a notebook computer, a desktop computer, etc.; the server side can be configured as an independent physical server, or can be configured as a server cluster or a distributed system composed of multiple physical servers, or can also be configured as a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms; the software can be an application that implements the service release management method, etc., but is not limited to the above forms.

[0054] The present application can be used in many general-purpose or special-purpose computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet-type devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronic devices, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, and so on. The present application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application can also be practiced in a distributed computing environment, where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media including storage devices.

[0055] It should be noted that in each specific embodiment of the present application, when it comes to relevant processing that needs to be based on data related to the user's identity or characteristics, such as user information, user behavior data, user historical data, and user location information, the user's permission or consent will be obtained first. Moreover, the collection, use, and processing of these data will comply with relevant laws, regulations, and standards. In addition, when the embodiments of the present application need to obtain the user's sensitive personal information, the user's separate permission or separate consent will be obtained through methods such as pop-up windows or jumping to a confirmation page. After clearly obtaining the user's separate permission or separate consent, the necessary user-related data for the normal operation of the embodiments of the present application will be obtained.

[0056] For this reason, with reference to Figure 1, embodiments of the present application provide a management method for service publishing. This method is applied to a central controller. The controller can be a server, an electronic device, a mobile terminal, etc., which is not specifically limited here. The method includes the following steps S110 to S140.

[0057] Step S110: Respond to the change instruction of the target service.

[0058] In this step, the change instruction includes a formal instruction for changing the target service, preferably including functions related to services such as update, addition, or removal. The target service refers to the service that needs to be published currently formed through service orchestration. In managing the target service, the service to be published is marked with its current status through a status identifier, which helps developers or managers understand the current situation of the system, and then facilitates developers or other change requirements to be updated through the change module interface, aiming to optimize the software publishing process and ensure its stability.

[0059] Specifically, in a microservices architecture, service orchestration refers to the process of combining multiple microservices according to service requirements to form a complete business process or service. The change module interface refers to a functional module or interface that can submit software or service change requests.

[0060] Furthermore, immediately after the service publishing process, a clear status identifier is given to the service that is about to be published currently. This identifier clearly defines the publishing stage where the service is currently located.

[0061] Among them, the status identifier of the service is preferably "being published", "waiting", or "not published", indicating the running status of the service in the process of the publishing system. For example, when the publishing is submitted, the running status of the service is marked as "being published", when the stuck point status of the publishing process is obtained, the running status of the service is marked as "waiting", and when the end status is obtained after the publishing process ends, the running status of the service is marked as "not published". Thus, by immediately giving the status identifier to the current service after the publishing process is submitted and locking all relevant change module interfaces, it effectively avoids publishing failures or service interruptions caused by improper changes during the publishing process, and then significantly enhances the stability of the software publishing process.

[0062] Specifically, the three states of "under release", "waiting", and "not under release" are specifically used for changes. These states exist in the release system. Among them, "waiting" is just a standby state. Some service changes need to use this state when the service release is paused. This state corresponds to the blocking state in the release system, which is equivalent to the state when the release is blocked and paused midway. Changes that do not involve the "waiting" change during the change are defaulted to locked, and the "waiting" state will only be called in specific scenarios. Therefore, if the blocking state "waiting" does not appear in the service release process, the state of "waiting" does not exist.

[0063] Step S120: Obtain the target interface to be changed from the change instruction. The target interface is linked to the target service.

[0064] In this step, to obtain the target interface to be changed from the change instruction, it is necessary to clarify the change requested in the change instruction from the change instruction, thereby understanding the specific requirements of the change, analyzing the change module related to the currently released service for the required change, and determining the target interface based on the determined change module.

[0065] Specifically, the service forms a complete business by linking multiple interfaces. The interfaces refer to various change module interfaces closely related to the service, including but not limited to the orchestration change submission interface of the target service, the change submission interface of the MSE configuration discovery center, the database change submission interface, and the middleware change submission interface, etc.

[0066] In some embodiments, after obtaining the target interface to be changed by the change instruction, the impact of the interface change on other related components and services can be evaluated, and then it can be confirmed whether it is necessary to adjust the data format, communication protocol, or security mechanism, so as to deploy the changed interface and service in a secure environment and conduct comprehensive tests, including unit tests, integration tests, end-to-end tests, etc., to ensure that the change works as expected.

[0067] Step S130: Determine the interface state of the target interface according to the release state of the target service.

[0068] In this step, under different release states of the target service, the interface states linked to the target service are all different. Therefore, it is necessary to determine the interface state of the target interface according to the release state of the target service.

[0069] Specifically, when the release status of the target service is "releasing", the interface status of the target interface is in a locked state. When the release status of the target service is "waiting" or "not releasing", the interface status of the target interface is the status set by the user when temporarily suspending the release, or when the release status of the target service is "not releasing", the interface status of the target interface is in an open state. Here, the locked state refers to a state where certain operations or functions are temporarily prohibited to prevent improper changes during the service release process, and the open state means that all types of change module interfaces closely related to the service are open and changes can be made.

[0070] Step S140: Determine the target change level of the target service.

[0071] In this step, from the preset change level information, determine the target change level of the target service. The change level information includes the correspondence between the service and the change level.

[0072] Specifically, pre-configure the change level information of the service. When the service is in different release states, determine its corresponding change level. Define the impact degree of different types of changes on the service through the change level information, and decide whether changes are allowed during the release process.

[0073] In some embodiments, the change level is preferably divided into different levels, and the level is set according to the impact of different change module interfaces on the service. For example, changes with a lower impact on the target service are set as level 1 (low impact), and changes with a greater impact on the service are set as level 2 (high impact).

[0074] Furthermore, find the correspondence between the target service and the target change level from the preset change level information, thereby determine the target change level of the target service, and then determine whether the target service changes by comparing the change instruction and the target change level.

[0075] Step S150: Adjust the interface status of the target interface according to the change instruction and the target change level.

[0076] In this step, determine whether the target service changes by comparing the change instruction and the target change level, and then manage the change requests during the service release process, reducing conflicts and errors caused by poor communication or information omission, and improving the efficiency and accuracy of team collaboration.

[0077] In some embodiments, if the change level is level 1 (low impact), adjust the interface status of the corresponding target interface, and then perform the change operation; if the change level is level 2 (high impact), lock the interface status of the target interface. If further changes are needed, the special change authorization process can be used to evaluate and decide whether to unlock the change.

[0078] In some embodiments, in step S140 of determining the target change level of the target service, the following steps are included:

[0079] Step S210: Determine the target change level of the target service from the preset change level information, where the change level information includes the correspondence between services and change levels.

[0080] In this step, by determining the correspondence between each service and its related change types, an appropriate change level is assigned to each change, thereby defining the change registration information for managing service changes and ensuring the security and controllability of the change process.

[0081] In some embodiments, the preset change level information includes predefined change levels. Each service has its specific functional modules and associated services, all of which may be objects of change. For example, in post-loan services, different types of changes may be involved, such as contract management configuration, MSE configuration discovery center, database structure, etc.

[0082] Specifically, the change levels are defined according to the management requirements during the service release process. In some embodiments, the change levels are defined as follows:

[0083] Level 1 (low impact / no impact): Refers to changes that have little impact on the service and will not significantly affect the release process or service quality, and can be allowed even during the release process.

[0084] Furthermore, for Level 1 changes, when the service status is not "releasing", the corresponding change interface can be directly unlocked to allow direct change operations; if it is during the release period but the change level is Level 1, unlocking can be considered under special circumstances.

[0085] Level 2 (high impact): Refers to changes that may have a greater impact on the service and may cause release failures or service interruptions. When there is a situation where a change must be made, strict control and approval processes are required.

[0086] Furthermore, for Level 2 changes, regardless of the service status, a detailed change process description is required, and the change can only be unlocked after authorization.

[0087] Furthermore, find the correspondence between the target service and specific change types from the change level information to determine the target change level of the target service.

[0088] In some embodiments, in step S150 of adjusting the interface status of the target interface according to the change instruction and the target change level, the following steps are included:

[0089] Step S310: When the target change level is less than or equal to the level threshold, adjust the interface state of the target interface to the first preset state according to the change instruction;

[0090] Step S320: When the target change level is greater than the level threshold, adjust the interface state of the target interface to the second preset state according to the change instruction.

[0091] In this step, by comparing the target change level of the target service with the level threshold, the interface state of the target interface that needs to be changed in the change instruction is adjusted.

[0092] Specifically, a level threshold is set as the judgment criterion. For example, the level threshold is set to level 1, indicating that all impact changes below the level threshold are allowed for change processing, while impact changes above the level threshold are not allowed for change. If special changes are required, a new change application and evaluation are needed to determine whether to change.

[0093] Furthermore, the target change level of the target service is compared with the set level threshold to adjust the interface state of the target interface.

[0094] In some embodiments, when the target change level is less than or equal to the level threshold, it indicates that the change in the current change instruction is a low-impact change. Therefore, the interface state of the target interface is adjusted to the first preset state according to the change instruction, where the first preset state is unlocked or change allowed.

[0095] Furthermore, when the target change level is greater than the level threshold, it indicates that the change in the current change instruction is a change with a greater impact. Therefore, the interface state of the target interface is adjusted to the second preset state according to the change instruction, where the second preset state is locked or waiting for approval.

[0096] In some embodiments, all change activities are recorded by logging the change log, including information such as the time of the change, the content, who initiated the change, and the result after the change. This ensures that the change process is both safe and efficient, while maintaining the stability of software release and service operation.

[0097] In some embodiments, in step S320 of adjusting the interface state of the target interface to the second preset state according to the change instruction, the following steps are included:

[0098] Step S410: Respond to the re-change instruction;

[0099] Step S420: Evaluate the re-change instruction to obtain the evaluation result of the re-change instruction;

[0100] Step S430: Control the service change interface corresponding to the re-change instruction according to the evaluation result.

[0101] In this step, when the interface status of the target interface is the second preset status (locked or waiting for approval), it indicates that the current change is not permitted. The change will be rejected and a rejection prompt will be output. After receiving the rejection prompt, the user can, through a specific change process description, elaborate on the consequences and impacts of this change on the release service, and then request a re - change.

[0102] Furthermore, in response to the user's re - change instruction, the re - change instruction can be evaluated through managers or other evaluation methods to obtain the evaluation result of the re - change instruction, so as to control the service change interface corresponding to the re - change instruction according to the evaluation result.

[0103] In some embodiments of this example, after receiving the rejection prompt, the user can, through a specific change process description, elaborate on the consequences and impacts of this change on the release service, and then request a re - change, which specifically includes: the user initiates a special change authorization process, submits a detailed change description to the release personnel or the evaluation model for evaluation, and only after obtaining the evaluation authorization will the relevant change module interface be unlocked to allow the change request to be processed.

[0104] Specifically, the evaluation process specifically includes evaluating the potential impacts of the change on aspects such as business processes, system stability, and security, checking whether there are other ongoing or planned changes that may conflict with this change, and reviewing whether the change will affect other relevant services or components.

[0105] Furthermore, when the evaluation result is to allow the change, the interface status of the target interface will be adjusted to the first preset status, that is, the change interface status of the target service will be adjusted to the first preset status of "unlocked" or "allow change", allowing the change to be directly carried out.

[0106] When the evaluation result is to reject, the interface status of the target interface will be adjusted to the third preset status. Among them, the third preset status is to remain locked, and a rejection notice will be sent to the change requester (user), and the reason for the rejection will be explained, so as to effectively manage and control the re - change instruction, ensure that each change can be fully evaluated, and be processed according to the established rules, thereby maintaining the stability and security of service release.

[0107] In some embodiments, after adjusting the interface status of the target interface according to the change instruction and the target change level in step S150, the following steps are included:

[0108] Step S310: Respond to the change end instruction;

[0109] Step S320: Obtain the service change interface corresponding to the change end instruction from the change end instruction, so as to adjust the interface status of the service change interface corresponding to the change end instruction.

[0110] In this step, when a change completion instruction is received, the service change interface corresponding to the change completion instruction is obtained from the change completion instruction, and then the interface status of the service change interface corresponding to the change completion instruction is adjusted.

[0111] In some embodiments of this, after the change is completed, the interface status of the service change interface corresponding to the change completion instruction is adjusted to a second preset status (locked or waiting for approval).

[0112] Furthermore, record the change, notify all relevant users of the change, and at the same time, specific change content can be set to notify managers or other users after the change according to user service management requirements.

[0113] In some embodiments, for various change module interfaces closely related to the service, including but not limited to the orchestration change submission interface of the current release service, the change submission interface of the MSE configuration discovery center, the database change submission interface, and the middleware change submission interface, etc., before submitting a change request through these interfaces, first call the release service module to obtain the current service status.

[0114] Specifically, if the service status shows "releasing", then the submission of all change requests is blocked to ensure the purity and consistency of the release process. However, in special cases, it can be determined whether to allow the change through evaluation, which provides flexibility for special changes in service management and ensures that necessary changes can be processed in a timely manner without affecting the overall progress of service release.

[0115] In some embodiments, the change management mechanism in the special change process specifically includes: first, identifying change requirements through internal or external factors (such as technological progress, changes in customer needs, regulatory updates, etc.), then evaluating the potential impact of the change on aspects such as business processes, systems, personnel, security, etc., and then clarifying the goals, scope, resource requirements, etc. of the change.

[0116] Furthermore, after determining that the change is allowed, implement the change step by step according to the change plan. Additionally, the effect after the change can be verified by executing the change.

[0117] In some embodiments, in the credit system, when user A needs to release a post-loan service, a release process will be initiated. At the same time, the release system will mark the service to be released currently (post-loan service) as the "releasing" status.

[0118] Specifically, for each service, there are different side-branch change operation interfaces or systems for various change operations. Before formally making a change, it is necessary to pre-configure the change level for each service.

[0119] Therefore, if user B needs to modify the contract content of "Contract Management Configuration" associated with the post-loan service being released, the release system will determine whether user B's modification will affect the current release based on the pre-configured change level of the post-loan service being released.

[0120] Specifically, if the change level is level 1 (low impact), when user B submits the change, the system will automatically unlock the corresponding change button or interface, allowing user B to directly perform the change operation.

[0121] On the other hand, if the change level is level 2 (high impact), user B needs to describe the specific change process in detail, explaining the consequences and impacts of this change on the release service. This description will be submitted to the release personnel for evaluation. After the release personnel evaluate and confirm, the system will decide whether to unlock or not unlock the "Contract Management Configuration" based on the evaluation results.

[0122] In this embodiment, the credit system includes systems such as the contract management system, the configuration center, and the gateway service. Among them, the post-loan service needs to call the parameters configured in these systems. When the post-loan service is being released, if a contract modification related to the post-loan service is submitted in the contract management system, and the contract modification has a change level of level 1 in the post-loan service and does not affect the release of the post-loan service, the change can be allowed.

[0123] Furthermore, after "Contract Management Configuration" receives the unlock instruction from the release system, user B can modify the contract content that needs to be changed, and after the modification is completed, select to save / submit (change end instruction).

[0124] When the system responds to user B's change end instruction, the corresponding change button or interface will be restored to the locked change state until the system release is completed. Among them, the contract management configuration is just one of the systems in the change system.

[0125] In some embodiments, considering that in certain special cases, it is indeed necessary to make necessary changes during the release process, the user can submit a re-change request. The re-change request needs to be explicitly confirmed and authorized by the release submitter before it can be unlocked and the change can be submitted.

[0126] Furthermore, after the change is completed, the system will automatically restore the locked state of the changed change interface to ensure the smooth progress of the subsequent release process. Among them, after the changer submits the change, it is considered that the change is completed. Each service-related change interface has a submit or save function, and only after submitting or saving is it considered that the change is completed by default.

[0127] Specifically, when a person making a change is prevented from discovering that someone is releasing a version during the preparation for the change, the current change can be evaluated to determine whether it will affect the current release. If it does not, a change request can be submitted with an explanation. The release personnel will then receive the information of the change request and evaluate again whether to grant permission based on the explanation submitted by the change personnel.

[0128] Furthermore, after the entire release process is completed, the status flag in the release module will automatically return to normal, indicating that the service has been successfully released and entered the stable operation stage. Through the management of the service, not only the controllability and stability of the software release process are improved, but also the risk of release failure or service interruption caused by improper changes is significantly reduced, providing strong support for the continuous integration and continuous delivery of software development.

[0129] In some embodiments, whenever a new version is ready to be released, the development team submits a release application, and the system automatically marks the service status of the current release as "releasing" and locks all related change functions to prevent unnecessary interference or errors during this process.

[0130] Furthermore, if other teams or individuals want to submit a change request, the system will first check the status of the current service. If the status of the current service is "releasing" and the corresponding change level is greater than level 1 change, the system will reject the change request and give a prompt message indicating that the applicant cannot make a change at this time.

[0131] Furthermore, when an emergency occurs and necessary changes need to be made during the release process, the changes can be made through a special change authorization process.

[0132] Specifically, if a special change is required, the change submitter needs to submit a change request. The system will first perform identity verification and permission check to ensure that the request is legal and compliant. After confirming that the change can be made without error, the system sends the change request to the evaluation module for evaluation. The change request can be evaluated by the release personnel or a trained evaluation large model, and then the relevant change functions are controlled according to the evaluation results.

[0133] When the evaluation result allows the change request to be processed, the corresponding change interface is controlled to allow the change.

[0134] Furthermore, when a change end instruction is received, it is first necessary to determine the corresponding change interface according to the change end instruction, and then adjust and restore the change interface corresponding to the change end instruction to the locked state to prevent other users from making changes until the service release is completed.

[0135] Furthermore, after the entire release process of the service is completed, the system will automatically restore the service status to the "non-release" status and unlock all related change functions, allowing normal change requests to continue to be submitted and processed. This not only facilitates users to manage the release service but also ensures the smooth progress of the service release process. At the same time, it can guarantee the stability and continuity of the service.

[0136] In this embodiment, when the release process is submitted, the release status management module immediately marks the current service status as "releasing". At the same time, this module locks all change module interfaces related to the service to prevent improper changes during the release process.

[0137] Regarding the handling of change requests, when a change request is submitted to the change request handling module, this module first calls the release status management module to obtain the current service status.

[0138] If the service status is "releasing", the change request handling module rejects the change request and returns an error message.

[0139] If the service status is "non-release", the change request handling module allows the change request to be submitted and updates the relevant configurations or data.

[0140] Regarding special change authorization, in special cases, if it is indeed necessary to make necessary changes during the release process, the release submitter can submit a change request through the special change authorization module. Among them, the change request does not have to be submitted by the release personnel. It can be members of the release personnel group or personnel with the relevant permission to change the release service.

[0141] Specifically, after receiving the request, the special change authorization module authenticates the identity of the change submitter and checks the permissions to ensure that the request comes from a legitimate user and has the corresponding permissions. After confirmation, the special change authorization module evaluates the special change and then performs corresponding operations according to the evaluation result of the special change.

[0142] Furthermore, when the evaluation result is to allow the change, the relevant change module interfaces in the change instruction are unlocked to allow the change to occur. When receiving the change end instruction, the special change authorization module determines the changed and ended change interfaces according to the change end instruction to restore the relevant change module interfaces to the locked state and update the status information in the release status management module.

[0143] On the other hand, when the evaluation result is to reject the change, the relevant change module interfaces in the change instruction are locked, the change is rejected, and a rejection change prompt is output. The reason for rejecting the change can be specifically described in the rejection change prompt to facilitate users to understand the process.

[0144] Specifically, restoring the release status of a service means that after the entire service release process is completed, the release status management module restores the status flag of the current service to "not in release", and unlocks all relevant change module interfaces according to the service status to facilitate users to perform change operations.

[0145] In this embodiment, as Figure 2 shown, Figure 2 is a schematic diagram of the execution of this embodiment, describing the entire process from the start of the release process to the end. The following is an explanation of the steps according to the flowchart:

[0146] "Start release process" in the figure indicates that the process starts here.

[0147] Furthermore, user A initiates a release, indicating that a certain user (marked as A) starts the service release process. At this time, the service is marked as being in the release state through the service release system, that is, the system determines the target service to be changed and marks the current state as "being in release".

[0148] Furthermore, it is determined whether a change is required. The determination process specifically includes: first, determining whether a change is currently supported according to the status of the release service, and determining the change permission according to different preset statuses. If the determination result of whether to change is "yes", the change process starts; if the determination result of whether to change is "no", the service change process ends.

[0149] When a change is allowed, the change process starts to respond to the user's change request.

[0150] Specifically, when a change request submitted by user B is received, the corresponding target service is determined through the change request, and then the target change level of the target service is determined to compare the target change level of the target service with the set level threshold to adjust the interface status of the target interface.

[0151] Furthermore, when the target change level is less than or equal to level 1 change (level threshold), it indicates that the change in the current change instruction is a low-impact change. Therefore, the interface status of the target interface is adjusted to allow change according to the change instruction, that is, the change button is automatically unlocked.

[0152] Furthermore, when the target change level is greater than level 2 change (level threshold), it indicates that the change in the current change instruction is a change with a greater impact. Therefore, the user's change instruction is rejected, and it is prompted that a special change requires submitting a change process description. After user B submits the change process description, the change process description is sent to the release personnel, and it is determined whether to allow the change through the evaluation of the release personnel.

[0153] Specifically, it is determined whether to perform special changes according to the evaluation results. When the evaluation result allows changes, the relevant change module button is unlocked, and changes are allowed to occur. On the other hand, when the evaluation result rejects changes, the relevant change module button is locked, that is, not unlocked, and changes are not allowed to occur, thereby ensuring the stability and reliability of software releases, reducing user dissatisfaction and complaints caused by service interruptions or release failures, and enhancing user satisfaction and loyalty.

[0154] Further, when a change end instruction is received, the change interface where the change occurs and ends is determined according to the change end instruction, so as to restore the relevant change module interface to the locked state and update the status information in the release status management module.

[0155] Further, after the entire release process is completed, the status flag in the release module will be adjusted to the "non-release" state, indicating that the service release has been completed and the stable operation stage can be entered. Through service management, not only the controllability and stability of the software release process are improved, ensuring that changes can only be executed after appropriate evaluation, but also the risk of release failures or service interruptions caused by improper changes is significantly reduced, providing strong support for the continuous integration and continuous delivery of software development.

[0156] In this embodiment, by responding to the change instruction of the target service; obtaining the target interface that needs to be changed from the change instruction, where the target interface is linked to the target service; determining the interface status of the target interface according to the release status of the target service; determining the target change level of the target service; and adjusting the interface status of the target interface according to the change instruction and the target change level, the efficiency and stability of service release can be improved, and further the risk of release failures or service interruptions caused by improper changes is significantly reduced, providing strong support for the continuous integration and continuous delivery of software development.

[0157] As Figure 3 shown, some embodiments of the present application provide a service release management system, which includes a response module 310, an acquisition module 320, a matching module 330, a confirmation module 340, and an adjustment module 350. Specifically:

[0158] The response module 310 is used to respond to the change instruction of the target service;

[0159] The acquisition module 320 is used to obtain the target interface that needs to be changed from the change instruction, where the target interface is linked to the target service;

[0160] The matching module 330 is used to determine the interface status of the target interface according to the release status of the target service;

[0161] The confirmation module 340 is used to determine the target change level of the target service;

[0162] An adjustment module 350 is configured to adjust the interface state of a target interface according to a change instruction and a target change level.

[0163] In some embodiments, the confirmation module 340 may include: determining a target change level of a target service from preset change level information, where the change level information includes a correspondence between services and change levels.

[0164] In some embodiments, the adjustment module 350 may include: when the target change level is less than or equal to a level threshold, adjusting the interface state of the target interface to a first preset state according to the change instruction.

[0165] In some embodiments, the adjustment module 350 may include: when the target change level is greater than the level threshold, adjusting the interface state of the target interface to a second preset state according to the change instruction.

[0166] In some embodiments, the adjustment module 350 may include: responding to a re-change instruction.

[0167] In some embodiments, the adjustment module 350 may include: evaluating the re-change instruction to obtain an evaluation result of the re-change instruction.

[0168] In some embodiments, the adjustment module 350 may include: controlling a service change interface corresponding to the re-change instruction according to the evaluation result.

[0169] In some embodiments, the adjustment module 350 may include: responding to a change end instruction.

[0170] In some embodiments, the adjustment module 350 may include: obtaining a service change interface corresponding to the change end instruction from the change end instruction to adjust the interface state of the service change interface corresponding to the change end instruction.

[0171] It should be noted that the service release management system provided in this embodiment and the above service release management method are based on the same inventive concept. Therefore, the relevant content of the above service release management method also applies to the content of the service release management system. Therefore, it will not be elaborated here.

[0172] In order for the system to respond to the change instruction of the target service; obtain the target interface to be changed from the change instruction, where the target interface is linked to the target service; determine the interface status of the target interface according to the release status of the target service; determine the target change level of the target service; and adjust the interface status of the target interface according to the change instruction and the target change level. In this way, the efficiency and stability of service release can be improved, and the risk of release failure or service interruption caused by improper changes can be significantly reduced, providing strong support for the continuous integration and continuous delivery of software development.

[0173] An embodiment of the present application also provides an electronic device, which includes a memory and a processor. The memory stores a computer program, and when the processor executes the computer program, the management method for service release described above is implemented.

[0174] As Figure 4 , Figure 4 is a schematic diagram of the hardware structure of the electronic device provided by the embodiment of the present application. The electronic device includes:

[0175] At least one battery;

[0176] At least one memory;

[0177] At least one processor;

[0178] At least one program;

[0179] The program is stored in the memory, and the processor executes at least one program to implement the management method for service release described above in the present disclosure.

[0180] The electronic device can be any intelligent terminal including a mobile phone, a tablet computer, a personal digital assistant (PDA), a vehicle-mounted computer, etc.

[0181] The following provides a detailed introduction to the electronic device of the embodiment of the present application.

[0182] The processor 1600 can be implemented by using a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, etc., and is used to execute relevant programs to implement the technical solutions provided by the embodiments of the present disclosure;

[0183] The memory 1700 can be implemented in the form of a Read Only Memory (ROM), a static storage device, a dynamic storage device, or a Random Access Memory (RAM), etc. The memory 1700 can store an operating system and other application programs. When implementing the technical solutions provided in the embodiments of this specification through software or firmware, the relevant program codes are stored in the memory 1700 and are called by the processor 1600 to execute a management method for service publishing in the embodiments of the present disclosure.

[0184] The input / output interface 1800 is used to implement information input and output;

[0185] The communication interface 1900 is used to implement communication interaction between this device and other devices. Communication can be achieved through wired means (such as USB, network cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.);

[0186] The bus 2000 transmits information between various components of the device (such as the processor 1600, the memory 1700, the input / output interface 1800, and the communication interface 1900);

[0187] Among them, the processor 1600, the memory 1700, the input / output interface 1800, and the communication interface 1900 are communicatively connected to each other inside the device through the bus 2000.

[0188] The embodiments of the present disclosure also provide a storage medium, which is a computer-readable storage medium. The computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to cause a computer to execute the above-mentioned management method for service publishing.

[0189] As a non-transitory computer-readable storage medium, the memory can be used to store non-transitory software programs and non-transitory computer-executable programs. In addition, the memory can include high-speed random access memory, and can also include non-transitory memory, such as at least one magnetic disk storage device, a flash memory device, or other non-transitory solid-state storage devices. In some embodiments, the memory optionally includes a memory remotely provided relative to the processor, and these remote memories can be connected to the processor through a network. Examples of the above-mentioned network include but are not limited to the Internet, an enterprise intranet, a local area network, a mobile communication network, and combinations thereof.

[0190] The embodiments of the present disclosure also provide a computer program product. When the instructions in the computer program product are executed by the processor of an electronic device, the electronic device is caused to execute the above-mentioned management method for service publishing.

[0191] The embodiments described in the embodiments of the present disclosure are to more clearly illustrate the technical solutions of the embodiments of the present disclosure, and do not constitute a limitation on the technical solutions provided by the embodiments of the present disclosure. Those skilled in the art will know that with the evolution of technology and the emergence of new application scenarios, the technical solutions provided by the embodiments of the present disclosure are equally applicable to similar technical problems.

[0192] Those skilled in the art can understand that the technical solutions shown in the figures do not constitute a limitation on the embodiments of the present disclosure, and may include more or fewer steps than those shown in the figures, or combine certain steps, or different steps.

[0193] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separated, that is, they may be located in one place, or may be distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0194] Those of ordinary skill in the art can understand that all or some of the steps in the methods disclosed above, and the functional modules / units in the systems and devices, can be implemented as software, firmware, hardware, and their appropriate combinations.

[0195] The terms "first", "second", "third", "fourth", etc. (if any) in the specification of this application and the above drawings are used to distinguish similar objects, and do not have to be used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances, so that the embodiments of this application described here can be implemented in an order other than those illustrated or described here. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units does not have to be limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or are inherent to these processes, methods, products, or devices.

[0196] It should be understood that in this application, "at least one (item)" means one or more, and "a plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that there can be three relationships. For example, "A and / or B" can mean: only A exists, only B exists, and both A and B exist at the same time. Among them, A and B can be singular or plural. The character " / " generally indicates that the associated objects before and after are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single item (item) or plural items (items). For example, at least one (item) of a, b, or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0197] In several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of units is only a logical function division. In actual implementation, there can be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling or direct coupling or communication connection between each other can be through some interfaces. The indirect coupling or communication connection of devices or units can be in electrical, mechanical or other forms.

[0198] The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they can be located in one place, or they can be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0199] In addition, the functional units in each embodiment of this application can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above integrated units can be implemented in the form of hardware or in the form of software functional units.

[0200] When an integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes multiple instructions for causing an electronic device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods of various embodiments of this application. The aforementioned storage medium includes: various media that can store programs, such as USB flash drives, mobile hard disks, read-only memories (ROM), random access memories (RAM), magnetic disks, or optical discs.

[0201] The above has specifically described the preferred implementation of the embodiments of this application, but the embodiments of this application are not limited to the above implementation manners. Those skilled in the art can also make various equivalent deformations or substitutions without departing from the spirit of the embodiments of this application, and these equivalent deformations or substitutions are all included within the scope defined by the claims of the embodiments of this application.

[0202] The above has described the embodiments of this application in detail with reference to the accompanying drawings, but this application is not limited to the above embodiments. Within the scope of knowledge possessed by those of ordinary skill in the art to which it pertains, various changes can also be made without departing from the purpose of this application.

Claims

1. A method for managing service publishing, characterized in that: The method comprises: Respond to change orders for target services; Acquire a target interface to be changed from the change instruction, wherein the target interface is linked to the target service; Determining the interface status of the target interface according to the publishing status of the target service; determining a target change level for the target service; The interface state of the target interface is adjusted according to the change instruction and the target change level.

2. The service publishing management method according to claim 1, characterized in that: Determining the target change level of the target service includes: A target change level of the target service is determined from preset change level information, wherein the change level information includes a correspondence between services and change levels.

3. The service publishing management method according to claim 1, characterized in that: The adjusting the interface state of the target interface according to the change instruction and the target change level includes: When the target change level is less than or equal to a level threshold, the interface state of the target interface is adjusted to a first preset state according to the change instruction.

4. The service publishing management method according to claim 3, characterized in that: The step of adjusting the interface state of the target interface according to the change instruction and the target change level further includes: When the target change level is greater than the level threshold, the interface state of the target interface is adjusted to a second preset state according to the change instruction.

5. The service publishing management method according to claim 4, characterized in that: After adjusting the interface state of the target interface to a second preset state according to the change instruction, the method further includes: Respond to the change instruction again; Evaluate the re-change instruction to obtain an evaluation result of the re-change instruction; The service change interface corresponding to the re-change instruction is controlled according to the evaluation result.

6. The service publishing management method according to claim 5, characterized in that: After adjusting the interface state of the target interface according to the change instruction and the target change level, the method further includes: Respond to the change end instruction; A service change interface corresponding to the change end instruction is obtained from the change end instruction to adjust an interface state of the service change interface corresponding to the change end instruction.

7. A service publishing management system, characterized in that: The system comprises: The response module is used to respond to the change instructions of the target service; An acquisition module, used for acquiring a target interface to be changed from the change instruction, wherein the target interface is linked to the target service; A matching module, used to determine the interface status of the target interface according to the publishing status of the target service; A confirmation module, used for determining a target change level of the target service; An adjustment module is used to adjust the interface state of the target interface according to the change instruction and the target change level.

8. An electronic device, characterized in that: It includes at least one control processor and a memory for communicating with the at least one control processor; the memory stores instructions that can be executed by the at least one control processor, and the instructions are executed by the at least one control processor to enable the at least one control processor to execute a service publishing management method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to enable a computer to execute the service publishing management method according to any one of claims 1 to 6.

10. A computer program product, characterized in that When the instructions in the computer program product are executed by a processor of an electronic device, the electronic device executes a service publishing management method as described in any one of claims 1 to 6.

Images