CN110096284B - A method, device, electronic device and storage medium for visually publishing software - Google Patents

Abstract

The embodiment of the invention provides a method, a device, electronic equipment and a storage medium for visually releasing software, wherein the method comprises the following steps: acquiring software to be distributed, and inquiring deployment information of the distributed software corresponding to the software to be distributed, wherein the deployment information of the distributed software comprises: node information of the nodes deploying the published software and node identification information of the nodes deploying the published software; calling a display interface corresponding to the deployment information of the released software, and displaying the deployment information; acquiring an issuing command input by a worker, issuing software to be issued according to the deployment information of the issued software, and displaying the deployment information of the software to be issued after deployment to a display interface. According to the embodiment of the invention, in the process of releasing the software, the release code is prevented from being manually input, so that the workload of releasing the new version software by a worker can be reduced, and errors in the process of releasing the new version software are reduced.

Description

A method, device, electronic device and storage medium for visually publishing software

technical field

The invention relates to the technical field of the Internet, in particular to a method, device, electronic equipment and storage medium for visually publishing software.

Background technique

With the development of the software industry, the number of software is increasing, and the types of software are also increasing. In order to ensure the stickiness of software to users, under normal circumstances, all kinds of software will update the software version regularly or irregularly. That is to release a new version of the software so that users can use the new version of the software to replace the old version of the software. For example, for a cloud computing service provider, a new version of the cloud server console software can be released on the server, and then the user can use the new version of the cloud server console software released on the server.

However, in the current related technologies, when a new version of software is released, the staff usually manually enters the release code on the back-end equipment connected to the server to realize the release of the new version of the software to the server. . And when there are many release codes, it is easy to input mistakes. Once the release codes are entered incorrectly, the new version of the software will not be released, and it is time-consuming to troubleshoot the error codes.

Contents of the invention

The purpose of the embodiments of the present invention is to provide a method, device, electronic device and storage medium for visually publishing software, so as to reduce the workload of staff for releasing new version software and reduce errors in the process of releasing new version software. The specific technical scheme is as follows:

In the first aspect, an embodiment of the present invention provides a method for visually publishing software, the method comprising:

Obtain the software to be released, and query the deployment information of the released software corresponding to the software to be released, where the deployment information of the released software includes: the node information of the node deploying the released software, the node identification information of the node deploying the released software ;

Call the display interface corresponding to the deployment information of the released software to display the deployment information;

Obtain the release command input by the staff, release the software to be released according to the deployment information of the released software, and display the deployment information of the software to be released on the display interface after deployment.

Optionally, the software to be released has multiple modules to be released, and the software to be released has multiple modules that have been released; the multiple modules to be released have a one-to-one correspondence with the multiple released modules;

Optionally, query the deployment information of released software corresponding to the software to be released, including:

Query the deployment information of each released module of the released software corresponding to the software to be released;

Optionally, call the display interface corresponding to the deployment information of the released software to display the deployment information, including:

Call the display interface corresponding to the deployment information of each released module to display the deployment information of each released module;

Optionally, release the software to be released according to the deployment information of the released software, and display the deployment information of the software to be released on the display interface after deployment, including:

According to the deployment information of each released module, the to-be-released modules corresponding to each released module are released, and the deployment information of each to-be-released module of the software to be released is displayed on the display interface after deployment.

Optionally, release the software to be released according to the deployment information of the released software, including:

Deploy the software to be released to the node corresponding to the deployment information of the released software.

Optionally, release the software to be released according to the deployment information of the released software, and display the deployment information of the software to be released on the display interface after deployment, including:

Deploy the software to be released to the nodes to be released with the same number of nodes as the nodes of the released software, and deploy the software to be released to the nodes to be released;

Modify the node information of the node to be released according to the node information of the node of the released software, and display the modified node information of the node to be released on the display interface.

Optionally, the method for visually publishing software also includes: obtaining the traffic switching time input by the staff;

After displaying the modified node information of the node to be released on the display interface, optionally, the method for visually publishing software further includes:

According to the traffic switching time, the traffic of the published node deploying the released software is switched to the unpublished node deploying the software to be released.

Optionally, switch the traffic of the published node deploying the released software to the unpublished node deploying the software to be released, including:

Acquiring the first configuration file of the released node deploying the released software and the second configuration file of the unpublished node deploying the software to be released;

Modify the second configuration file to the first configuration file;

Restart the node to be released on which the software to be released is deployed, so that the modified second configuration file takes effect.

In the second aspect, the embodiment of the present invention also provides a device for visually releasing software, the device comprising:

The obtaining module is used to obtain the software to be released, and query the deployment information of the released software corresponding to the software to be released, wherein the deployment information of the released software includes: the node information of the node deploying the released software, the node information of the deployed software The node identification information of the node;

The display module is used to call the display interface corresponding to the deployment information of the published software, and display the deployment information;

The deployment module is used to obtain the release command input by the staff, release the software to be released according to the deployment information of the released software, and display the deployment information of the software to be released on the display interface after deployment.

Optionally, the software to be released has multiple modules to be released, and the software to be released has multiple modules that have been released; the multiple modules to be released have a one-to-one correspondence with the multiple released modules;

Optionally, obtain modules, specifically for:

Query the deployment information of each released module of the released software corresponding to the software to be released;

Optionally, display modules, specifically for:

Call the display interface corresponding to the deployment information of each released module to display the deployment information of each released module;

Optionally, deploy modules, specifically for:

According to the deployment information of each released module, the to-be-released modules corresponding to each released module are released, and the deployment information of each to-be-released module of the software to be released is displayed on the display interface after deployment.

Optionally, deploy modules, specifically for:

Deploy the software to be released to the node corresponding to the deployment information of the released software.

Optionally, deploy modules, including:

The node deployment sub-module is used to deploy the software to be released to the nodes to be released with the same number of nodes as the nodes of the released software, and deploy the software to be released to the nodes to be released;

The node information modification sub-module is used to modify the node information of the node to be released according to the node information of the node of the released software, and display the modified node information of the node to be released to the display interface.

Optionally, the device for visually publishing software also includes: a traffic switching time acquisition module, used to acquire the traffic switching time input by the staff;

The traffic switching module is configured to switch the traffic of the published node deploying the released software to the waiting node deploying the software to be released according to the traffic switching time.

Optionally, the traffic switching module includes:

The configuration file obtaining submodule is used to obtain the first configuration file of the released node deploying the released software and the second configuration file of the unpublished node deploying the software to be released;

The configuration file modification sub-module is used to modify the second configuration file to the first configuration file;

The restart sub-module is used to restart the node to be released on which the software to be released is deployed, so that the modified second configuration file takes effect.

In a third aspect, an embodiment of the present invention also provides an electronic device, including a processor and a machine-readable storage medium, the machine-readable storage medium stores machine-executable instructions that can be executed by the processor, and the processor is executed by the machine Instruction prompts: implement the steps of a method for visually releasing software provided in the first aspect above.

In the fourth aspect, the embodiment of the present invention also provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed by the processor, the visual release software provided in the first aspect above is implemented. method steps.

In the fifth aspect, the embodiment of the present invention also provides a computer program product containing instructions, which, when run on a computer, causes the computer to execute the steps of the method for visually publishing software provided in the first aspect above.

In the sixth aspect, the embodiment of the present invention also provides a computer program, which, when running on a computer, causes the computer to execute the steps of the method for visually publishing software provided in the first aspect above.

The embodiments of the present invention provide a method, device, electronic device, and storage medium for visually publishing software. After obtaining the software to be released, the deployment information of the released software corresponding to the software to be released can be queried. Then call the display interface corresponding to the deployment information of the released software to display the deployment information, so that the staff can clearly understand the deployment of the released software. Information publishes the software to be released. After the software to be released is released, the deployment information of the software to be released after deployment can be displayed on the display interface. In this way, the staff can clearly understand the release situation of the software to be released. It can be seen that through the embodiment of the present invention, in the software release process, manual input of the release code is avoided, thereby reducing the cost of the staff to release the new version of the software. Reduce workload and reduce errors during the release of new version software. Of course, implementing any product or method of the present invention does not necessarily need to achieve all the above-mentioned advantages at the same time.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only These are some embodiments of the present invention. Those skilled in the art can also obtain other drawings based on these drawings without creative work.

FIG. 1 is a flowchart of a first implementation of a method for visually publishing software according to an embodiment of the present invention;

FIG. 2 is a flowchart of a second implementation of a method for visually publishing software according to an embodiment of the present invention;

Fig. 3 is a schematic diagram of a display interface in the method for visually releasing software shown in Fig. 2;

FIG. 4 is a flow chart of a third implementation of a method for visually publishing software according to an embodiment of the present invention;

Fig. 5 is a schematic diagram of a display interface in the method for visually publishing software shown in Fig. 4;

FIG. 6 is a flowchart of a fourth implementation manner of a method for visually publishing software according to an embodiment of the present invention;

FIG. 7 is a flowchart of a fifth implementation manner of a method for visually publishing software according to an embodiment of the present invention;

FIG. 8 is a schematic structural diagram of an apparatus for visually publishing software according to an embodiment of the present invention;

FIG. 9 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some, not all, embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

In order to solve the problems existing in the prior art, the embodiment of the present invention provides a method, device, electronic equipment, and storage medium for visually publishing software, so as to reduce the workload of staff for releasing new version software and reduce the process of releasing new version software error in .

In the following, a method for visually distributing software according to an embodiment of the present invention is firstly introduced. As shown in FIG. 1 , it is a flowchart of a first implementation mode of a method for visually distributing software according to an embodiment of the present invention. The method may include :

S110. Acquire software to be released, and query deployment information of released software corresponding to the software to be released.

Wherein, the deployment information of the released software includes: the node information of the node deploying the released software, the node identification information of the node deploying the released software, the node information of the node deploying the released software may include: the node information of the node deploying the released software IP address, port information, etc.

In some examples, when an electronic device using a method for visually releasing software according to an embodiment of the present invention releases the software to be released, the staff can first upload the software to be released to the electronic device, so that the electronic device can obtain to the software to be released.

After the above-mentioned electronic device obtains the software to be released, it can call the display interface corresponding to the software to be released, and display the software to be released, so that the staff can see each file in the software to be released and the software to be released. The structure of the released software to ensure that the software uploaded is the software to be released.

In some examples, after acquiring the software to be released, the electronic device may query deployment information of released software corresponding to the software to be released. To keep staff informed about the deployment of the released software.

In some examples, the software to be released may be the software of the next version of the released software, and the released software may be the software of the previous version of the software to be released. For version iteration, the two versions of the software must have the same deployment status to reduce the impact of version iteration on user usage.

In some examples, the node may be multiple server nodes deployed at different locations, or multiple server nodes deployed at the same location to provide services for users in different regions.

S120. Invoking a display interface corresponding to the deployment information of the published software to display the deployment information.

After obtaining the deployment information of the released software, the above-mentioned electronic device can call a display interface corresponding to the deployment information of the released software to display the deployment information, so that the staff can view the deployment information of the released software.

S130. Obtain a release command input by the staff, release the software to be released according to the deployment information of the released software, and display the deployed deployment information of the software to be released on the display interface.

In some examples, the display interface corresponding to the deployment information of the released software may provide a button of "Start Publishing", and the staff may click the "Start Publishing" button after checking the deployment information of the released software, Release the software to be released.

After the aforementioned electronic device obtains the release command input by the staff, it can release the software to be released according to the deployment information of the released software.

In some examples, when the electronic device releases the software to be released according to the deployment information of the released software, the electronic device may deploy the software to be released to the node corresponding to the deployment information of the released software. That is, the software to be released is sent to the node corresponding to the deployment information of the released software, and then the released software is deleted in each node.

In some examples, after the above-mentioned electronic device releases the software to be released, in order to enable the staff to clearly understand the release situation of the software to be released, the deployment information of the software to be released after deployment can be displayed on the display interface . In some examples, the display interface may be the same as or similar to the display interface corresponding to the published software.

Through a method for visually publishing software in an embodiment of the present invention, after obtaining the software to be released, the deployment information of the released software corresponding to the software to be released can be queried. Then call the display interface corresponding to the deployment information of the released software to display the deployment information, so that the staff can clearly understand the deployment of the released software. Information publishes the software to be released. After the software to be released is released, the deployment information of the software to be released after deployment can be displayed on the display interface. In this way, the staff can clearly understand the release situation of the software to be released. It can be seen that through the embodiment of the present invention, in the software release process, manual input of the release code is avoided, thereby reducing the cost of the staff to release the new version of the software. Reduce workload and reduce errors during the release of new version software.

In some examples, the to-be-released software may have multiple to-be-released modules, and the released software may also have multiple released modules; the multiple to-be-released modules have a one-to-one correspondence with the multiple released modules. Multiple Released Modules of the Released Software may be deployed on different nodes.

In this regard, on the basis of the method for visually publishing software shown in FIG. 1, the embodiment of the present invention also provides a possible implementation, as shown in FIG. A flow chart of the second embodiment of the method, the method may include:

S111. Acquire the software to be released, and query the deployment information of each released module of the released software corresponding to the software to be released.

In some examples, when the released software has multiple released modules, and the multiple released modules are deployed on different nodes, the above-mentioned electronic device is querying the deployment information of the released software corresponding to the software to be released , you can query the deployment information of each released module of the released software.

In some examples, the released module may be a software module of the released software, which may be used to provide users with a part of specific services in the released software.

S121, call a display interface corresponding to the deployment information of each released module, and display the deployment information of each released module.

After the above-mentioned electronic device inquires about the deployment information of each released module of the released software corresponding to the software to be released, it can call a display interface corresponding to the deployment information of each released module to display the deployment information of each released module. information. As shown in FIG. 3 , it is a schematic diagram of a display interface in a method for visually publishing software shown in FIG. 2 , and the display interface can display deployment information of the host console module in the published cloud host management software. In Figure 3, the task name is "host console switching", which is a module in the cloud host management software, and the module "kec-api-preview" is the English name of the host console control module, see Figure 3, the host The console module is deployed on two nodes, namely "Node 1" and "Node 2". The node information of "Node 1" is the IP address "10.69.32.54" of "Node 1", and the node information of "Node 2" The IP address "10.69.32.232" of the "node 2", it can be seen that the host console module is deployed on two different nodes.

By displaying the deployment information of each released module of the released software, the staff can clearly know the node information and node name of the node where each released module of the released software is deployed.

S131. Obtain the release command input by the staff, release the modules to be released corresponding to each released module according to the deployment information of each released module, and display the deployed deployment information of each module to be released of the software to be released to UI.

After the above-mentioned electronic device displays the deployment information of each released module, the staff can check the nodes where each released module is deployed to ensure the normal operation of the nodes where each released module is deployed, and then input a release command. Therefore, the above-mentioned electronic device can receive the issuing command input by the worker.

After receiving the release command input by the staff, the above-mentioned electronic device can release the corresponding module to be released according to the deployment information of each released module, and after the release of the corresponding module to be released is completed, it can display the module to be released. Publish the deployment information of each module to be released in the software to the display interface for the staff to review.

Through the embodiment of the present invention, each module to be released of the software to be released can be deployed according to the deployment information of each released module of the released software, so that each module to be released can be deployed on different nodes. The flexibility of the method for visually publishing software applied in the embodiment of the present invention is increased.

On the basis of the method for visually distributing software shown in FIG. 1 , this embodiment of the present invention also provides a possible implementation, as shown in FIG. 4 , which is a third method for visually distributing software in an embodiment of the present invention. In the flow chart of this embodiment, in step S120, after calling the display interface corresponding to the deployment information of the released software and displaying the deployment information, the method may include:

S132. Deploy the software to be released to the nodes to be released with the same number of nodes as the nodes of the released software, and deploy the software to be released to the nodes to be released.

In some examples, in addition to deploying the software to be released to the node of the released software, the above-mentioned electronic device can also pre-set the node to be released for the software to be released, and then upload the software to be released to the node to be released in the publishing node.

In some examples, the electronic device may be communicatively connected to a plurality of nodes, and then, among the plurality of nodes, a node having the same number of nodes as the nodes having released the software is selected as a node to be released.

After the above-mentioned electronic device selects the node to be released to obtain the software to be released, in order to release the software to be released, the software to be released may be uploaded to the node to be released.

S133. Modify the node information of the node to be released according to the node information of the node of the released software, and display the modified node information of the node to be released on the display interface.

After the above-mentioned electronic device uploads the software to be released to the node to be released, in order for the user to access the node to be released to complete the release of the software to be released, the software can be modified according to the node information of the node of the released software. Node information of the node to be published.

For example, it is assumed that the node information of the node to be released is the IP address of the node to be released in the intranet of the company. The node information of the published node is the IP address of the published node in the external network, then the electronic device can modify the IP address of the node to be published in the company's intranet to the IP address of the published node in the external network . In this way, the user can access the node to be published through the IP address of the external network.

In some examples, after the above-mentioned electronic device modifies the node information of the node to be released, it may display the modified node information of the node to be released, for example, as shown in FIG. 5 , as shown in FIG. 4 The schematic diagram of the display interface in the method of visual publishing software, in Figure 5, may include the nodes to be released "Node 1" and "Node 2", and the modified node information corresponding to "Node 1" is the IP address "10.69.32.229 ", the modified status is "successful"; the modified node information corresponding to "node 2" is the IP address "10.69.32.228", and the modified status is "successful".

In some examples, the above-mentioned electronic device can also output the log file during the modification process. When the modification is successful, the log file that is successfully modified can be output as the correct file. When the modification fails, the log file that cannot be modified can be used as an error file. Output, so that the staff can view the errors that occur according to the error file, so as to correct the errors.

In some examples, when the node information is modified, some reminder information or alarm information may appear. For this, the above-mentioned electronic device also provides an operation for the reminder information or alarm information, and the operation for the reminder information or alarm information Can include Ignore, Repeat, and Stop. Wherein, the "ignore" operation is used to ignore the reminder information or the alarm information, and the "repeat" operation is used to repeatedly execute the step of modifying the node information after the reminder information or the alarm information appears. The "stop" operation is used to stop executing the step of modifying node information after a reminder message or an alarm message appears.

Through the embodiment of the present invention, it is convenient for the staff to release the software to be released, that is, by modifying the node information of the node corresponding to the software to be released, the release of the software to be released can be realized, thereby reducing the number of staff members to release new versions of software. workload.

On the basis of the method for visually distributing software shown in Figure 2, this embodiment of the present invention also provides a possible implementation, as shown in Figure 6, which is the fourth method for visually distributing software in this embodiment of the present invention In the flow chart of this embodiment, in step S121, after calling the display interface corresponding to the deployment information of each released module and displaying the deployment information of each released module, the method may include:

S134. For each to-be-released module of the software to be released, set the same to-be-released node as the nodes of each released module of the released software, and deploy each to-be-released module of the to-be-released software to the corresponding to-be-released node.

In some examples, when the software to be released has multiple modules to be released, and the software to be released has multiple modules that have been released, the above-mentioned electronic device can set a released module corresponding to the module to be released for each module to be released. The module node is the same as the node to be released, and then the module to be released is uploaded to the corresponding node to be released.

In this way, each module to be released of the software to be released can have a corresponding node to be released.

S135. According to the node information of the nodes of each released module of the released software, modify the node information of the corresponding to-be-released node of the to-be-released module, and display the modified node information of the to-be-released module of the to-be-released node on the display interface.

After the above-mentioned electronic device has set corresponding nodes to be released for each module of the software to be released, in order to allow users to access each node to be released, so that each module in the node to be released can serve the user, the above-mentioned electronic device The device may modify the node information of the nodes to be released of the corresponding modules to be released according to the node information of the nodes of the released modules of the released software.

For example, suppose the software to be released has "Module 1 to be released" and "Module 2 to be released", the software to be released has "Module 1 to be released" and "Module 2 to be released", and "Module In node 1" and "released node 2", "released module 2" is set in "released node 3" and "released node 4", then the above-mentioned electronic device can be set for the "to be released module 1" "Node 1 to be released" and "Node to be released 2", set "node 3 to be released" and "node 4 to be released" for the "module 2 to be released".

Then, the above-mentioned electronic device can upload "module 1 to be released" to "node 1 to be released" and "node 2 to be released", and upload "module 2 to be released" to "node 3 to be released" and "node 2 to be released" respectively. Publish node 4".

Finally, the node information of "Node 1 to be released" can be modified according to the node information of "Node 1 released", and the node information of "Node 2 to be released" can be modified according to the node information of "Node 2 to be released". The node information of the "published node 3" is modified to the node information of the "to-be-published node 3", and the node information of the "to-be-published node 4" is modified according to the node information of the "published node 4".

In this way, the software to be released can completely replace the released software to provide services to users after it is released.

After the modification of the node information of the above-mentioned electronic device is completed, in order to enable the staff to view the modified node information of the node to be released, the node information of the module to be released of the modified node to be released can be displayed on the display interface.

Through the embodiment of the present invention, the staff can clearly understand the deployment status of each module to be released, and when a problem occurs during the deployment process, they can clearly understand the module to be released or the module to be released corresponding to the problem. Release nodes, which can facilitate troubleshooting and reduce the workload of staff to release new versions of software.

On the basis of the method for visually publishing software shown in Figure 4, the embodiment of the present invention also provides a possible implementation, as shown in Figure 7, which is the fifth method for visually publishing software in the embodiment of the present invention In the flow chart of this embodiment, in S133, after modifying the node information of the node to be released according to the node information of the node that has released the software, and displaying the modified node information of the node to be released to the display interface, the method of visually releasing software , which can also include:

S140. Obtain the traffic switching time input by the staff.

S150. According to the traffic switching time, switch the traffic of the released node deploying the released software to the waiting node deploying the software to be released.

In some examples, after the software to be released is released, users can access the software to be released, that is, user traffic corresponding to the released software is switched to the released software to be released.

In some examples, the above-mentioned electronic device may start traffic switching after displaying the modified node information of the node to be published on the display interface.

In some examples, the above-mentioned display interface can also be provided with a "switch traffic" button, which the staff can click on. After the flow command, start the flow switching.

In some other examples, the above-mentioned display interface may also be provided with an input box of "flow switching time", and the staff may input the time of switching the flow in the input box. After receiving the switching traffic time input by the staff, the above-mentioned electronic device can switch the traffic of the published node deploying the released software to the waiting node deploying the software to be released according to the switching traffic time.

In some examples, the above-mentioned electronic device may adopt the following steps to switch the traffic of the published node deploying the released software to the unpublished node deploying the software to be released:

Step A, obtaining the first configuration file of the released node deploying the released software and the second configuration file of the unpublished node deploying the software to be released.

Step B, modify the second configuration file to the first configuration file.

Step C, restarting the node to be released on which the software to be released is deployed, so that the modified second configuration file takes effect.

In some examples, the configuration file may be the published correspondence between the IP address of the node and the domain name. By modifying the configuration file, the to-be-released node of the software to be released can have the same configuration file as the released node of the released software. Thus, the user can access the node to be published.

After the above-mentioned electronic device modifies the second configuration file of the node to be released, in order to make the second configuration file take effect, it may send a restart instruction to the node to be released deploying the software to be released, so that the node to be released is restarted. , after the node to be released is restarted, the modified second configuration file will take effect.

When the above-mentioned electronic device switches the traffic of the published node deploying the released software to the unpublished node deploying the software to be released, it can be switched according to the percentage of the total traffic, for example, the total traffic of the published node that will deploy the released software 30% of the traffic will be switched to the unpublished node deploying the software to be released, or 50% of the total traffic of the published nodes deploying the released software will be switched to the unpublished node deploying the unpublished software Publish node.

Through the embodiment of the present invention, it is possible to automatically switch the traffic at regular intervals, and it is not necessary for the staff to manually switch the traffic, so that the workload of the staff for releasing new version software can be reduced.

Corresponding to the above-mentioned method embodiment, the embodiment of the present invention also provides a device for visually publishing software, as shown in FIG. 8 , which is a schematic structural diagram of a device for visually publishing software according to an embodiment of the present invention. :

The obtaining module 810 is used to obtain the software to be released, and query the deployment information of the released software corresponding to the software to be released, wherein the deployment information of the released software includes: the node information of the node deploying the released software, the deployment information of the released software The node identification information of the node;

A display module 820, configured to call a display interface corresponding to the deployment information of the published software, and display the deployment information;

The deployment module 830 is configured to acquire the release command input by the staff, release the software to be released according to the deployment information of the released software, and display the deployed deployment information of the software to be released on the display interface.

An apparatus for visually publishing software in an embodiment of the present invention can query deployment information of released software corresponding to the software to be released after acquiring the software to be released. Then call the display interface corresponding to the deployment information of the released software to display the deployment information, so that the staff can clearly understand the deployment of the released software. Information publishes the software to be released. After the software to be released is released, the deployment information of the software to be released after deployment can be displayed on the display interface. In this way, the staff can clearly understand the release situation of the software to be released. It can be seen that through the embodiment of the present invention, in the software release process, manual input of the release code is avoided, thereby reducing the cost of the staff to release the new version of the software. Reduce workload and reduce errors during the release of new version software.

In some examples, the software to be released has multiple modules to be released, and the software to be released has multiple modules that have been released; the multiple modules to be released have a one-to-one correspondence with the multiple released modules;

In some examples, module 810 is obtained for:

Query the deployment information of each released module of the released software corresponding to the software to be released;

In some examples, module 820 is shown for:

Call the display interface corresponding to the deployment information of each released module to display the deployment information of each released module;

In some examples, module 830 is deployed to:

According to the deployment information of each released module, the to-be-released modules corresponding to each released module are released, and the deployment information of each to-be-released module of the software to be released is displayed on the display interface after deployment.

In some examples, module 830 is deployed to:

Deploy the software to be released to the node corresponding to the deployment information of the released software.

In some examples, the deployment module 830 includes:

The node deployment sub-module is used to deploy the software to be released to the nodes to be released with the same number of nodes as the nodes of the released software, and deploy the software to be released to the nodes to be released;

The node information modification sub-module is used to modify the node information of the node to be released according to the node information of the node of the released software;

In some examples, the device for visually publishing software also includes: a traffic switching time acquisition module, configured to acquire the traffic switching time input by the staff;

The traffic switching module is configured to switch the traffic of the published node deploying the released software to the waiting node deploying the software to be released according to the traffic switching time.

In some examples, traffic switching modules include:

The configuration file obtaining submodule is used to obtain the first configuration file of the released node deploying the released software and the second configuration file of the unpublished node deploying the software to be released;

The configuration file modification sub-module is used to modify the second configuration file to the first configuration file;

The restart sub-module is used to restart the node to be released on which the software to be released is deployed, so that the modified second configuration file takes effect.

An embodiment of the present invention also provides an electronic device. As shown in FIG. 9 , it is a schematic structural diagram of a method for visually publishing software in an embodiment of the present invention applied to an electronic device. The electronic device may include a processor 901 and a machine that can Read the storage medium 902, the machine-readable storage medium 902 stores machine-executable instructions that can be executed by the processor 901, and the processor 901 is prompted by the machine-executable instructions: implement the following steps:

Obtain the software to be released, and query the deployment information of the released software corresponding to the software to be released, wherein the deployment information includes: the node information of the node deploying the released software, and the node identification information of the node deploying the released software;

Call the display interface corresponding to the deployment information of the released software to display the deployment information;

Obtain the release command input by the staff, release the software to be released according to the deployment information of the released software, and display the deployment information of the software to be released on the display interface after deployment.

The machine-readable storage medium 902 may include a random access memory (Random Access Memory, RAM), and may also include a non-volatile memory (Non-Volatile Memory, NVM), such as at least one magnetic disk memory. Optionally, the memory may also be at least one storage device located far away from the aforementioned processor.

The above-mentioned processor 901 can be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), etc.; it can also be a digital signal processor (DigitalSignal Processing, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

An electronic device according to an embodiment of the present invention can query deployment information of released software corresponding to the software to be released after acquiring the software to be released. Then call the display interface corresponding to the deployment information of the released software to display the deployment information, so that the staff can clearly understand the deployment of the released software. Information publishes the software to be released. After the software to be released is released, the deployment information of the software to be released after deployment can be displayed on the display interface. In this way, the staff can clearly understand the release situation of the software to be released. It can be seen that through the embodiment of the present invention, in the software release process, manual input of the release code is avoided, thereby reducing the cost of the staff to release the new version of the software. Reduce workload and reduce errors during the release of new version software.

The embodiment of the present invention also provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, the following steps are implemented:

Obtain the software to be released, and query the deployment information of the released software corresponding to the software to be released, wherein the deployment information includes: the node information of the node deploying the released software, and the node identification information of the node deploying the released software;

Call the display interface corresponding to the deployment information of the released software to display the deployment information;

Obtain the release command input by the staff, release the software to be released according to the deployment information of the released software, and display the deployment information of the software to be released on the display interface after deployment.

A computer-readable storage medium according to an embodiment of the present invention can query deployment information of released software corresponding to the software to be released after acquiring the software to be released. Then call the display interface corresponding to the deployment information of the released software to display the deployment information, so that the staff can clearly understand the deployment of the released software. Information publishes the software to be released. After the software to be released is released, the deployment information of the software to be released after deployment can be displayed on the display interface. In this way, the staff can clearly understand the release situation of the software to be released. It can be seen that through the embodiment of the present invention, in the software release process, manual input of the release code is avoided, thereby reducing the cost of the staff to release the new version of the software. Reduce workload and reduce errors during the release of new version software.

The embodiment of the present invention also provides a computer program product containing instructions, which, when run on a computer, causes the computer to perform the following steps:

Obtain the software to be released, and query the deployment information of the released software corresponding to the software to be released, wherein the deployment information includes: the node information of the node deploying the released software, and the node identification information of the node deploying the released software;

Call the display interface corresponding to the deployment information of the released software to display the deployment information;

Obtain the release command input by the staff, release the software to be released according to the deployment information of the released software, and display the deployment information of the software to be released on the display interface after deployment.

A computer program product including instructions according to an embodiment of the present invention can query deployment information of released software corresponding to the software to be released after acquiring the software to be released. Then call the display interface corresponding to the deployment information of the released software to display the deployment information, so that the staff can clearly understand the deployment of the released software. Information publishes the software to be released. After the software to be released is released, the deployment information of the software to be released after deployment can be displayed on the display interface. In this way, the staff can clearly understand the release situation of the software to be released. It can be seen that through the embodiment of the present invention, in the software release process, manual input of the release code is avoided, thereby reducing the cost of the staff to release the new version of the software. Reduce workload and reduce errors during the release of new version software.

An embodiment of the present invention also provides a computer program that, when run on a computer, causes the computer to perform the following steps:

Obtain the software to be released, and query the deployment information of the released software corresponding to the software to be released, wherein the deployment information includes: the node information of the node deploying the released software, and the node identification information of the node deploying the released software;

Call the display interface corresponding to the deployment information of the released software to display the deployment information;

Obtain the release command input by the staff, release the software to be released according to the deployment information of the released software, and display the deployment information of the software to be released on the display interface after deployment.

A computer program according to an embodiment of the present invention can query deployment information of released software corresponding to the software to be released after acquiring the software to be released. Then call the display interface corresponding to the deployment information of the released software to display the deployment information, so that the staff can clearly understand the deployment of the released software. Information publishes the software to be released. After the software to be released is released, the deployment information of the software to be released after deployment can be displayed on the display interface. In this way, the staff can clearly understand the release situation of the software to be released. It can be seen that through the embodiment of the present invention, in the software release process, manual input of the release code is avoided, thereby reducing the cost of the staff to release the new version of the software. Reduce workload and reduce errors during the release of new version software.

It should be noted that in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that there is a relationship between these entities or operations. There is no such actual relationship or order between them. Furthermore, the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus comprising a set of elements includes not only those elements, but also includes elements not expressly listed. other elements of or also include elements inherent in such a process, method, article, or device. Without further limitations, an element defined by the phrase "comprising a ..." does not preclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element.

Each embodiment in this specification is described in a related manner, the same and similar parts of each embodiment can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for relevant parts, refer to part of the description of the method embodiment.

The foregoing are only preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principles of the present invention are included in the protection scope of the present invention.

Claims (12)

1. A method for visual release software, characterized in that the method comprises: Acquiring the software to be released, and querying the deployment information of the released software corresponding to the software to be released, wherein the deployment information of the released software includes: node information of the node deploying the released software, deploying the released software Node identification information of the node that released the software; calling a display interface corresponding to the deployment information of the released software to display the deployment information; Obtaining the release command input by the staff, publishing the software to be released according to the deployment information of the released software, and displaying the deployment information of the software to be released on the display interface after deployment; The publishing of the software to be released according to the deployment information of the released software, and displaying the deployment information of the software to be released to the display interface after deployment includes: Deploying to-be-released nodes the same number of nodes as the nodes of the released software to the to-be-released software, and deploying the to-be-released software to the to-be-released nodes; Modifying the node information of the node to be released according to the node information of the node of the released software, and displaying the modified node information of the node to be released on the display interface. 2. The method according to claim 1, wherein the software to be released has a plurality of modules to be released, and the released software has a plurality of released modules; released modules have a one-to-one correspondence; The querying of deployment information of released software corresponding to the software to be released includes: Querying the deployment information of each released module of the released software corresponding to the software to be released; The calling the display interface corresponding to the deployment information of the released software to display the deployment information includes: calling a display interface corresponding to the deployment information of each released module, and displaying the deployment information of each released module; The publishing of the software to be released according to the deployment information of the released software, and displaying the deployment information of the software to be released to the display interface after deployment includes: According to the deployment information of each released module, publish the modules to be released corresponding to the released modules, and display the deployed deployment information of each module to be released of the software to be released on the display interface. 3. The method according to claim 1, wherein publishing the software to be released according to the deployment information of the released software comprises: Deploying the software to be released to nodes corresponding to the deployment information of the released software. 4. The method according to claim 1, further comprising: obtaining the traffic switching time input by the staff; After displaying the modified node information of the node to be published on the display interface, the method further includes: According to the traffic switching time, switch the traffic of the published node deploying the released software to the unpublished node deploying the software to be released. 5. The method according to claim 4, wherein the switching the traffic of the published node deploying the released software to the unpublished node deploying the software to be released comprises: Acquiring a first configuration file of the published node deploying the released software and a second configuration file of the unpublished node deploying the unpublished software; modifying the second configuration file to the first configuration file; Restarting the to-be-released node deploying the to-be-released software, so that the modified second configuration file takes effect. 6. A device for visually publishing software, characterized in that the device comprises: An acquisition module, configured to acquire the software to be released, and query the deployment information of the released software corresponding to the software to be released, wherein the deployment information of the released software includes: node information of the node where the released software is deployed . Node identification information of the node deploying the released software; A display module, configured to call a display interface corresponding to the deployment information of the published software, and display the deployment information; The deployment module is used to obtain the release command input by the staff, publish the software to be released according to the deployment information of the released software, and display the deployment information of the software to be released on the display interface after deployment; The deployment module includes: A node deployment submodule, configured to deploy nodes to be released with the same number of nodes as the nodes of the released software to the software to be released, and deploy the software to be released to the nodes to be released; The node information modification sub-module is used to modify the node information of the node to be released according to the node information of the node of the released software, and display the modified node information of the node to be released on the display interface. 7. The device according to claim 6, wherein the software to be released has a plurality of modules to be released, and the released software has a plurality of released modules; released modules have a one-to-one correspondence; The acquisition module is specifically used for: Querying the deployment information of each released module of the released software corresponding to the software to be released; The display module is specifically used for: calling a display interface corresponding to the deployment information of each released module, and displaying the deployment information of each released module; The deployment module is specifically used for: According to the deployment information of each released module, publish the modules to be released corresponding to the released modules, and display the deployed deployment information of each module to be released of the software to be released on the display interface. 8. The device according to claim 6, wherein the deployment module is specifically used for: Deploying the software to be released to nodes corresponding to the deployment information of the released software. 9. The device according to claim 6, further comprising: a traffic switching time acquisition module, configured to acquire the traffic switching time input by the staff; A traffic switching module, configured to switch the traffic of the published node deploying the released software to the unpublished node deploying the unpublished software according to the traffic switching time. 10. The device according to claim 9, wherein the traffic switching module comprises: The configuration file obtaining submodule is used to obtain the first configuration file of the released node deploying the released software and the second configuration file of the unpublished node deploying the software to be released; a configuration file modification submodule, configured to modify the second configuration file to the first configuration file; The restart sub-module is used to restart the to-be-released node deploying the to-be-released software, so that the modified second configuration file takes effect. 11. An electronic device, characterized in that it comprises a processor and a machine-readable storage medium, the machine-readable storage medium stores machine-executable instructions that can be executed by the processor, and the processor is controlled by the The machine-executable instructions cause: implementing the method steps described in any one of claims 1-5. 12. A computer-readable storage medium, wherein a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, the method according to any one of claims 1 to 5 is implemented step.

Images