CN113741906A - Application publishing method and device - Google Patents
Application publishing method and device Download PDFInfo
- Publication number
- CN113741906A CN113741906A CN202010477059.5A CN202010477059A CN113741906A CN 113741906 A CN113741906 A CN 113741906A CN 202010477059 A CN202010477059 A CN 202010477059A CN 113741906 A CN113741906 A CN 113741906A
- Authority
- CN
- China
- Prior art keywords
- application
- release
- issued
- issuing
- workflow
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 54
- 238000003860 storage Methods 0.000 claims description 13
- 238000004590 computer program Methods 0.000 claims description 10
- 230000008569 process Effects 0.000 description 16
- 238000010586 diagram Methods 0.000 description 15
- 230000006870 function Effects 0.000 description 11
- 238000004891 communication Methods 0.000 description 8
- 235000017166 Bambusa arundinacea Nutrition 0.000 description 7
- 235000017491 Bambusa tulda Nutrition 0.000 description 7
- 241001330002 Bambuseae Species 0.000 description 7
- 235000015334 Phyllostachys viridis Nutrition 0.000 description 7
- 239000011425 bamboo Substances 0.000 description 7
- 238000012545 processing Methods 0.000 description 6
- 239000008186 active pharmaceutical agent Substances 0.000 description 5
- 238000012552 review Methods 0.000 description 5
- 238000012550 audit Methods 0.000 description 4
- 230000003993 interaction Effects 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 238000009826 distribution Methods 0.000 description 3
- 238000007726 management method Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000011112 process operation Methods 0.000 description 3
- 230000000007 visual effect Effects 0.000 description 3
- 244000141359 Malus pumila Species 0.000 description 2
- 230000008901 benefit Effects 0.000 description 2
- 235000014510 cooky Nutrition 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 230000002452 interceptive effect Effects 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 235000021016 apples Nutrition 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000002360 preparation method Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 238000010200 validation analysis Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses a method and a device for issuing an application, and relates to the technical field of computers. One embodiment of the method comprises: receiving an application release request of a user, and acquiring a release identifier of an application to be released; acquiring the release workflow of the application to be released from a preset release workflow library according to the release identifier; and issuing the application to be issued to a target server according to the issuing workflow. The implementation method can automatically release the application to be released to the target server side, one-key release is realized, and labor and time cost are greatly saved.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a method and a device for issuing applications.
Background
In the prior art, when application publishing is performed, a user often publishes an application to be published to a target server, the publishing process seriously depends on manual operation of the user, the publishing process is complicated in operation, and the labor cost and the time cost are high.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method and an apparatus for issuing an application, which can automatically issue an application to be issued to a target server, so as to implement one-key issuing, thereby greatly saving labor and time costs.
To achieve the above object, according to an aspect of an embodiment of the present invention, there is provided an application publishing method, including:
receiving an application release request of a user, and acquiring a release identifier of an application to be released;
acquiring the release workflow of the application to be released from a preset release workflow library according to the release identifier;
and issuing the application to be issued to a target server according to the issuing workflow.
Optionally, the publishing identity includes: an application identification and a version identification.
Optionally, before obtaining the release workflow of the application to be released from a preset release workflow library, the method further includes:
acquiring interface parameters of each calling interface required by the application to be issued;
and assembling each calling interface according to the service logic of the application to be issued and the interface parameters of each calling interface to obtain the issuing workflow of the application to be issued.
Optionally, obtaining interface parameters of each call interface required for issuing the application to be issued includes:
acquiring request encryption information of the target server;
and logging in the target server according to the request encryption information to obtain interface parameters of each calling interface required by the application to be issued.
According to a second aspect of the embodiments of the present invention, there is provided an apparatus for application publishing, including:
the receiving module is used for receiving an application issuing request of a user and acquiring an issuing identifier of an application to be issued;
the acquisition module acquires the release workflow of the application to be released from a preset release workflow library according to the release identifier;
and the issuing module is used for issuing the application to be issued to the target server according to the issuing workflow.
Optionally, the publishing identity includes: an application identification and a version identification.
Optionally, the obtaining module is further configured to: before acquiring the release workflow of the application to be released from a preset release workflow library,
acquiring interface parameters of each calling interface required by the application to be issued;
and assembling each calling interface according to the service logic of the application to be issued and the interface parameters of each calling interface to obtain the issuing workflow of the application to be issued.
Optionally, the obtaining module obtains the interface parameters of each calling interface required for issuing the application to be issued, including:
acquiring request encryption information of the target server;
and logging in the target server according to the request encryption information to obtain interface parameters of each calling interface required by the application to be issued.
According to a third aspect of the embodiments of the present invention, there is provided an electronic device for application distribution, including:
one or more processors;
a storage device for storing one or more programs,
when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the method provided by the first aspect of the embodiments of the present invention.
According to a fourth aspect of embodiments of the present invention, there is provided a computer readable medium, on which a computer program is stored, which when executed by a processor, implements the method provided by the first aspect of embodiments of the present invention.
One embodiment of the above invention has the following advantages or benefits: the application publishing is realized by adopting a uniform publishing platform, and the publishing workflow library is preset, so that data interaction between each user and the target server is not needed, each application to be published can be automatically published to the target server, one-key publishing is realized, and the labor and time cost are greatly saved.
Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.
Drawings
The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:
FIG. 1 is a schematic diagram of the main flow of a method of application publication in an embodiment of the invention;
FIG. 2 is a schematic diagram of a method of application publication in an alternative embodiment of the invention;
FIG. 3 is a schematic diagram of a method for publishing a formal version of an application in an alternative embodiment of the invention;
FIG. 4 is a schematic flow chart illustrating release of a formal version of an application in an alternative embodiment of the present invention;
FIG. 5 is a schematic diagram of the main modules of an apparatus for application publishing in an embodiment of the present invention;
FIG. 6 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;
fig. 7 is a schematic block diagram of a computer system suitable for use in implementing a terminal device or server of an embodiment of the invention.
Detailed Description
Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
According to one aspect of the embodiment of the invention, a method for publishing an application is provided.
Fig. 1 is a schematic diagram of a main flow of an application publishing method according to an embodiment of the present invention, and as shown in fig. 1, the application publishing method includes: step S101, and step S103.
In step S101, an application publishing request of a user is received, and a publishing identifier of an application to be published is obtained.
The application identification is an application identification to be issued, and each application identification uniquely corresponds to one issuing workflow in a preset issuing workflow library. One application identifier may uniquely correspond to one application to be published, for example, the application identifier of application a is a, and the application identifier of application B is B; of course, one application identifier may also only uniquely correspond to one version of the application to be released, for example, the application identifier of the grayscale version of the application a is a1, the application identifier of the formal version of the application a is a2, and the like. Optionally, the publishing identity includes: the application identifier and the version identifier can meet the different requirements of different applications and different versions of the release process.
In step S102, according to the release identifier, a release workflow of the application to be released is obtained from a preset release workflow library.
The issuing workflow refers to a workflow formed by connecting all business process operation nodes related to issuing the application to be issued in series. In the release workflow, each node presets the operation of the next node, so that the operations of the nodes related to the release of one application can be connected in series, and the automatic and flow operation of the application release can be realized.
And in the application release process, multiple interactive operations with the target server side are required, and a corresponding calling interface is required to be called during each interaction. In an optional embodiment of the present invention, before obtaining the release workflow of the application to be released from a preset release workflow library, the method further includes: acquiring interface parameters of each calling interface required by the application to be issued; and assembling each calling interface according to the service logic of the application to be issued and the interface parameters of each calling interface to obtain the issuing workflow of the application to be issued. The interface parameters may include an interface name, an interface address (i.e., a Uniform Resource Locator, URL), and the like.
When the publishing process for publishing the application in the target server is transparent to the outside, each calling interface and interface parameters thereof required for publishing the application to be published can be directly obtained. When the publishing process for publishing the application in the target server is not open and transparent to the outside, the calling interfaces and interface parameters thereof required for publishing the application to be published cannot be directly obtained. At this time, the interface parameters of each calling interface required for issuing the application to be issued can be acquired according to the following steps: acquiring request encryption information of a target server; and logging in a target server according to the request encryption information, and acquiring interface parameters of each calling interface required by issuing the application to be issued.
For example, it is assumed that the target server does not provide each calling interface and interface parameters thereof required for releasing the formal version application C, and a security check is set for each calling request in the process of releasing the formal version application C. At this time, information such as a network request mode, a request header, a body, and a cookie (data stored in a user local terminal for identifying a user identity and performing session tracking) may be analyzed by a tool such as a crawler or a browser element-web, and encrypted key information (service-key) is acquired and disguised as a web page (web) to log in for secure access, and then various related call interfaces (APIs) are issued by the crawler analysis formal version, such as: downloading, editing and uploading metadata interfaces, interfaces for checking and inquiring the state of the interfaces for submission and the like, and finally connecting and assembling all the APIs in series to form an executable program and deploying the executable program into a release workflow library.
In step S103, the application to be published is published to a target server according to the publishing workflow. The target service end mentioned in the step refers to various application stores, such as an apple application store supporting an iOS system, a Google Play store supporting an Android system, and the like.
In the prior art, when application publishing is performed, a user performs interactive operation with a target server, and directly publishes an application to be published to the target server. Because the application issuing process needs to be interactively operated with the target server for many times, the application issuing process seriously depends on manual operation of a user, and the issuing process is complicated in operation and high in labor and time cost. The method provided by the embodiment of the invention provides a uniform publishing platform to realize application publishing, and presets the publishing workflow library, so that each application to be published can be automatically published to the target server without data interaction between each user and the target server, one-key publishing is realized, and the labor and time cost are greatly saved.
In the embodiment of the invention, in order to facilitate visual viewing and operation, each method step in the embodiment of the invention can be presented in a webpage form in a visual way.
In some alternative embodiments, the method for implementing embodiments of the present invention includes two parts: a pipeline part (for pipeline tasks of the automatic publishing system, such as uploading, querying, reviewing, etc.) and a scheduling part (for scheduling some services, scheduling functions of the automatic publishing system). The production line part realizes each core function of gray scale or formal version application through investigating service logic, bottom API and tools, and connects each core function in series to realize automatic flow operation. The scheduling part realizes scheduling work among various core functions. The realized functions are presented through the web (webpage) by virtue of webcore (a type of typesetting engine) development, and visual viewing and operation are realized. The embodiment may include integrated process operations such as App Store Connect supporting iOS, *** play of Android, and channel package distribution. The system (i.e., an execution subject for implementing the method of the embodiment of the present invention) provides account management, and supports core workflows such as user selection of app (application), submission of app, inquiry of an audit state, gray level test, and on-shelf release of app. The steps are divided into gray scale release and formal release according to the dispatching ability of the Bamboo service, and the release workflow is preset. Each step presets the operation of the next node to run in tandem. The scheduling work is performed aiming at one-time business process operation of the edition sending personnel, and is not used for scheduling a plurality of pipelines. The whole implementation is completed by the mutual cooperation of the server and the pipeline, namely, the Bamboo service is responsible for scheduling, informs the Bamboo pipeline of a certain operation (such as uploading app) which needs to be performed currently, the Bamboo pipeline performs specific logic processing, and informs the Bamboo service of executing state after the completion, so that the workflow continues to run. Fig. 2 shows a scheduling process comprising: the method comprises the steps of collecting service logic of the application which can be published in advance, constructing a publishing pipeline of the application, and providing a publishing page for a user. After the user uploads the application to be published on the publishing page, the system uploads the application to be published uploaded by the user to a target server such as an App Store Connect or Google Play, and the user can perform asynchronous effective state query through the system. After the uploading is successful, the system automatically carries out gray level submission, and a user can inquire the gray level submission state through the system. After the gray level submission passes, the system automatically performs material preparation before formal submission (multi-role cooperation process), and then performs automatic pre-review and formal package submission.
A release workflow of a grayscale version generally includes several nodes: uploading, validation state, submission and audit state. A formal version of a release workflow generally includes several nodes: uploading, taking effect, downloading metadata, editing metadata, uploading (pre-review), formal review and audit states. Fig. 3 is a schematic diagram of a method for releasing a formal version application in an alternative embodiment of the present invention, and as shown in fig. 3, after an application to be released is uploaded to an App Store, a system queries an effective state of the upload. If the uploading is effective, configuring metadata; otherwise, the flow ends. Configuration metadata refers to downloading and editing metadata. After the metadata is configured, the system automatically carries out pre-review work, and if the pre-review passes, formal submission is carried out; otherwise, the flow ends. And the formal submission state is synchronized to the Bamboo service so as to facilitate the query of the user. And the target server returns the submission state to the Bamboo service. If the submission is passed, the application to be issued is successfully issued to the App Store, and the issuing process is ended; otherwise, the issuing process of the application to be issued is rejected, namely the application is not successfully issued to the App Store.
When the release flow for releasing the application in the target server is not open and transparent to the outside, the release flow of the target server can be cracked first, and then the release workflow of the application to be released is constructed. Fig. 4 is a schematic flow diagram of release of a formal version application in an alternative embodiment of the present invention, as shown in fig. 4, information such as a web request mode, a request header/body/cookie, and the like of a target server is analyzed by a crawler, a browser element-web tool, and the like, an encrypted key information service-key is obtained and disguised as a web login through secure access thereof, and then various APIs related to the formal version release are analyzed by the crawler, such as: downloading, editing and uploading metadata interfaces, submission interfaces, audit state query interfaces and the like, and finally connecting and assembling all the APIs in series to form an executable program and deploying the executable program into a release workflow library.
According to the embodiment, the applications to be published can be automatically published to the target server, one-key publishing is realized, labor and time cost are greatly saved, communication with channel markets of the target servers such as apples, Google and Android can be realized, and application development and popularization are facilitated.
According to a second aspect of the embodiments of the present invention, there is provided an apparatus for implementing the above method.
Fig. 5 is a schematic diagram of main modules of an apparatus for application publishing according to an embodiment of the present invention, and as shown in fig. 5, the apparatus 500 for application publishing includes:
the receiving module 501 receives an application publishing request of a user, and obtains a publishing identifier of an application to be published;
an obtaining module 502, configured to obtain, according to the release identifier, a release workflow of the application to be released from a preset release workflow library;
the issuing module 503 issues the application to be issued to the target server according to the issuing workflow.
Optionally, the publishing identity includes: an application identification and a version identification.
Optionally, the obtaining module is further configured to: before acquiring the release workflow of the application to be released from a preset release workflow library,
acquiring interface parameters of each calling interface required by the application to be issued;
and assembling each calling interface according to the service logic of the application to be issued and the interface parameters of each calling interface to obtain the issuing workflow of the application to be issued.
Optionally, the obtaining module obtains the interface parameters of each calling interface required for issuing the application to be issued, including:
acquiring request encryption information of the target server;
and logging in the target server according to the request encryption information to obtain interface parameters of each calling interface required by the application to be issued.
According to a third aspect of the embodiments of the present invention, there is provided an electronic device for application distribution, including:
one or more processors;
a storage device for storing one or more programs,
when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the method provided by the first aspect of the embodiments of the present invention.
According to a fourth aspect of embodiments of the present invention, there is provided a computer readable medium, on which a computer program is stored, which when executed by a processor, implements the method provided by the first aspect of embodiments of the present invention.
Fig. 6 illustrates an exemplary system architecture 600 of an apparatus to which the method of application publication or application publication of embodiments of the invention may be applied.
As shown in fig. 6, the system architecture 600 may include terminal devices 601, 602, 603, a network 604, and a server 605. The network 604 serves to provide a medium for communication links between the terminal devices 601, 602, 603 and the server 605. Network 604 may include various types of connections, such as wire, wireless communication links, or fiber optic cables, to name a few.
A user may use the terminal devices 601, 602, 603 to interact with the server 605 via the network 604 to receive or send messages or the like. The terminal devices 601, 602, 603 may have installed thereon various communication client applications, such as shopping applications, web browser applications, search applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only).
The terminal devices 601, 602, 603 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 605 may be a server providing various services, such as a background management server (for example only) providing support for shopping websites browsed by users using the terminal devices 601, 602, 603. The backend management server may analyze and perform other processing on the received data such as the product information query request, and feed back a processing result (for example, target push information, product information — just an example) to the terminal device.
It should be noted that the method for issuing the application provided by the embodiment of the present invention is generally executed by the server 605, and accordingly, the apparatus for issuing the application is generally disposed in the server 605.
It should be understood that the number of terminal devices, networks, and servers in fig. 6 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 7, shown is a block diagram of a computer system 700 suitable for use with a terminal device implementing an embodiment of the present invention. The terminal device shown in fig. 7 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.
As shown in fig. 7, the computer system 700 includes a Central Processing Unit (CPU)701, which can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)702 or a program loaded from a storage section 608 into a Random Access Memory (RAM) 703. In the RAM 703, various programs and data necessary for the operation of the system 700 are also stored. The CPU 701, the ROM 702, and the RAM 703 are connected to each other via a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.
The following components are connected to the I/O interface 705: an input portion 706 including a keyboard, a mouse, and the like; an output section 707 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 708 including a hard disk and the like; and a communication section 709 including a network interface card such as a LAN card, a modem, or the like. The communication section 709 performs communication processing via a network such as the internet. A drive 710 is also connected to the I/O interface 705 as needed. A removable medium 711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 710 as necessary, so that a computer program read out therefrom is mounted into the storage section 708 as necessary.
In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 709, and/or installed from the removable medium 711. The computer program performs the above-described functions defined in the system of the present invention when executed by the Central Processing Unit (CPU) 701.
It should be noted that the computer readable medium shown in the present invention can 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 of the computer readable storage medium may include, but are not limited to: 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 present invention, 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. In the present invention, however, 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, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
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 invention. 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 or flowchart illustration, and combinations of blocks in the block diagrams 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 modules described in the embodiments of the present invention may be implemented by software or hardware. The described modules may also be provided in a processor, which may be described as: a processor comprising: the receiving module is used for receiving an application issuing request of a user and acquiring an issuing identifier of an application to be issued; the acquisition module acquires the release workflow of the application to be released from a preset release workflow library according to the release identifier; and the issuing module is used for issuing the application to be issued to the target server according to the issuing workflow. The names of these modules do not form a limitation on the modules themselves in some cases, for example, a receiving module may also be described as a "module for publishing the application to be published to a target server according to the publishing workflow".
As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to comprise: receiving an application release request of a user, and acquiring a release identifier of an application to be released; acquiring the release workflow of the application to be released from a preset release workflow library according to the release identifier; and issuing the application to be issued to a target server according to the issuing workflow.
According to the technical scheme of the embodiment of the invention, the application release is realized by adopting a uniform release platform, the release workflow library is preset, data interaction between each user and the target server side is not needed, each application to be released can be automatically released to the target server side, one-key release is realized, and the labor and time cost are greatly saved.
The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. A method for application publishing, comprising:
receiving an application release request of a user, and acquiring a release identifier of an application to be released;
acquiring the release workflow of the application to be released from a preset release workflow library according to the release identifier;
and issuing the application to be issued to a target server according to the issuing workflow.
2. The method of claim 1, wherein publishing an identification comprises: an application identification and a version identification.
3. The method of claim 1, wherein before obtaining the release workflow of the application to be released from a preset release workflow library, the method further comprises:
acquiring interface parameters of each calling interface required by the application to be issued;
and assembling each calling interface according to the service logic of the application to be issued and the interface parameters of each calling interface to obtain the issuing workflow of the application to be issued.
4. The method of claim 3, wherein obtaining interface parameters of each call interface required for publishing the application to be published comprises:
acquiring request encryption information of the target server;
and logging in the target server according to the request encryption information to obtain interface parameters of each calling interface required by the application to be issued.
5. An apparatus for application publishing, comprising:
the receiving module is used for receiving an application issuing request of a user and acquiring an issuing identifier of an application to be issued;
the acquisition module acquires the release workflow of the application to be released from a preset release workflow library according to the release identifier;
and the issuing module is used for issuing the application to be issued to the target server according to the issuing workflow.
6. The apparatus of claim 5, wherein publishing the identity comprises: an application identification and a version identification.
7. The apparatus of claim 5, wherein the acquisition module is further to: before acquiring the release workflow of the application to be released from a preset release workflow library,
acquiring interface parameters of each calling interface required by the application to be issued;
and assembling each calling interface according to the service logic of the application to be issued and the interface parameters of each calling interface to obtain the issuing workflow of the application to be issued.
8. The apparatus of claim 7, wherein the obtaining module obtains the interface parameters of each calling interface required for issuing the application to be issued, and includes:
acquiring request encryption information of the target server;
and logging in the target server according to the request encryption information to obtain interface parameters of each calling interface required by the application to be issued.
9. An electronic device for application publishing, comprising:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-4.
10. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010477059.5A CN113741906A (en) | 2020-05-29 | 2020-05-29 | Application publishing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010477059.5A CN113741906A (en) | 2020-05-29 | 2020-05-29 | Application publishing method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113741906A true CN113741906A (en) | 2021-12-03 |
Family
ID=78724750
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010477059.5A Pending CN113741906A (en) | 2020-05-29 | 2020-05-29 | Application publishing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113741906A (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105144092A (en) * | 2013-03-14 | 2015-12-09 | 微软技术许可有限责任公司 | Software release workflow management |
| CN106095479A (en) * | 2016-05-31 | 2016-11-09 | 北京中亦安图科技股份有限公司 | A kind of enterprise application dissemination method, Apparatus and system |
| CN106155751A (en) * | 2016-08-02 | 2016-11-23 | 传线网络科技（上海）有限公司 | Application packing and issuing method and device |
| CN106528628A (en) * | 2016-10-08 | 2017-03-22 | 广东小天才科技有限公司 | Application publishing method and device for application store |
| CN107220066A (en) * | 2017-06-28 | 2017-09-29 | 北京金山安全软件有限公司 | Method and device for releasing application software in application store |
| CN109542468A (en) * | 2018-11-23 | 2019-03-29 | 北京金山安全软件有限公司 | Application program release method and device and electronic equipment |
| CN109558146A (en) * | 2018-11-12 | 2019-04-02 | 泰康保险集团股份有限公司 | Application issued method, apparatus and storage medium |
| CN109710262A (en) * | 2018-12-12 | 2019-05-03 | 深圳市多元世纪信息技术股份有限公司 | Software distribution method and device, computer readable storage medium |
| CN109814910A (en) * | 2018-12-14 | 2019-05-28 | 深圳壹账通智能科技有限公司 | Automate gray scale dissemination method, device, computer system and storage medium |
-
2020
- 2020-05-29 CN CN202010477059.5A patent/CN113741906A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105144092A (en) * | 2013-03-14 | 2015-12-09 | 微软技术许可有限责任公司 | Software release workflow management |
| CN106095479A (en) * | 2016-05-31 | 2016-11-09 | 北京中亦安图科技股份有限公司 | A kind of enterprise application dissemination method, Apparatus and system |
| CN106155751A (en) * | 2016-08-02 | 2016-11-23 | 传线网络科技（上海）有限公司 | Application packing and issuing method and device |
| CN106528628A (en) * | 2016-10-08 | 2017-03-22 | 广东小天才科技有限公司 | Application publishing method and device for application store |
| CN107220066A (en) * | 2017-06-28 | 2017-09-29 | 北京金山安全软件有限公司 | Method and device for releasing application software in application store |
| CN109558146A (en) * | 2018-11-12 | 2019-04-02 | 泰康保险集团股份有限公司 | Application issued method, apparatus and storage medium |
| CN109542468A (en) * | 2018-11-23 | 2019-03-29 | 北京金山安全软件有限公司 | Application program release method and device and electronic equipment |
| CN109710262A (en) * | 2018-12-12 | 2019-05-03 | 深圳市多元世纪信息技术股份有限公司 | Software distribution method and device, computer readable storage medium |
| CN109814910A (en) * | 2018-12-14 | 2019-05-28 | 深圳壹账通智能科技有限公司 | Automate gray scale dissemination method, device, computer system and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107302597B (en) | Message file pushing method and device | |
| CN107491382B (en) | Log output method and device | |
| CN112860451A (en) | Multi-tenant data processing method and device based on SaaS | |
| CN109981322B (en) | Method and device for cloud resource management based on label | |
| CN110851468A (en) | Method and device for making simulation response to test request of client | |
| CN111460129A (en) | Method and device for generating identification, electronic equipment and storage medium | |
| CN111444077A (en) | Method and device for generating flow node test data | |
| CN109218041B (en) | Request processing method and device for server system | |
| CN113177822A (en) | Cross-border e-commerce multi-channel order management method, system and equipment | |
| CN111767157A (en) | Request processing method and device based on service grid | |
| CN108932640B (en) | Method and device for processing orders | |
| CN111461754A (en) | Method and device for determining flow source of order | |
| CN112947919A (en) | Method and device for constructing service model and processing service request | |
| CN113378346A (en) | Method and device for model simulation | |
| CN116737662A (en) | Method, device, electronic equipment and storage medium for processing business data | |
| CN112948138A (en) | Method and device for processing message | |
| CN112100168A (en) | Method and device for determining data association relationship | |
| CN113741906A (en) | Application publishing method and device | |
| CN112783903B (en) | Method and device for generating update log | |
| CN114610895A (en) | Work order pushing method and device, electronic equipment and storage medium | |
| CN109087097B (en) | Method and device for updating same identifier of chain code | |
| CN110909269B (en) | Log reporting method and device | |
| CN113743630A (en) | Method and device for executing intelligent call reservation | |
| CN113722315A (en) | Data generation method and device, electronic equipment and computer readable medium | |
| CN113821430A (en) | Multi-service testing method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |