CN118295692A - Resource release method, medium, device and computing equipment - Google Patents

Abstract

The embodiment of the disclosure provides a resource release method, medium, device and computing equipment, and relates to the technical field of Internet. The resource release method comprises the following steps: generating a resource release package based on resource information corresponding to the resource to be released; a publishing instance package is then generated based on the resource publishing package and the target server to send the publishing instance package to the target server. The method solves the problems that resources are required to be derived from each sub-service during resource release in the related technology, and the efficiency is poor, simplifies user operation during resource release, effectively reduces the working cost of resource release, and improves the resource release efficiency. Further, embodiments of the present disclosure provide a medium, apparatus, and computing device.

Description

Resource release method, medium, device and computing equipment

Technical Field

The embodiment of the disclosure relates to the technical field of internet, and more particularly, to a resource publishing method, medium, device and computing equipment.

Background

This section is intended to provide a background or context to the embodiments of the disclosure recited in the claims. The description herein is not admitted to be prior art by inclusion in this section.

In the related art, a development process of programs such as software, applications, functions, services and the like includes a release link from an offline development environment to an online environment. To ensure that a published program can be applied in an online environment, it is often necessary to publish all resources corresponding to the program from a development environment into the online environment.

Because the resources corresponding to the program generally comprise a plurality of different types, in the process of releasing the resources, the resources of the corresponding types need to be derived from the sub-services where the resources of the respective types are located, and then the resources are derived in the online environment of the releasing party, which is quite low in efficiency.

Disclosure of Invention

The disclosure provides a resource release method, medium, device and computing equipment, which are used for solving the problem that resources are required to be derived from all sub-services during resource release in the related technology, and the efficiency is poor.

In a first aspect of the embodiments of the present disclosure, a resource publishing method is provided, applied to a publisher server, where the publisher server is configured to send out a resource to be published, and includes:

Generating a resource release package based on resource information corresponding to the resource to be released;

Based on the resource release package and the target server, a release instance package is generated to send the release instance package to the target server, and the target server is used for receiving the release instance package.

In a second aspect of the embodiments of the present disclosure, there is provided a resource publishing method applied to a target server, where the target server is configured to receive a resource to be published, including:

determining resources to be distributed in a distribution instance package;

and selecting at least one resource from the resources to be published, and performing publication processing.

In a third aspect of the disclosed embodiments, there is provided a computer-readable storage medium comprising:

computer-readable storage medium having stored therein computer-executable instructions which, when executed by a processor, are adapted to carry out a resource issuing method according to the first aspect of embodiments of the present disclosure; and/or computer-executable instructions, when executed by a processor, for implementing a resource distribution method as in the second aspect of embodiments of the present disclosure.

In a fourth aspect of the embodiments of the present disclosure, there is provided a resource publishing device applied to a publisher server, where the publisher server is configured to publish a resource to be published, the device including:

the generation module is used for generating a resource release package based on resource information corresponding to the resource to be released;

the sending module is used for generating a release instance package based on the resource release package and the target server so as to send the release instance package to the target server, and the target server is used for receiving the release instance package.

In a fifth aspect of the embodiments of the present disclosure, there is provided a resource publishing device applied to a target server, where the target server is configured to receive a resource to be published, the device including:

the selection module is used for determining resources to be distributed in the distribution instance package;

and the release module is used for selecting at least one from the resources to be released and carrying out release processing.

In a sixth aspect of embodiments of the present disclosure, there is provided a computing device comprising:

At least one processor;

and a memory communicatively coupled to the at least one processor;

Wherein the memory stores instructions executable by the at least one processor to cause the computing device to perform a resource issuing method as in the first aspect of the present disclosure; and/or to cause the computing device to perform the resource publishing method as in the second aspect of the present disclosure.

According to the resource release method, medium, device and computing equipment of the embodiment of the disclosure, a resource release package is generated based on resource information corresponding to resources to be released; a publishing instance package is then generated based on the resource publishing package and the target server to send the publishing instance package to the target server. Therefore, unified flow and standard of data resource release can be provided, the resource release can be completed through the flow and standard no matter what type of resource to be released, and the resource to be released is packaged into a resource release package, so that the resource corresponding upstream dependent resource can be conveniently and automatically added into the resource release package, and a user does not need to configure the resource corresponding upstream dependent resource and various bottom layer detail information during resource release, so that the user operation during resource release is simplified, the working cost of resource release is effectively reduced, and the resource release efficiency is improved.

Drawings

The above, as well as additional purposes, features, and advantages of exemplary embodiments of the present disclosure will become readily apparent from the following detailed description when read in conjunction with the accompanying drawings. Several embodiments of the present disclosure are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings, in which:

FIG. 1 schematically illustrates an application scenario diagram according to an embodiment of the present disclosure;

FIG. 2 schematically illustrates a flow diagram of a resource publishing method according to another embodiment of the present disclosure;

FIG. 3a schematically illustrates a flow diagram of a resource publishing method according to another embodiment of the present disclosure;

FIG. 3b schematically illustrates a flow chart of a resource list determination method provided by the embodiment of FIG. 3 a;

FIG. 3c schematically illustrates a flow chart of a method for adding resources to a resource distribution pool provided by the embodiment of FIG. 3 a;

FIG. 3d schematically illustrates a flow chart of a method of generating a resource publication package provided by the embodiment of FIG. 3 a;

FIG. 3e schematically illustrates a flow chart of a method for determining upstream resources to publish resource dependent provided by the embodiment of FIG. 3 a;

FIG. 3f schematically illustrates a flow chart of a method of sending a publishing instance package provided by the embodiment of FIG. 3 a;

FIG. 4 schematically illustrates a flow diagram of a resource publishing method according to another embodiment of the present disclosure;

FIG. 5 schematically illustrates a flow diagram of a resource publishing method in accordance with another embodiment of the present disclosure;

FIG. 6 schematically illustrates a structural schematic diagram of a storage medium according to still another embodiment of the present disclosure;

FIG. 7 schematically illustrates a schematic configuration of a resource issuing apparatus according to still another embodiment of the present disclosure;

FIG. 8 schematically illustrates a schematic configuration of a resource issuing apparatus according to still another embodiment of the present disclosure;

fig. 9 schematically illustrates a structural schematic diagram of a computing device according to still another embodiment of the present disclosure.

In the drawings, the same or corresponding reference numerals indicate the same or corresponding parts.

Detailed Description

The principles and spirit of the present disclosure will be described below with reference to several exemplary embodiments. It should be understood that these embodiments are presented merely to enable one skilled in the art to better understand and practice the present disclosure and are not intended to limit the scope of the present disclosure in any way. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

Those skilled in the art will appreciate that embodiments of the present disclosure may be implemented as a system, apparatus, device, method, or computer program product. Accordingly, the present disclosure may be embodied in the following forms, namely: complete hardware, complete software (including firmware, resident software, micro-code, etc.), or a combination of hardware and software.

According to an embodiment of the disclosure, a resource release method, medium, device and computing equipment are provided.

Herein, it is to be understood that the terminology referred to is for convenience only and is not intended to be limiting in meaning. Furthermore, any number of elements in the figures is for illustration and not limitation, and any naming is used for distinction only and not for any limiting sense.

The following are descriptions of terms involved in this disclosure:

and (3) resource release: in the scheme, the method is used for representing the process of importing a developed program from a development environment to an operation environment, wherein the development environment is a system environment where the program is developed, such as a linux system and a java virtual machine system; the running environment is the system environment where the program is actually running, such as windows system and android system.

Resource to be distributed: in the scheme, the program for the development corresponding to the resource release process can be in the form of software, application, function, service and the like.

Upstream and downstream dependencies: in this scheme, an upstream dependency is used to indicate a program that is necessary for a developed program to run, and a downstream dependency is used to indicate a program that is necessary for a corresponding program to run while it is dependent on the present development.

Sub-services: in this scheme, the service provided by the data development platform is represented by a data development sub-service, a metadata management sub-service, a data service sub-service, a data quality sub-service and the like.

Herein, it is to be understood that the terminology referred to is for convenience only and is not intended to be limiting in meaning. Furthermore, any number of elements in the figures is for illustration and not limitation, and any naming is used for distinction only and not for any limiting sense.

It should be noted that, the user information (including, but not limited to, user equipment information, user personal information, etc.) and the data (including, but not limited to, data for analysis, stored data, presented data, etc.) related to the present disclosure are information and data authorized by the user or sufficiently authorized by each party, and the collection, use and processing of the related data need to comply with the related laws and regulations and standards, and be provided with corresponding operation entries for the user to select authorization or rejection.

Furthermore, any number of elements in the figures is for illustration and not limitation, and any naming is used for distinction only and not for any limiting sense.

Summary of The Invention

The inventor discovers that the development process of programs such as software, application, functions, services and the like comprises links such as task coding, arrangement, testing, code examination, release, online deployment and the like, namely DataOps methodology (a methodology for ensuring the timely and efficient delivery of high-quality data to a final user through continuous integration, deployment, testing and monitoring of data flows), wherein the task coding is a link for writing codes, the arrangement is a link for parameter and upstream and downstream dependence during program configuration operation, and the testing is a link for comparing and automatically returning program operation results through data testing services provided by a data development platform; a step of auditing the quality of the program codes by SQL code scanning and the like; and (3) issuing a link of the program from an offline development environment to an online environment. In the release link, to ensure that a released program can be applied in an online environment, all resources (including upstream and downstream dependencies) corresponding to the program are usually required to be released from a development environment to the online environment.

In the related art, since the resources corresponding to the program generally include a plurality of different types, in the process of publishing the resources, it is necessary to derive the resources of the corresponding types from the sub-services where the resources of the respective types are located, and then derive the resources in the online environment of the publisher, which is quite inefficient.

In the scheme, the resources to be distributed are packaged into the resource distribution package, and the distribution instance package is generated by combining the configuration of the target server, so that all types of resources corresponding to the program can be directly and completely transmitted to the target server through the distribution instance package, the resources are not required to be respectively exported from all sub-services, the resource distribution efficiency is obviously improved, and the workload of developers in the resource distribution process is saved.

Having described the basic principles of the present disclosure, various non-limiting embodiments of the present disclosure are specifically described below.

Application scene overview

Referring to fig. 1, in the process of publishing a resource, a publisher server 100 packages a resource 110 to be published into a resource publishing packet 120, combines with a target server 130 to generate a publishing instance packet 140, and then sends the publishing instance packet 140 to the target server 130 (a linear arrow in the figure indicates a sending process), and the target server 130 obtains the resource 110 to be published according to the publishing instance packet 140 and performs a publishing process, thereby completing the resource publishing process.

It should be noted that, in the scenario shown in fig. 1, the publisher server, the resource to be published, the resource publishing package, the target server, and the publishing instance package are only illustrated by taking one example as an example, but the disclosure is not limited thereto, that is, the number of the publisher server, the resource to be published, the resource publishing package, the target server, and the publishing instance package may be arbitrary.

Exemplary method

A resource publishing method according to an exemplary embodiment of the present disclosure is described below with reference to fig. 2 to 5 in conjunction with the application scenario of fig. 1. It should be noted that the above application scenario is only shown for the convenience of understanding the spirit and principles of the present disclosure, and the embodiments of the present disclosure are not limited in any way in this respect. Rather, embodiments of the present disclosure may be applied to any scenario where applicable.

Fig. 2 is a flowchart of a resource publishing method according to an embodiment of the present disclosure. As shown in fig. 2, the resource publishing method provided in this embodiment is applied to a publisher server, where the publisher server is configured to send out a resource to be published, and includes the following steps:

step S201, generating a resource release package based on resource information corresponding to the resource to be released.

Specifically, the resource to be distributed is a program in development, and the links of task coding, arrangement, testing and code examination are passed, so that the resource to be distributed needs to be distributed from a development environment to an online environment.

The resource to be distributed typically includes a plurality of different kinds of files, such as executable program files, encrypted document files, etc., and may also be a single file that has been packaged.

The resource information of the resource to be distributed comprises resource composition information such as the file name of the file corresponding to the resource to be distributed, the corresponding sub-service, a specific path and the like; the resource information of the resource to be distributed generally further includes resource configuration information such as a system environment required by the whole resource to be distributed, a relative path of each file in the distribution environment, an upstream dependent resource of the resource to be distributed and a specific path where the upstream dependent resource is located.

The publisher server provides a uniform universal interface, when a resource publishing packet is generated, the resource to be published can be directly obtained from each sub-service (the position or the server) of the data publishing platform according to the resource composition information in the resource information, and the upstream dependent resource corresponding to the resource to be published is obtained based on the resource configuration information to carry out integral packaging.

Therefore, a developer can directly complete packaging of the resources to be distributed through the universal interface, the resources to be distributed and the upstream dependent resources thereof do not need to be acquired from each sub-server, and the workload of the developer is remarkably saved.

Step S202, generating a release instance package based on the resource release package and the target server, and sending the release instance package to the target server.

The target server is used for receiving the release instance package.

Specifically, in the process of publishing the resource to be published to the target server, the resource to be published needs to be imported according to the environment, storage position and other information provided by the target server. Therefore, after obtaining the resource publishing package, it is further necessary to combine the information of the target server (i.e. the information of the system environment and the storage location provided by the target server), so as to obtain the publishing instance package that can be directly exported to the target server.

Therefore, when the target server receives the release instance package, the target server can directly unpack and install the release instance package, so that the adapted resources to be released can be obtained in the online environment provided by the target server, environment configuration operation for the resources to be released is not needed, the workload of a developer at the target server side is remarkably saved, and the resource release efficiency is improved.

In addition, the process in the embodiment can be directly finished on line without a developer carrying out a large amount of data export and import operation, so that the resource release efficiency is greatly improved.

According to the resource release method of the embodiment of the disclosure, a resource release package is generated based on resource information corresponding to resources to be released; a publishing instance package is then generated based on the resource publishing package and the target server to send the publishing instance package to the target server. Therefore, unified flow and standard of data resource release can be provided, the resource release can be completed through the flow and standard no matter what type of resource to be released, and the resource to be released is packaged into a resource release package, so that the resource corresponding upstream dependent resource can be conveniently and automatically added into the resource release package, and a user does not need to configure the resource corresponding upstream dependent resource and various bottom layer detail information during resource release, so that the user operation during resource release is simplified, the working cost of resource release is effectively reduced, and the resource release efficiency is improved.

Fig. 3a is a flowchart of a resource publishing method according to an embodiment of the present disclosure. As shown in fig. 3a, the resource publishing method provided in this embodiment is applied to a publisher server, and includes the following steps:

Step S301, determining resources to be distributed from a resource list, and determining resource information of the resources to be distributed.

The resource list is used for recording resource information of the reserved release resource.

Specifically, the resource list may be in the form of a web page or a visible program window, so as to display information of various resources supporting release (i.e. resources supporting release are resources for preparation release), and a developer may hook the resources supporting release in the resource list, and use the hooked resources as the resources to be released, so as to further determine the resource information corresponding to the resources to be released, and perform packaging release.

In one embodiment of the present disclosure, the publisher server and the target server are configured based on DataOps Pipeline architecture. DataOps Pipeline is a data operation pipeline architecture, which is an architecture for deploying a data development center on a server and completing links such as task coding, arrangement, testing, code examination, release, online deployment and the like in a program development process by providing various sub-services. In the data development center, a part for completing task release links is a release center. By configuring the publisher server and the target server as DataOps Pipeline architecture, the resource publishing package and the publishing instance package are conveniently configured in the publisher server, the publishing instance package can be conveniently imported in the target server, the resources to be published in the publishing instance package can be directly published, the operations such as environment configuration are not needed, and the convenience of the resource publishing process is improved.

In one embodiment of the present disclosure, the resource type of the resource to be issued includes at least one of: offline development tasks, real-time development tasks, structure tables, data transmission tasks, data quality monitoring tasks, data service program interfaces, real-time flow tables, parameter sets, and custom structure functions. The off-line development task is a program developed off-line, the real-time development task can be a program developed on-line, and the data transmission task and the data quality monitoring task are programs, services and the like for executing corresponding functions.

Further, as shown in fig. 3b, it is a flowchart of a resource list determination method, which includes the following steps:

step S3011, in response to an adding operation of adding the preliminary issue resource to the resource list, determines a resource origin server corresponding to the preliminary issue resource.

Specifically, when configuring the resource list, it is first necessary to determine a preliminary distribution resource in the distribution center, and add the preliminary distribution resource to the resource list. The publishing center automatically determines the corresponding resource source server according to the prepared publishing resources added to the resource list.

Illustratively, the publishing center provides a visual interface (such as a web page) to display the resources supporting the publication therein, that is, the resources for the preparation publication (at this time, the resources for the preparation publication may belong to different resource origin servers, but they are all preconfigured with the attribute supporting the publication, so that the publishing center can obtain the information of the resources), and the developer can check the resources for the preparation publication to be added to the resource list in the visual interface, that is, complete the operation of adding the resources for the preparation publication to the resource list (after the corresponding control is triggered again, complete the operation of adding). The publishing center can automatically determine the corresponding resource source server of the updated preparation publishing resource when the resource list is updated.

Step S3012, acquiring resource information corresponding to the resource to be released from the resource source server based on the resource information query interface.

Specifically, in the resource source server, resource information corresponding to the resource to be released is recorded.

The publishing center may configure resource information query interfaces for querying details of various types of resources from each sub-service, querying upstream resources on which the various types of resources depend, querying a resource list of resources to be published of a specified type, and the like. Meanwhile, the corresponding sub-service is required to support the interfaces and provide data for the issuing center through the resource information query interface.

Based on the resource information query interface, the publishing center can automatically acquire resource information corresponding to the resource to be published from the determined resource source server.

Step S3013, add the resource information of the preliminary release resource to the resource list.

Specifically, after the resource information of the resources to be released is obtained, the release center adds the resource information into the resource list, so that when the resources to be released are determined later, the corresponding resource information can be directly obtained from the resource list, and the efficiency of resource packaging in the resource release process is improved.

Step S302, at least one preparation release resource is selected from the resource list to serve as a resource to be released, and the resource to be released is added into the resource release pool.

The resource release pool is used for recording resource information of the resource to be released corresponding to the resource to be released by the resource release package to be generated.

Specifically, the resource release pool supports to arrange and package different types of resources from a plurality of different sub-services together at the same time, so that the problem that a batch import export resource scheme independently realized by each sub-service cannot handle cross-resource type dependence in the related technology (the batch import export scheme in the related technology is independently realized by each sub-service, each sub-service only can manage respective resource types and lacks global view, and cannot perceive other types of resource information can be solved. The developer can uniformly package and release the resources to be released with the relevant relationship by means of the release pool, so that the operation flow of cross-platform release of the data development task is simplified.

In one embodiment of the disclosure, through a resource-dependent query interface provided by a publishing center, the publishing center can also acquire other resource information of the resource dependence to be published from a source sub-service corresponding to the resource to be published, so that a resource publishing pool can intelligently detect other resources on which the resource is dependent and automatically add the other resources to a current resource publishing pool based on the resource to be published which is already added to the resource publishing pool (because the existing batch import and export schemes are respectively implemented on the sub-service side, lack global views, and are different in respective implementation schemes, the same intelligent scanning as the method and the function cost of adding the dependent resources are extremely high to be implemented), and a batch of resources with association relations can be conveniently bundled, packaged and published together.

For example, the resource to be distributed is an offline data development task, and references a Hive table resource (i.e. the Hive table resource is an upstream dependent resource of the resource to be distributed), at this time, only the offline data development task resource needs to be added to the resource distribution pool, and then the distribution center automatically adds the Hive table resource referenced by the resource distribution pool to the resource distribution pool through the intelligent adding function of the resource distribution pool.

Further, as shown in fig. 3c, which is a flowchart of a method for adding resources to a resource distribution pool, the method includes the steps of:

step S3021, determining the preliminary publishing resource selected from the resource list as a resource to be published.

Specifically, the publishing center can display the resource publishing pool in a Web page mode, a developer can select the preparation publishing resource which needs to be added into the resource publishing pool from the resource list based on the Web page, and the selected preparation publishing resource can be used as the resource to be published which is added into the resource publishing pool.

Step S3022, determining resource information of the resource to be distributed.

Specifically, the publishing center automatically determines resource information including information such as upstream dependent resources according to the selected resource to be published.

Step S3023, adding the resource to be distributed to the resource distribution pool.

Specifically, after determining resource information of the resource to be published, the publishing center automatically adds the resource to be published to the resource publishing pool.

Step S3024, adding the resource information of the resource to be distributed to the resource distribution pool.

Specifically, in addition to the resource to be distributed, the distribution center also adds the resource information (including the upstream dependent resource) of the resource to be distributed to the resource distribution pool.

For example, in the manner that the task1 and the Hive table tableA referenced by the task are offline developed to be distributed in the publisher server, and the batch import and export of the resource distribution in the related art, a developer needs to query the table structure of tableA through the metadata sub-service in the publisher server and create the table with the same structure in the target server, and then go to the offline development sub-service of the publisher server to export the offline package of the task1 and import the offline package to the target server, so that the flow is quite complex.

Based on the resource release pool provided by the disclosure, a developer only needs to add the offline development task1 to the resource release pool in the release center of the publisher server, the release center can automatically add the Hive table tableA on which the upstream is dependent to the resource release pool, and then a resource release package is created to release the resource to the target server, so that separate package release of the Hive table and the offline development task resource is not needed.

Step S303, generating a resource release package based on the resources to be released and the resource information thereof.

Specifically, the resource release package is the minimum release carrier of the resources to be released in the release process, and one resource release package can contain resources of various different types of resources. Through the resource release package, various different types of resources to be released and resource information thereof can be conveniently packaged and released to the target server, and the resource release flow is saved.

Further, as shown in fig. 3d, it is a flowchart of a method for generating a resource release package, which includes the following steps:

Step S3031, determining an upstream resource on which the resource to be distributed depends based on the resource information of the resource to be distributed.

Specifically, as described above, the resource release pool can store and package different types of resources temporarily, and can perform intelligent scanning according to the dependency relationship of the resources to be released, and the upstream resources on which the resources to be released are dependent in the resource release pool are automatically added into the release pool without manually searching and adding the upstream resources one by one, so that the repeated workload of resource release is obviously reduced. The implementation of this section is further described below.

Further, as shown in fig. 3e, which is a flowchart of a method for determining an upstream resource on which a resource depends to be issued, the method includes the steps of:

And A1, determining a source server corresponding to the resource to be distributed based on the resource information of the resource to be distributed.

Specifically, the resource information includes a source server corresponding to the sub-service that provides the resource to be distributed (the source server may be a publisher server, for example, the resource to be distributed is stored on the publisher server, or may be other servers other than the publisher server), so that the distribution center can determine the source server corresponding to the sub-service according to the resource information of the resource to be distributed.

And step A2, acquiring resource information of an upstream resource on which the resource to be distributed depends from a source server through a dependent resource query interface.

Specifically, the resource information query interface includes a dependent resource query interface for querying an upstream dependent resource (i.e., an upstream resource). The developer can add the most downstream resource (such as offline development task resource) to be released to the resource release pool from the release center Web page, and at this time, the intelligent dependency scanning task of the resource release pool is automatically triggered, namely, the resource information of the upstream resource is acquired from the source server through the dependency resource query interface.

In one embodiment of the disclosure, if there are multiple levels of upstream resources based on the resource dependence to be distributed, determining the upstream origin server where all the upstream resources are located step by step through the dependence resource query interface, and acquiring resource information of all the upstream resources on which the resource dependence to be distributed is located from the upstream origin server.

Specifically, the processing logic is as follows: by means of the resource dependence query interface, the issuing center can pull upstream dependence information of the current resource from the corresponding sub-service, then continuously scan the upstream dependence of the upstream dependence resource of the current resource in the same mode, recursively layer by layer until all the upstream resources directly and indirectly dependent on the current resource are scanned, and after the scanned resources are added to the resource issuing pool, the intelligent dependence scanning is finished.

Step S3032, adding the resource information of the upstream resource to the resource release package.

Specifically, after determining the upstream dependent resource, the corresponding resource information can be automatically added into the resource release package.

Further, there may be different specific ways to package the resources to be distributed into the resource distribution package corresponding to different kinds of resources to be distributed.

In one embodiment of the present disclosure, a manner of quickly creating a publishing package by using a single resource or multiple resources of the same type may be directly based on the resource list of the same type of ready publishing resource to generate a resource publishing package, i.e. the corresponding resources are checked from a resource list page of a publishing center and packaged in batches (the creation of the resource publishing package may not be completed by the resource publishing pool), which is very convenient for publishing resources without upstream and downstream dependency.

In one embodiment of the disclosure, there is a way of creating a resource release package by using resources that depend on upstream and downstream, the most downstream resource that needs to be released is required to be added to a resource release pool from a resource list page, then the dependent upstream resource is automatically added to the resource release pool through an intelligent adding function of the resource release pool, and finally the resources to be released with an association relationship in the resource release pool are packaged in batches (the problem of sequence of the resources is not required to be concerned during packaging, the voluntary type is contained in the resource information, and when the resource release operation is actually triggered, the resource release sequence arrangement is automatically performed according to the resource type of the resources to be released in the release instance package and the dependency relationship among the resources.

For example, if the developer only needs to publish Hive table resources tableA and tableB, since Hive table resources belong to the top-level resources (no upstream dependent resources), the developer can choose to directly sort out and publish two resources tableA and tableB in the publishing center resource list page.

If the developer needs to issue an offline development task1, the task1 depends on the Hive table resource tableA or other resources; the recommendation developer firstly adds the offline development task1 to the release pool, then uses the intelligent adding function of the release pool to add the upstream dependent resource of the task1 to the release pool, and finally packages and releases the associated resource together based on the release pool.

The developer does not need to care about which resources the task1 depends on, and the publishing center can automatically complete the scanning of the resources the task1 depends on. If the conventional batch import and export scheme is adopted, under this scenario, the developer needs to explicitly know which resources the task1 depends on, and then issue the dependent upstream resources to the target server where the receiver is located, and then the task1 may be issued, which is quite time-consuming and laborious in the whole flow, and cannot guarantee one success (because there may be situations of resource-dependent omission, configuration errors of relative addresses between different resources, etc.).

Step S304, determining a release strategy of the resources to be released in the resource release package.

The publishing policy comprises resource source server address information of the resource to be published in publishing, target address information stored in the target server and mapping configuration information, wherein the mapping configuration information is used for representing configuration information of an upstream resource which is relied in the migration process of the resource to be published from the resource source server to the target server.

Specifically, after the resource release package is created, the resource release package only contains the resource information of the resources to be released, and the resource release operation cannot be completed directly based on the resource information. There is also a need to generate a published instance package on the basis thereof.

The publishing instance package is an object which is really used for publishing and generated by the resource publishing package according to the publishing configuration under the appointed publishing policy, and the object not only contains the original resource information of the resource publishing package, but also contains information such as mapping configuration from a publisher to a receiver, namely the publishing policy.

Therefore, to publish the resource publication package to the target server, a publication policy needs to be selected to generate the publication instance package.

Step S305, generating a release instance package based on the resource release package and the release policy, so as to send the release instance package to the target server.

The publishing instance package comprises resource information of the resource to be published and a publishing policy.

Specifically, the resource publishing package and the publishing policy are combined together to generate a publishing instance package for performing the resource publishing operation at the target server. After the publishing instance package is obtained, it can be sent to the target server.

In one embodiment of the present disclosure, the published instance package may be sent to the target server directly based on the target address information.

Specifically, if the publisher server can be directly connected with the target server in a communication manner, the publisher instance package can be directly sent to the target server based on the target address information, so that the resource publishing efficiency is ensured.

Further, as shown in fig. 3f, which is a flowchart of a method for sending a published instance package, the method includes the steps of:

Step S3051, based on the target address information, transmits a release environment detection request to the target server.

Specifically, when determining the target server, the publishing center automatically determines the corresponding address information, namely the target address information, so as to communicate with the target server based on the target address information.

The publishing center may send an environment detection request to the target server to determine that the system environment in the target server meets the environment requirements of the resource publishing operation of the publishing instance package.

Step S3052, in response to the received detection passing information, a resource release request is sent to a target server to generate an approval work order corresponding to the release instance package.

The resource release request comprises a release instance package, and the approval work order is used for auditing a release strategy and resources to be released contained in the release instance package.

Specifically, the target server compares the environment requirement contained in the received environment detection request with the system environment of the target server, and when the system environment of the target server meets the environment requirement, the target server returns detection passing information.

The publishing center may then send a resource publishing request to the target server to confirm that the publishing instance package can be sent to the target server.

When the target server receives the resource release request, an approval work order is generated based on the resource release request so as to check whether the release instance package is received or not.

The approval work order comprises resource information corresponding to the resources to be distributed in the distribution instance package, application account information (namely account information corresponding to the distribution side server) and receiving account information (namely account information corresponding to the target server).

Further, the approval work order is a trigger entry of the actual release action of the resource, and is also an authority management and control point in the resource release process, and the approval work order contains resource information (usually displayed in a list form) of all the resources to be released, which are to be released after the approval of the corresponding resource release request is passed, user account information for initiating the resource release application, receiving account information of a receiver corresponding to the current release instance package, and the like, so that a work order approver can intuitively know which user wants to release which resources to be positioned, or an auditing system can conveniently confirm and record the release party and the receiver corresponding to the resources to be released.

After the resource release request is initiated, an administrator with relevant authority or a corresponding auditing system can truly trigger the release operation of the resource after the approval work order is approved.

In one embodiment of the present disclosure, the resource publishing package and the publishing policy may also be exported to the set storage address, so that the target server obtains the publishing instance package based on the resource publishing package and the publishing policy in the set storage address.

Specifically, if the publisher server can not realize communication connection with the target server, it is necessary to export the resource publishing package and the publishing policy to a set storage address (for example, export to a usb disk) at this time, and generate a publishing instance package accordingly, so as to import the publishing instance package to the target server from the set storage address, thereby ensuring the security of resource publishing.

According to the resource release method of the embodiment of the disclosure, the resource information of the reserved release resources is added into the resource list, at least one reserved release resource is selected from the resource list to serve as a resource to be released, the resource to be released is added into the resource release pool, then a resource release package is generated based on the resource to be released and the resource information thereof, the release strategy of the resource to be released in the resource release package is determined, so that a release instance package is generated based on the resource release package and the release strategy, and the release instance package is sent to the target server. Therefore, various different resources can be packaged in batches, a resource release package is generated and released to the environment of the target server, the user does not need to consider the dependency relationship of the resources to be released, the resource release efficiency is obviously improved, and the reliability of system release is enhanced.

Fig. 4 is a flowchart of a resource publishing method according to an embodiment of the present disclosure. As shown in fig. 4, the resource publishing method provided in this embodiment is applied to a target server, where the target server is configured to receive a resource to be published, and includes the following steps:

Step S401, determining resources to be distributed in a distribution instance package.

Specifically, in the resource release process, the target server mainly works to confirm and receive the release instance package, confirm the resources to be released therein according to the release instance package, and then perform resource release operation on the resources to be released.

And step S402, selecting at least one from the resources to be published, and performing the publishing process.

Specifically, not all resources to be published in the publishing instance packet received by the target server need to be published. The manager can pre-configure rules or manually select to select part of the resources from the resources to be distributed for distribution, such as distributing the related resources of the program which are already developed offline, but not distributing the related resources of the program which also need to be developed online.

According to the resource publishing method of the embodiment of the disclosure, the resource to be published in the publishing instance package is determined, and at least one resource to be published is selected for publishing. Therefore, the method and the device can receive and release the resources to be released in the target server where the receiver is located, and can simultaneously complete the resource release operation of a plurality of different types of resources to be released in the same release instance package, without importing and releasing resources one by one as in the related technology, thereby obviously improving the resource release efficiency.

Fig. 5 is a flowchart of a resource publishing method according to an embodiment of the present disclosure. As shown in fig. 5, the resource publishing method provided in this embodiment is applied to a target server, where the target server is configured to receive a resource to be published, and includes the following steps:

In step S501, in response to the received environment detection request, it is determined that the environment in the target server meets the requirement of publishing the environment, and detection passing information corresponding to the environment detection request is returned, so as to obtain the resource publishing request.

Specifically, as described in the foregoing embodiment, in the resource publishing process, the target server may first receive the environment detection request, and compare the system environment in the target server with the publishing environment requirement in the environment detection request.

When the system environment in the target server meets the release environment requirement in the environment detection request, the target server returns detection passing information corresponding to the environment detection request.

In one embodiment of the disclosure, in response to a received environment detection request, it is determined that an environment in a target server does not meet a release environment requirement, and detection failure information corresponding to the environment detection request is returned.

Specifically, there may be a case that the system environment in the target server does not meet the release environment requirement in the environment detection request, at this time, the target server may return detection failure information corresponding to the environment detection request, suspend the resource release process, and release alarm information to the relevant manager, so that the relevant manager reconfigures the system environment in the target server, or the publisher server reconfigures the release environment requirement corresponding to the resource to be released.

Step S502, responding to the received resource release request, and generating an approval work order corresponding to the resource release request.

The approval work order comprises a resource list corresponding to the resources to be distributed in the distribution instance package, application account information and receiving account information.

Specifically, after the environment detection passes, the target server receives a resource release request, where the resource release request includes resource information of a resource to be released, where the resource information includes application account information corresponding to a resource release application corresponding to the resource to be released and receiving account information of the resource to be released. And generating an approval work order based on the information so as to audit and record the related information of the resources to be distributed, wherein the information is convenient for an audit system or an auditor to confirm through a resource list, account information application and account information receiving corresponding to the resources to be distributed.

Step S503, receiving a release instance package corresponding to the resource release request in response to the received approval result of the approval work order.

Specifically, after the examination and approval work order is finished (and the recording of the relevant information of the resource to be distributed is finished), the target server starts to receive the corresponding distribution instance package.

In one embodiment of the present disclosure, for a case where the publisher server and the target server do not implement a communication connection, a publication instance package may be generated based on a resource publication package and a publication policy acquired from a set storage address. The subsequent resource release action can be completed through the release instance package generated offline.

Step S504, determining resources to be distributed and a distribution strategy in the distribution instance package.

The publishing policy comprises resource source server address information of the resource to be published in publishing, target address information stored in the target server and mapping configuration information, wherein the mapping configuration information is used for representing configuration information of an upstream resource which is relied in the migration process of the resource to be published from the resource source server to the target server.

Specifically, to ensure successful release of the resource, a release policy in the release instance package needs to be combined to ensure correct configuration of the resource to be released.

Step S505, at least one resource is selected from the resources to be published, and the publishing process is performed based on the mapping configuration information.

Specifically, in combination with mapping configuration information in the release policy, resources to be released, which need to be released, can be selected from the release policy to be released, and release processing is performed.

In an embodiment of the present disclosure, the manner of performing the publishing process may further be: and selecting at least two resources from the resources to be published, and performing the publishing processing based on the mapping configuration information corresponding to the resources to be published and the set resource class ordering mode.

Specifically, when more than two resources to be issued need to be issued, the resources to be issued are issued in sequence based on the mapping configuration information and the set ordering mode (namely, the resource class ordering mode).

In actual processing, when the examination and approval work order passes, the issuing operation of the issuing instance package is automatically executed, at this time, the issuing center in the target server firstly performs issuing arrangement of the resource type level according to the dependency relationship of the resource type, the resources contained in the dependent resource type are ensured to be issued before the dependent resource type is dependent on the resource, and then the issuing sequence of the resources of the same type in the same issuing instance package is arranged by the sub-service after the resources are sent to the sub-service.

In one embodiment of the present disclosure, the resource categories involved in the resource category ordering approach include at least one of: offline development tasks, real-time development tasks, structure tables, data transmission tasks, data quality monitoring tasks, data service program interfaces, real-time flow tables, parameter sets and custom structure functions; the release priority sequence among different types of resources comprises the following steps: the priority is sequentially reduced from offline development tasks, real-time development tasks, structure tables, data transmission tasks, data quality monitoring tasks, data service program interfaces, real-time flow tables, parameter sets to custom structure functions.

Specifically, based on the release sequence, effective and safe release of a plurality of resources to be released in different categories can be effectively ensured.

Further, corresponding to different relationships between the resources to be published, the specific publishing process includes the following conditions:

And in the first case, if the at least two selected resources to be distributed are of different types, performing distribution processing based on distribution priority sequences and mapping configuration information among the resources of different types.

Specifically, when the types of the resources to be distributed are different, but there is no inter-dependency relationship, the distribution processing is performed according to the distribution sequence based on the corresponding mapping configuration information.

And in the second case, if the at least two selected resources to be distributed are of the same category and the at least two resources to be distributed have a dependency relationship, the dependent resources to be distributed are distributed preferentially based on the mapping configuration information, and then the dependent resources to be distributed are distributed.

Specifically, if there is a dependency relationship between the resources to be issued, the dependency relationship is considered first, and if the classes of the resources to be issued are the same, the dependent resources to be issued (i.e., upstream dependent resources) are issued preferentially based on the mapping configuration information, and then the dependent resources to be issued (i.e., downstream dependent resources) are issued.

And thirdly, if the selected at least two resources to be distributed are of the same category and no dependency relationship exists among the resources to be distributed, distributing the at least two resources to be distributed based on the mapping configuration information.

Specifically, the resources to be distributed, which have no dependency relationship in the same category, can be distributed one by one according to the mapping configuration information, and other sequence relationships are not required to be referred to.

By the method, batch release of various different resources can be realized. Compared with the related batch import export scheme, the method has the advantages that a layer of arrangement is made according to the release sequence of the resource types, the automatic resource release capability which cannot be completed by the batch import export scheme is realized, and because the batch import export scheme can only support one type of resource release at a time, if the dependency relationship exists among different types of resources, only the dependent resource type of resources can be released manually, and then the downstream resource can not be released manually.

In one embodiment of the present disclosure, the environment in which the target server is considered includes an online environment and a development environment; the publishing process of the resource to be published also includes two cases, namely:

selecting at least one to-be-online resource from the to-be-distributed resources, and distributing the to-be-online resource to an online environment; or selecting at least one development state resource from the resources to be distributed, and distributing the resources to the development environment.

Specifically, the resources to be distributed include the resources to be on-line and the resources in the development state, and the environment of the target server includes the on-line environment and the development environment. For different release demands of resources to be released, different release operations of releasing the resources to an online environment and a development environment can be realized, and the different demands of resource release are met to the maximum extent.

According to the resource release method of the embodiment of the disclosure, after the environment detection request is received and passed, the resource release request is received, an approval work order is generated according to the resource release request, a release instance package can be obtained after the approval work order passes, and at least one resource to be released is selected for release processing. Therefore, the resources to be distributed received by the target server can be effectively distributed, the mapping configuration relation required by the distribution of the resources to be distributed in the target server can be met, the distribution of the resources in batches is realized, and the reliability and the efficiency of the distribution of the resources are obviously improved.

Exemplary Medium

Having described the method of the exemplary embodiments of the present disclosure, next, a storage medium of the exemplary embodiments of the present disclosure will be described with reference to fig. 6.

Referring to fig. 6, a program product 60 for implementing the above-described method according to an embodiment of the present disclosure is described, which may employ a portable compact disc read-only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present disclosure is not limited thereto.

The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium would include the following: an electrical connection having one or more wires, a portable disk, a hard disk, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

The readable signal medium may include a data signal propagated in baseband or as part of a carrier wave with readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. The readable signal medium may also be any readable medium other than a readable storage medium.

Program code for carrying out operations of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, partly on a remote computing device, or entirely on the remote computing device or server. In the context of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN).

Exemplary apparatus

Having described the medium of the exemplary embodiments of the present disclosure, the resource issuing device of the exemplary embodiments of the present disclosure will be described with reference to fig. 7 and 8, where the resource issuing device shown in fig. 7 is used to implement the resource issuing method in the method embodiment shown in fig. 2 to 3a, and the resource issuing device shown in fig. 8 is used to implement the resource issuing method in the method embodiment shown in fig. 4 to 5, and the implementation principle and technical effects thereof are similar to those of the foregoing corresponding method embodiment and are not repeated herein.

As shown in fig. 7, the resource publishing device 700 provided in the present disclosure is applied to a publisher server, where the publisher server is configured to send out a resource to be published, and includes:

a generating module 710, configured to generate a resource publishing packet based on resource information corresponding to a resource to be published;

And a sending module 720, configured to generate a publishing instance package based on the resource publishing package and a target server, so as to send the publishing instance package to the target server, where the target server is configured to receive the publishing instance package.

In one exemplary embodiment of the present disclosure, the generating module 710 is further configured to: before generating a resource release package based on resource information corresponding to the resource to be released, determining the resource to be released from a resource list, and determining resource information of the resource to be released, wherein the resource list is used for recording resource information of the resource to be released; or selecting at least one preparation release resource from the resource list as a resource to be released, and adding the resource to be released into a resource release pool, wherein the resource release pool is used for recording resource information of a resource release packet to be generated corresponding to the resource to be released; and generating a resource release package based on the resources to be released and the resource information thereof.

In an exemplary embodiment of the present disclosure, the generating module 710 is specifically configured to: determining the prepared release resource selected from the resource list as a resource to be released; determining resource information of resources to be distributed; adding the resources to be distributed into a resource distribution pool; and adding the resource information of the resources to be distributed to a resource distribution pool.

In an exemplary embodiment of the present disclosure, the generating module 710 is specifically configured to: determining an upstream resource on which the resource to be distributed depends based on the resource information of the resource to be distributed; and adding the resource information of the upstream resource to the resource release package.

In an exemplary embodiment of the present disclosure, the generating module 710 is specifically configured to: the publisher server comprises a dependent resource query interface, and determines a source server corresponding to the resource to be published based on the resource information of the resource to be published; resource information of an upstream resource on which the resource dependence is to be distributed is acquired from a source server through a dependent resource query interface.

In one exemplary embodiment of the present disclosure, the generating module 710 is further configured to: if the upstream resource depending on the resource to be distributed has multiple stages, determining the upstream source server where all the upstream resources are located step by step through the depending resource query interface, and acquiring the resource information of all the upstream resources depending on the resource to be distributed from the upstream source server.

In an exemplary embodiment of the present disclosure, the generating module 710 is specifically configured to: the resource list is obtained by: if the publisher server comprises a resource information query interface, determining a resource source server corresponding to the preliminary publication resource in response to an adding operation of adding the preliminary publication resource to the resource list; acquiring resource information corresponding to the resource to be released from a resource source server based on a resource information query interface; the resource information of the preliminary published resource is added to the resource list.

In an exemplary embodiment of the present disclosure, the generating module 710 specifically includes: the resource type of the resource to be issued comprises at least one of the following: offline development tasks, real-time development tasks, structure tables, data transmission tasks, data quality monitoring tasks, data service program interfaces, real-time flow tables, parameter sets, and custom structure functions.

In an exemplary embodiment of the present disclosure, the sending module 720 is specifically configured to: the resource information comprises resource source server address information corresponding to the resource to be distributed; determining a release strategy of a resource to be released in a resource release package, wherein the release strategy comprises resource source server address information of the resource to be released when released, target address information stored in a target server and mapping configuration information, and the mapping configuration information is used for representing configuration information of an upstream resource which is dependent in a migration process of the resource to be released from the resource source server to the target server; based on the resource release package and the release policy, a release instance package is generated to send the release instance package to the target server, wherein the release instance package contains resource information of resources to be released and the release policy.

In one exemplary embodiment of the present disclosure, the sending module 720 is further configured to: after generating a release instance package based on a predetermined release policy and a resource release package, transmitting the release instance package to a target server based on target address information; or exporting the resource release package and the release policy to the set storage address so that the target server obtains the release instance package based on the resource release package and the release policy in the set storage address.

In an exemplary embodiment of the present disclosure, the sending module 720 is specifically configured to: based on the target address information, sending a release environment detection request to a target server; and responding to the received detection passing information, sending a resource release request to a target server to generate an approval work order corresponding to the release instance package, wherein the resource release request comprises the release instance package, and the approval work order is used for auditing the release strategy and the resources to be released contained in the release instance package.

In an exemplary embodiment of the present disclosure, the transmitting module 720 specifically includes: the resource information comprises application account information corresponding to a resource release application corresponding to the resource to be released and receiving account information of the resource to be released; the approval work order comprises a resource list corresponding to the resources to be distributed in the distribution instance package, application account information and receiving account information.

In an exemplary embodiment of the present disclosure, the transmitting module 720 specifically includes: the publisher server and the target server are configured based on DataOpsPipeline architecture.

As shown in fig. 8, the resource publishing device 800 provided in the present disclosure is applied to a target server, where the target server is configured to receive a resource to be published, and includes:

A selection module 810, configured to determine resources to be published in a publishing instance package;

and the release module 820 is used for selecting at least one from the resources to be released and performing release processing.

In one exemplary embodiment of the present disclosure, the selection module 810 is further configured to: before determining to-be-issued resources in the issue instance package, responding to the received resource issue request, and generating an approval work order corresponding to the resource issue request, wherein the approval work order comprises a resource list corresponding to the to-be-issued resources in the issue instance package, application account information and receiving account information; and receiving a release instance package corresponding to the resource release request in response to the received approval result of the approval work order.

In one exemplary embodiment of the present disclosure, the selection module 810 is further configured to: before generating an approval work order corresponding to the resource release request in response to the received resource release request, determining that the environment in the target server meets the release environment requirement in response to the received environment detection request, and returning detection passing information corresponding to the environment detection request to acquire the resource release request; or responding to the received environment detection request, determining that the environment in the target server does not meet the requirement of the release environment, and returning the detection failing information corresponding to the environment detection request.

In one exemplary embodiment of the present disclosure, the selection module 810 is specifically configured to: determining resources to be distributed and a distribution strategy in a distribution instance package, wherein the distribution strategy comprises resource source server address information of the resources to be distributed when the resources to be distributed are distributed, target address information stored in a target server and mapping configuration information, and the mapping configuration information is used for representing configuration information of upstream resources which are relied on in the migration process of the resources to be distributed from the resource source server to the target server; at least one resource is selected from the resources to be published, and the publishing process comprises the following steps: and selecting at least one resource from the resources to be published, and carrying out the publishing processing based on the mapping configuration information.

In one exemplary embodiment of the present disclosure, the selection module 810 is further configured to: before determining the resources to be distributed and the distribution strategy in the distribution instance package, generating the distribution instance package based on the resource distribution package and the distribution strategy acquired from the set storage address.

In one exemplary embodiment of the present disclosure, the publication module 820 is specifically configured to: and selecting at least two resources from the resources to be published, and performing the publishing processing based on the mapping configuration information corresponding to the resources to be published and the set resource class ordering mode.

In one exemplary embodiment of the present disclosure, the publication module 820 is specifically configured to: if the at least two selected resources to be distributed are of different types, carrying out distribution processing based on distribution priority sequences and mapping configuration information among the resources of different types; or if the selected at least two resources to be distributed are of the same category and the at least two resources to be distributed have a dependency relationship, based on the mapping configuration information, preferentially distributing the dependent resources to be distributed, and then distributing the dependent resources to be distributed; or if the selected at least two resources to be distributed are of the same category and no dependency relationship exists among the resources to be distributed, distributing the at least two resources to be distributed based on the mapping configuration information.

In one exemplary embodiment of the present disclosure, the publication module 820 specifically includes: the resource categories include at least one of: offline development tasks, real-time development tasks, structure tables, data transmission tasks, data quality monitoring tasks, data service program interfaces, real-time flow tables, parameter sets and custom structure functions; the release priority sequence among different types of resources comprises the following steps: the priority is sequentially reduced from offline development tasks, real-time development tasks, structure tables, data transmission tasks, data quality monitoring tasks, data service program interfaces, real-time flow tables, parameter sets to custom structure functions.

In one exemplary embodiment of the present disclosure, the publication module 820 is specifically configured to: if the resources to be distributed comprise the resources to be on-line and the resources in the development state, the environment of the target server comprises an on-line environment and a development environment; selecting at least one to-be-online resource from the to-be-distributed resources, and distributing the to-be-online resource to an online environment; or selecting at least one development state resource from the resources to be distributed, and distributing the resources to the development environment.

Exemplary computing device

Having described the methods, media, and apparatus of exemplary embodiments of the present disclosure, a computing device of exemplary embodiments of the present disclosure is next described with reference to fig. 9.

The computing device 90 shown in fig. 9 is merely an example and should not be taken as limiting the functionality and scope of use of embodiments of the present disclosure.

As shown in fig. 9, the computing device 90 is in the form of a general purpose computing device. Components of computing device 90 may include, but are not limited to: the at least one processing unit 901, the at least one storage unit 902, and a bus 903 connecting different system components (including the processing unit 901 and the storage unit 902).

Bus 903 includes a data bus, a control bus, and an address bus.

The storage unit 902 may include readable media in the form of volatile memory, such as Random Access Memory (RAM) 9021 and/or cache memory 9022, and may further include readable media in the form of non-volatile memory, such as Read Only Memory (ROM) 9023.

The storage unit 902 may also include a program/utility 9025 having a set (at least one) of program modules 9024, such program modules 9024 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment.

The computing device 90 may also communicate with one or more external devices 904 (e.g., keyboard, pointing device, etc.). Such communication may occur through an input/output (I/O) interface 905. Moreover, the computing device 90 may also communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN) and/or a public network, such as the Internet, through a network adapter 909. As shown in fig. 9, the network adapter 909 communicates with other modules of the computing device 90 via the bus 903. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with computing device 90, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.

It should be noted that while several units/modules or sub-units/modules of the supply chain policy determination means and the object scoring model training means are mentioned in the above detailed description, such a division is merely exemplary and not mandatory. Indeed, the features and functionality of two or more units/modules described above may be embodied in one unit/module in accordance with embodiments of the present disclosure. Conversely, the features and functions of one unit/module described above may be further divided into ones that are embodied by a plurality of units/modules.

Furthermore, although the operations of the methods of the present disclosure are depicted in the drawings in a particular order, this is not required or suggested that these operations must be performed in this particular order or that all of the illustrated operations must be performed in order to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step to perform, and/or one step decomposed into multiple steps to perform.

While the spirit and principles of the present disclosure have been described with reference to several particular embodiments, it is to be understood that this disclosure is not limited to the particular embodiments disclosed nor does it imply that features in these aspects are not to be combined to benefit from this division, which is done for convenience of description only. The disclosure is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

Claims (10)

1. A resource publishing method, applied to a publisher server, the publisher server configured to send out a resource to be published, the method comprising:

Generating a resource release package based on resource information corresponding to the resource to be released;

and generating a release instance package based on the resource release package and a target server, so as to send the release instance package to the target server, wherein the target server is used for receiving the release instance package.

2. The resource publishing method of claim 1, wherein before generating the resource publishing packet based on the resource information corresponding to the resource to be published, further comprises:

Determining resources to be distributed from a resource list, and determining resource information of the resources to be distributed, wherein the resource list is used for recording resource information of resources to be distributed;

Or selecting at least one preparation release resource from a resource list as the resource to be released, and adding the resource to be released into a resource release pool, wherein the resource release pool is used for recording resource information of a resource release packet to be generated corresponding to the resource to be released;

And generating a resource release package based on the resource to be released and the resource information thereof.

3. The resource publishing method of claim 2, wherein selecting at least one preliminary publishing resource from a list of resources as the resource to be published and adding the resource to be published to a resource publishing pool comprises:

Determining the prepared release resource selected from the resource list as a resource to be released;

determining resource information of the resources to be distributed;

Adding the resource to be distributed to the resource distribution pool;

and adding the resource information of the resources to be distributed to the resource distribution pool.

4. The resource publishing method of claim 3, wherein generating a resource publishing packet based on the resource to be published and the resource information thereof comprises:

Determining an upstream resource on which the resource to be distributed depends based on the resource information of the resource to be distributed;

and adding the resource information of the upstream resource to the resource release package.

5. The resource publishing method of claim 4, wherein the publisher server comprises a dependent resource query interface,

The determining, based on the resource information of the resource to be distributed, an upstream resource on which the resource to be distributed depends, further includes:

determining a source server corresponding to the resource to be distributed based on the resource information of the resource to be distributed;

And acquiring the resource information of the upstream resource on which the resource to be distributed depends from the source server through the resource-dependent query interface.

6. A resource publishing method, applied to a target server, where the target server is configured to receive a resource to be published, the method comprising:

determining resources to be distributed in a distribution instance package;

and selecting at least one resource from the resources to be published, and performing publication processing.

7. A computer-readable storage medium, comprising: the computer-readable storage medium having stored therein computer-executable instructions that, when executed by a processor, are for implementing the resource distribution method according to any one of claims 1 to 5; and/or the computer-executable instructions, when executed by a processor, for implementing the resource distribution method of claim 6.

8. A resource issuing apparatus, applied to an issuer server for issuing a resource to be issued, comprising:

the generation module is used for generating a resource release package based on resource information corresponding to the resource to be released;

and the sending module is used for generating a release instance package based on the resource release package and the target server so as to send the release instance package to the target server, and the target server is used for receiving the release instance package.

9. A resource publishing device for use with a target server, the target server configured to receive a resource to be published, the device comprising:

the selection module is used for determining resources to be distributed in the distribution instance package;

And the release module is used for selecting at least one from the resources to be released and carrying out release processing.

10. A computing device, comprising: at least one processor;

and a memory communicatively coupled to the at least one processor;

Wherein the memory stores instructions executable by the at least one processor to cause the computing device to perform the resource distribution method of any of claims 1 to 5; and/or to cause a computing device to perform the resource publication method of claim 6.