CN114398061A

CN114398061A - Publishing method, device, equipment and storage medium

Info

Publication number: CN114398061A
Application number: CN202210040978.5A
Authority: CN
Inventors: 梁江玲
Original assignee: China Construction Bank Corp
Current assignee: China Construction Bank Corp
Priority date: 2022-01-14
Filing date: 2022-01-14
Publication date: 2022-04-26

Abstract

The embodiment of the invention relates to the technical field of big data access, in particular to a publishing method, a publishing device, publishing equipment and a storage medium. The method comprises the following steps: obtaining an issue request, wherein the issue request includes: project configuration information and deployment server configuration information; sending the release request to a target server according to the configuration information of the deployment server so that the target server constructs a release package according to the configuration information of the project; receiving a publishing packet address sent by the target server, and downloading a publishing packet according to the publishing packet address; the method and the device for issuing the target package solve the problems of large workload of manual intervention and high error probability through the technical scheme of the invention, can strip the public part to the maximum extent, and only needs simple configuration by a user, thereby reducing the requirement on the user.

Description

Publishing method, device, equipment and storage medium

Technical Field

The embodiment of the invention relates to the technical field of big data access, in particular to a publishing method, a publishing device, publishing equipment and a storage medium.

Background

For a software system, iterative updating is an essential important link, and program construction and distribution operations are required.

Currently, general operation and maintenance personnel can perform the following methods:

a. operated manually

And local manual compiling, generating an issuing package, uploading the issuing package to a server, and starting the service by inputting a corresponding command. The disadvantages are as follows: each link needs manual intervention, if target servers needing to be published are multiple, the workload can be greatly increased, and meanwhile, the error probability can be increased.

b. Using Jenkins tools

Jenkins provides the ability to continue integration, supporting plug-ins, through a variety of configurations, completely replacing manual operations. The disadvantages are as follows: the interface operation is not intelligent, and if a branch is selected and manual filling is needed, errors can occur. The display is not friendly, and the habit of a general user, such as a constructed process and an information display mode of service starting, is not met. For some complex conditions, such as the dependency relationship between projects, more steps are required to be configured or the writing of shell scripts is complicated, so that the requirements on users are improved. And the authority management and the data filtering among layers which are in accordance with the enterprise specification are not supported.

C. Using the vops tool

Many dehaps tools are available on the market at present, and most of the implementation principles of the dehaps tools depend on Jenkins. The method has the defects that the granularity division is too fine, a plurality of new concepts are promoted, the method is too flexible, the configuration is more, the operation process is complicated, and the method can be used only by special training.

Disclosure of Invention

The embodiment of the invention provides a publishing method, a publishing device, equipment and a storage medium, which not only solve the problems that each link needs manual intervention, the workload is large and the error probability is large because a publishing packet is generated and uploaded to a server through local manual compiling and then a service is started through inputting a corresponding command, but also solve the problems that the Jenkins tool interface is not intelligent in operation and unfriendly in display, the requirements for a user are improved, the public part can be stripped to the maximum extent, and the user only needs simple configuration, so that the requirements for the user are reduced.

In a first aspect, an embodiment of the present invention provides a publishing method, applied to a client, including:

obtaining an issue request, wherein the issue request includes: project configuration information and deployment server configuration information;

sending the release request to a target server according to the configuration information of the deployment server so that the target server constructs a release package according to the configuration information of the project;

receiving a publishing packet address sent by the target server, and downloading a publishing packet according to the publishing packet address;

obtaining the type of the publishing packet, wherein the type of the publishing packet comprises: at least one of a front end package, Jar package, and War package;

and executing target issuing operation on the issuing packet according to the issuing packet type.

Further, receiving the address of the publishing packet sent by the target server, and downloading the publishing packet according to the address of the publishing packet includes:

receiving a publishing packet address sent by the target server;

and when the triggering operation of the downloading control on the issuing request interface is detected, downloading the issuing package according to the issuing package address.

Further, the issuing request further includes: code repository configuration information;

correspondingly, obtaining the issue request includes:

when the triggering operation of the release control on the editing interface is detected, jumping to a release request interface;

when the editing operation of the code warehouse area on the release request interface is detected, obtaining code warehouse configuration information;

when the editing operation of the deployment server area on the release request interface is detected, acquiring the configuration information of the deployment server;

and when the editing operation of the project construction area on the issuing request interface is detected, acquiring project configuration information.

Further, the project configuration information includes: code address, application issue path, and start command.

Further, executing a target publishing operation on the publishing packet according to the publishing packet type, including:

if the release packet is a front-end packet, decompressing the release packet to a path corresponding to the code address;

if the issuing package is a Jar package, moving the issuing package to the application issuing path, and executing a program starting script according to the starting command;

and if the issuing package is the War package, moving the issuing package to a directory corresponding to the application issuing path.

Further, if the publishing packet is a Jar packet, moving the publishing packet to the application publishing path, and executing a program start script according to the start command, including:

if the publishing packet is a Jar packet, killing the back-end service process;

moving the publishing packet to the application publishing path;

executing a program starting script according to the starting command;

and starting the back-end service process.

Further, if the publishing packet is the War packet, moving the publishing packet to the directory corresponding to the application publishing path includes:

if the release packet is War packet, killing the WEB server process;

moving the publishing packet to a directory corresponding to the application publishing path;

and starting the WEB server process.

Further, sending the publishing request to a target server according to the deployment server configuration information, so that the target server constructs a publishing package according to the project configuration information, including:

determining the network state of a target server according to the server quota IP of the issuing end and the service port;

if the network state of the target server is the target state, determining the address information of the target server according to the configuration information of the deployment server;

and sending the publishing request to a target server according to the address information of the target server so that the target server constructs a publishing packet according to the project configuration information.

In a second aspect, an embodiment of the present invention further provides a publishing device, configured at a client, where the publishing device includes:

a first obtaining module, configured to obtain an issue request, where the issue request includes: project configuration information and deployment server configuration information;

the sending module is used for sending the publishing request to a target server according to the configuration information of the deployment server so that the target server constructs a publishing packet according to the project configuration information;

the receiving module is used for receiving the address of the publishing packet sent by the target server and downloading the publishing packet according to the address of the publishing packet;

a second obtaining module, configured to obtain the type of the publishing packet, where the type of the publishing packet includes: at least one of a front end package, Jar package, and War package;

and the execution module is used for executing target issuing operation on the issuing package according to the type of the issuing package.

Further, the receiving module is specifically configured to:

receiving a publishing packet address sent by the target server;

correspondingly, the obtaining module is specifically configured to:

Further, the execution module is specifically configured to:

In a third aspect, an embodiment of the present invention further provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor executes the computer program to implement the method according to any one of the embodiments of the present invention.

In a fourth aspect, the present invention further provides a computer-readable storage medium, on which a computer program is stored, which when executed by a processor implements the method according to any one of the embodiments of the present invention.

In a fifth aspect, the embodiment of the present invention further provides a computer program product, where the computer program implements the method according to any one of the embodiments of the present invention when executed by a processor.

The embodiment of the invention obtains the issuing request, wherein the issuing request comprises the following steps: project configuration information and deployment server configuration information; sending the release request to a target server according to the configuration information of the deployment server so that the target server constructs a release package according to the configuration information of the project; receiving a publishing packet address sent by the target server, and downloading a publishing packet according to the publishing packet address; the method comprises the steps of obtaining the type of the issuing packet, executing target issuing operation on the issuing packet according to the type of the issuing packet, solving the problems that manual compiling is performed locally, the issuing packet is generated and then uploaded to a server, and then corresponding commands are input to start service, so that all links need manual intervention, the workload is large, the error probability is large, and the problems that Jenkins tool interface operation is not intelligent, display is not friendly, the requirement on a user is improved are solved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained according to the drawings without inventive efforts.

FIG. 1a is a flowchart of a publishing method according to a first embodiment of the invention;

FIG. 1b is a flowchart illustrating a release process according to a first embodiment of the present invention;

FIG. 1c is a diagram of a code repository area on a publish request interface in accordance with a first embodiment of the present invention;

FIG. 1d is a diagram of a deployment server area on a publish request interface in a first embodiment of the present invention;

FIG. 1e is a diagram of a project build area on a publish request interface in a first embodiment of the present invention;

FIG. 2 is a flowchart of a publishing method in the second embodiment of the invention;

fig. 3 is a schematic structural diagram of a distribution apparatus in the third embodiment of the present invention;

fig. 4 is a schematic structural diagram of an electronic device in a fourth embodiment of the present invention;

fig. 5 is a schematic structural diagram of a computer-readable storage medium containing a computer program in a fifth embodiment of the present invention.

Detailed Description

The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures. In addition, the embodiments and features of the embodiments in the present invention may be combined with each other without conflict.

Before discussing exemplary embodiments in more detail, it should be noted that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart may describe the operations (or steps) as a sequential process, many of the operations can be performed in parallel, concurrently or simultaneously. In addition, the order of the operations may be re-arranged. The process may be terminated when its operations are completed, but may have additional steps not included in the figure. The processes may correspond to methods, functions, procedures, subroutines, and the like. In addition, the embodiments and features of the embodiments in the present invention may be combined with each other without conflict.

The term "include" and variations thereof as used herein are intended to be open-ended, i.e., "including but not limited to". The term "based on" is "based, at least in part, on". The term "one embodiment" means "at least one embodiment".

It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. Meanwhile, in the description of the present invention, the terms "first", "second", and the like are used only for distinguishing the description, and are not to be construed as indicating or implying relative importance.

According to the technical scheme, the data are acquired, stored and/or processed, and relevant regulations of national laws and regulations are met.

Example one

Fig. 1a is a flowchart of a publishing method according to an embodiment of the present invention, where this embodiment is applicable to a publishing situation, and the method may be executed by a publishing device in an embodiment of the present invention, and the publishing device may be implemented in a software and/or hardware manner, as shown in fig. 1a, the method specifically includes the following steps:

s110, obtaining a publishing request, wherein the publishing request comprises: project configuration information and deployment server configuration information.

Wherein the issuing request may include: project configuration information and deployment server configuration information. The issue request may also include: code repository configuration information, project configuration information, and deployment server configuration information.

Specifically, the manner of obtaining the issue request may be: when the triggering operation of the release control on the editing interface is detected, jumping to a release request interface; when the editing operation of the code warehouse area on the release request interface is detected, obtaining code warehouse configuration information; when the editing operation of the deployment server area on the release request interface is detected, acquiring the configuration information of the deployment server; and when the editing operation of the project construction area on the issuing request interface is detected, acquiring project configuration information.

S120, sending the publishing request to a target server according to the deployment server configuration information so that the target server constructs a publishing package according to the project configuration information.

The method for sending the release request to the target server according to the deployment server configuration information may be as follows: and acquiring the server quota IP of the issuing end and a service port in the configuration information of the deployment server to determine a target server, and sending the issuing request to the target server.

Specifically, the publishing request is sent to a target server according to the deployment server configuration information, so that the target server constructs a publishing packet according to the project configuration information, for example, the publishing request may be sent to the target server to obtain a publishing end server quota IP and a service port in the deployment server configuration information to determine the target server, so that the target server pulls up a latest code according to a branch specified in the project configuration information. If the code is git warehouse code, operating a jgit toolkit to operate the relevant interfaces of git to realize corresponding functions, such as pull, check out and the like, if the code is Svn, operating an svnkit toolkit to realize corresponding operation, and calling a shell script through java to construct a corresponding distribution package.

S130, receiving the address of the publishing packet sent by the target server, and downloading the publishing packet according to the address of the publishing packet.

The method for downloading the publishing packet according to the publishing packet address can be as follows: and when the triggering operation of the downloading control on the issuing request interface is detected, downloading the issuing package according to the issuing package address.

Specifically, the address of the publishing packet sent by the target server is received, and the publishing packet is downloaded according to the address of the publishing packet, for example, the publishing packet may be placed in a file server, and each publishing server is asynchronously notified to perform a publishing operation. And the client receives the publishing packet address sent by the target server and downloads the publishing packet according to the publishing packet address.

S140, obtaining the type of the publishing packet.

Wherein the type of the distribution package comprises: at least one of a head end package, Jar package, and War package.

S150, executing target issuing operation on the issuing package according to the issuing package type.

Specifically, target issuing operation is executed on the issuing package according to the type of the issuing package. For example, if the release packet is a front-end packet, the release packet may be decompressed to a path corresponding to the code address; if the issuing package is a Jar package, moving the issuing package to the application issuing path, and executing a program starting script according to the starting command; and if the issuing package is the War package, moving the issuing package to a directory corresponding to the application issuing path.

Optionally, receiving the publishing packet address sent by the target server, and downloading the publishing packet according to the publishing packet address, including:

receiving a publishing packet address sent by the target server;

The trigger operation may be a preset operation, for example, a single-click download control or a double-click download control, which is not limited in this embodiment of the present invention.

Optionally, the issuing request further includes: code repository configuration information;

correspondingly, obtaining the issue request includes:

Wherein the code repository configuration information comprises: application name, url address, item dependencies, user name, password, and notes.

Wherein the deployment server configuration information comprises: home team, device name, server IP, and remarks.

Wherein the project building area comprises: a front-end project building area and a back-end project building area.

Wherein the project configuration information comprises: front-end project configuration information and back-end project configuration information; the front-end project configuration information includes: the method comprises the steps of building a name, a code address, a deployment server, an application service port, a server root directory, a script, a release environment, a code branch, a release package file name, an application release path, a log complete path and a start command. The backend server configuration information includes: the method comprises the steps of building a name, a code address, a deployment server, an application service port, a server root directory, a script, a release environment, a code branch, a release package file name, an application release path, a log complete path and a start command.

Optionally, sending the publishing request to a target server according to the deployment server configuration information, so that the target server constructs a publishing package according to the project configuration information, where the publishing request includes:

Wherein the target state is a network unobstructed state.

Specifically, the method for determining the network state of the target server according to the credit IP of the issuing end server and the service port may be: inputting the credit IP of the issuing end server and the service port into an objective function to obtain the network state of the target server, where the objective function is a function that is stored in advance and used for determining the network state, and the embodiment of the present invention is not limited to this.

In one illustrative example, jenkins is mainly contrasted. Jenkins have the disadvantage that the user is involved in more configurations and the requirements on the user are higher, as shown in Table 1:

TABLE 1

The embodiment of the invention mainly comprises 2 modules, namely a service building module and a service publishing module. The construction service module is mainly used for building and compiling project codes into a specified package according to the configuration, then sending the package to a directory specified by the file server, and then informing the construction service module. The publishing service module is mainly used for downloading the publishing packet after receiving a publishing request for constructing the service end and then publishing the publishing packet according to conditions. The specific publishing process is shown in fig. 1 b:

1: the user's build issues a request. And jumping to the 2 nd step when the code information is not configured, jumping to the 3 rd step when the server is not configured, and jumping to the 4 th step when the project information is not configured. And jumping to the 5 th step when the related information is configured.

2: the code repository configuration is performed, as shown in fig. 1c, which is a code repository area on the issue request interface in fig. 1 c.

3: and configuring the deployment server, as shown in fig. 1d, where fig. 1d is a deployment server area on the issue request interface.

4: and (4) configuring project construction release information, as shown in fig. 1e, wherein fig. 1e is a project construction area on a release request interface.

5: and monitoring the client network. And judging whether the network of the publishing server is smooth or not through the configured quota IP of the publishing server and the service port.

6: and (5) updating the code. The latest code is pulled according to the specified branch. If the code is git warehouse code, operating the jgit toolkit to operate the relevant interface of git to realize the corresponding function, such as pull, check out and the like, and if the code is Svn, operating the svnkit toolkit to realize the corresponding operation.

7: the build script is executed. And calling the shell script through java to construct a corresponding distribution package.

8: and the publishing packets are put into the file servers, and each publishing server is asynchronously informed of publishing operation. Entering the publishing server portion.

9: and downloading the publishing packet. And when the issuing server receives the issuing request, downloading the issuing package according to the transmitted parameters such as the address of the issuing package and the like.

10: and backing up the old publishing package. And backing up the previous publishing package to prevent the rollback operation when the publishing fails.

11: and judging the type of the distribution packet. When the front package is distributed, the process jumps to the 12 th step, when the front package is Jar package, the process jumps to the 13 th step, and when the front package is War package, the process jumps to the 16 th step.

12: the distribution packet is decompressed to the specified path. And jumping to the step 19 to complete the issuing operation.

13: and killing the back-end service process.

14: the distribution package moves to the specified directory. And according to the project configuration, putting the publishing packet to a specified position.

15: a specified start command is executed. The program start script is executed. And jumping to the step 19 to complete the issuing operation.

16: and killing the WEB server process. Although web servers all support hot deployment, occasionally failure situations are encountered. For insurance, the process is killed.

17: and moving the publishing packet to a specified directory of the WEB server. The Web server program places a directory.

18: and starting the WEB server process.

19: the release is complete.

Data authority isolation: the embodiment of the invention divides the roles of 6 authority types according to the general architecture, departments, project groups, groups and individuals of an enterprise, and is used for mutually isolating data. The method comprises the following specific steps: a. the administrator: and the authority of viewing all data is possessed. b. Comprehensive operation and maintenance management personnel: data of arbitrarily set departments or groups can be seen. c. Department operation and maintenance manager: see the department and all data rights below. d. The project group operation and maintenance manager: the data rights of the group of items and the different groups under the group of items can be seen. e. And (4) small groups of operation and maintenance personnel: see the data of this group plus the data rights of the parent project group. f. Individual developers: only see its own data rights.

The embodiment of the invention divides the system release into 2 parts, one part is responsible for construction, the other part is responsible for release, and the 2 parts of the system encapsulates most of conventional operations, so that the configuration part of the shell script is greatly simplified, and the technical threshold of users is reduced. The build system simply needs to configure the packed commands and then place them in the specified locations (configuration parameters). The issuing system only needs the configuration start command (the configuration parameters can be used) when the Jar package is available, and the front-end packages and War do not need any configuration script.

The embodiment of the invention provides a set of management system integrating a construction function and a release function in a software system. It is characterized in that:

a. the operation is easy: the interface is convenient to operate and simple to configure, most of general operations are packaged at the rear end, and a user can complete the whole configuration work only by setting basic information of a project and a small amount of commonly used shell scripts or without the shell scripts.

b. Real-time: when the building and releasing are used, detailed information of the whole process of network monitoring, code updating, building, file transmission and service starting can be seen in real time under the condition that the terminal is in a blank screen only by one-key operation.

c. Permission: the system also provides control functions of various types of data authorities, such as upwards inheriting public project data by team personnel, downwards operating data of different teams by research and development responsible personnel and the like. Can completely meet the general requirements of enterprises.

d. Logging: the system provides a function of checking transaction logs, is convenient for searching problems, can check the log information of the whole transaction process from the request start to the data return through the transaction pipeline ID, and supports the searching of multiple machines.

It should be noted that the client part may be replaced by executing a corresponding script after the server logs in by using SSH. This can reduce the complexity of first deployment, but will also lose some flexibility, increasing the complexity of executing script configurations. The publish-subscribe function of REDIS may be changed to MQ middleware such as other Kafka, etc., because the publish-subscribe function of REDIS does not guarantee the order of messages, and sometimes the information received by the client is reversed, for example, the information output after the publish process is shown in the front. However, such errors are less important for overall function. But adding a piece of middleware such as Kafka increases the complexity of the overall architecture.

According to the technical scheme of the embodiment, the issuing request is acquired, wherein the issuing request comprises: project configuration information and deployment server configuration information; sending the release request to a target server according to the configuration information of the deployment server so that the target server constructs a release package according to the configuration information of the project; receiving a publishing packet address sent by the target server, and downloading a publishing packet according to the publishing packet address; the method comprises the steps of obtaining the type of the issuing packet, executing target issuing operation on the issuing packet according to the type of the issuing packet, solving the problems that manual compiling is performed locally, the issuing packet is generated and then uploaded to a server, and then corresponding commands are input to start service, so that all links need manual intervention, the workload is large, the error probability is large, and the problems that Jenkins tool interface operation is not intelligent, display is not friendly, the requirement on a user is improved are solved.

Example two

Fig. 2 is a flowchart of an issuing method according to a second embodiment of the present invention, where the present embodiment is optimized based on the foregoing embodiment, and as shown in fig. 2, the method specifically includes the following steps:

s210, when the triggering operation of the release control on the editing interface is detected, jumping to a release request interface.

Wherein the issue request interface includes: a code warehouse area, a deployment server area, and a project build area. Wherein the project building area comprises: a front-end project building area and a back-end project building area.

Specifically, when the triggering operation of the release control on the editing interface is detected, the user jumps to the release request interface. For example, a user clicking a publishing control on the editing interface is detected, and then the user jumps to a publishing request interface.

And S220, acquiring code warehouse configuration information when the editing operation of the code warehouse area on the release request interface is detected.

Wherein the editing operation comprises: an input operation and/or a selection operation.

Specifically, when the editing operation on the code repository area on the release request interface is detected, the manner of obtaining the code repository configuration information may be: after the input operation of the code warehouse area on the release request interface is detected, when the selection operation of a user on a determination control of the code warehouse area on the release request interface is detected, the code warehouse configuration information is obtained.

Specifically, the code repository configuration information is obtained when an editing operation on the code repository area on the release request interface is detected, for example, the code repository configuration information is obtained when a selection operation of a user on data in a drop-down box of the code repository area on the release request interface is detected.

And S230, acquiring the configuration information of the deployment server when the editing operation of the deployment server area on the release request interface is detected.

Specifically, when the editing operation on the deployment server area on the release request interface is detected, the manner of acquiring the deployment server configuration information may be: after the input operation of the user on the deployment server area on the release request interface is detected, when the touch operation of the user on the determination control of the deployment server area on the release request interface is detected, the configuration information of the deployment server is obtained.

S240, when the editing operation of the project construction area on the issuing request interface is detected, project configuration information is obtained.

Specifically, if the editing operation on the project building area on the release request interface is detected, the manner of acquiring the project configuration information may be: after detecting the input operation of a user on the front-end project building area on the issuing request interface, acquiring front-end project configuration information when detecting the touch operation of the user on the determination control of the front-end project building area on the issuing request interface, and acquiring rear-end project configuration information when detecting the input operation of the user on the rear-end project building area on the issuing request interface and detecting the touch operation of the user on the determination control of the rear-end project building area on the issuing request interface. When the editing operation on the project building area on the release request interface is detected, the manner of acquiring the project configuration information may also be: and after detecting the input operation of a user on the front-end project building area on the issuing request interface and the input operation of the user on the rear-end project building area on the issuing request interface, acquiring front-end project configuration information and rear-end project configuration information when detecting the touch operation of the user on a determination control of the project building area on the issuing request interface.

S250, sending the release request to a target server according to the configuration information of the deployment server, so that the target server constructs a release package according to the configuration information of the project.

And S260, receiving the address of the publishing packet sent by the target server, and downloading the publishing packet according to the address of the publishing packet.

S270, obtaining the type of the publishing packet.

Wherein the type of the distribution package comprises: at least one of a front end package, Jar package, and War package;

s280, executing target issuing operation on the issuing package according to the type of the issuing package.

Optionally, the item configuration information includes: code address, application issue path, and start command.

Optionally, executing a target publishing operation on the publishing packet according to the publishing packet type includes:

If the publishing package is a Jar package, moving the publishing package to the application publishing path, and executing a program starting script according to the starting command may be: if the publishing packet is a Jar packet, killing the back-end service process; moving the publishing packet to the application publishing path; executing a program starting script according to the starting command; and starting the back-end service process.

If the publishing packet is the War packet, the method for moving the publishing packet to the directory corresponding to the application publishing path may be: if the release packet is War packet, killing the WEB server process; moving the publishing packet to a directory corresponding to the application publishing path; and starting the WEB server process.

Optionally, if the publishing packet is a Jar packet, moving the publishing packet to the application publishing path, and executing a program start script according to the start command, where the method includes:

if the publishing packet is a Jar packet, killing the back-end service process;

moving the publishing packet to the application publishing path;

executing a program starting script according to the starting command;

and starting the back-end service process.

Optionally, if the publishing packet is the War packet, moving the publishing packet to the directory corresponding to the application publishing path includes:

if the release packet is War packet, killing the WEB server process;

and starting the WEB server process.

According to the technical scheme of the embodiment, the method comprises the steps that a release request interface is skipped to when a trigger operation on a release control on an editing interface is detected, and code warehouse configuration information is acquired when an editing operation on a code warehouse area on the release request interface is detected; when the editing operation of the deployment server area on the release request interface is detected, acquiring the configuration information of the deployment server; when the editing operation of a project construction area on the release request interface is detected, acquiring project configuration information, and sending the release request to a target server according to the deployment server configuration information so that the target server constructs a release package according to the project configuration information; receiving a publishing packet address sent by the target server, and downloading a publishing packet according to the publishing packet address; according to the publishing package is published, the problems that each link needs manual intervention, workload is large and error probability is large due to the fact that local manual compiling is used for generating the publishing package and then the publishing package is uploaded to a server, and then service is started through inputting a corresponding command are solved, the problems that Jenkins tool interface operation is not intelligent and display is not friendly are solved, the requirement for a user is improved, a public part can be stripped to the maximum extent, the user only needs to be simply configured, and the requirement for the user is lowered.

EXAMPLE III

Fig. 3 is a schematic structural diagram of an issuing device according to a third embodiment of the present invention. The present embodiment may be applicable to the case of publishing, and the apparatus may be implemented in a software and/or hardware manner, and the apparatus may be integrated in any device providing a publishing function, as shown in fig. 3, where the publishing apparatus specifically includes: a first obtaining module 310, a sending module 320, a sending module 330, a second obtaining module 340, and an executing module 350.

The first obtaining module is configured to obtain an issue request, where the issue request includes: project configuration information and deployment server configuration information;

Optionally, the receiving module is specifically configured to:

receiving a publishing packet address sent by the target server;

correspondingly, the obtaining module is specifically configured to:

The product can execute the method provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method.

Example four

Fig. 4 is a schematic structural diagram of an electronic device according to a fourth embodiment of the present invention. FIG. 4 illustrates a block diagram of an electronic device 312 suitable for use in implementing embodiments of the present invention. The electronic device 312 shown in fig. 4 is only an example, and should not bring any limitation to the functions and the scope of the use of the embodiment of the present invention. Device 312 is a computing device for typical trajectory fitting functions.

As shown in fig. 4, electronic device 312 is in the form of a general purpose computing device. The components of the electronic device 312 may include, but are not limited to: one or more processors 316, a storage device 328, and a bus 318 that couples the various system components including the storage device 328 and the processors 316.

Bus 318 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, such architectures include, but are not limited to, an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MCA) bus, an enhanced ISA bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus.

Electronic device 312 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by electronic device 312 and includes both volatile and nonvolatile media, removable and non-removable media.

Storage 328 may include computer system readable media in the form of volatile Memory, such as Random Access Memory (RAM) 330 and/or cache Memory 332. The electronic device 312 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 334 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 4, and commonly referred to as a "hard drive"). Although not shown in FIG. 4, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a Compact disk-Read Only Memory (CD-ROM), a Digital Video disk (DVD-ROM), or other optical media) may be provided. In these cases, each drive may be connected to bus 318 by one or more data media interfaces. Storage 328 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.

Program 336 having a set (at least one) of program modules 326 may be stored, for example, in storage 328, such program modules 326 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which may comprise an implementation of a network environment, or some combination thereof. Program modules 326 generally carry out the functions and/or methodologies of embodiments of the invention as described herein.

Electronic device 312 may also communicate with one or more external devices 314 (e.g., keyboard, pointing device, camera, display 324, etc.), with one or more devices that enable a user to interact with electronic device 312, and/or with any devices (e.g., network card, modem, etc.) that enable electronic device 312 to communicate with one or more other computing devices. Such communication may occur via input/output (I/O) interfaces 322. Also, the electronic device 312 may communicate with one or more networks (e.g., a Local Area Network (LAN), Wide Area Network (WAN), and/or a public Network, such as the internet) via the Network adapter 320. As shown, a network adapter 320 communicates with the other modules of the electronic device 312 via the bus 318. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the electronic device 312, including but not limited to: microcode, device drivers, Redundant processing units, external disk drive Arrays, disk array (RAID) systems, tape drives, and data backup storage systems, to name a few.

The processor 316 executes various functional applications and data processing by executing programs stored in the storage 328, for example, implementing the distribution method provided by the above-described embodiment of the present invention:

Fig. 5 is a schematic structural diagram of a computer-readable storage medium containing a computer program according to an embodiment of the present invention. Embodiments of the present invention provide a computer-readable storage medium 61, on which a computer program 610 is stored, which when executed by one or more processors implements the distribution method as provided by all inventive embodiments of the present application:

Any combination of one or more computer-readable media may be employed. The computer readable medium may be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

In some embodiments, the clients, servers may communicate using any currently known or future developed network Protocol, such as HTTP (Hyper Text Transfer Protocol), and may interconnect with any form or medium of digital data communication (e.g., a communications network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the Internet (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed network.

The computer readable medium may be embodied in the electronic device; or may exist separately without being assembled into the electronic device.

Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + +, or the like, as well as conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units described in the embodiments of the present disclosure may be implemented by software or hardware. Where the name of an element does not in some cases constitute a limitation on the element itself.

The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), systems on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), and the like.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

Embodiments of the present invention further provide a computer program product, including a computer program, which, when executed by a processor, implements the method according to any of the embodiments of the present invention.

It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A publishing method applied to a client side, the publishing method comprising:

obtaining a type of a distribution packet, wherein the type of the distribution packet comprises: at least one of a front end package, Jar package, and War package;

2. The method of claim 1, wherein receiving an address of the publishing packet sent by the target server and downloading the publishing packet according to the address of the publishing packet comprises:

receiving a publishing packet address sent by the target server;

3. The method of claim 1, wherein issuing the request further comprises: code repository configuration information;

correspondingly, obtaining the issue request includes:

4. The method of claim 3, wherein the project configuration information comprises: code address, application issue path, and start command.

5. The method of claim 4, wherein performing a target publishing operation on the publishing packet according to the publishing packet type comprises:

6. The method according to claim 5, wherein if the publishing packet is a Jar packet, moving the publishing packet to the application publishing path, and executing a program start script according to the start command comprises:

if the publishing packet is a Jar packet, killing the back-end service process;

moving the publishing packet to the application publishing path;

executing a program starting script according to the starting command;

and starting the back-end service process.

7. The method of claim 5, wherein if the publishing packet is War packet, moving the publishing packet to a directory corresponding to the application publishing path comprises:

if the release packet is War packet, killing the WEB server process;

and starting the WEB server process.

8. The method of claim 1, wherein sending the publishing request to a target server according to the deployment server configuration information to enable the target server to construct a publishing package according to the project configuration information comprises:

9. A distribution apparatus configured to a client, the distribution apparatus comprising:

a second obtaining module, configured to obtain a type of a distribution packet, where the type of the distribution packet includes: at least one of a front end package, Jar package, and War package;

10. The apparatus of claim 9, wherein the receiving module is specifically configured to:

receiving a publishing packet address sent by the target server;

11. The apparatus of claim 9, wherein the request to issue further comprises: code repository configuration information;

correspondingly, the obtaining module is specifically configured to:

12. The apparatus of claim 11, wherein the item configuration information comprises: code address, application issue path, and start command.

13. The apparatus of claim 12, wherein the execution module is specifically configured to:

14. An electronic device, comprising:

one or more processors;

a memory for storing one or more programs;

the one or more programs, when executed by the one or more processors, cause the processors to implement the method of any of claims 1-8.

15. A computer-readable storage medium containing a computer program, on which the computer program is stored, characterized in that the program, when executed by one or more processors, implements the method according to any one of claims 1-8.

16. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any one of claims 1-8.