CN118151950A

CN118151950A - Service release method and device, electronic equipment and storage medium

Info

Publication number: CN118151950A
Application number: CN202211510009.8A
Authority: CN
Inventors: 段晨
Original assignee: Douyin Vision Co Ltd
Current assignee: Douyin Vision Co Ltd
Priority date: 2022-11-29
Filing date: 2022-11-29
Publication date: 2024-06-07

Abstract

The present disclosure provides a service publishing method, a device, an electronic apparatus and a storage medium, wherein the method is to receive configuration change information of each requirement for target service publishing, wherein the configuration change information is input by filling notification information for the prompted requirement; generating a release plan of the target service according to the configuration change information of each requirement; when the target service release is triggered, configuration change and synchronization are carried out according to the release plan so as to complete the release of the target service, thereby realizing the capability of unified management of the configuration change, reducing the risk of the configuration change and improving the release efficiency.

Description

Service release method and device, electronic equipment and storage medium

Technical Field

The disclosure relates to the technical field of computers, and in particular relates to a service release method, a service release device, electronic equipment and a storage medium.

Background

The pipeline mode is a scheme for integrating a series of delivery process requirements such as construction, deployment, automatic test and the like, can be suitable for a release process of a service such as software and the like, meets the current service update iteration speed and release frequency, generally relates to various configuration changes in the release process, and in the related technology, the configuration changes in the release process are mainly operated on different tools or platforms by manpower, but the configuration changes of a plurality of tools or platforms are possibly involved in the release process of one service, different research and development personnel respectively perform manual operation, the configuration change state is opaque, configuration change information is easy to miss and cannot be synchronized in time, so that the release is problematic or failed, and the release efficiency is reduced.

Disclosure of Invention

The embodiment of the disclosure at least provides a service release method, a device, electronic equipment and a storage medium.

In a first aspect, an embodiment of the present disclosure provides a service publishing method, including:

Receiving configuration change information of each requirement issued by a target service, wherein the configuration change information is input by filling notification information for the prompted requirement;

generating a release plan of the target service according to the configuration change information of each requirement;

And when the target service release is triggered, carrying out configuration change and synchronization according to the release plan so as to complete the release of the target service.

In an alternative embodiment, before receiving the configuration change information for each requirement of the target service publication, the method further includes:

determining a target object corresponding to each requirement according to the preset object identifier corresponding to each requirement;

And sending requirement filling notification information to the target object corresponding to each requirement so that the target object inputs corresponding configuration change information.

In an alternative embodiment, generating the distribution plan of the target service according to the configuration change information of each requirement includes:

Determining the executed stage, the dependency relationship and the configuration type of the configuration change information of each requirement, and sorting the configuration change information of each requirement according to the executed stage, the dependency relationship and the configuration type of the configuration change information of each requirement and the preset sorting priority;

and generating a release plan of the target service according to the ordered configuration change information of each requirement.

In an optional implementation manner, after generating the release plan of the target service, the method further includes:

The release plan is sent to a corresponding preset auditing object, so that whether the preset auditing object passes the release plan or not is confirmed by the preset auditing object;

And after the preset auditing object confirms that the release plan passes, determining to trigger the release of the target service.

In an alternative embodiment, according to the distribution plan, performing configuration change and synchronization to complete distribution of the target service includes: and calling a service interface of each service platform associated with the configuration change information according to the release plan, carrying out configuration change and synchronization, and determining that after the configuration change and synchronization of each associated service platform are completed, updating the configuration state of the configuration change information to be completed.

In an alternative embodiment, according to the distribution plan, performing configuration change and synchronization to complete distribution of the target service includes: receiving confirmation information of whether the configuration change of each configuration change information in the release plan is completed or not; and when receiving the completed confirmation information, updating the configuration state of the configuration change information to be completed.

In an alternative embodiment, the method further comprises: and when the problem of the release of the target business is determined, generating a rollback plan according to the release plan so as to perform rollback operation according to the rollback plan.

and receiving the supported configuration type set for the target service, so that corresponding configuration change information is input for the supported configuration type.

In an alternative embodiment, the service publishing method is implemented based on an atomic node that is configured to be deployed in any publishing stage involved in the target service publication.

In a second aspect, an embodiment of the present disclosure further provides a service publishing device, including:

the receiving module is used for receiving configuration change information of each requirement issued for the target service, wherein the configuration change information is input by filling notification information for the prompted requirement;

the generation module is used for generating a release plan of the target service according to the configuration change information of each requirement;

And the release module is used for carrying out configuration change and synchronization according to the release plan so as to finish the release of the target service when the release of the target service is triggered.

In an optional embodiment, before receiving the configuration change information of each requirement for the target service release, the sending module is further configured to:

In an optional implementation manner, when generating the release plan of the target service according to the configuration change information of each requirement, the generating module is configured to:

In an optional implementation manner, after generating the release plan of the target service, the method further includes a confirmation module for:

In an alternative embodiment, when performing configuration change and synchronization according to the distribution plan to complete distribution of the target service, the distribution module is configured to: and calling a service interface of each service platform associated with the configuration change information according to the release plan, carrying out configuration change and synchronization, and determining that after the configuration change and synchronization of each associated service platform are completed, updating the configuration state of the configuration change information to be completed.

In an alternative embodiment, when performing configuration change and synchronization according to the distribution plan to complete distribution of the target service, the distribution module is configured to: receiving confirmation information of whether the configuration change of each configuration change information in the release plan is completed or not; and when receiving the completed confirmation information, updating the configuration state of the configuration change information to be completed.

In an alternative embodiment, the rollback module is further configured to: and when the problem of the release of the target business is determined, generating a rollback plan according to the release plan so as to perform rollback operation according to the rollback plan.

In an alternative embodiment, before receiving the configuration change information of each requirement for the target service release, the configuration change module is further configured to:

In a third aspect, an optional implementation manner of the disclosure further provides an electronic device, including a processor, and a memory, where the memory stores machine-readable instructions executable by the processor, and the processor is configured to execute the machine-readable instructions stored in the memory, where the machine-readable instructions, when executed by the processor, perform the steps in the first aspect, or any possible implementation manner of the first aspect.

In a fourth aspect, an alternative implementation of the present disclosure further provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the first aspect, or any of the possible implementation manners of the first aspect.

In the embodiment of the disclosure, configuration change information of each requirement issued for a target service is received, wherein the configuration change information is input by filling notification information for the prompted requirement; generating a release plan of the target service according to the configuration change information of each requirement; when the target business is triggered to be released, configuration change and synchronization are carried out according to the release plan so as to complete the release of the target business, thus configuration change information of different requirements is collected in advance to generate the release plan, and the configuration change and synchronization are carried out according to the release plan during release, thereby realizing the capability of configuration change management, reducing the risk of configuration change, improving the release efficiency, and being capable of flexibly adapting each release platform, and being simple and convenient to realize.

The description of the effects of the service issuing device, the electronic device, and the computer-readable storage medium is referred to the description of the service issuing method, and is not repeated here.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the aspects of the disclosure.

The foregoing objects, features and advantages of the disclosure will be more readily apparent from the following detailed description of the preferred embodiments taken in conjunction with the accompanying drawings.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings required for the embodiments are briefly described below, which are incorporated in and constitute a part of the specification, these drawings showing embodiments consistent with the present disclosure and together with the description serve to illustrate the technical solutions of the present disclosure. It is to be understood that the following drawings illustrate only certain embodiments of the present disclosure and are therefore not to be considered limiting of its scope, for the person of ordinary skill in the art may admit to other equally relevant drawings without inventive effort.

Fig. 1 shows a flowchart of a service publishing method provided by an embodiment of the present disclosure;

FIG. 2 illustrates an exemplary diagram of a notification card requiring fill-in notification information provided by an embodiment of the present disclosure;

FIG. 3 illustrates an exemplary diagram of a notification card of a configuration state provided by an embodiment of the present disclosure;

FIG. 4 is a flowchart of another method for distributing services according to an embodiment of the present disclosure;

FIG. 5 illustrates a logical block diagram of a delivery process for a pipeline-mode-based target service provided by an embodiment of the present disclosure;

Fig. 6 is a schematic diagram of a service publishing device according to an embodiment of the present disclosure;

fig. 7 shows a schematic diagram of an electronic device provided by an embodiment of the disclosure.

Detailed Description

It will be appreciated that prior to using the technical solutions disclosed in the embodiments of the present disclosure, the user should be informed and authorized of the type, usage range, usage scenario, etc. of the personal information related to the present disclosure in an appropriate manner according to the relevant legal regulations.

For the purposes of making the objects, technical solutions and advantages of the embodiments of the present disclosure more apparent, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure, and it is apparent that the described embodiments are only some embodiments of the present disclosure, but not all embodiments. The components of the disclosed embodiments generally described and illustrated herein may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present disclosure is not intended to limit the scope of the disclosure, as claimed, but is merely representative of selected embodiments of the disclosure. All other embodiments, which can be made by those skilled in the art based on the embodiments of this disclosure without making any inventive effort, are intended to be within the scope of this disclosure.

For the convenience of understanding the technical solutions of the present disclosure, technical terms in the embodiments of the present disclosure will be described first:

DevOps: development (Development) and Operations (Operations) are a set of general terms of processes, methods and systems, and are used for promoting communication, collaboration, integration and the like among Development, technical operation and quality assurance departments, so that software modules can be standardized, and a series of delivery process requirements such as integrated construction, deployment, dynamic test and the like can be met. By creating a unified template, continuous delivery of different languages and different release objects is supported, and a series of automatic quality assurance capabilities such as version control, code scanning and security scanning are integrated by unifying arrangement stages and executable nodes in the template.

And (3) pipeline: representing a set of automated processes that enable professionals and developers to reliably and efficiently compile, build and deploy their code to production for use by users of the product or business. The pipeline mode may divide a task into a plurality of steps or sub-tasks for execution, such that different steps or sub-tasks may be executed in parallel, the plurality of steps or sub-tasks having a dependency relationship therebetween, the output of a previous sub-task being the input of a subsequent sub-task.

Demand: a demand refers to a functional property that a product is required to possess, which is often a solution to a particular problem for a user or an additional value to the user.

Release planning: in order to deploy product demands on-line for users, a series of on-line changing operations are required, and the distribution plan is to sequence the changing operations so that the changing operations can be performed in a planned order.

Rollback planning: if the expected effect is not achieved after the change is generated on the line, the change on the line is rolled back to the state before the change is not generated, a series of plans are required to be formulated for the rollback, and the problem that certain functions cannot be normally used due to the rollback is avoided.

Atomic node: based on the pipeline's operation, for a single independently executable action, for example: interface automation, code security scanning, service upgrades, etc. For example, in the embodiment of the present disclosure, a distribution plan management atom node may be deployed, where the distribution plan management atom is an independently operable atom for executing and implementing the service distribution method in the embodiment of the present disclosure.

According to research, service release is performed based on a pipeline mode, the method is very convenient and efficient, risks of one delivery are not only derived from code change, risks are possibly brought to data change, configuration change, network change and the like, and therefore each delivery also needs to be provided with a rollback plan for completing release schedule and having unpredictable problems. At present, most platforms pay attention to the risk of solving code change, and aiming at various configuration changes, in the related technology, the configuration changes in the release process are mainly operated on different tools or platforms by manpower, but the configuration changes of a plurality of tools or platforms may be involved in one service release process, the inlets of the tools or platforms are scattered, different research and development personnel respectively operate manually, the configuration change state is opaque, configuration change information is easy to miss and cannot be synchronized in time, so that the problem or failure of release occurs, and the release efficiency is also reduced.

Based on the above study, the present disclosure provides a service publishing method, which receives configuration change information of each requirement for target service publishing, wherein the configuration change information is input by filling notification information for the prompted requirement; according to the configuration change information of each requirement, generating a release plan of the target service, and further when the release of the target service is triggered, carrying out configuration change and synchronization according to the release plan to complete the release of the target service, so that the configuration change information is prompted and collected before release, the release plan is generated, and the configuration change synchronization can be carried out according to the release plan during release, thereby realizing the capability of unifying configuration change management, controlling the risks brought by the configuration change, improving the release efficiency and reducing the online problems.

The present invention is directed to a method for manufacturing a semiconductor device, and a semiconductor device manufactured by the method.

It should be noted that: like reference numerals and letters denote like items in the following figures, and thus once an item is defined in one figure, no further definition or explanation thereof is necessary in the following figures.

For the convenience of understanding the present embodiment, first, a detailed description will be given of a service publishing method disclosed in an embodiment of the present disclosure, and an execution body of the service publishing method provided in the embodiment of the present disclosure is generally an electronic device with a certain computing capability, where the electronic device includes, for example: the terminal device or server or other processing device may be a User Equipment (UE), a mobile device, a cellular phone, a cordless phone, a Personal digital assistant (Personal DIGITAL ASSISTANT, PDA), a handheld device, a computing device, a vehicle-mounted device, a wearable device, etc., where the Personal digital assistant is a handheld electronic device, has some functions of an electronic computer, may be used to manage Personal information, may browse internet, send and receive e-mails, etc., and may be called a palm computer. In some possible implementations, the service issuing method may be implemented by a processor calling computer readable instructions stored in a memory.

The service publishing method provided by the embodiment of the present disclosure is described below by taking an execution body as a server as an example.

Referring to fig. 1, a flowchart of a service publishing method provided by an embodiment of the present disclosure is shown, where the method includes:

S101: and receiving configuration change information of each requirement issued by the target service, wherein the configuration change information is input by filling notification information for the prompted requirement.

The target service is, for example, application software, database table changing service, middleware changing service, and the like, which are not limited in the embodiment of the disclosure. Before delivering or publishing the target service, a series of processes such as development, test, pre-publishing and the like are performed, and in the embodiment of the present disclosure, the service publishing method is configured in the pipeline mode mainly aiming at the scene of the publishing schedule management of the target service based on the pipeline mode, so as to realize the management of configuration change, thereby reducing the risk of configuration change. Specifically, in the pipeline mode, different atomic nodes can be configured according to the use requirement, based on this, in the embodiment of the disclosure, the service publishing method is implemented based on the set atomic nodes, the atomic nodes are deployed in any publishing stage related to the target service publishing, for example, a publishing plan management atomic node can be configured, and the publishing plan management atomic node is used for implementing the function of the service publishing method in the embodiment of the disclosure, and further, according to the differentiated requirement of different services, the publishing plan management atomic node can be configured in any publishing stage related to the publishing, so that the implementation is more flexible and convenient.

The relevant personnel may be prompted to fill in configuration change information for information collection, before this step S101 is performed, and in particular the present disclosure provides one possible implementation,

1) And determining a target object corresponding to each requirement according to the preset object identifier corresponding to each requirement.

The object identifier herein may be understood as a user identifier, for example, a mobile phone number, a job number, etc. of the user, and is not limited thereto.

Typically, the development of a target service involves multiple demands, and to improve efficiency, multiple demands may be allocated to different users for processing, for example, target service a includes eight demands, where demands 1 to 3 may be allocated to user a, demands 4 to 6 may be allocated to user b, and demands 7 to 8 may be allocated to user c.

2) And sending the requirement filling notification information to the target object corresponding to each requirement so as to enable the target object to input corresponding configuration change information.

The configuration change information may include, but is not limited to, a configuration type, a change content, and the like.

For example, in the release plan making stage or the release plan collecting stage, the requirement filling notification information can be respectively sent to the corresponding target objects in the form of notification cards, so that the interaction convenience is improved. Referring to fig. 2, in an exemplary diagram of a notification card for filling notification information in a request, as shown in fig. 2, the notification card includes a request name, a filling control, and the like, after a target object receives the notification card, if it is determined that there is no change item or the request is filled, the notification card can be closed by clicking the filling control, and the notification card is not pushed any more, if the request needs to be filled, the filling control can be clicked, and corresponding configuration change information is input at an input position in the notification card, or the target object can jump to a filling page and input at the filling page without limitation.

In this way, the requirement filling notification information is pushed to the corresponding target object, and the relevant user can be reminded to timely fill in the configuration change information through interaction with the user, so that the risk of configuration change omission is reduced, and development, testing, on-line release blocking or on-line problems caused by the configuration change omission are also reduced.

Further, in the embodiment of the present disclosure, a preset configuration type supported by each service is further supported, and a possible implementation manner is provided specifically, a supported configuration type set for a target service is received, so that corresponding configuration change information is input for the supported configuration type.

Because the middleware or the storage types and the like related to each service may not be the same, in order to further meet the needs of the user, the user can configure the supported configuration types in a self-defined mode according to the needs, and further push the needed filling notification information and input the configuration change information according to the preset configuration types, so that collection of all the configuration change information is realized.

In addition, if the supported configuration type is not preset for the target service, in the embodiment of the present disclosure, the default configuration type may also be supported.

S102: and generating a release plan of the target service according to the configuration change information of each requirement.

In the embodiment of the present disclosure, according to the configuration change information of each requirement, a release plan may be automatically generated by aggregation, and when this step S102 is specifically executed, a possible implementation manner is provided:

1) Determining the execution stage, the dependency relationship and the configuration type of the configuration change information of each requirement, and sequencing the configuration change information of each requirement according to the execution stage, the dependency relationship and the configuration type of the configuration change information of each requirement and the preset sequencing priority.

The stage representation executed by the configuration change information is each stage of pre-dividing the release process, for example, the release process can be divided into four stages of pre-release, post-release, pre-generation and post-generation; the dependency relationship indicates whether one configuration change depends on the result of other configuration changes, and the configuration change sequence of the configuration items with the dependency relationship can be controlled through weights; the configuration type represents each service platform involved in the service.

The sorting priority is a stage, a weight and a configuration type in sequence, namely sorting can be performed according to the stage, then the configuration change information in the same stage is sorted according to the weight, the configuration change information belonging to the same configuration type is aggregated, the interaction efficiency and experience of the cross-service platform can be improved, the configuration change information of each requirement can be sorted and aggregated according to the sorting priority, namely a release plan is generated, the release stage is entered, each configuration change information is not checked by a requirement dimension any more, and the configuration change synchronization can be completed more quickly and accurately.

2) And generating a release plan of the target service according to the ordered configuration change information of each demand.

The release plan includes changing content corresponding to each configuration type, and the like, so that a user can conveniently view and synchronize each configuration changing information.

Further, after generating the release plan of the target service, in order to improve reliability and avoid problems such as omission or error, the release plan can be pushed to related users for reconfirmation, and in particular, the present disclosure provides a possible implementation manner, the release plan is sent to a corresponding preset audit object, so that whether the preset audit object passes the verification of the release plan or not; and after the preset auditing object confirms that the release plan passes, determining to trigger the target service release.

In this way, in the embodiment of the disclosure, after the release plan is generated, the release plan is pushed to the preset auditing object for auditing and confirmation, and after the auditing is passed, the release stage can be entered, so that the configuration change risk can be further reduced, and the release problem is reduced.

S103: when the release of the target service is triggered, configuration change and synchronization are carried out according to the release plan so as to complete the release of the target service.

In the embodiment of the present disclosure, after entering the release phase, all configuration changes may be uniformly managed according to the release plan, so as to support automatic change synchronization and manual change synchronization for adapting to different scenarios, and when the step S103 is specifically executed, the following possible embodiments are provided:

One possible implementation manner, according to a release plan, performs configuration change and synchronization to complete release of a target service, including: and calling a service interface of each service platform associated with the configuration change information according to the release plan, carrying out configuration change and synchronization, and determining that after the configuration change and synchronization of each associated service platform are completed, updating the configuration state of the configuration change information to be completed.

In the embodiment of the disclosure, a scene of a callable service interface is provided for each service platform related to the target service, so that configuration change and synchronization can be automatically completed. For example, for a configuration item of a certain service platform, a service interface of the service platform is called, configuration change is performed according to the change content of the configuration item, after the operation of the configuration change is performed, the configuration change is synchronized to other service platforms, the configuration change of the configuration item is informed to be completed, further, after the synchronization success is determined, the configuration state of the configuration item is updated to be completed, if any service platform is not successful in synchronization, at this time, the service platform which is not successful in synchronization does not know which configuration item is subjected to the configuration change, and the subsequent flow of the service platform is possibly affected, so that errors are generated or the expected effect is not achieved, and therefore, the configuration state is updated after the configuration change and the synchronization are completed, consistency can be ensured, and problems and risks are reduced.

In another possible implementation manner, according to the distribution plan, performing configuration change and synchronization to complete distribution of the target service includes: receiving confirmation information of whether the configuration change of each configuration change information in the release plan is completed or not; and when receiving the completed confirmation information, updating the configuration state of the configuration change information to be completed.

In the embodiment of the disclosure, for a scenario that each service platform related to the target service does not provide a callable service interface, automatic change and synchronization cannot be realized, at this time, a manual mode may be adopted, for example, a user manually performs configuration change on a configuration item in a certain service platform according to a release plan, and further, by setting whether detection is completed, the configuration state may be updated to be completed after the detection is passed, or the user may also confirm that the configuration change is completed by clicking a confirmation button.

Further, in the embodiment of the present disclosure, to further ensure whether the configuration change and synchronization are completed, the configuration state may be obtained periodically and prompted to the user, for example, according to the distribution plan, the change content in each configuration change information is synchronized to the corresponding service platform according to the configuration type, further, according to the preset period, the configuration state of each configuration change information is obtained periodically, after the success of the change is confirmed, the next stage is entered, and the card is notified of the configuration state of each required configuration change information, and also the specific change content and configuration type of the configuration change information may be notified. For example, referring to fig. 3, which is an exemplary diagram of a notification card of a configuration state in an embodiment of the present disclosure, as shown in fig. 3, a user may conveniently learn which configuration change information is not filled yet, which is filled or which is configured to be changed and completed synchronously, and further may prompt a relevant user who does not complete filling to fill in time according to the notification card. V-shaped design

In addition, a rollback operation may be supported in the embodiments of the present disclosure, and in a possible embodiment, when it is determined that a problem occurs in the release of the target service, a rollback plan is generated according to the release plan, so that the rollback operation is performed according to the rollback plan.

Therefore, after the problem occurs, the rollback plan can be automatically generated, the rollback plan is clear and definite, the rollback operation sequence can be definitely determined according to the rollback plan, the condition that the rollback operation sequence can be correctly rolled back to the previous state is ensured, and the positioning and the solving of the related problem are facilitated.

In the embodiment of the disclosure, configuration change information of each requirement aiming at target service release is received, and according to the configuration change information of each requirement, a release plan of the target service is generated, and further when the target service release is triggered, the configuration change and synchronization are performed according to the release plan to complete the release of the target service, so that configuration change information is collected, the release plan is generated, and when release is performed, the configuration change and synchronization are performed, thereby initiating and following the configuration change and real-time synchronization in the whole release process, realizing unified management of the configuration change, reducing omission or sequence error of non-code type configuration change in the online process, improving release efficiency and reducing online problems.

The following describes a service publishing method in the embodiment of the present disclosure by using a specific application scenario, where the service publishing method is implemented by using a configured publishing plan management atomic node, for example, as shown in fig. 4, and is a flowchart of another service publishing method in the embodiment of the present disclosure, and the method is mainly divided into two major parts: and making a release plan and releasing a process according to the release plan.

1) A plan is published.

As shown in fig. 4, if the target service has multiple requirements, for example, including a requirement a and a requirement B, configuration change information of the requirement a is received and configuration change information of the requirement B is received for the requirement a and the requirement B respectively, so as to complete information collection of the distribution plan of the requirement a and information collection of the distribution plan of the requirement B.

And the demand A release plan can be sent to a preset auditing object for auditing and confirmation, the demand B release plan can be sent to the preset auditing object for auditing and confirmation, automatic aggregation can be carried out after the demand A release plan passes the verification, and a release plan of a target service can be generated.

2) And publishing the process according to the publishing plan.

In the embodiment of the present disclosure, the publishing process may be divided into four stages, including pre-publishing, post-pre-publishing, pre-generating and post-generating, where change synchronization and notification may be performed on configuration change information of each stage according to a publishing plan, and a next stage is performed after configuration state update is completed in each stage, for example, update synchronization and notification is performed before pre-publishing environment deployment, after configuration state update is determined to be completed, pre-publishing environment deployment is performed, change synchronization and notification is performed after pre-publishing environment deployment, change synchronization and notification is performed before production environment deployment is determined to be completed, configuration state update is determined to be completed, production environment deployment is performed, change synchronization and notification is performed after production environment deployment is determined to be performed, and configuration state update in each stage is determined to be completed, that is, follow-up and notification of configuration change information in the entire publishing process is completed, so that unified management of configuration change in a target service may be implemented, omission and sequence error of configuration change may be reduced.

In this way, in the embodiment of the disclosure, the service release method is implemented through the independently operated atomic node, and the atomic node can be deployed at any stage in research and development, test or release according to requirements, so that the atomic node has a flexible use mode, and the unified management of configuration change is implemented in a mode of automatically changing synchronization in the release process by collecting and checking configuration change information in advance, so that the effect of problem interception is achieved, and the release efficiency is improved.

The service publishing method in the embodiment of the present disclosure is described below with another specific application scenario. Taking the whole release process of setting up a certain target service based on a pipeline mode as an example for explanation, for example, referring to fig. 5, a logic block diagram of a delivery process of the target service based on the pipeline mode in the example of the disclosure is shown, and a complete delivery process may be divided into a development stage, a test stage and a release stage, specifically:

1) And (3) a development stage.

As shown in fig. 5, the development phase may include: packaging, planning and deploying each relevant user, and then performing extraction and measurement admittance, wherein research and Development (RESEARCH AND Development, RD) can perform extraction and measurement after the admittance examples provided by quality assurance (quality assurance, QA) pass through.

2) And (3) a testing stage.

The testing stage may include test environment packaging, test deployment by each relevant user, write interface automation, configuration change information collection, and test verification.

In the embodiment of the disclosure, in the testing stage, the requirement filling notification information can be sent to the target user corresponding to each requirement, so that the target user can input the corresponding configuration change information after receiving the requirement filling notification information, and after filling, the user can confirm and support modification after confirmation, thereby meeting the actual requirement.

In addition, in the embodiment of the disclosure, after the test is completed, a release plan of the target service is generated according to each configuration change information, and in order to ensure accuracy, the release plan can be pushed to a corresponding user to be checked and confirmed, and a release stage can be entered after the release plan passes the check, wherein the release plan can comprise a release flow and a rollback flow which needs to be rolled back if a problem occurs.

3) And a release stage.

The release phase includes, for example, processes of packaging, pre-release configuration change synchronization and check, pre-release environment deployment, pre-release configuration change synchronization and check, …, release admission, pre-release configuration change synchronization and check, …, post-release configuration change synchronization and check, on-line notification, and the like.

In the embodiment of the disclosure, after entering the release stage, when different processes in the release stage are completed, the process initiation and the configuration state collection of the worksheet process of the configuration change of the non-code type corresponding to the process can be performed, the code change deployment of the service is performed after all the configuration changes are completed, and the configuration state change is notified in real time, so that all relevant personnel of the target project can acquire the configuration change condition.

In this way, in the embodiment of the disclosure, in the delivery process of the target service based on the pipeline mode, the distribution plan management atomic node can be configured in the pipeline, so that the capability of configuration change management is realized, the configuration change is ensured not to be missed or wrong, the configuration state is transparent and synchronous in real time, the risk of configuration change is reduced, and the distribution efficiency is improved.

It will be appreciated by those skilled in the art that in the above-described method of the specific embodiments, the written order of steps is not meant to imply a strict order of execution but rather should be construed according to the function and possibly inherent logic of the steps.

Based on the same inventive concept, the embodiments of the present disclosure further provide a service publishing device corresponding to the service publishing method, and since the principle of solving the problem by the device in the embodiments of the present disclosure is similar to that of the service publishing method in the embodiments of the present disclosure, the implementation of the device may refer to the implementation of the method, and the repetition is omitted.

Referring to fig. 6, a schematic diagram of a service publishing device according to an embodiment of the present disclosure is shown, where the device includes:

a receiving module 61, configured to receive configuration change information of each requirement issued for a target service, where the configuration change information is input for a requirement filling notification information of a prompt;

A generating module 62, configured to generate a distribution plan of the target service according to the configuration change information of each requirement;

and the release module 63 is configured to perform configuration change and synchronization according to the release plan to complete release of the target service when the release of the target service is triggered.

In an alternative embodiment, before receiving the configuration change information for each requirement of the target service publication, the sending module 64 is further configured to:

In an alternative embodiment, when generating the distribution plan of the target service according to the configuration change information of each requirement, the generating module 62 is configured to:

In an alternative embodiment, after generating the release plan of the target service, the confirmation module 65 is further configured to:

In an alternative embodiment, when performing configuration change and synchronization to complete the release of the target service according to the release plan, the release module 63 is configured to: and calling a service interface of each service platform associated with the configuration change information according to the release plan, carrying out configuration change and synchronization, and determining that after the configuration change and synchronization of each associated service platform are completed, updating the configuration state of the configuration change information to be completed.

In an alternative embodiment, when performing configuration change and synchronization to complete the release of the target service according to the release plan, the release module 63 is configured to: receiving confirmation information of whether the configuration change of each configuration change information in the release plan is completed or not; and when receiving the completed confirmation information, updating the configuration state of the configuration change information to be completed.

In an alternative embodiment, the rollback module 66 is further configured to: and when the problem of the release of the target business is determined, generating a rollback plan according to the release plan so as to perform rollback operation according to the rollback plan.

In an alternative embodiment, before receiving the configuration change information for each requirement of the target service publication, the setting module 67 is further configured to: and receiving the supported configuration type set for the target service, so that corresponding configuration change information is input for the supported configuration type.

The process flow of each module in the apparatus and the interaction flow between the modules may be described with reference to the related descriptions in the above method embodiments, which are not described in detail herein.

The embodiment of the disclosure further provides an electronic device, as shown in fig. 7, which is a schematic structural diagram of the electronic device provided by the embodiment of the disclosure, including:

a processor 71 and a memory 72; the memory 72 stores machine readable instructions executable by the processor 71, the processor 71 being configured to execute the machine readable instructions stored in the memory 72, the machine readable instructions when executed by the processor 71, the processor 71 performing the steps of:

In an alternative embodiment, before receiving the configuration change information for each requirement of the target service release, the processor 71 is further configured to:

determining a target object corresponding to each requirement according to the preset object identifier corresponding to each requirement; and sending requirement filling notification information to the target object corresponding to each requirement so that the target object inputs corresponding configuration change information.

In an alternative embodiment, when generating the distribution plan of the target service according to the configuration change information of each requirement, the processor 71 is configured to:

In an alternative embodiment, after generating the release schedule of the target service, the processor 71 is further configured to:

The release plan is sent to a corresponding preset auditing object, so that whether the preset auditing object passes the release plan or not is confirmed by the preset auditing object; and after the preset auditing object confirms that the release plan passes, determining to trigger the release of the target service.

In an alternative embodiment, when performing configuration change and synchronization to complete the distribution of the target service according to the distribution plan, the processor 71 is configured to: and calling a service interface of each service platform associated with the configuration change information according to the release plan, carrying out configuration change and synchronization, and determining that after the configuration change and synchronization of each associated service platform are completed, updating the configuration state of the configuration change information to be completed.

In an alternative embodiment, when performing configuration change and synchronization to complete the distribution of the target service according to the distribution plan, the processor 71 is configured to: receiving confirmation information of whether the configuration change of each configuration change information in the release plan is completed or not; and when receiving the completed confirmation information, updating the configuration state of the configuration change information to be completed.

In an alternative embodiment, the processor 71 is further configured to: and when the problem of the release of the target business is determined, generating a rollback plan according to the release plan so as to perform rollback operation according to the rollback plan.

The memory 72 includes a memory 721 and an external memory 722; the memory 721 is also referred to as an internal memory, and is used for temporarily storing operation data in the processor 71 and data exchanged with the external memory 722 such as a hard disk, and the processor 71 exchanges data with the external memory 722 via the memory 721.

The specific execution process of the above instruction may refer to the steps of the service issuing method described in the embodiments of the present disclosure, which is not described herein.

The disclosed embodiments also provide a computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the service distribution method described in the above method embodiments. Wherein the storage medium may be a volatile or nonvolatile computer readable storage medium.

The embodiments of the present disclosure further provide a computer program product, where the computer program product carries program code, where instructions included in the program code may be used to perform the steps of the service issuing method described in the foregoing method embodiments, and specifically reference may be made to the foregoing method embodiments, which are not described herein in detail.

Wherein the above-mentioned computer program product may be realized in particular by means of hardware, software or a combination thereof. In an alternative embodiment, the computer program product is embodied as a computer storage medium, and in another alternative embodiment, the computer program product is embodied as a software product, such as a software development kit (Software Development Kit, SDK), or the like.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described system and apparatus may refer to corresponding procedures in the foregoing method embodiments, which are not described herein again. In the several embodiments provided in the present disclosure, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. The above-described apparatus embodiments are merely illustrative, for example, the division of the units is merely a logical function division, and there may be other manners of division in actual implementation, and for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some communication interface, device or unit indirect coupling or communication connection, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present disclosure may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a non-volatile computer readable storage medium executable by a processor. Based on such understanding, the technical solution of the present disclosure may be embodied in essence or a part contributing to the prior art or a part of the technical solution, or in the form of a software product stored in a storage medium, including several instructions for causing an electronic device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in the embodiments of the present disclosure. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

Finally, it should be noted that: the foregoing examples are merely specific embodiments of the present disclosure, and are not intended to limit the scope of the disclosure, but the present disclosure is not limited thereto, and those skilled in the art will appreciate that while the foregoing examples are described in detail, it is not limited to the disclosure: any person skilled in the art, within the technical scope of the disclosure of the present disclosure, may modify or easily conceive changes to the technical solutions described in the foregoing embodiments, or make equivalent substitutions for some of the technical features thereof; such modifications, changes or substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the disclosure, and are intended to be included within the scope of the present disclosure. Therefore, the protection scope of the present disclosure shall be subject to the protection scope of the claims.

Claims

1. A service distribution method, comprising:

2. The method of claim 1, further comprising, prior to receiving configuration change information for each requirement of the target service publication:

3. The method according to claim 1 or 2, wherein generating the distribution plan of the target service according to the configuration change information of each requirement includes:

4. The method of claim 3, further comprising, after generating the release schedule for the target service:

5. The method of claim 1, wherein performing configuration changes and synchronization to complete the publication of the target service according to the publication plan comprises:

And calling a service interface of each service platform associated with the configuration change information according to the release plan, carrying out configuration change and synchronization, and determining that after the configuration change and synchronization of each associated service platform are completed, updating the configuration state of the configuration change information to be completed.

6. The method of claim 1, wherein performing configuration changes and synchronization to complete the publication of the target service according to the publication plan comprises:

Receiving confirmation information of whether the configuration change of each configuration change information in the release plan is completed or not;

And when receiving the completed confirmation information, updating the configuration state of the configuration change information to be completed.

7. The method of any one of claims 1-6, further comprising:

And when the problem of the release of the target business is determined, generating a rollback plan according to the release plan so as to perform rollback operation according to the rollback plan.

8. The method according to claim 1 or 2, further comprising, before receiving the configuration change information for each requirement of the target service release:

9. The method according to claim 1, characterized in that the service publication method is implemented based on an atomic node being set, which is deployed in any publication stage involved in the target service publication.

10. A service issuing apparatus, comprising:

11. An electronic device, comprising: a processor, a memory storing machine-readable instructions executable by the processor for executing the machine-readable instructions stored in the memory, which when executed by the processor, perform the steps of the service distribution method according to any of claims 1 to 9.

12. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a computer program which, when being executed by a processor, performs the steps of the service distribution method according to any of claims 1 to 9.