CN111984268A

CN111984268A - Application publishing method and application publishing platform

Info

Publication number: CN111984268A
Application number: CN202010842440.7A
Authority: CN
Inventors: 王昱森; 黄缨宁
Original assignee: 4Paradigm Beijing Technology Co Ltd
Current assignee: 4Paradigm Beijing Technology Co Ltd
Priority date: 2020-08-20
Filing date: 2020-08-20
Publication date: 2020-11-24

Abstract

An application publishing method and an application publishing platform are provided, the application publishing method comprises the following steps: executing an application execution internal test in response to a first request for the application execution internal test input by a user; after the application is tested, responding to a second request for performing audit on the application, which is input by a user, and performing on-shelf audit on the application; and after the application passes the on-shelf audit, responding to a third request input by a user for executing the release of the application, and executing the release of the application.

Description

Application publishing method and application publishing platform

Technical Field

The present disclosure relates to the field of application publishing, and more particularly, to an application publishing method and an application publishing platform.

Background

The current application publishing platform mainly has the following problems:

on one hand, the lack of application release specifications leads to uneven application quality, and especially in an enterprise-level scene, the applications with non-uniform specifications and uncontrolled quality can greatly hinder business development. On the other hand, only the applications developed autonomously inside an enterprise can be operated and maintained well, but after all, the research and development capability of a single enterprise is limited, and once the business problem which is difficult to solve by internal research and development is involved, when the help of an open source community or a third party organization is required, the external applications are difficult to integrate.

Secondly, the difficulty of application construction is high, and before a platform does not exist, developers need to undertake development of all dimensions, so that the development system not only comprises business problems, but also comprises operation and maintenance problems and engineering efficiency problems, the requirements on the developers are extremely high, and the application output quantity is greatly reduced. In addition, since many aspects of the capabilities are reusable, the development of a single application is costly and inefficient in a conventional manner.

Disclosure of Invention

Exemplary embodiments of the present disclosure may or may not address at least the above-mentioned problems.

According to an aspect of the present disclosure, there is provided an application publishing method, including: executing an application execution internal test in response to a first request for the application execution internal test input by a user; after the application is tested, responding to a second request for performing audit on the application, which is input by a user, and performing on-shelf audit on the application; and after the application passes the on-shelf audit, responding to a third request input by a user for executing the release of the application, and executing the release of the application.

Optionally, the first request may include information about a developer certificate and a description file of the application; wherein the executing the internal test on the application may include: authenticating the user based on the information about the developer certificate; packaging the application into a preset application format based on the description file of the application; and after the user passes the identity authentication, testing the application in the preset application format in the same internal test environment as the real platform environment.

Optionally, the second request may include information about a developer certificate; wherein the performing an on-shelf audit on the application may include: authenticating the user based on the information about the developer certificate; and after the user passes the identity authentication, checking whether the normalization of the application conforms to the upper frame standard.

Optionally, the verifying whether the normalization of the application meets the upper frame standard after the user passes the identity authentication may include at least one of the following steps: checking whether the performance of the application meets the production requirement; auditing whether the safety of the application meets enterprise-level requirements; auditing whether the application passes vulnerability scanning; auditing whether the application has high availability and reaches a specified level; checking whether the layout of the application page is standard; auditing whether the application adopts an open source product; auditing whether the application is subjected to intellectual property authentication or not; and checking whether the help document of the application is complete.

Optionally, the third request may include information about a developer certificate; wherein the executing the publication of the application may include: based on the information about the developer certificate, performing identity authentication on the user and confirming whether the user has the packaging right; after the user passes identity authentication and is confirmed to have the package-out authority, receiving information about the application selected by the user and to be issued and the version number of the application; checking whether a code branch of an underlying module on which the application having the version number is issued depends is correct, based on information about the application selected by a user to be issued and the version number thereof; receiving information regarding the user marked out-of-packet usage if the code branch is correct; tagging and/or remarking the application with the version number based on information about the out-of-package use of the user tag; generating an installation package for the application having the version number to install and publish the application on a publication platform.

Optionally, the application publishing method may further include: in response to a request to register a developer account input by a user, the developer account is registered for the user and a developer certificate is issued to the user.

Optionally, the application publishing method may further include: the application development is performed in response to a request for developing an application input by a user.

Optionally, the executing application development in response to a request for developing an application input by a user may include: developing an application interface of the application in response to planning information about the application interface input by a user; developing data manipulation and storage capabilities of the application in response to design information input by a user regarding data manipulation and storage; developing a multi-page jump implementation capability of the application in response to user-entered design information regarding a multi-page jump implementation; developing a service implementation capability of the application in response to user-entered configuration information regarding the service implementation; in response to configuration information input by a user about perfecting application characteristics and details, perfecting the application characteristics and details of the application; executing a code self-test on the application in response to a request for application testing input by a user; in response to a user-entered request for application packaging and signing, packaging and signing are performed on the application.

Optionally, the executing application development in response to a request for developing an application input by a user may include: providing the user with one or more packaged characteristic capabilities related to the basic capabilities of the operation and maintenance and/or artificial intelligence application; and receiving configuration information of the characteristic capability in the one or more characteristic capabilities, which is input by a user, and calling the corresponding characteristic capability to execute application development.

Optionally, the one or more characteristic capabilities may include at least one of: the system comprises operation and maintenance characteristic capacity, security characteristic capacity, service management characteristic capacity, online and offline mixed arrangement characteristic capacity, storage characteristic capacity and artificial intelligence algorithm parameter adjusting characteristic capacity; wherein the operation and maintenance characteristic capability may comprise at least one of: load balancing feature capability, dynamic scaling capability, manual scaling capability, exposed service path feature capability, gateway security policy feature capability, timing policy feature capability, publishing policy feature capability.

Optionally, the application publishing method may further include: after the user completes application development, responding to a request for executing debugging on the application input by the user, and providing a cloud environment for the user to execute debugging.

According to another aspect of the present disclosure, there is provided an application publishing platform comprising: an interface module configured to receive a user input; an internal test module configured to execute an internal test on an application in response to a first request for the application execution internal test input by a user; the auditing module is configured to respond to a second request for auditing the application input by a user after the application is tested, and to perform on-shelf auditing on the application; and the publishing module is configured to respond to a third request for publishing the application, which is input by a user, after the application passes the on-shelf audit, and publish the application.

Optionally, the first request may include information about a developer certificate and a description file of the application; the application publishing platform can also comprise a permission module; wherein the internal measurement module may be configured to: authenticating, by the permission module, a user based on the information about the developer certificate; packaging the application into a preset application format based on the description file of the application; and after the user passes the identity authentication, testing the application in the preset application format in the same internal test environment as the real platform environment.

Optionally, the second request may include information about a developer certificate; the application publishing platform can also comprise a permission module; wherein the audit module is configurable to: authenticating, by the permission module, a user based on the information about the developer certificate; and after the user passes the identity authentication, checking whether the normalization of the application conforms to the upper frame standard.

Optionally, the auditing module may be configured to perform at least one of the following steps: checking whether the performance of the application meets the production requirement; auditing whether the safety of the application meets enterprise-level requirements; auditing whether the application passes vulnerability scanning; auditing whether the application has high availability and reaches a specified level; checking whether the layout of the application page is standard; auditing whether the application adopts an open source product; auditing whether the application is subjected to intellectual property authentication or not; and checking whether the help document of the application is complete.

Optionally, the third request may include information about a developer certificate; the application publishing platform can also comprise a permission module; wherein the publication module is configurable to: authenticating, by the permission module, the user based on the information about the developer certificate; confirming whether the package-out authority is provided or not based on the information about the developer certificate; after the user passes the identity authentication and is confirmed to have the package-out authority, receiving information about the application selected by the user and to be issued and the version number thereof through an interface module; checking whether a code branch of an underlying module on which the application having the version number is issued depends is correct, based on information about the application selected by a user to be issued and the version number thereof; receiving information about the user marked out-packet use through an interface module if the code branch is correct; tagging and/or remarking the application with the version number based on information about the out-of-package use of the user tag; generating an installation package for the application having the version number to install and publish the application on a publication platform.

Optionally, the application publishing platform may further include: and the permission module is configured to register the developer account for the user and issue a developer certificate to the user in response to a request for registering the developer account input by the user.

Optionally, the application publishing platform may further include: and the development module is configured to respond to the request for developing the application input by the user and execute application development.

Optionally, the development module may be configured to: developing an application interface of the application in response to planning information about the application interface input by a user; developing data manipulation and storage capabilities of the application in response to design information input by a user regarding data manipulation and storage; developing a multi-page jump implementation capability of the application in response to user-entered design information regarding a multi-page jump implementation; developing a service implementation capability of the application in response to user-entered configuration information regarding the service implementation; in response to configuration information input by a user about perfecting application characteristics and details, perfecting the application characteristics and details of the application; executing a code self-test on the application in response to a request for application testing input by a user; in response to a user-entered request for application packaging and signing, packaging and signing are performed on the application.

Optionally, the development module may be configured to: providing the user with one or more packaged characteristic capabilities related to the basic capabilities of the operation and maintenance and/or artificial intelligence application; and receiving configuration information of the characteristic capability in the one or more characteristic capabilities, which is input by a user, and calling the corresponding characteristic capability to execute application development.

Optionally, the application publishing platform may further include: and the debugging module is configured to respond to a request for executing debugging on the application input by a user after the user completes application development, and provide a cloud environment for the user to execute debugging.

According to another aspect of the present disclosure, there is provided a computer-readable storage medium storing instructions that, when executed by at least one computing device, cause the at least one computing device to perform an application publishing method of the present disclosure.

According to another aspect of the present disclosure, there is provided a system comprising at least one computing device and at least one storage device storing instructions, wherein the instructions, when executed by the at least one computing device, cause the at least one computing device to perform the application publishing method of the present disclosure.

According to the application release method and the application release platform disclosed by the invention, a standard application release process covering from internal examination to release is provided, a standard application development and application release process covering a full-process link from registration to development to debugging to internal examination to release is also provided, and a standard application development and release standard which is standard and is convenient for a user or an enterprise to execute development and release management is provided.

In addition, according to the application release method and the application release platform disclosed by the invention, strict application quality auditing capability is provided, and the control of the application quality facing the public is facilitated.

In addition, according to the application publishing method and the application publishing platform disclosed by the disclosure, resources available to the application publishing platform are organized and packaged to provide entities related to operation and maintenance or common capabilities of applications (for example, AI applications), so that developers do not need to perform code development of the operation and maintenance or the common capabilities, and only need to specify which operation and maintenance characteristics or AI characteristics need to be added in a configuration file to directly call the packaged related capabilities, so that the application developers only need to develop the business capabilities, and the operation and maintenance related capabilities only need to be uniformly developed and managed by platform operation and maintenance personnel, thereby improving the operation and maintenance efficiency.

Drawings

These and/or other aspects and advantages of the present disclosure will become apparent and more readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:

fig. 1 is a flowchart illustrating an application publication method according to an exemplary embodiment of the present disclosure.

Fig. 2 is a flowchart illustrating an application publication method according to another exemplary embodiment of the present disclosure.

FIG. 3 is a block diagram illustrating an application publication platform according to an exemplary embodiment of the present disclosure.

Fig. 4 is a block diagram illustrating an application publication platform according to another exemplary embodiment of the present disclosure.

Detailed Description

The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of the embodiments of the disclosure as defined by the claims and their equivalents. Various specific details are included to aid understanding, but these are to be considered exemplary only. 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 present disclosure. In addition, descriptions of well-known functions and constructions are omitted for clarity and conciseness.

In this case, the expression "at least one of the items" in the present disclosure means a case where three types of parallel expressions "any one of the items", "a combination of any plural ones of the items", and "the entirety of the items" are included. For example, "include at least one of a and B" includes the following three cases in parallel: (1) comprises A; (2) comprises B; (3) including a and B. For another example, "at least one of the first step and the second step is performed", which means that the following three cases are juxtaposed: (1) executing the step one; (2) executing the step two; (3) and executing the step one and the step two.

In order to solve the problem of the current application publishing platform, the disclosure provides an application publishing method and an application publishing platform. First, in order to solve the problem of lack of application release specifications, the present disclosure provides a standard application release process covering from internal examination to release, and also provides a standard application development and application release process covering a full-process link from registration to development to debugging to internal examination to release. The method and the device have the advantages that the type selection with highest market occupancy rate and best adaptability in the technical field is researched, Docker is used as an application input basis, in addition, the on-shelf auditing capability is provided, all applications are judged according to a unified standard, and only the applications meeting the standard can be issued on a platform. Secondly, in order to solve the problem of high difficulty in application construction, the method for abstracting and productizing the operation, maintenance and engineering efficiency problems is provided, specifically, resources which can be used by an application release platform are organized and packaged to provide entities related to common abilities in operation, maintenance or AI applications, so that developers do not need to develop codes of the operation, maintenance or common abilities, and only need to specify which operation, maintenance and AI characteristics need to be added in a configuration file to directly call the packaged related abilities, and therefore the application developers only need to develop the business abilities, and the operation, maintenance related abilities only need to be uniformly developed and managed by platform operation and maintenance personnel to improve the operation and maintenance efficiency. In addition, the application publishing method and the application development function in the application publishing platform provided by the disclosure can be applied to not only an AI scenario, but also application construction of any scenario, including a big data analysis scenario, CRM, visualization, and the like, as long as the application is positioned to solve a specific business problem using a code scheme.

An application publication method and an application publication platform according to an exemplary embodiment of the present disclosure are described in detail below with reference to fig. 1 to 4.

Referring to fig. 1, in step 101, in response to a first request for an application execution internal test input by a user, the application execution internal test may be executed.

According to an example embodiment of the present disclosure, the first request may include information about the developer certificate and a description file of the application. For example, the user may fill in an application description file in advance according to a predetermined application publishing process proposed by the application publishing platform, upload information about a developer certificate (e.g., a developer certificate number, a developer certificate picture, etc.), perform permission and authority authentication, and perform internal testing on the application only when the user passes the permission and authority authentication. Of course, the information about the developer certificate and the description file of the application may be uploaded before or after the first request, or the information about the developer certificate may be uploaded before or after the first request, and the description file of the application may be uploaded before or after the first request, in addition to being uploaded together with the first request. The present disclosure does not limit the order of uploading of the description file of the information and application regarding the developer certificate and the transmission of the first request.

According to an exemplary embodiment of the present disclosure, the step of performing an internal test on the application may include: authenticating a user (herein, a user may refer to an application developer) based on information about a developer certificate; packaging the application into a preset application format based on the description file of the application; and after the user passes the identity authentication, testing the application in the preset application format in the internal testing environment which is the same as the real platform environment. Of course, the operation of packaging the application may be performed before or after the user authentication operation is performed. Here, the predetermined application format may be an official application format to which the application distribution platform is applicable. The internal test environment which is completely the same as the real platform environment can be provided for the user to test, the sandbox environment test can help the user to find problems in time, and the influence on the service in the real environment is avoided.

At step 102, after the application is tested, an on-shelf audit can be performed on the application in response to a second request to perform an audit on the application entered by a user. That is, after the functional test of the application is completed, strict checking of the normative is required for unified management and seamless integration. The audited content may include, but is not limited to, at least one of performance, security, high availability, page layout, and compliance.

According to an example embodiment of the present disclosure, the second request may include information about the developer certificate. The user can upload information (such as a developer certificate number, a developer certificate picture and the like) about a developer certificate according to a preset application publishing process proposed by the application publishing platform, execute permission and authority authentication, and can activate the starting of the on-shelf audit and execute the on-shelf audit on the application when the user passes the permission and authority authentication. Here, the activation process may be user unaware and automatically done by the application publishing platform. Of course, the information about the developer's credentials may be uploaded before or after the second request, in addition to being uploaded with the second request. The present disclosure does not limit the order of uploading of information regarding the developer's credentials and sending of the second request.

According to an exemplary embodiment of the present disclosure, the step of performing an on-shelf audit on the application may include: authenticating the user based on the information about the developer certificate; and after the user passes the identity authentication, checking whether the normalization of the application conforms to the upper frame standard.

According to an exemplary embodiment of the present disclosure, the step of reviewing whether the normalization of the application complies with the upper rack standard may include at least one of the following steps: checking whether the performance of the application meets the production requirement; auditing whether the safety of the application meets enterprise-level requirements; auditing whether the application passes vulnerability scanning; auditing whether the application has high availability and reaches a specified level; checking whether the layout of the application page is standard; auditing whether the application adopts an open source product; auditing whether the application is subjected to intellectual property authentication or not; and checking whether the help document of the application is complete.

In step 103, after the application passes the on-shelf audit, publication may be performed on the application in response to a third request for performing publication on the application, which is input by a user.

According to an example embodiment of the present disclosure, the publishing (i.e., out-of-package publishing) function may include at least one of: user management, including user information management with authority to make package publishing, key (AK) management, etc., for verifying whether the user has the package publishing authority; module management, namely, the application bottom layer realizes module management and is used for configuring the code branch of the bottom layer module on which the published application depends; product management, for managing all applications developed by the user; version management, including managing product version numbers and module version numbers, for managing versions of each application; tag management, including management of tags, e.g., marking specific use customers, projects, departments, etc., for managing the use of each package out.

According to an example embodiment of the present disclosure, the third request may include information about the developer certificate. The user can upload information (such as a developer certificate number, a developer certificate picture and the like) about a developer certificate according to a preset application publishing flow proposed by the application publishing platform, execute permission and authority authentication, and execute application publishing only when the user passes the permission and authority authentication and is determined to have the outsourcing authority. Of course, the information about the developer certificate may be uploaded before or after the third request, in addition to being uploaded together with the third request. The present disclosure does not limit the order of uploading of information regarding the developer certificate and sending of the third request.

According to an exemplary embodiment of the present disclosure, performing publishing on the application may include the following processes: based on the information about the developer certificate, performing identity authentication on the user and confirming whether the user has the packaging right; after the user passes identity authentication and is confirmed to have the package-out authority, receiving information about the application selected by the user and to be issued and the version number of the application; checking whether a code branch of an underlying module on which the application having the version number is issued depends is correct, based on information about the application selected by a user to be issued and the version number thereof; receiving information regarding the user marked out-of-packet usage if the code branch is correct; tagging and/or remarking the application with the version number based on information about the out-of-package use of the user tag; generating an installation package for the application having the version number to install and publish the application on a publication platform. After the application is installed and published on the publishing platform, the application may be launched and put into use.

Further, according to an exemplary embodiment of the present disclosure, the application issuing method may further include a user registration process of registering the developer account for the user and issuing the developer certificate to the user in response to a request for registering the developer account input by the user. That is, when a user first uses the application publishing platform to develop or publish an application, the user needs to register and acquire a developer account for identity authentication and authorization.

For example, the developer account system may be divided into two types, i.e., a personal account and an enterprise account, depending on the type. The personal account number and the enterprise account number may differ in the number of applications that can be developed and in the charging pattern. For example, the number of applications that can be developed by an individual account is limited, the charging mode is free registration, and the charge to the application user is proportionally distributed according to the developed applications. The enterprise account is not limited to the application development quantity, and supports the addition of sub-accounts under the company account, so that internal division of labor and collaborative development are facilitated, the charging mode is a common enterprise-level software subscription mode, and subscription cost and service cost are charged annually.

Further, according to an exemplary embodiment of the present disclosure, the application publishing method may further include an application development process of performing application development in response to a request for developing an application input by a user. That is, when a user has developed an application, instrumentation, auditing, and publishing may be performed on the application publishing platform. When the user does not develop the application, the application development can be executed on the application publishing platform, and internal test, audit and publishing are executed after the application is developed.

According to the exemplary embodiments of the present disclosure, a user may be given the maximum degree of freedom in development, and the user may perform development of any kind of applications on an application publishing platform, for example, development may be performed based on a Docker ecology. For better standardization, a proposed standard development flow may be provided, and various Software Development Kits (SDKs) and gadgets may be provided to help users complete application development. For example, a debug tool commonly used for code error correction, a profile tool commonly used for performance analysis, and the like may be provided. The user only needs to utilize the provided SDK and the small tool to execute development according to the process, and the convenience and the efficiency of the user can be improved. For example, an application development flow may include, but is not limited to, developing an application interface for an application in response to user input of planning information about the application interface; developing data manipulation and storage capabilities of the application in response to design information input by a user regarding data manipulation and storage; developing a multi-page jump implementation capability of the application in response to user-entered design information regarding a multi-page jump implementation; developing a service implementation capability of the application in response to user-entered configuration information regarding the service implementation; in response to configuration information input by a user about perfecting application characteristics and details, perfecting the application characteristics and details of the application; executing a code self-test on the application in response to a request for application testing input by a user; in response to a user-entered request for application packaging and signing, packaging and signing are performed on the application. Of course, the sequence of the above-described flows is only exemplary, the above-described development processes may also be performed in any sequence, and furthermore, some or all of the above-described operations may also be omitted or any other operations required for developing an application may be added as needed.

According to the exemplary embodiment of the disclosure, resources which can be used by an application publishing platform can be organized and packaged into entities related to operation and maintenance or basic AI common capabilities, and are directly provided for users to avoid code configuration. That is, the user may not need to perform code development of operation and maintenance or common capabilities, but only need to specify in the configuration file which operation and maintenance features or AI features need to be added to directly invoke the packaged relevant capabilities. Entities that have encapsulated available resources for direct invocation of related capabilities may be referred to as feature capabilities. The application publishing platform may provide a property capability library including at least one property capability, which may include property capabilities that may include, but are not limited to, the following: traffic and network (e.g., ingress, load balancing, automatic scaling, manual scaling, etc.), security (e.g., secure transport layer protocol (TLS), etc.), service management (e.g., timed tasks, monitoring metrics, gray scale publishing, etc.), architecture (e.g., online and offline hybrid orchestration), storage (e.g., data source docking, dataforms, time-to-live values (TTL), etc.), artificial intelligence algorithm parametrization (e.g., grid search, random search, bayesian search, etc.).

According to an exemplary embodiment of the present disclosure, the step of performing application development may include: providing the user with one or more packaged characteristic capabilities related to the basic capabilities of the operation and maintenance and/or artificial intelligence application; and receiving configuration information of the characteristic capability in the one or more characteristic capabilities, which is input by a user, and calling the corresponding characteristic capability to execute application development. For example, the one or more characteristic capabilities include, but are not limited to, at least one of: the system comprises an operation and maintenance characteristic capability, a security characteristic capability, a service management characteristic capability, an online and offline mixed arrangement characteristic capability, a storage characteristic capability and an artificial intelligence algorithm tuning parameter capability. For example, the operation and maintenance characteristic capabilities include, but are not limited to, at least one of: load balancing feature capability, dynamic scaling capability, manual scaling capability, exposed service path feature capability, gateway security policy feature capability, timing policy feature capability, publishing policy feature capability.

In addition, according to an exemplary embodiment of the present disclosure, the application publishing method may further include an application debugging process, that is, after the user completes the application development, in response to a request for performing debugging on the application, which is input by the user, the user is provided with a cloud environment for the developer to perform debugging. In order to facilitate rapid iterative verification and low-cost trial and error of a developer, a cloud environment can be provided for debugging a user, and at this stage, the developer does not perform integrated test but performs various module tests, so that identity verification does not need to be uploaded, and application description files do not need to be filled in advance. Debugging may be understood as local testing.

In the following, the overall flow from user registration to application publication is described with reference to fig. 2, according to an exemplary embodiment of the present disclosure. Fig. 2 is a flowchart illustrating an application publication method according to another exemplary embodiment of the present disclosure.

Referring to fig. 2, a developer account may be registered with a user and a developer certificate may be issued to the user in response to a request for registering the developer account input by the user in step 201.

At step 202, application development may be performed in response to a request to develop an application input by a user.

In step 203, a cloud environment may be provided to the user for the user to perform debugging in response to a user input request to perform debugging of the application.

At step 204, an internal test may be executed on the application in response to a user-entered request for the application execution internal test.

At step 205, an on-shelf audit can be performed on the application in response to a user input request to perform an audit on the application.

At step 206, publication may be performed on the application in response to a user input request to perform publication on the application.

According to an exemplary embodiment of the present disclosure, a user may perform development and release of an application on an application release platform according to the present disclosure according to the flow described with reference to fig. 2. If the user has previously registered a developer account, then execution of step 201 may be omitted. If the user wishes to publish the developed application on the application publication platform, then steps 202 and 203 may be omitted.

Referring to fig. 3, an application publication platform 300 according to an exemplary embodiment of the present disclosure may include an interface module 310, an inline module 320, an audit module 330, and a publication module 340.

The interface module 310 may be used to interact with a user, for example, provide an interactive interface (e.g., an instrumented interface, an audit interface, a publishing interface, etc.) to a user, receive user input (e.g., a request input by a user to perform an instrumented, a request input by a user to perform an audit, a request input by a user to perform a publishing, etc.), feedback to a user, and so forth.

Internal test module 320 may be operative to execute an internal test on an application in response to a first request for the application input by a user.

According to an example embodiment of the present disclosure, the application publication platform 300 may further include a rights module (not shown) for authenticating a user (e.g., licensing and rights authentication). Before the inline module 320 performs the application test, the authority module is required to authenticate the user based on the information about the developer's credentials. After the user passes the identity authentication, the internal test module 320 may package the application into a predetermined application format based on the description file of the application, and perform a test on the application in the predetermined application format in the internal test environment identical to the real platform environment. Of course, the packaging of the application by the instrumentation module 320 may be performed before or after the user authentication performed by the permission module. Of course, a separate authority module for authenticating the user may not be required, and the internal test module 320 may include a function for authenticating the user. Here, the predetermined application format may be an official application format to which the application distribution platform is applicable. Here, the internal test module 320 may provide an internal test environment that is the same as the real platform environment for the user to test, belongs to a sandbox environment test, and may help the user to find a problem in time, so as to avoid affecting the service in the real environment.

The review module 330 may be configured to perform an on-shelf review on the application in response to a second request input by a user to perform a review on the application after the application has been tested. That is, after the functional test of the application is completed, strict checking of the normative is required for unified management and seamless integration. The audited content may include, but is not limited to, at least one of performance, security, high availability, page layout, and compliance.

According to an example embodiment of the present disclosure, the application publication platform 300 may further include a rights module (not shown) for authenticating a user (e.g., licensing and rights authentication). Before the review module 330 performs the on-shelf review, the permission module is required to authenticate the user based on information about the developer's credentials. After the user passes the identity authentication, the auditing module 330 may audit whether the normalization of the application complies with the upper-shelf standard. Of course, a separate permission module for authenticating the user may not be required, and the audit module 330 may include functionality for authenticating the user.

According to an exemplary embodiment of the disclosure, the audit module 330 may be configured to perform at least one of the following steps: checking whether the performance of the application meets the production requirement; auditing whether the safety of the application meets enterprise-level requirements; auditing whether the application passes vulnerability scanning; auditing whether the application has high availability and reaches a specified level; checking whether the layout of the application page is standard; auditing whether the application adopts an open source product; auditing whether the application is subjected to intellectual property authentication or not; and checking whether the help document of the application is complete.

The publishing module 340 may be configured to perform publishing for the application in response to a third request to perform publishing for the application input by the user after the application passes the on-shelf audit.

According to an exemplary embodiment of the present disclosure, the publishing module 340 may include at least one of the following modules according to a publishing (i.e., out-of-package publishing) function: the user management module comprises user information management, secret key (AK) management and the like which execute the authority to make package publishing and is used for verifying whether the user has the package publishing authority; the module management module comprises an execution application bottom layer realization module management and is used for configuring the code branch of the bottom layer module which is depended by the release application; the product management module is used for managing all applications developed by a user; the version management module manages the product version number and the module version number and is used for managing the version of each application; a tag management module, including management of tags, e.g., marking specific use customers, projects, departments, etc., for managing the use of each package out.

According to an example embodiment of the present disclosure, the application publication platform 300 may further include a rights module (not shown) for authenticating a user (e.g., licensing and rights authentication). Before the publishing module 340 performs out-package publishing, the rights module is required to authenticate the user based on information about the developer's credentials. After the user is authenticated, the publishing module 340 may perform application publishing. Of course, a separate permission module for authenticating the user may not be required, and the audit module 330 may include functionality for authenticating the user. For example, the publishing module 340 may be configured to: authenticating, by the permission module, the user based on the information about the developer certificate; confirming whether the package-out authority is provided or not based on the information about the developer certificate; after the user passes the identity authentication and is confirmed to have the package-out authority, receiving information about the application selected by the user to be issued and the version number thereof through the interface module 310; checking whether a code branch of an underlying module on which the application having the version number is issued depends is correct, based on information about the application selected by a user to be issued and the version number thereof; receiving information about the user marked out-of-packet usage through the interface module 310 if the code branch is correct; tagging and/or remarking the application with the version number based on information about the out-of-package use of the user tag; generating an installation package for the application having the version number to install and publish the application on a publication platform. After the application is installed and published on the publishing platform, the application may be launched and put into use.

Further, according to an exemplary embodiment of the present disclosure, the application issuing platform 300 may further include a permission module (not shown) configured to register a developer account for the user and issue a developer certificate to the user in response to a request for registering the developer account input by the user. That is, when a user first uses the application publishing platform to develop or publish an application, the user needs to register and acquire a developer account for identity authentication and authorization. Further, the rights module may be configured to authenticate the user (e.g., permissions and rights authentication) as described above.

Further, according to an exemplary embodiment of the present disclosure, the application publishing platform 300 may further include a development module (not shown) configured to perform application development in response to a request for developing an application input by a user. That is, when a user has developed an application, instrumentation, auditing, and publishing may be performed on the application publishing platform. When the user does not develop the application, the application development can be executed on the application publishing platform, and internal test, audit and publishing are executed after the application is developed.

According to an exemplary embodiment of the present disclosure, the application publishing platform 300 may give the user maximum development freedom, and the user may perform development of any kind of applications on the application publishing platform 300, for example, development may be performed based on a Docker ecology. For better standardization, the application publishing platform 300 may provide a proposed standard development flow and provide various Software Development Kits (SDKs) and gadgets to help users complete application development. For example, a debug tool commonly used for code error correction, a profile tool commonly used for performance analysis, and the like may be provided. The user only needs to utilize the provided SDK and the small tool to execute development according to the process, and the convenience and the efficiency of the user can be improved. For example, the development module is configured to apply a development process, but is not limited to, developing an application interface of an application in response to user input of planning information about the application interface; developing data manipulation and storage capabilities of the application in response to design information input by a user regarding data manipulation and storage; developing a multi-page jump implementation capability of the application in response to user-entered design information regarding a multi-page jump implementation; developing a service implementation capability of the application in response to user-entered configuration information regarding the service implementation; in response to configuration information input by a user about perfecting application characteristics and details, perfecting the application characteristics and details of the application; executing a code self-test on the application in response to a request for application testing input by a user; in response to a user-entered request for application packaging and signing, packaging and signing are performed on the application. Of course, the sequence of the above-described flows is only exemplary, the above-described development processes may also be performed in any sequence, and furthermore, some or all of the above-described operations may also be omitted or any other operations required for developing an application may be added as needed.

According to an exemplary embodiment of the disclosure, the application publishing platform 300 may organize and encapsulate available resources into entities regarding the common capabilities of the operation and maintenance or the basic AI, and directly provide the entities to the user for code-free configuration. That is, the user may not need to perform code development of operation and maintenance or common capabilities, but only need to specify in the configuration file which operation and maintenance features or AI features need to be added to directly invoke the packaged relevant capabilities. Entities that have encapsulated available resources for direct invocation of related capabilities may be referred to as feature capabilities. The application publication platform 300 may provide a property capability library including at least one property capability, which may include property capabilities that may include, but are not limited to, the following: traffic and network (e.g., ingress, load balancing, automatic scaling, manual scaling, etc.), security (e.g., secure transport layer protocol (TLS), etc.), service management (e.g., timed tasks, monitoring metrics, gray scale publishing, etc.), architecture (e.g., online and offline hybrid orchestration), storage (e.g., data source docking, dataforms, time-to-live values (TTL), etc.), artificial intelligence algorithm parametrization (e.g., grid search, random search, bayesian search, etc.).

According to an example embodiment of the present disclosure, the development module may be configured to: providing the user with one or more packaged characteristic capabilities related to the basic capabilities of the operation and maintenance and/or artificial intelligence application; and receiving configuration information of the characteristic capability in the one or more characteristic capabilities, which is input by a user, and calling the corresponding characteristic capability to execute application development. For example, the one or more characteristic capabilities include, but are not limited to, at least one of: the system comprises an operation and maintenance characteristic capability, a security characteristic capability, a service management characteristic capability, an online and offline mixed arrangement characteristic capability, a storage characteristic capability and an artificial intelligence algorithm tuning parameter capability. For example, the operation and maintenance characteristic capabilities include, but are not limited to, at least one of: load balancing feature capability, dynamic scaling capability, manual scaling capability, exposed service path feature capability, gateway security policy feature capability, timing policy feature capability, publishing policy feature capability.

In addition, according to an exemplary embodiment of the present disclosure, the application publishing platform 300 may further include a debugging module configured to provide a cloud environment to a user for a developer to perform debugging in response to a request for performing debugging on the application, which is input by the user, after the user completes the application development. In order to facilitate rapid iterative verification and low-cost trial and error by developers, the application publishing platform 300 may provide a cloud environment for users to debug, and at this stage, the developers do not perform an integrated test but perform various module tests, so that the developers do not need to upload identity verification or fill in application description files in advance. Debugging may be understood as local testing.

Referring to fig. 4, an application publishing platform 400 according to an exemplary embodiment of the present disclosure may include an interface module 410, a rights module 420, a development module 430, a debugging module 440, an introspection module 450, an auditing module 460, and a publishing module 470. FIG. 4 provides functional modules of a full flow from user registration to application publication in accordance with an exemplary embodiment of the present disclosure.

The interface module 410 may be used to interact with a user, for example, provide an interactive interface (e.g., a user registration interface, a development interface, a debugging interface, an introspection interface, an audit interface, a publishing interface, etc.) to a user, receive user input (e.g., a request to register a developer account input by a user, a request to develop an application input by a user, a request to perform debugging input by a user, a request to perform introspection input by a user, a request to perform audit input by a user, a request to perform publishing input by a user, etc.), feedback to a user, and so forth.

The permissions module 420 may register a developer account for a user and issue a developer certificate to the user in response to a request to register the developer account input by the user. In addition, the rights module 420 may authenticate the user (e.g., permit and rights authentication). Here, the authority module 420 has the same function as the authority module (not shown) described with reference to fig. 3, and thus, is not described in detail herein.

The development module 430 may perform application development in response to a request for developing an application input by a user. Here, the authority module 430 has the same function as the development module (not shown) described with reference to fig. 3, and thus, is not described in detail herein.

The debugging module 440 may provide a cloud environment to the user for the user to perform debugging in response to a user-entered request to perform debugging of the application. Here, the debugging module 440 has the same function as the debugging module (not shown) described with reference to fig. 3, and thus, will not be described herein again.

In response to a request for the application to execute an internal test entered by a user, internal test module 450 may execute an internal test on the application. Here, the debugging module 450 has the same function as the internal test module 320 described with reference to fig. 3, and thus, is not described herein again.

The review module 460 may perform an on-shelf review for the application in response to a user input request to perform a review for the application. Here, the auditing module 460 has the same function as the auditing module 330 described with reference to fig. 3, and therefore, will not be described in detail here.

The publication module 470 may perform publication for the application in response to a user input request to perform publication for the application. Here, the auditing module 470 has the same function as the publishing module 340 described with reference to fig. 3, and thus, will not be described again here.

According to an exemplary embodiment of the present disclosure, a user may perform development and release of an application on the application release platform 400 according to the present disclosure according to the flow described with reference to fig. 2. If the user has previously registered a developer account, then execution of step 201 by the permissions module 420 may be omitted. If the user wishes to publish the developed application on the application publication platform, steps 202 and 203 may be omitted from being performed by the development module 430 and the debugging module 440, respectively.

In addition, the application publishing method and the application publishing platform disclosed by the invention can be applied to not only AI scenes, but also application construction of any scene can be supported, including big data analysis scenes, CRM, visualization and the like, as long as the application is positioned for solving a specific business problem by using a code scheme.

In addition, the application publishing method and the application publishing platform can be applied to public clouds, private clouds, hybrid clouds, all-in-one machines and the like.

The application publishing method and the application publishing platform according to the exemplary embodiments of the present disclosure have been described above with reference to fig. 1 to 4.

The various modules in the application distribution platform shown in fig. 3 and 4 may be configured as software, hardware, firmware, or any combination thereof that performs particular functions. For example, each module may correspond to a dedicated integrated circuit, to pure software code, or to a combination of software and hardware. Furthermore, one or more functions implemented by the respective modules may also be uniformly executed by components in a physical entity device (e.g., a processor, a client, a server, or the like).

Further, the application distribution method described with reference to fig. 1 and 2 may be implemented by a program (or instructions) recorded on a computer-readable storage medium. For example, according to an exemplary embodiment of the present disclosure, a computer-readable storage medium storing instructions may be provided, wherein the instructions, when executed by at least one computing device, cause the at least one computing device to perform an application publishing method according to the present disclosure.

The computer program in the computer-readable storage medium may be executed in an environment deployed in a computer device such as a client, a host, a proxy device, a server, and the like, and it should be noted that the computer program may also be used to perform additional steps other than or more specifically processes when the steps are performed, and the content of the additional steps and the further processes are mentioned in the description of the related methods with reference to fig. 1 and 2, and therefore will not be described in detail here to avoid repetition.

It should be noted that each module in the application publishing platform according to the exemplary embodiment of the present disclosure may completely depend on the running of the computer program to realize the corresponding function, that is, each module corresponds to each step in the functional architecture of the computer program, so that the whole system is called by a special software package (e.g., lib library) to realize the corresponding function.

Alternatively, the various modules shown in fig. 3 and 4 may be implemented by hardware, software, firmware, middleware, microcode, or any combination thereof. When implemented in software, firmware, middleware or microcode, the program code or code segments to perform the corresponding operations may be stored in a computer-readable medium such as a storage medium, so that a processor may perform the corresponding operations by reading and executing the corresponding program code or code segments.

For example, exemplary embodiments of the present disclosure may also be implemented as a computing device including a storage component having stored therein a set of computer-executable instructions that, when executed by a processor, perform an application publishing method according to exemplary embodiments of the present disclosure.

In particular, computing devices may be deployed in servers or clients, as well as on node devices in a distributed network environment. Further, the computing device may be a PC computer, tablet device, personal digital assistant, smart phone, web application, or other device capable of executing the set of instructions.

The computing device need not be a single computing device, but can be any device or collection of circuits capable of executing the instructions (or sets of instructions) described above, individually or in combination. The computing device may also be part of an integrated control system or system manager, or may be configured as a portable electronic device that interfaces with local or remote (e.g., via wireless transmission).

In a computing device, a processor may include a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a programmable logic device, a special purpose processor system, a microcontroller, or a microprocessor. By way of example, and not limitation, processors may also include analog processors, digital processors, microprocessors, multi-core processors, processor arrays, network processors, and the like.

Some of the operations described in the application publication method according to the exemplary embodiment of the present disclosure may be implemented by software, some of the operations may be implemented by hardware, and further, the operations may be implemented by a combination of software and hardware.

The processor may execute instructions or code stored in one of the memory components, which may also store data. The instructions and data may also be transmitted or received over a network via a network interface device, which may employ any known transmission protocol.

The memory component may be integral to the processor, e.g., having RAM or flash memory disposed within an integrated circuit microprocessor or the like. Further, the storage component may comprise a stand-alone device, such as an external disk drive, storage array, or any other storage device usable by a database system. The storage component and the processor may be operatively coupled or may communicate with each other, such as through an I/O port, a network connection, etc., so that the processor can read files stored in the storage component.

In addition, the computing device may also include a video display (such as a liquid crystal display) and a user interaction interface (such as a keyboard, mouse, touch input device, etc.). All components of the computing device may be connected to each other via a bus and/or a network.

The application publication method according to an exemplary embodiment of the present disclosure may be described as various interconnected or coupled functional blocks or functional diagrams. However, these functional blocks or functional diagrams may be equally integrated into a single logic device or operated on by non-exact boundaries.

Thus, the application publishing method described with reference to fig. 1 and 2 may be implemented by a system comprising at least one computing device and at least one storage device storing instructions.

According to an exemplary embodiment of the present disclosure, the at least one computing device is a computing device for executing the application publishing method according to an exemplary embodiment of the present disclosure, the storage device having stored therein a set of computer-executable instructions that, when executed by the at least one computing device, perform the application publishing method described with reference to fig. 1 and 2.

While various exemplary embodiments of the present disclosure have been described above, it should be understood that the above description is exemplary only, and not exhaustive, and that the present disclosure is not limited to the disclosed exemplary embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the disclosure. Therefore, the protection scope of the present disclosure should be subject to the scope of the claims.

Claims

1. An application publishing method, comprising:

executing an application execution internal test in response to a first request for the application execution internal test input by a user;

after the application is tested, responding to a second request for performing audit on the application, which is input by a user, and performing on-shelf audit on the application;

and after the application passes the on-shelf audit, responding to a third request input by a user for executing the release of the application, and executing the release of the application.

2. The application issuing method according to claim 1, wherein the first request includes information on a developer certificate and a description file of the application;

wherein the executing an internal test on the application comprises:

authenticating the user based on the information about the developer certificate;

packaging the application into a preset application format based on the description file of the application;

and after the user passes the identity authentication, testing the application in the preset application format in the same internal test environment as the real platform environment.

3. The application issuing method according to claim 1, wherein the second request includes information on a developer certificate;

wherein the performing an on-shelf audit on the application comprises:

and after the user passes the identity authentication, checking whether the normalization of the application conforms to the upper frame standard.

4. The application issuing method according to claim 3, wherein the verifying whether the application normative complies with the upper frame standard after the user passes the identity authentication includes at least one of the following steps:

checking whether the performance of the application meets the production requirement;

auditing whether the safety of the application meets enterprise-level requirements;

auditing whether the application passes vulnerability scanning;

auditing whether the application has high availability and reaches a specified level;

checking whether the layout of the application page is standard;

auditing whether the application adopts an open source product;

auditing whether the application is subjected to intellectual property authentication or not;

and checking whether the help document of the application is complete.

5. The application issuing method according to claim 1, wherein the third request includes information on a developer certificate;

wherein the executing publishing of the application comprises:

based on the information about the developer certificate, performing identity authentication on the user and confirming whether the user has the packaging right;

after the user passes identity authentication and is confirmed to have the package-out authority, receiving information about the application selected by the user and to be issued and the version number of the application;

checking whether a code branch of an underlying module on which the application having the version number is issued depends is correct, based on information about the application selected by a user to be issued and the version number thereof;

receiving information regarding the user marked out-of-packet usage if the code branch is correct;

tagging and/or remarking the application with the version number based on information about the out-of-package use of the user tag;

generating an installation package for the application having the version number to install and publish the application on a publication platform.

6. The application publication method of claim 1, further comprising:

in response to a request to register a developer account input by a user, the developer account is registered for the user and a developer certificate is issued to the user.

7. The application publication method of claim 1, further comprising:

the application development is performed in response to a request for developing an application input by a user.

8. An application publication platform comprising:

an interface module configured to receive a user input;

an internal test module configured to execute an internal test on an application in response to a first request for the application execution internal test input by a user;

the auditing module is configured to respond to a second request for auditing the application input by a user after the application is tested, and to perform on-shelf auditing on the application;

and the publishing module is configured to respond to a third request for publishing the application, which is input by a user, after the application passes the on-shelf audit, and publish the application.

9. A computer-readable storage medium storing instructions that, when executed by at least one computing device, cause the at least one computing device to perform the application publication method of any one of claims 1 to 7.

10. A system comprising at least one computing device and at least one storage device storing instructions that, when executed by the at least one computing device, cause the at least one computing device to perform the application publishing method of any of claims 1 to 7.