Data processing method and device, electronic equipment and computer readable storage medium

Abstract

Embodiments of the present application disclose a data processing method and device, electronic equipment and computer readable storage medium, the method comprises: in response to receiving the installation file construction request party sends installation file construction request, obtain the installation file construction information carried by the installation file construction request; according to the installation file construction information obtains installation file data, based on the installation file data construction obtains installation file, and according to installation file construction process generates installation file construction record;The installation file construction request party returns installation file construction completion message.The technical scheme does not need to rely on manual in the inspection, construction and release process of installation file, so it can greatly save the labor cost, and can also realize the automatic detection of data addition, deletion and change, and then improve the accuracy of data processing, in addition, the technical scheme can be suitable for SDK, EXE, MSI and other types of installation file, so the applicability is strong and can be widely promoted.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and more particularly to a data processing method, device, electronic device, and computer-readable storage medium. Background Art

[0002] With the development of data technology and smart terminals, there is a need to frequently release installation files such as SDKs (Software Development Kits), EXEs, and MSIs (Windows Installers). Existing technologies for releasing installation files rely primarily on manual comparison of dependency changes between new and old versions. This also requires manual organization of the installation file data and manual release of the installation files to external systems. This process obviously requires significant labor costs, is unable to promptly detect data additions, deletions, and changes, and results in low data processing accuracy. Summary of the Invention

[0003] Embodiments of the present invention provide a data processing method, device, electronic device, and computer-readable storage medium.

[0004] In a first aspect, an embodiment of the present invention provides a data processing method.

[0005] Specifically, the data processing method includes:

[0006] In response to receiving an installation file construction request sent by an installation file construction requester, obtaining installation file construction information carried in the installation file construction request, wherein the installation file construction information includes at least one or more of the following information: a target repository address, target branch identification information, and target version information;

[0007] Acquiring installation file data according to the installation file construction information, constructing an installation file based on the installation file data, and generating an installation file construction record according to the installation file construction process, wherein the installation file construction record includes at least one or more of the following information: installation file related information and the installation file construction process;

[0008] Return an installation file construction completion message to the installation file construction requester.

[0009] In conjunction with the first aspect, the embodiment of the present invention, in a first implementation of the first aspect, further includes:

[0010] The installation file is sent to a local tester so that the local tester performs a local test on the installation file and sends an installation file publishing request to a publishing server after the test passes.

[0011] In combination with the first aspect and the first implementation of the first aspect, the embodiment of the present invention, in the second implementation of the first aspect, further includes:

[0012] In response to receiving the installation file construction record acquisition request sent by the publishing server, the installation file construction records of the current version and the previous version are sent to the publishing server according to the installation file construction record acquisition request.

[0013] In combination with the first aspect, the first implementation of the first aspect, and the second implementation of the first aspect, the third implementation of the first aspect of the present disclosure further includes:

[0014] Receive the application file construction command sent by the publishing server, build the application file according to the application file construction command and the updated dependency data, and after the application file is successfully built, send an application file construction success message to the publishing server.

[0015] In a second aspect, an embodiment of the present invention provides a data processing method.

[0016] Specifically, the data processing method includes:

[0017] In response to receiving the installation file release request sent by the installation file release requester, obtaining the installation file build record information of the current version and the previous version from the build server;

[0018] Parsing the installation file build record information to obtain the installation file build record data of the current version and the previous version, and extracting the corresponding dependency data;

[0019] A publishing file is obtained based on the dependency data, and the publishing file is published.

[0020] In conjunction with the second aspect, in a first implementation of the second aspect of an embodiment of the present invention, obtaining a release file based on the dependency data and publishing the release file are implemented as follows:

[0021] Obtaining a current version installation file data identification list and a previous version installation file data identification list according to the dependency data;

[0022] Obtaining a list of installation file data identification differences based on the current version installation file data identification list and the previous version installation file data identification list as a release file;

[0023] The publishing file is sent to a preset execution server for publishing.

[0024] In combination with the second aspect and the first implementation of the second aspect, the embodiment of the present invention further includes, in the second implementation of the second aspect:

[0025] The release file is verified, and after the verification is passed, it is confirmed that the release file is successfully released.

[0026] In combination with the second aspect, the first implementation of the second aspect, and the second implementation of the second aspect, in a third implementation of the second aspect of the present disclosure, the verification of the release file is implemented as follows:

[0027] Confirming that the release file is successfully stored in the preset execution server;

[0028] The dependency data in the release file is updated for stability, and an application file building command is sent to the build server, so that the build server builds the application file according to the updated dependency data.

[0029] In combination with the first implementation manner of the second aspect, the second implementation manner of the second aspect, and the third implementation manner of the second aspect, the fourth implementation manner of the second aspect of the present disclosure further includes:

[0030] In response to receiving the application file construction success message sent by the construction server, a release file publishing report is generated according to the release file construction process information and the release file publishing report is returned to the installation file construction requester.

[0031] In a third aspect, an embodiment of the present invention provides a data processing method.

[0032] Specifically, the data processing method includes:

[0033] The installation file building request direction sends an installation file building request to the building server;

[0034] The build server obtains the installation file build information carried in the installation file build request, obtains the installation file data according to the installation file build information, builds the installation file based on the installation file data, generates an installation file build record according to the installation file build process, and returns an installation file build completion message to the installation file build requester, wherein the installation file build information includes at least one or more of the following information: a target repository address, target branch identification information, and target version information, and the installation file build record includes at least one or more of the following information: installation file related information and the installation file build process;

[0035] The installation file publishing requester sends an installation file publishing request to the publishing server;

[0036] The publishing server obtains the installation file construction record information of the current version and the previous version from the build server, parses the installation file construction record information, obtains the installation file construction record data of the current version and the previous version, extracts the corresponding dependency data, obtains the publishing file based on the dependency data, and publishes the publishing file.

[0037] In conjunction with the third aspect, in a first implementation of the third aspect of an embodiment of the present invention, obtaining a release file based on the dependency data and publishing the release file are implemented as follows:

[0038] Obtaining a current version installation file data identification list and a previous version installation file data identification list according to the dependency data;

[0039] Obtaining a list of installation file data identification differences based on the current version installation file data identification list and the previous version installation file data identification list as a release file;

[0040] The publishing file is sent to a preset execution server for publishing.

[0041] In combination with the third aspect and the first implementation method of the third aspect, in the second implementation method of the third aspect of an embodiment of the present invention, the build server also sends the installation file to the local testing party, so that the local testing party performs local testing on the installation file and sends an installation file release request to the release server after the test passes.

[0042] In combination with the third aspect, the first implementation method of the third aspect and the second implementation method of the third aspect, in the third implementation method of the third aspect of the present disclosure, the build server also responds to receiving the installation file build record acquisition request sent by the publishing server, and sends the installation file build records of the current version and the previous version to the publishing server according to the installation file build record acquisition request.

[0043] In combination with the first implementation method of the third aspect, the second implementation method of the third aspect and the third implementation method of the third aspect, in the fourth implementation method of the third aspect of the present disclosure, the publishing server also verifies the publishing file and, after the verification is passed, confirms that the publishing file is successfully published.

[0044] In combination with the third aspect, the first implementation manner of the third aspect, the second implementation manner of the third aspect, the third implementation manner of the third aspect, and the fourth implementation manner of the third aspect, in a fifth implementation manner of the third aspect of the present disclosure, the verifying the published file is implemented as follows:

[0045] Confirming that the release file is successfully stored in the preset execution server;

[0046] The dependency data in the release file is updated for stability, and an application file building command is sent to the build server, so that the build server builds the application file according to the updated dependency data.

[0047] In combination with the third aspect, the first implementation of the third aspect, the second implementation of the third aspect, the third implementation of the third aspect, the fourth implementation of the third aspect and the fifth implementation of the third aspect, in a sixth implementation of the third aspect of the present disclosure, the build server also receives an application file build command sent by the publishing server, builds the application file according to the application file build command and the updated dependency data, and sends an application file build success message to the publishing server after the application file is successfully built.

[0048] In combination with the third aspect, the first implementation of the third aspect, the second implementation of the third aspect, the third implementation of the third aspect, the fourth implementation of the third aspect, the fifth implementation of the third aspect and the sixth implementation of the third aspect, in the seventh implementation of the third aspect of the present disclosure, the publishing server also generates a publishing file publishing report based on the publishing file building process information in response to receiving the application file building success message sent by the build server and returns the publishing file publishing report to the installation file building requester.

[0049] In a fourth aspect, an embodiment of the present invention provides a data processing device.

[0050] Specifically, the data processing device includes:

[0051] a first acquisition module configured to, in response to receiving an installation file build request sent by an installation file build requester, acquire installation file build information carried in the installation file build request, wherein the installation file build information includes at least one or more of the following information: a target repository address, target branch identification information, and target version information;

[0052] a first construction module configured to obtain installation file data according to the installation file construction information, construct an installation file based on the installation file data, and generate an installation file construction record according to the installation file construction process, wherein the installation file construction record includes at least one or more of the following information: installation file related information and the installation file construction process;

[0053] The returning module is configured to return an installation file construction completion message to the installation file construction requester.

[0054] In conjunction with the fourth aspect, the embodiment of the present invention, in a first implementation of the fourth aspect, further includes:

[0055] The first sending module is configured to send the installation file to a local tester, so that the local tester performs a local test on the installation file, and sends an installation file publishing request to a publishing server after the test passes.

[0056] In combination with the fourth aspect and the first implementation of the fourth aspect, the embodiment of the present invention, in the second implementation of the fourth aspect, further includes:

[0057] The second sending module is configured to, in response to receiving an installation file construction record acquisition request sent by the publishing server, send the installation file construction records of the current version and the previous version to the publishing server according to the installation file construction record acquisition request.

[0058] In combination with the fourth aspect, the first implementation of the fourth aspect, and the second implementation of the fourth aspect, the present disclosure, in a third implementation of the fourth aspect, further includes:

[0059] The second construction module is configured to receive an application file construction command sent by the publishing server, construct an application file according to the application file construction command and the updated dependency data, and send an application file construction success message to the publishing server after the application file is successfully constructed.

[0060] In a fifth aspect, an embodiment of the present invention provides a data processing device.

[0061] Specifically, the data processing device includes:

[0062] A second obtaining module is configured to obtain the installation file build record information of the current version and the previous version from the build server in response to receiving the installation file release request sent by the installation file release requester;

[0063] A parsing module is configured to parse the installation file construction record information to obtain the installation file construction record data of the current version and the previous version, and extract the corresponding dependency data;

[0064] The publishing module is configured to obtain a publishing file based on the dependency data and publish the publishing file.

[0065] In conjunction with the fifth aspect, in a first implementation of the fifth aspect of the embodiment of the present invention, the publishing module is configured as follows:

[0066] Obtaining a current version installation file data identification list and a previous version installation file data identification list according to the dependency data;

[0067] Obtaining a list of installation file data identification differences based on the current version installation file data identification list and the previous version installation file data identification list as a release file;

[0068] The publishing file is sent to a preset execution server for publishing.

[0069] In combination with the fifth aspect and the first implementation of the fifth aspect, the embodiment of the present invention, in the second implementation of the fifth aspect, further includes:

[0070] The verification module is configured to verify the release file and confirm that the release file is successfully released after the verification is passed.

[0071] In combination with the fifth aspect, the first implementation manner of the fifth aspect, and the second implementation manner of the fifth aspect, in a third implementation manner of the fifth aspect of the present disclosure, the part for verifying the published file is configured as follows:

[0072] Confirming that the release file is successfully stored in the preset execution server;

[0073] The dependency data in the release file is updated for stability, and an application file building command is sent to the build server, so that the build server builds the application file according to the updated dependency data.

[0074] In combination with the first implementation manner of the fifth aspect, the second implementation manner of the fifth aspect, and the third implementation manner of the fifth aspect, the present disclosure, in a fourth implementation manner of the fifth aspect, further includes:

[0075] The generation module is configured to generate a release file publishing report according to the release file building process information in response to receiving the application file building success message sent by the build server and return the release file publishing report to the installation file building requester.

[0076] In a sixth aspect, an embodiment of the present invention provides a data processing device.

[0077] Specifically, the data processing device includes:

[0078] An installation file building requester is configured to send an installation file building request to a building server;

[0079] The build server is configured to obtain installation file build information carried in the installation file build request, obtain installation file data based on the installation file build information, build an installation file based on the installation file data, generate an installation file build record according to the installation file build process, and return an installation file build completion message to the installation file build requester, wherein the installation file build information includes at least one or more of the following information: a target repository address, target branch identification information, and target version information, and the installation file build record includes at least one or more of the following information: installation file related information and the installation file build process;

[0080] The installation file publishing requester is configured to send an installation file publishing request to the publishing server;

[0081] The publishing server is configured to obtain the installation file construction record information of the current version and the previous version from the build server, parse the installation file construction record information, obtain the installation file construction record data of the current version and the previous version, extract the corresponding dependency data, obtain the publishing file based on the dependency data, and publish the publishing file.

[0082] In conjunction with the sixth aspect, in a first implementation of the sixth aspect of an embodiment of the present invention, the portion that obtains a release file based on the dependency data and publishes the release file is configured as follows:

[0083] Obtaining a current version installation file data identification list and a previous version installation file data identification list according to the dependency data;

[0084] Obtaining a list of installation file data identification differences based on the current version installation file data identification list and the previous version installation file data identification list as a release file;

[0085] The publishing file is sent to a preset execution server for publishing.

[0086] In combination with the sixth aspect and the first implementation method of the sixth aspect, in the second implementation method of the sixth aspect of an embodiment of the present invention, the build server is also configured to send the installation file to a local testing party so that the local testing party performs local testing on the installation file and sends an installation file release request to the release server after the test passes.

[0087] In combination with the sixth aspect, the first implementation method of the sixth aspect and the second implementation method of the sixth aspect, in the third implementation method of the sixth aspect of the present disclosure, the build server is further configured to respond to receiving the installation file build record acquisition request sent by the publishing server, and send the installation file build records of the current version and the previous version to the publishing server according to the installation file build record acquisition request.

[0088] In combination with the first implementation method of the sixth aspect, the second implementation method of the sixth aspect and the third implementation method of the sixth aspect, in the fourth implementation method of the sixth aspect of the present disclosure, the publishing server is further configured to verify the publishing file and, after the verification is passed, confirm that the publishing file is successfully published.

[0089] In combination with the sixth aspect, the first implementation manner of the sixth aspect, the second implementation manner of the sixth aspect, the third implementation manner of the sixth aspect, and the fourth implementation manner of the sixth aspect, the part for verifying the release file is configured as follows:

[0090] Confirming that the release file is successfully stored in the preset execution server;

[0091] The dependency data in the release file is updated for stability, and an application file building command is sent to the build server, so that the build server builds the application file according to the updated dependency data.

[0092] In combination with the sixth aspect, the first implementation manner of the sixth aspect, the second implementation manner of the sixth aspect, the third implementation manner of the sixth aspect, the fourth implementation manner of the sixth aspect and the fifth implementation manner of the sixth aspect, in the sixth implementation manner of the sixth aspect of the present disclosure, the build server is further configured to receive the application file build command sent by the publishing server, build the application file according to the application file build command and the updated dependency data, and after the application file is successfully built, send an application file build success message to the publishing server.

[0093] In combination with the sixth aspect, the first implementation of the sixth aspect, the second implementation of the sixth aspect, the third implementation of the sixth aspect, the fourth implementation of the sixth aspect, the fifth implementation of the sixth aspect and the sixth implementation of the sixth aspect, in the seventh implementation of the sixth aspect of the present disclosure, the publishing server is further configured to, in response to receiving the application file construction success message sent by the build server, generate a publishing file publishing report based on the publishing file construction process information and return the publishing file publishing report to the installation file construction requester.

[0094] In a seventh aspect, an embodiment of the present invention provides an electronic device comprising a memory and a processor, wherein the memory is configured to store one or more computer instructions that support a data processing device in executing the aforementioned data processing method, and the processor is configured to execute the computer instructions stored in the memory. The data processing device may further include a communication interface for communicating with other devices or a communication network.

[0095] In an eighth aspect, an embodiment of the present invention provides a computer-readable storage medium for storing computer instructions used by a data processing device, which includes computer instructions involved in the data processing device for executing the above-mentioned data processing method.

[0096] The technical solution provided by the embodiment of the present invention may have the following beneficial effects:

[0097] The above technical solution utilizes request information and combines automated installation file construction and publishing processes to achieve automated inspection, construction, and release of installation files. This technical solution eliminates manual labor during the inspection, construction, and release process, significantly reducing labor costs. It also automatically detects data additions, deletions, and changes, improving data processing accuracy. Furthermore, this technical solution is applicable to a variety of installation file types, including SDKs, EXEs, and MSIs, making it highly adaptable and widely applicable.

[0098] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the embodiments of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0099] Other features, purposes and advantages of the embodiments of the present invention will become more apparent through the following detailed description of non-limiting embodiments in conjunction with the accompanying drawings. In the accompanying drawings:

[0100] Figure 1 A flowchart showing a data processing method according to an embodiment of the present invention;

[0101] Figure 2 A flowchart showing a data processing method according to another embodiment of the present invention;

[0102] Figure 3 A flowchart showing a data processing method according to yet another embodiment of the present invention;

[0103] Figure 4 is an overall flow chart of a data processing method according to an embodiment of the present disclosure;

[0104] Figure 5 A structural block diagram of a data processing device according to an embodiment of the present invention is shown;

[0105] Figure 6 A structural block diagram showing a data processing device according to another embodiment of the present invention;

[0106] Figure 7 A structural block diagram of a data processing device according to another embodiment of the present invention is shown;

[0107] Figure 8 It is a structural diagram of a computer system suitable for implementing a data processing method according to an embodiment of the present invention. DETAILED DESCRIPTION

[0108] Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art can easily implement them. In addition, for the sake of clarity, parts not related to the description of the exemplary embodiments are omitted in the accompanying drawings.

[0109] In the embodiments of the present invention, it should be understood that terms such as "including" or "having" are intended to indicate the existence of features, numbers, steps, behaviors, components, parts or their combinations disclosed in this specification, and are not intended to exclude the possibility of one or more other features, numbers, steps, behaviors, components, parts or their combinations existing or being added.

[0110] It should also be noted that, in the absence of conflict, the embodiments and features of the embodiments of the present invention may be combined with each other. The embodiments of the present invention will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0111] The technical solution provided by the embodiments of the present invention utilizes request information and combines automated installation file construction and publishing processes to achieve automatic inspection, construction, and release of installation files. This technical solution eliminates manual labor during the inspection, construction, and release of installation files, significantly saving labor costs. It also enables automatic detection of data additions, deletions, and changes, thereby improving data processing accuracy. Furthermore, this technical solution is applicable to a variety of installation file types, including SDKs, EXEs, and MSIs, making it highly adaptable and widely applicable.

[0112] Figure 1 A flow chart showing a data processing method according to an embodiment of the present invention is shown, which is applicable to building a server, such as Figure 1 As shown, the data processing method includes the following steps S101-S103:

[0113] In step S101, in response to receiving an installation file construction request sent by an installation file construction requester, obtaining installation file construction information carried in the installation file construction request, wherein the installation file construction information includes at least one or more of the following information: target repository address, target branch identification information, and target version information;

[0114] In step S102, installation file data is obtained according to the installation file construction information, an installation file is constructed based on the installation file data, and an installation file construction record is generated according to the installation file construction process, wherein the installation file construction record includes at least one or more of the following information: information related to the installation file and the installation file construction process;

[0115] In step S103, an installation file construction completion message is returned to the installation file construction requester.

[0116] As mentioned above, with the development of data technology and smart terminals, there is a need to frequently release installation files such as SDKs, EXEs, and MSIs. Existing technologies for releasing installation files rely primarily on manual comparison of dependency changes between new and old versions. This also requires manual organization of the installation file data and manual release of the installation files to external systems. This approach clearly incurs significant labor costs, fails to promptly detect data additions, deletions, and changes, and results in low data processing accuracy.

[0117] In light of the above issues, this embodiment proposes a data processing method that utilizes request information and a combination of automated installation file construction and release processes to automatically check, build, and release installation files. This technical solution eliminates manual labor during the installation file inspection, construction, and release process, significantly saving labor costs. It also automatically detects data additions, deletions, and changes, thereby improving data processing accuracy. Furthermore, this technical solution is applicable to a variety of installation file types, including SDKs, EXEs, and MSIs, making it highly adaptable and widely applicable.

[0118] In one embodiment of the present invention, the construction server refers to a server used to construct installation files.

[0119] In one embodiment of the present invention, the installation file construction request refers to a request for causing the construction server to create an installation file corresponding to the installation file construction request. The installation file construction request is issued by the installation file construction requester.

[0120] In one embodiment of the present invention, the installation file construction requester refers to the entity that issues the installation file construction request. The installation file construction requester can be a user, an application, a program, or the data processing system itself, i.e., the data processing system automatically initiates the installation file construction request. Alternatively, the installation file construction requester can be any other entity capable of issuing an installation file construction request, such as a client. The present invention does not impose any specific limitations on the installation file construction requester.

[0121] In one embodiment of the present invention, the installation file construction information is used to represent the installation file construction requirements of the installation file construction requester, so that the construction server can construct the installation file according to the installation file construction information.

[0122] Among them, the installation file construction information may include one or more of the following information: target warehouse address, target branch identification information and target version information, wherein the target warehouse address refers to the address of the target warehouse where the file data related to the installation file to be created is stored, and the target warehouse where the required file data is stored can be determined based on this address. The file data related to the installation file to be created can be, for example, code data related to the installation file to be created, etc.; the target branch identification information refers to information used to distinguish the target branch in the target warehouse where the required file data is stored, such as the name or ID of the target branch in the target warehouse where the required file data is stored, etc.; the target version information refers to the version information of the created installation file.

[0123] According to the target warehouse address, target branch identification information and other information in the installation file construction information, the target warehouse and the corresponding target branch can be determined, and then the installation file data is obtained from the target branch, and then the installation file is constructed based on the installation file data, and an installation file construction record is generated according to the construction process of the installation file to provide data support for subsequent installation file verification, construction process query and other operations, and finally the installation file construction completion message is returned to the installation file construction requester to notify the installation file construction requester that the installation file has been constructed. Among them, the installation file construction record includes at least one or more of the following information: installation file related information, installation file construction process, wherein the installation file related information refers to information related to the installation file and has an impact on the installation file, such as dependency data such as the dependency tree related to the installation file, etc. It should be noted that the dependency data used when constructing the installation file is internal dependency data, which may not be disclosed to the outside world. Therefore, the stability of the internal dependency data will be updated in the subsequent installation file release process and updated to stable external dependency data.

[0124] In one embodiment of the present invention, the method further includes the step of performing local testing on the created installation file, that is, the data processing method includes the following steps:

[0125] In response to receiving an installation file construction request sent by an installation file construction requester, obtaining installation file construction information carried in the installation file construction request, wherein the installation file construction information includes at least one or more of the following information: a target repository address, target branch identification information, and target version information;

[0126] Acquiring installation file data according to the installation file construction information, constructing an installation file based on the installation file data, and generating an installation file construction record according to the installation file construction process, wherein the installation file construction record includes at least one or more of the following information: installation file related information and the installation file construction process;

[0127] Returning an installation file construction completion message to the installation file construction requester;

[0128] The installation file is sent to a local tester so that the local tester performs a local test on the installation file and sends an installation file publishing request to a publishing server after the test passes.

[0129] To determine whether the installation file can be used normally, particularly in the environment in which it will be used, in this embodiment, after the installation file is created, it is sent to a local tester, which then performs local testing on the installation file. After the installation file passes the test, a request for the installation file to be published is sent to the publishing server, notifying the publishing server that the file has been created and tested successfully and is ready for publication. The local tester can be the party requesting the installation file, or the entity that performs the test in the environment in which the installation file will be used, such as a test application, a test program, a test client, etc.

[0130] In one embodiment of the present invention, the method further includes the step of sending the installation file construction record requested by the publishing server to the publishing server, that is, the data processing method includes the following steps:

[0131] In response to receiving an installation file construction request sent by an installation file construction requester, obtaining installation file construction information carried in the installation file construction request, wherein the installation file construction information includes at least one or more of the following information: a target repository address, target branch identification information, and target version information;

[0132] Acquiring installation file data according to the installation file construction information, constructing an installation file based on the installation file data, and generating an installation file construction record according to the installation file construction process, wherein the installation file construction record includes at least one or more of the following information: installation file related information and the installation file construction process;

[0133] Returning an installation file construction completion message to the installation file construction requester;

[0134] Sending the installation file to a local tester so that the local tester performs a local test on the installation file and sends a request to the publishing server to publish the installation file after the test passes;

[0135] In response to receiving the installation file construction record acquisition request sent by the publishing server, the installation file construction records of the current version and the previous version are sent to the publishing server according to the installation file construction record acquisition request.

[0136] In this embodiment, after receiving the installation file build record acquisition request sent by the publishing server, the latest current version and the previous version of the installation file build record stored by it are sent to the publishing server according to the installation file build record acquisition request, so that the publishing server can compare the installation file build records and determine the differences in the build records.

[0137] In one embodiment of the present invention, the method further includes the step of constructing an application file according to the application file construction command of the publishing server, that is, the data processing method includes the following steps:

[0138] In response to receiving an installation file construction request sent by an installation file construction requester, obtaining installation file construction information carried in the installation file construction request, wherein the installation file construction information includes at least one or more of the following information: a target repository address, target branch identification information, and target version information;

[0139] Acquiring installation file data according to the installation file construction information, constructing an installation file based on the installation file data, and generating an installation file construction record according to the installation file construction process, wherein the installation file construction record includes at least one or more of the following information: installation file related information and the installation file construction process;

[0140] Returning an installation file construction completion message to the installation file construction requester;

[0141] Sending the installation file to a local tester so that the local tester performs a local test on the installation file and sends a request to the publishing server to publish the installation file after the test passes;

[0142] In response to receiving the installation file construction record acquisition request sent by the publishing server, sending the installation file construction records of the current version and the previous version to the publishing server according to the installation file construction record acquisition request;

[0143] Receive the application file construction command sent by the publishing server, build the application file according to the application file construction command and the updated dependency data, and after the application file is successfully built, send an application file construction success message to the publishing server.

[0144] Considering that after the publishing server successfully publishes the installation file and updates the dependent data, it is still necessary to build the corresponding application file to ensure the integrity of the installation file publishing process. Therefore, in this embodiment, after the build server receives the application file build command sent by the publishing server, it builds the application file according to the application file build command and the updated dependent data used by the build server. After the application file is successfully built, it sends a message to the publishing server indicating that the application file has been successfully built. The application file can be a mobile application file that can be used on a mobile terminal, etc.

[0145] Figure 2 A flow chart showing a data processing method according to another embodiment of the present invention is shown, which is applicable to a publishing server, such as Figure 2 As shown, the data processing method includes the following steps S201-S203:

[0146] In step S201, in response to receiving the installation file release request sent by the installation file release requester, the installation file build record information of the current version and the previous version is obtained from the build server;

[0147] In step S202, the installation file construction record information is parsed to obtain the installation file construction record data of the current version and the previous version, and the corresponding dependency data is extracted;

[0148] In step S203, a publishing file is obtained based on the dependency data, and the publishing file is published.

[0149] As mentioned above, with the development of data technology and smart terminals, there is a need to frequently release installation files such as SDKs, EXEs, and MSIs. Existing technologies for releasing installation files rely primarily on manual comparison of dependency changes between new and old versions. This also requires manual organization of the installation file data and manual release of the installation files to external systems. This approach clearly incurs significant labor costs, fails to promptly detect data additions, deletions, and changes, and results in low data processing accuracy.

[0150] In light of the above issues, this embodiment proposes a data processing method that utilizes request information and a combination of automated installation file construction and release processes to automatically check, build, and release installation files. This technical solution eliminates manual labor during the installation file inspection, construction, and release process, significantly saving labor costs. It also automatically detects data additions, deletions, and changes, thereby improving data processing accuracy. Furthermore, this technical solution is applicable to a variety of installation file types, including SDKs, EXEs, and MSIs, making it highly adaptable and widely applicable.

[0151] In one embodiment of the present invention, the publishing server refers to a server used to execute a publishing operation on the installation file constructed by the construction server.

[0152] In one embodiment of the present invention, the installation file publishing request refers to a request for causing the publishing server to execute a publishing operation on the corresponding installation file. The installation file publishing request is issued by an installation file publishing requester.

[0153] In one embodiment of the present invention, the installation file release requester refers to the entity that issues the installation file release request, which may be the same as or different from the installation file construction requester. The installation file release requester may be a user, an application, a program, or the data processing system itself, where the data processing system automatically initiates the installation file release request. Alternatively, the installation file release requester may be another entity capable of issuing an installation file release request, such as a client. The present invention does not impose any specific limitations on the installation file release requester.

[0154] As mentioned above, the installation file construction record includes at least one or more of the following information: installation file related information, installation file construction process. In one embodiment of the present invention, the installation file construction record information can be information such as the address for obtaining the installation file construction record. The installation file construction record and the corresponding dependency data can be obtained by parsing the installation file construction record information.

[0155] After receiving the installation file publishing request sent by the installation file publishing requester, the publishing server sends an installation file build record acquisition request to the build server, so that the build server sends the latest current version and the previous version of the installation file build record to the publishing server according to the installation file build record acquisition request; after receiving the installation file build record, the publishing server parses it to obtain the latest current version and the previous version of the installation file build record data, and extracts corresponding dependency data therefrom; finally, the publishing server obtains the publishing file based on the dependency data and publishes the publishing file.

[0156] In one embodiment of the present invention, step S203, i.e., obtaining a release file based on the dependency data and publishing the release file, may be implemented as follows:

[0157] Obtaining a current version installation file data identification list and a previous version installation file data identification list according to the dependency data;

[0158] Obtaining a list of installation file data identification differences based on the current version installation file data identification list and the previous version installation file data identification list as a release file;

[0159] The publishing file is sent to a preset execution server for publishing.

[0160] In this embodiment, when generating and publishing the release file, first, a current version installation file data identification list and a previous version installation file data identification list are obtained based on the dependency data, wherein the data identification refers to information that distinguishes the storage location, acquisition location or other acquisition path of the corresponding data. The data identification can be, for example, GAV (GroupId, ArtifactId, Version) coordinate information that can determine the storage location of the installation file, wherein GroupId is used to define the identification information of the target warehouse to which the current installation file belongs, the identification information of the target organization to which it belongs, or the identification information of the target project to which it belongs; ArtifactId is used to define the target branch, target unit or target module in the target warehouse, target organization or target project to which the current installation file belongs; Version is used to define the current version information of the current installation file; then the current version installation file data identification list and the previous version installation file data identification list are compared to obtain a list of installation file data identification differences that can characterize the differences in the contents of different versions of installation files, and use it as the release file to be released, and finally send the release file to the preset execution server to perform the release operation, wherein the preset execution server can be, for example, a Maven server.

[0161] In one embodiment of the present invention, the method further includes a step of verifying the published file, that is, the data processing method includes the following steps:

[0162] In response to receiving the installation file release request sent by the installation file release requester, obtaining the installation file build record information of the current version and the previous version from the build server;

[0163] Parsing the installation file build record information to obtain the installation file build record data of the current version and the previous version, and extracting the corresponding dependency data;

[0164] Obtaining a release file based on the dependency data, and publishing the release file;

[0165] The release file is verified, and after the verification is passed, it is confirmed that the release file is successfully released.

[0166] In order to confirm the correctness and validity of the release document and save the file release process, in this embodiment, after the release document is released, the release document is also verified. If the verification passes, it is confirmed that the release document is successfully released.

[0167] In one embodiment of the present invention, the step of verifying the release file may be implemented as follows:

[0168] Confirming that the release file is successfully stored in the preset execution server;

[0169] The dependency data in the release file is updated for stability, and an application file building command is sent to the build server, so that the build server builds the application file according to the updated dependency data.

[0170] In this embodiment, when verifying the release file, it is first confirmed whether the release file is successfully stored in the preset execution server, for example, it can be confirmed by a search operation on the release file; if the storage is successful, the dependency data in the release file is updated for stability, and an application file build command is sent to the build server, so that the build server builds the application file according to the updated dependency data.

[0171] Among them, the stability update of the dependency data refers to updating the internal dependency data corresponding to the installation file previously constructed based on the internal snapshot data to stable external dependency data. The stability update of the dependency data can enable the file user to effectively utilize the dependency data and avoid the situation where the dependency data cannot be used due to the non-disclosure of internal data.

[0172] To ensure the integrity of the installation file publishing process, in this embodiment, after the publishing server successfully publishes the installation file and performs stability updates on the dependent data, it also needs to notify the build server to build the corresponding application file based on the installation file. The application file can be a mobile application file that can be used on a mobile terminal.

[0173] In one embodiment of the present invention, the method further comprises the step of generating a release report of the release document, that is, the data processing method comprises the following steps:

[0174] In response to receiving the installation file release request sent by the installation file release requester, obtaining the installation file build record information of the current version and the previous version from the build server;

[0175] Parsing the installation file build record information to obtain the installation file build record data of the current version and the previous version, and extracting the corresponding dependency data;

[0176] Obtaining a release file based on the dependency data, and publishing the release file;

[0177] Verify the release document and, after verification, confirm that the release document has been successfully released;

[0178] In response to receiving the application file construction success message sent by the construction server, a release file publishing report is generated according to the release file construction process information and the release file publishing report is returned to the installation file construction requester.

[0179] In order to facilitate the query and archiving of information, in this embodiment, after receiving the application file construction success message sent by the construction server, the publishing server generates a publishing file release report based on the publishing file construction process information, and returns the publishing file release report to the installation file construction requester, so that it can archive the publishing file release information in the publishing file release report for necessary subsequent queries, wherein the publishing file release report at least includes the publishing file construction process information.

[0180] Figure 2 Some technical features of the embodiments shown and related to the above Figure 1 Some technical features of the embodiments shown in the figure are the same or similar. For the specific explanation and description of the technical features, please refer to the above description of the technical features. Figure 1 The description of the illustrated and related embodiments will not be repeated here.

[0181] Figure 3A flowchart showing a data processing method according to another embodiment of the present invention is applicable to a data processing system including an installation file construction requester, an installation file publishing requester, a construction server, a publishing server, and a preset execution server. Figure 3 As shown, the data processing method includes the following steps S301-S304:

[0182] In step S301, the installation file construction requester sends an installation file construction request to the construction server;

[0183] In step S302, the build server obtains the installation file build information carried in the installation file build request, obtains the installation file data according to the installation file build information, builds the installation file based on the installation file data, generates an installation file build record according to the installation file build process, and returns an installation file build completion message to the installation file build requester, wherein the installation file build information includes at least one or more of the following information: target repository address, target branch identification information, and target version information, and the installation file build record includes at least one or more of the following information: installation file related information and the installation file build process;

[0184] In step S303, the installation file publishing requester sends an installation file publishing request to the publishing server;

[0185] In step S304, the publishing server obtains the installation file construction record information of the current version and the previous version from the build server, parses the installation file construction record information, obtains the installation file construction record data of the current version and the previous version, extracts the corresponding dependency data, obtains the publishing file based on the dependency data, and publishes the publishing file.

[0186] As mentioned above, with the development of data technology and smart terminals, there is a need to frequently release installation files such as SDKs, EXEs, and MSIs. Existing technologies for releasing installation files rely primarily on manual comparison of dependency changes between new and old versions. This also requires manual organization of the installation file data and manual release of the installation files to external systems. This approach clearly incurs significant labor costs, fails to promptly detect data additions, deletions, and changes, and results in low data processing accuracy.

[0187] In light of the above issues, this embodiment proposes a data processing method that utilizes request information and a combination of automated installation file construction and release processes to automatically check, build, and release installation files. This technical solution eliminates manual labor during the installation file inspection, construction, and release process, significantly saving labor costs. It also automatically detects data additions, deletions, and changes, thereby improving data processing accuracy. Furthermore, this technical solution is applicable to a variety of installation file types, including SDKs, EXEs, and MSIs, making it highly adaptable and widely applicable.

[0188] In one embodiment of the present invention, the step of obtaining a release file based on the dependency data and publishing the release file may be implemented as follows:

[0189] Obtaining a current version installation file data identification list and a previous version installation file data identification list according to the dependency data;

[0190] Obtaining a list of installation file data identification differences based on the current version installation file data identification list and the previous version installation file data identification list as a release file;

[0191] The publishing file is sent to a preset execution server for publishing.

[0192] In one embodiment of the present invention, the build server further sends the installation file to a local tester, so that the local tester performs a local test on the installation file and sends an installation file publishing request to the publishing server after the test passes.

[0193] In one embodiment of the present invention, the build server further sends the installation file build records of the current version and the previous version to the publishing server in response to receiving the installation file build record acquisition request sent by the publishing server according to the installation file build record acquisition request.

[0194] In one embodiment of the present invention, the publishing server further verifies the publishing file, and after the verification is passed, confirms that the publishing file is successfully published.

[0195] In one embodiment of the present invention, the step of verifying the release file may be implemented as follows:

[0196] Confirming that the release file is successfully stored in the preset execution server;

[0197] The dependency data in the release file is updated for stability, and an application file building command is sent to the build server, so that the build server builds the application file according to the updated dependency data.

[0198] In one embodiment of the present invention, the build server also receives an application file build command sent by the publishing server, builds an application file according to the application file build command and the updated dependency data, and after the application file is successfully built, sends an application file build success message to the publishing server.

[0199] In one embodiment of the present invention, in response to receiving the application file construction success message sent by the construction server, the publishing server also generates a publishing file publishing report based on the publishing file construction process information and returns the publishing file publishing report to the installation file construction requester.

[0200] Figure 3 Some technical features of the embodiments shown and related to the above Figure 1-Figure 2 Some technical features of the embodiments shown in the figure are the same or similar. For the specific explanation and description of the technical features, please refer to the above description of the technical features. Figure 1-Figure 2 The description of the illustrated and related embodiments will not be repeated here.

[0201] Figure 4 is an overall flow chart of a data processing method according to an embodiment of the present disclosure, as shown in FIG. Figure 4As shown, in the data processing process, the installation file construction request direction sends an installation file construction request to the construction server; the construction server obtains the installation file construction information carried by the installation file construction request, obtains the installation file data according to the installation file construction information, constructs the installation file based on the installation file data, generates an installation file construction record according to the installation file construction process, and returns an installation file construction completion message to the installation file construction request party, and the construction server sends the installation file to the local test party, such as the installation file construction request party, so that the local test party performs local testing on the installation file, wherein the installation file construction information includes at least one or more of the following information: target warehouse address, target branch identification information and target version information, and the installation file construction record includes at least one or more of the following information: installation file related information, installation file construction process; after the test passes, the installation file release request direction sends an installation file release request to the release server; the release server obtains the installation file construction record information of the current version and the previous version from the construction server, parses the installation file construction record information, and obtains the installation file construction record data of the current version and the previous version. According to the data, corresponding dependency data is extracted, and a current version installation file data identifier list and a previous version installation file data identifier list are obtained based on the dependency data. A list of installation file data identifier differences is obtained based on the current version installation file data identifier list and the previous version installation file data identifier list, and the list is used as a release file. The release file is sent to a Maven server for release. Afterwards, the release server further verifies the release file, for example, confirms that the release file is successfully stored in the preset execution server, updates the dependency data in the release file for stability, and sends an application file build command to the build server. After receiving the application file build command sent by the build server, the build server builds the application file according to the application file build command and the updated dependency data, and after the application file is successfully built, sends an application file build success message to the release server. In response to receiving the application file build success message sent by the build server, the release server generates a release file release report based on the release file build process information and returns the release file release report to the installation file build requester. At this time, the verification is considered to have passed, confirming that the release file has been successfully released.

[0202] The following are embodiments of the apparatus of the present invention, which can be used to implement embodiments of the method of the present invention.

[0203] Figure 5The block diagram of the data processing device according to one embodiment of the present invention is shown. The device can be implemented as part or all of an electronic device through software, hardware or a combination of both, and can be implemented as a server. Figure 5 As shown, the data processing device includes:

[0204] A first obtaining module 501 is configured to, in response to receiving an installation file building request sent by an installation file building requester, obtain installation file building information carried in the installation file building request, wherein the installation file building information includes at least one or more of the following information: a target repository address, target branch identification information, and target version information;

[0205] A first construction module 502 is configured to obtain installation file data according to the installation file construction information, construct an installation file based on the installation file data, and generate an installation file construction record according to the installation file construction process, wherein the installation file construction record includes at least one or more of the following information: installation file related information and the installation file construction process;

[0206] The return module 503 is configured to return an installation file construction completion message to the installation file construction requester.

[0207] As mentioned above, with the development of data technology and smart terminals, there is a need to frequently release installation files such as SDKs, EXEs, and MSIs. Existing technologies for releasing installation files rely primarily on manual comparison of dependency changes between new and old versions. This also requires manual organization of the installation file data and manual release of the installation files to external systems. This approach clearly incurs significant labor costs, fails to promptly detect data additions, deletions, and changes, and results in low data processing accuracy.

[0208] In light of the above issues, this embodiment proposes a data processing device that, using request information, automatically checks, builds, and publishes installation files through a combination of automated installation file construction and publishing processes. This technical solution eliminates manual labor during the inspection, construction, and publication of installation files, significantly saving labor costs. It also automatically detects data additions, deletions, and changes, thereby improving data processing accuracy. Furthermore, this technical solution is applicable to a variety of installation file types, including SDKs, EXEs, and MSIs, making it highly adaptable and widely applicable.

[0209] In one embodiment of the present invention, the construction server refers to a server used to construct installation files.

[0210] In one embodiment of the present invention, the installation file construction request refers to a request for causing the construction server to create an installation file corresponding to the installation file construction request. The installation file construction request is issued by the installation file construction requester.

[0211] In one embodiment of the present invention, the installation file construction requester refers to the entity that issues the installation file construction request. The installation file construction requester can be a user, an application, a program, or the data processing system itself, i.e., the data processing system automatically initiates the installation file construction request. Alternatively, the installation file construction requester can be any other entity capable of issuing an installation file construction request, such as a client. The present invention does not impose any specific limitations on the installation file construction requester.

[0212] In one embodiment of the present invention, the installation file construction information is used to represent the installation file construction requirements of the installation file construction requester, so that the construction server can construct the installation file according to the installation file construction information.

[0213] Among them, the installation file construction information may include one or more of the following information: target warehouse address, target branch identification information and target version information, wherein the target warehouse address refers to the address of the target warehouse where the file data related to the installation file to be created is stored, and the target warehouse where the required file data is stored can be determined based on this address. The file data related to the installation file to be created can be, for example, code data related to the installation file to be created, etc.; the target branch identification information refers to information used to distinguish the target branch in the target warehouse where the required file data is stored, such as the name or ID of the target branch in the target warehouse where the required file data is stored, etc.; the target version information refers to the version information of the created installation file.

[0214] According to the target warehouse address, target branch identification information and other information in the installation file construction information, the target warehouse and the corresponding target branch can be determined, and then the installation file data is obtained from the target branch, and then the installation file is constructed based on the installation file data, and an installation file construction record is generated according to the construction process of the installation file to provide data support for subsequent installation file verification, construction process query and other operations, and finally the installation file construction completion message is returned to the installation file construction requester to notify the installation file construction requester that the installation file has been constructed. Among them, the installation file construction record includes at least one or more of the following information: installation file related information, installation file construction process, wherein the installation file related information refers to information related to the installation file and has an impact on the installation file, such as dependency data such as the dependency tree related to the installation file, etc. It should be noted that the dependency data used when constructing the installation file is internal dependency data, which may not be disclosed to the outside world. Therefore, the stability of the internal dependency data will be updated in the subsequent installation file release process and updated to stable external dependency data.

[0215] In one embodiment of the present invention, the device further includes a portion for performing local testing on the created installation file, that is, the data processing device includes:

[0216] a first acquisition module configured to, in response to receiving an installation file build request sent by an installation file build requester, acquire installation file build information carried in the installation file build request, wherein the installation file build information includes at least one or more of the following information: a target repository address, target branch identification information, and target version information;

[0217] a first construction module configured to obtain installation file data according to the installation file construction information, construct an installation file based on the installation file data, and generate an installation file construction record according to the installation file construction process, wherein the installation file construction record includes at least one or more of the following information: installation file related information and the installation file construction process;

[0218] A returning module, configured to return an installation file construction completion message to the installation file construction requester;

[0219] The first sending module is configured to send the installation file to a local tester, so that the local tester performs a local test on the installation file, and sends an installation file publishing request to a publishing server after the test passes.

[0220] To determine whether the installation file can be used normally, particularly in the environment in which it will be used, in this embodiment, after the installation file is created, it is sent to a local tester, which then performs local testing on the installation file. After the installation file passes the test, a request for the installation file to be published is sent to the publishing server, notifying the publishing server that the file has been created and tested successfully and is ready for publication. The local tester can be the party requesting the installation file, or the entity that performs the test in the environment in which the installation file will be used, such as a test application, a test program, a test client, etc.

[0221] In one embodiment of the present invention, the device further includes a portion for sending the installation file construction record requested by the publishing server to the publishing server, that is, the data processing device includes:

[0222] a first acquisition module configured to, in response to receiving an installation file build request sent by an installation file build requester, acquire installation file build information carried in the installation file build request, wherein the installation file build information includes at least one or more of the following information: a target repository address, target branch identification information, and target version information;

[0223] a first construction module configured to obtain installation file data according to the installation file construction information, construct an installation file based on the installation file data, and generate an installation file construction record according to the installation file construction process, wherein the installation file construction record includes at least one or more of the following information: installation file related information and the installation file construction process;

[0224] A returning module, configured to return an installation file construction completion message to the installation file construction requester;

[0225] A first sending module is configured to send the installation file to a local tester, so that the local tester performs a local test on the installation file, and sends an installation file publishing request to a publishing server after the test passes;

[0226] The second sending module is configured to, in response to receiving an installation file construction record acquisition request sent by the publishing server, send the installation file construction records of the current version and the previous version to the publishing server according to the installation file construction record acquisition request.

[0227] In this embodiment, after receiving the installation file build record acquisition request sent by the publishing server, the latest current version and the previous version of the installation file build record stored by it are sent to the publishing server according to the installation file build record acquisition request, so that the publishing server can compare the installation file build records and determine the differences in the build records.

[0228] In one embodiment of the present invention, the device further includes a portion for constructing an application file according to an application file construction command of the publishing server, that is, the data processing device includes the following steps:

[0229] a first acquisition module configured to, in response to receiving an installation file build request sent by an installation file build requester, acquire installation file build information carried in the installation file build request, wherein the installation file build information includes at least one or more of the following information: a target repository address, target branch identification information, and target version information;

[0230] a first construction module configured to obtain installation file data according to the installation file construction information, construct an installation file based on the installation file data, and generate an installation file construction record according to the installation file construction process, wherein the installation file construction record includes at least one or more of the following information: installation file related information and the installation file construction process;

[0231] A returning module, configured to return an installation file construction completion message to the installation file construction requester;

[0232] A first sending module is configured to send the installation file to a local tester, so that the local tester performs a local test on the installation file, and sends an installation file publishing request to a publishing server after the test passes;

[0233] a second sending module configured to, in response to receiving an installation file construction record acquisition request sent by the publishing server, send the installation file construction records of the current version and the previous version to the publishing server according to the installation file construction record acquisition request;

[0234] The second construction module is configured to receive an application file construction command sent by the publishing server, construct an application file according to the application file construction command and the updated dependency data, and send an application file construction success message to the publishing server after the application file is successfully constructed.

[0235] Considering that after the publishing server successfully publishes the installation file and updates the dependent data, it is still necessary to build the corresponding application file to ensure the integrity of the installation file publishing process. Therefore, in this embodiment, after the build server receives the application file build command sent by the publishing server, it builds the application file according to the application file build command and the updated dependent data used by the build server. After the application file is successfully built, it sends a message to the publishing server indicating that the application file has been successfully built. The application file can be a mobile application file that can be used on a mobile terminal, etc.

[0236] Figure 6 FIG2 shows a block diagram of a data processing device according to another embodiment of the present invention. The device can be implemented as part or all of an electronic device through software, hardware, or a combination of both, and can be implemented as a publishing server. Figure 6 As shown, the data processing device includes:

[0237] The second acquisition module 601 is configured to obtain the installation file build record information of the current version and the previous version from the build server in response to receiving the installation file release request sent by the installation file release requester;

[0238] The parsing module 602 is configured to parse the installation file construction record information to obtain the installation file construction record data of the current version and the previous version, and extract the corresponding dependency data;

[0239] The publishing module 603 is configured to obtain a publishing file based on the dependency data and publish the publishing file.

[0240] As mentioned above, with the development of data technology and smart terminals, there is a need to frequently release installation files such as SDKs, EXEs, and MSIs. Existing technologies for releasing installation files rely primarily on manual comparison of dependency changes between new and old versions. This also requires manual organization of the installation file data and manual release of the installation files to external systems. This approach clearly incurs significant labor costs, fails to promptly detect data additions, deletions, and changes, and results in low data processing accuracy.

[0241] In light of the above issues, this embodiment proposes a data processing device that, using request information, automatically checks, builds, and publishes installation files through a combination of automated installation file construction and publishing processes. This technical solution eliminates manual labor during the inspection, construction, and publication of installation files, significantly saving labor costs. It also automatically detects data additions, deletions, and changes, thereby improving data processing accuracy. Furthermore, this technical solution is applicable to a variety of installation file types, including SDKs, EXEs, and MSIs, making it highly adaptable and widely applicable.

[0242] In one embodiment of the present invention, the publishing server refers to a server used to execute a publishing operation on the installation file constructed by the construction server.

[0243] In one embodiment of the present invention, the installation file publishing request refers to a request for causing the publishing server to execute a publishing operation on the corresponding installation file. The installation file publishing request is issued by an installation file publishing requester.

[0244] In one embodiment of the present invention, the installation file release requester refers to the entity that issues the installation file release request, which may be the same as or different from the installation file construction requester. The installation file release requester may be a user, an application, a program, or the data processing system itself, where the data processing system automatically initiates the installation file release request. Alternatively, the installation file release requester may be another entity capable of issuing an installation file release request, such as a client. The present invention does not impose any specific limitations on the installation file release requester.

[0245] As mentioned above, the installation file construction record includes at least one or more of the following information: installation file related information, installation file construction process. In one embodiment of the present invention, the installation file construction record information can be information such as the address for obtaining the installation file construction record. The installation file construction record and the corresponding dependency data can be obtained by parsing the installation file construction record information.

[0246] After receiving the installation file publishing request sent by the installation file publishing requester, the publishing server sends an installation file build record acquisition request to the build server, so that the build server sends the latest current version and the previous version of the installation file build record to the publishing server according to the installation file build record acquisition request; after receiving the installation file build record, the publishing server parses it to obtain the latest current version and the previous version of the installation file build record data, and extracts corresponding dependency data therefrom; finally, the publishing server obtains the publishing file based on the dependency data and publishes the publishing file.

[0247] In one embodiment of the present invention, the publishing module 603 may be configured to:

[0248] Obtaining a current version installation file data identification list and a previous version installation file data identification list according to the dependency data;

[0249] Obtaining a list of installation file data identification differences based on the current version installation file data identification list and the previous version installation file data identification list as a release file;

[0250] The publishing file is sent to a preset execution server for publishing.

[0251] In this embodiment, when generating and publishing the release file, first, a current version installation file data identification list and a previous version installation file data identification list are obtained based on the dependency data, wherein the data identification refers to information that distinguishes the storage location, acquisition location or other acquisition path of the corresponding data. The data identification can be, for example, GAV (GroupId, ArtifactId, Version) coordinate information that can determine the storage location of the installation file, wherein GroupId is used to define the identification information of the target warehouse to which the current installation file belongs, the identification information of the target organization to which it belongs, or the identification information of the target project to which it belongs; ArtifactId is used to define the target branch, target unit or target module in the target warehouse, target organization or target project to which the current installation file belongs; Version is used to define the current version information of the current installation file; then the current version installation file data identification list and the previous version installation file data identification list are compared to obtain a list of installation file data identification differences that can characterize the differences in the contents of different versions of installation files, and use it as the release file to be released, and finally send the release file to the preset execution server to perform the release operation, wherein the preset execution server can be, for example, a Maven server.

[0252] In one embodiment of the present invention, the device further includes a portion for verifying the published document, that is, the data processing device includes:

[0253] A second obtaining module is configured to obtain the installation file build record information of the current version and the previous version from the build server in response to receiving the installation file release request sent by the installation file release requester;

[0254] A parsing module is configured to parse the installation file construction record information to obtain the installation file construction record data of the current version and the previous version, and extract the corresponding dependency data;

[0255] A publishing module is configured to obtain a publishing file based on the dependency data and publish the publishing file;

[0256] The verification module is configured to verify the release file and confirm that the release file is successfully released after the verification is passed.

[0257] In order to confirm the correctness and validity of the release document and save the file release process, in this embodiment, after the release document is released, the release document is also verified. If the verification passes, it is confirmed that the release document is successfully released.

[0258] In one embodiment of the present invention, the part for verifying the published file may be configured as follows:

[0259] Confirming that the release file is successfully stored in the preset execution server;

[0260] The dependency data in the release file is updated for stability, and an application file building command is sent to the build server, so that the build server builds the application file according to the updated dependency data.

[0261] In this embodiment, when verifying the release file, it is first confirmed whether the release file is successfully stored in the preset execution server, for example, it can be confirmed by a search operation on the release file; if the storage is successful, the dependency data in the release file is updated for stability, and an application file build command is sent to the build server, so that the build server builds the application file according to the updated dependency data.

[0262] Among them, the stability update of the dependency data refers to updating the internal dependency data corresponding to the installation file previously constructed based on the internal snapshot data to stable external dependency data. The stability update of the dependency data can enable the file user to effectively utilize the dependency data and avoid the situation where the dependency data cannot be used due to the non-disclosure of internal data.

[0263] To ensure the integrity of the installation file publishing process, in this embodiment, after the publishing server successfully publishes the installation file and performs stability updates on the dependent data, it also needs to notify the build server to build the corresponding application file based on the installation file. The application file can be a mobile application file that can be used on a mobile terminal.

[0264] In one embodiment of the present invention, the device further includes a portion for generating a release report of a release document, that is, the data processing device includes:

[0265] A second obtaining module is configured to obtain the installation file build record information of the current version and the previous version from the build server in response to receiving the installation file release request sent by the installation file release requester;

[0266] A parsing module is configured to parse the installation file construction record information to obtain the installation file construction record data of the current version and the previous version, and extract the corresponding dependency data;

[0267] A publishing module is configured to obtain a publishing file based on the dependency data and publish the publishing file;

[0268] A verification module is configured to verify the release file and confirm that the release file is successfully released after the verification is passed;

[0269] The generation module is configured to generate a release file publishing report according to the release file building process information in response to receiving the application file building success message sent by the build server and return the release file publishing report to the installation file building requester.

[0270] In order to facilitate the query and archiving of information, in this embodiment, after receiving the application file construction success message sent by the construction server, the publishing server generates a publishing file release report based on the publishing file construction process information, and returns the publishing file release report to the installation file construction requester, so that it can archive the publishing file release information in the publishing file release report for necessary subsequent queries, wherein the publishing file release report at least includes the publishing file construction process information.

[0271] Figure 6 Some technical features of the embodiments shown and related to the above Figure 5 Some technical features of the embodiments shown in the figure are the same or similar. For the specific explanation and description of the technical features, please refer to the above description of the technical features. Figure 5 The description of the illustrated and related embodiments will not be repeated here.

[0272] Figure 7 The following is a block diagram showing the structure of a data processing device according to another embodiment of the present invention. The device can be implemented as part or all of an electronic device through software, hardware, or a combination of both. It can be implemented as a data processing system including an installation file construction requester, an installation file publishing requester, a construction server, a publishing server, and a preset execution server. Figure 7 As shown, the data processing device includes:

[0273] The installation file construction requester 701 is configured to send an installation file construction request to the construction server;

[0274] The build server 702 is configured to obtain the installation file build information carried in the installation file build request, obtain the installation file data according to the installation file build information, build the installation file based on the installation file data, generate an installation file build record according to the installation file build process, and return an installation file build completion message to the installation file build requester, wherein the installation file build information includes at least one or more of the following information: a target repository address, a target branch identification information, and a target version information, and the installation file build record includes at least one or more of the following information: information related to the installation file and the installation file build process;

[0275] The installation file publishing requester 703 is configured to send an installation file publishing request to the publishing server;

[0276] The publishing server 704 is configured to obtain the installation file build record information of the current version and the previous version from the build server, parse the installation file build record information, obtain the installation file build record data of the current version and the previous version, extract the corresponding dependency data, obtain the publishing file based on the dependency data, and publish the publishing file.

[0277] As mentioned above, with the development of data technology and smart terminals, there is a need to frequently release installation files such as SDKs, EXEs, and MSIs. Existing technologies for releasing installation files rely primarily on manual comparison of dependency changes between new and old versions. This also requires manual organization of the installation file data and manual release of the installation files to external systems. This approach clearly incurs significant labor costs, fails to promptly detect data additions, deletions, and changes, and results in low data processing accuracy.

[0278] In light of the above issues, this embodiment proposes a data processing device that, using request information, automatically checks, builds, and publishes installation files through a combination of automated installation file construction and publishing processes. This technical solution eliminates manual labor during the inspection, construction, and publication of installation files, significantly saving labor costs. It also automatically detects data additions, deletions, and changes, thereby improving data processing accuracy. Furthermore, this technical solution is applicable to a variety of installation file types, including SDKs, EXEs, and MSIs, making it highly adaptable and widely applicable.

[0279] In one embodiment of the present invention, the part of obtaining the release file based on the dependency data and publishing the release file is configured as follows:

[0280] Obtaining a current version installation file data identification list and a previous version installation file data identification list according to the dependency data;

[0281] Obtaining a list of installation file data identification differences based on the current version installation file data identification list and the previous version installation file data identification list as a release file;

[0282] The publishing file is sent to a preset execution server for publishing.

[0283] In one embodiment of the present invention, the build server is further configured to send the installation file to a local tester, so that the local tester performs a local test on the installation file and sends an installation file publishing request to the publishing server after the test passes.

[0284] In one embodiment of the present invention, the build server is further configured to, in response to receiving an installation file build record acquisition request sent by the publishing server, send the installation file build records of the current version and the previous version to the publishing server according to the installation file build record acquisition request.

[0285] In one embodiment of the present invention, the publishing server is further configured to verify the publishing file and confirm that the publishing file is successfully published after the verification is passed.

[0286] In one embodiment of the present invention, the part for verifying the published file is configured as follows:

[0287] Confirming that the release file is successfully stored in the preset execution server;

[0288] The dependency data in the release file is updated for stability, and an application file building command is sent to the build server, so that the build server builds the application file according to the updated dependency data.

[0289] In one embodiment of the present invention, the build server is further configured to receive an application file build command sent by the publishing server, build an application file according to the application file build command and the updated dependency data, and after the application file is successfully built, send an application file build success message to the publishing server.

[0290] In one embodiment of the present invention, the publishing server is also configured to generate a publishing file release report based on the publishing file construction process information in response to receiving the application file construction success message sent by the construction server and return the publishing file release report to the installation file construction requester.

[0291] Figure 7 Some technical features of the embodiments shown and related to the above Figure 5-Figure 6 Some technical features of the embodiments shown in the figure are the same or similar. For the specific explanation and description of the technical features, please refer to the above description of the technical features. Figure 5-Figure 6 The description of the illustrated and related embodiments will not be repeated here.

[0292] An embodiment of the present invention further discloses an electronic device, which includes a memory and a processor; wherein:

[0293] The memory is used to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor to implement any of the above method steps.

[0294] Figure 8 It is a structural diagram of a computer system suitable for implementing a data processing method according to an embodiment of the present invention.

[0295] like Figure 8As shown, the computer system 800 includes a processing unit 801, which can execute various processes in the above-mentioned embodiments according to a program stored in a read-only memory (ROM) 802 or a program loaded from a storage unit 808 into a random access memory (RAM) 803. Various programs and data required for the operation of the system 800 are also stored in the RAM 803. The processing unit 801, the ROM 802, and the RAM 803 are connected to each other via a bus 804. An input / output (I / O) interface 805 is also connected to the bus 804.

[0296] The following components are connected to the I / O interface 805: an input section 806 including a keyboard, a mouse, etc.; an output section 807 including a cathode ray tube (CRT), a liquid crystal display (LCD), a speaker, etc.; a storage section 808 including a hard disk, etc.; and a communication section 809 including a network interface card such as a LAN card, a modem, etc. The communication section 809 performs communication processing via a network such as the Internet. A drive 810 is also connected to the I / O interface 805 as needed. A removable medium 811, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 810 as needed so that a computer program read therefrom can be installed into the storage section 808 as needed. Among them, the processing unit 801 can be implemented as a processing unit such as a CPU, a GPU, an FPGA, or an NPU.

[0297] In particular, according to embodiments of the present invention, the methods described above may be implemented as computer software programs. For example, embodiments of the present invention include a computer program product comprising a computer program tangibly embodied on a computer-readable medium, the computer program comprising program code for executing the data processing method. In such embodiments, the computer program may be downloaded and installed from a network via the communication portion 809 and / or installed from a removable medium 811.

[0298] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of the systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each box in the diagram or block diagram can represent a module, program segment, or portion of code, which contains one or more executable instructions for implementing the specified logical functions. It should also be noted that in some alternative implementations, the functions marked in the boxes can also occur in an order different from that marked in the accompanying drawings. For example, two boxes shown in succession can actually be executed substantially in parallel, or they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flow chart, as well as the combination of boxes in the block diagram and / or flow chart, can be implemented using a dedicated hardware-based system that performs the specified functions or operations, or can be implemented using a combination of dedicated hardware and computer instructions.

[0299] The units or modules involved in the embodiments described in the present invention may be implemented by software or hardware. The units or modules described may also be provided in a processor, and the names of these units or modules do not, in certain circumstances, constitute limitations on the units or modules themselves.

[0300] As another aspect, embodiments of the present invention further provide a computer-readable storage medium. This computer-readable storage medium may be included in the apparatus described in the above embodiments, or may be a standalone computer-readable storage medium not incorporated into the apparatus. The computer-readable storage medium stores one or more programs, which are used by one or more processors to execute the methods described in the embodiments of the present invention.

[0301] The above description is merely an illustration of the preferred embodiments of the present invention and the technical principles employed. Those skilled in the art should understand that the scope of the invention involved in the embodiments of the present invention is not limited to the technical solutions formed by the specific combination of the above-mentioned technical features, but also encompasses other technical solutions formed by any combination of the above-mentioned technical features or their equivalents without departing from the inventive concept. For example, a technical solution formed by replacing the above-mentioned features with (but not limited to) technical features with similar functions disclosed in the embodiments of the present invention.

Claims

1. A data processing method, suitable for building a server, characterized in that: include: In response to receiving an installation file construction request sent by an installation file construction requester, obtaining installation file construction information carried in the installation file construction request, wherein the installation file construction information includes at least one or more of the following information: a target repository address, target branch identification information, and target version information; Acquiring installation file data according to the installation file construction information, constructing an installation file based on the installation file data, and generating an installation file construction record according to the installation file construction process, wherein the installation file construction record includes at least one or more of the following information: installation file related information and the installation file construction process; Returning an installation file construction completion message to the installation file construction requester; In response to receiving an installation file build record acquisition request sent by a publishing server, sending the installation file build records of the current version and the previous version to the publishing server according to the installation file build record acquisition request, so that the publishing server parses the installation file build record information to obtain the installation file build record data of the current version and the previous version, extracts corresponding dependency data, obtains a publishing file based on the dependency data, and publishes the publishing file; A release file is obtained based on the dependency data, and the release file is released, including: obtaining a current version installation file data identification list and a previous version installation file data identification list according to the dependency data; the data identification is GAV coordinate information for determining the storage location of the installation file; wherein the GAV coordinate information includes GroupId, ArtifactId and Version; the GroupId is used to define the identification information of the target warehouse to which the current installation file belongs, the identification information of the target organization to which it belongs, or the identification information of the target project to which it belongs; the ArtifactId is used to define the target branch, target unit or target module in the target warehouse, target organization or target project to which the current installation file belongs; the Version is used to define the current version information of the current installation file; Obtaining, based on the current version installation file data identification list and the previous version installation file data identification list, an installation file data identification difference list representing content differences of the installation files of different versions as a release file; The publishing file is sent to a preset execution server for publishing.

2. The method according to claim 1, characterized in that Also includes: The installation file is sent to a local tester so that the local tester performs a local test on the installation file and sends an installation file publishing request to a publishing server after the test passes.

3. The method according to claim 1, characterized in that Also includes: Receive the application file construction command sent by the publishing server, build the application file according to the application file construction command and the updated dependency data, and after the application file is successfully built, send an application file construction success message to the publishing server.

4. A data processing method, applicable to a publishing server, characterized in that: include: The build server, in response to receiving an installation file build request sent by an installation file build requester, obtains installation file build information carried in the installation file build request, the installation file build information including at least one or more of the following information: a target repository address, target branch identification information, and target version information; obtains installation file data according to the installation file build information, constructs an installation file based on the installation file data, and generates an installation file build record according to the installation file build process, the installation file build record including at least one or more of the following information: installation file related information and the installation file build process; In response to receiving the installation file release request sent by the installation file release requester, obtaining the installation file build record information of the current version and the previous version from the build server; Parsing the installation file build record information to obtain the installation file build record data of the current version and the previous version, and extracting the corresponding dependency data; Obtaining a release file based on the dependency data, and publishing the release file; The obtaining of the release file based on the dependency data and publishing the release file is implemented as follows: A list of data identifiers of the current version of the installation file and a list of data identifiers of the previous version of the installation file are obtained based on the dependency data; the data identifier is the GAV coordinate information for determining the storage location of the installation file; wherein the GAV coordinate information includes GroupId, ArtifactId and Version; the GroupId is used to define the identification information of the target warehouse to which the current installation file belongs, the identification information of the target organization to which it belongs, or the identification information of the target project to which it belongs; the ArtifactId is used to define the target branch, target unit or target module in the target warehouse, target organization or target project to which the current installation file belongs; the Version is used to define the current version information of the current installation file; Obtaining, based on the current version installation file data identification list and the previous version installation file data identification list, an installation file data identification difference list representing content differences of the installation files of different versions as a release file; The publishing file is sent to a preset execution server for publishing.

5. The method according to claim 4, characterized in that Also includes: The release file is verified, and after the verification is passed, it is confirmed that the release file is successfully released.

6. The method according to claim 5, characterized in that The verification of the release file is implemented as follows: Confirming that the release file is successfully stored in the preset execution server; The dependency data in the release file is updated for stability, and an application file building command is sent to the build server, so that the build server builds the application file according to the updated dependency data.

7. The method according to claim 6, characterized in that Also includes: In response to receiving the application file construction success message sent by the construction server, a release file publishing report is generated according to the release file construction process information and the release file publishing report is returned to the installation file construction requester.

8. A data processing method, applicable to a data processing system including an installation file construction requester, an installation file publishing requester, a construction server, a publishing server, and a preset execution server, characterized in that: include: The installation file building request direction sends an installation file building request to the building server; The build server obtains the installation file build information carried in the installation file build request, obtains the installation file data according to the installation file build information, builds the installation file based on the installation file data, generates an installation file build record according to the installation file build process, and returns an installation file build completion message to the installation file build requester, wherein the installation file build information includes at least one or more of the following information: a target repository address, target branch identification information, and target version information, and the installation file build record includes at least one or more of the following information: installation file related information and the installation file build process; The installation file publishing requester sends an installation file publishing request to the publishing server; The publishing server obtains the installation file construction record information of the current version and the previous version from the build server, parses the installation file construction record information to obtain the installation file construction record data of the current version and the previous version, extracts the corresponding dependency data, obtains the publishing file based on the dependency data, and publishes the publishing file; The obtaining of the release file based on the dependency data and publishing the release file is implemented as follows: A list of data identifiers of the current version of the installation file and a list of data identifiers of the previous version of the installation file are obtained based on the dependency data; the data identifier is the GAV coordinate information for determining the storage location of the installation file; wherein the GAV coordinate information includes GroupId, ArtifactId and Version; the GroupId is used to define the identification information of the target warehouse to which the current installation file belongs, the identification information of the target organization to which it belongs, or the identification information of the target project to which it belongs; the ArtifactId is used to define the target branch, target unit or target module in the target warehouse, target organization or target project to which the current installation file belongs; the Version is used to define the current version information of the current installation file; Obtaining, based on the current version installation file data identification list and the previous version installation file data identification list, an installation file data identification difference list representing content differences of the installation files of different versions as a release file; The publishing file is sent to a preset execution server for publishing.

9. The method according to claim 8, characterized in that The build server also sends the installation file to a local tester, so that the local tester performs a local test on the installation file, and sends an installation file publishing request to the publishing server after the test passes.

10. The method according to claim 8, characterized in that In response to receiving the installation file construction record acquisition request sent by the publishing server, the construction server sends the installation file construction records of the current version and the previous version to the publishing server according to the installation file construction record acquisition request.

11. The method according to claim 8, characterized in that The publishing server also verifies the publishing file and confirms that the publishing file is successfully published after the verification is passed.

12. The method according to claim 11, characterized in that The verification of the release file is implemented as follows: Confirming that the release file is successfully stored in the preset execution server; The dependency data in the release file is updated for stability, and an application file building command is sent to the build server, so that the build server builds the application file according to the updated dependency data.

13. The method according to claim 12, characterized in that The build server also receives the application file build command sent by the publishing server, builds the application file according to the application file build command and the updated dependency data, and sends an application file build success message to the publishing server after the application file is successfully built.

14. The method according to any one of claims 8, 12 and 13, characterized in that: In response to receiving the application file construction success message sent by the construction server, the publishing server also generates a publishing file publishing report according to the publishing file construction process information and returns the publishing file publishing report to the installation file construction requester.

15. A data processing device, suitable for building a server, characterized in that: include: a first acquisition module configured to, in response to receiving an installation file build request sent by an installation file build requester, acquire installation file build information carried in the installation file build request, wherein the installation file build information includes at least one or more of the following information: a target repository address, target branch identification information, and target version information; a first construction module configured to obtain installation file data according to the installation file construction information, construct an installation file based on the installation file data, and generate an installation file construction record according to the installation file construction process, wherein the installation file construction record includes at least one or more of the following information: installation file related information and the installation file construction process; A returning module, configured to return an installation file construction completion message to the installation file construction requester; In response to receiving an installation file build record acquisition request sent by a publishing server, sending the installation file build records of the current version and the previous version to the publishing server according to the installation file build record acquisition request, so that the publishing server parses the installation file build record information to obtain the installation file build record data of the current version and the previous version, extracts corresponding dependency data, obtains a publishing file based on the dependency data, and publishes the publishing file; A release file is obtained based on the dependency data, and the release file is released, including: obtaining a current version installation file data identification list and a previous version installation file data identification list according to the dependency data; the data identification is GAV coordinate information for determining the storage location of the installation file; wherein the GAV coordinate information includes GroupId, ArtifactId and Version; the GroupId is used to define the identification information of the target warehouse to which the current installation file belongs, the identification information of the target organization to which it belongs, or the identification information of the target project to which it belongs; the ArtifactId is used to define the target branch, target unit or target module in the target warehouse, target organization or target project to which the current installation file belongs; the Version is used to define the current version information of the current installation file; Obtaining, based on the current version installation file data identification list and the previous version installation file data identification list, an installation file data identification difference list representing content differences of the installation files of different versions as a release file; The publishing file is sent to a preset execution server for publishing.

16. The device according to claim 15, characterized in that Also includes: The first sending module is configured to send the installation file to a local tester, so that the local tester performs a local test on the installation file, and sends an installation file publishing request to a publishing server after the test passes.

17. The device according to claim 16, characterized in that Also includes: The second sending module is configured to, in response to receiving an installation file construction record acquisition request sent by the publishing server, send the installation file construction records of the current version and the previous version to the publishing server according to the installation file construction record acquisition request.

18. The device according to claim 17, characterized in that Also includes: The second construction module is configured to receive an application file construction command sent by the publishing server, construct an application file according to the application file construction command and the updated dependency data, and send an application file construction success message to the publishing server after the application file is successfully constructed.

19. A data processing device, suitable for use with a publishing server, characterized in that: include: The build server, in response to receiving an installation file build request sent by an installation file build requester, obtains installation file build information carried in the installation file build request, the installation file build information including at least one or more of the following information: a target repository address, target branch identification information, and target version information; obtains installation file data according to the installation file build information, constructs an installation file based on the installation file data, and generates an installation file build record according to the installation file build process, the installation file build record including at least one or more of the following information: installation file related information and the installation file build process; A second obtaining module is configured to obtain the installation file build record information of the current version and the previous version from the build server in response to receiving the installation file release request sent by the installation file release requester; A parsing module is configured to parse the installation file construction record information to obtain the installation file construction record data of the current version and the previous version, and extract the corresponding dependency data; A publishing module is configured to obtain a publishing file based on the dependency data and publish the publishing file; The publishing module is configured to: A list of data identifiers of the current version of the installation file and a list of data identifiers of the previous version of the installation file are obtained based on the dependency data; the data identifier is the GAV coordinate information for determining the storage location of the installation file; wherein the GAV coordinate information includes GroupId, ArtifactId and Version; the GroupId is used to define the identification information of the target warehouse to which the current installation file belongs, the identification information of the target organization to which it belongs, or the identification information of the target project to which it belongs; the ArtifactId is used to define the target branch, target unit or target module in the target warehouse, target organization or target project to which the current installation file belongs; the Version is used to define the current version information of the current installation file; Obtaining, based on the current version installation file data identification list and the previous version installation file data identification list, an installation file data identification difference list representing content differences of the installation files of different versions as a release file; The publishing file is sent to a preset execution server for publishing.

20. The device according to claim 19, characterized in that Also includes: The verification module is configured to verify the release file and confirm that the release file is successfully released after the verification is passed.

21. The device according to claim 20, characterized in that The part for verifying the published file is configured to: Confirming that the release file is successfully stored in the preset execution server; The dependency data in the release file is updated for stability, and an application file building command is sent to the build server, so that the build server builds the application file according to the updated dependency data.

22. The device according to claim 21, characterized in that Also includes: The generation module is configured to generate a release file publishing report according to the release file building process information in response to receiving the application file building success message sent by the build server and return the release file publishing report to the installation file building requester.

23. A data processing device, applicable to a data processing system comprising an installation file construction requester, an installation file publishing requester, a construction server, a publishing server, and a preset execution server, characterized in that: include: An installation file building requester is configured to send an installation file building request to a building server; The build server is configured to obtain installation file build information carried in the installation file build request, obtain installation file data based on the installation file build information, build an installation file based on the installation file data, generate an installation file build record according to the installation file build process, and return an installation file build completion message to the installation file build requester, wherein the installation file build information includes at least one or more of the following information: a target repository address, target branch identification information, and target version information, and the installation file build record includes at least one or more of the following information: installation file related information and the installation file build process; The installation file publishing requester is configured to send an installation file publishing request to the publishing server; The publishing server is configured to obtain installation file build record information of the current version and the previous version from the build server, parse the installation file build record information to obtain installation file build record data of the current version and the previous version, extract corresponding dependency data, obtain a publishing file based on the dependency data, and publish the publishing file; The part of obtaining the release file based on the dependency data and publishing the release file is configured as follows: A list of data identifiers of the current version of the installation file and a list of data identifiers of the previous version of the installation file are obtained based on the dependency data; the data identifier is the GAV coordinate information for determining the storage location of the installation file; wherein the GAV coordinate information includes GroupId, ArtifactId and Version; the GroupId is used to define the identification information of the target warehouse to which the current installation file belongs, the identification information of the target organization to which it belongs, or the identification information of the target project to which it belongs; the ArtifactId is used to define the target branch, target unit or target module in the target warehouse, target organization or target project to which the current installation file belongs; the Version is used to define the current version information of the current installation file; Obtaining, based on the current version installation file data identification list and the previous version installation file data identification list, an installation file data identification difference list representing content differences of the installation files of different versions as a release file; The publishing file is sent to a preset execution server for publishing.

24. The device according to claim 23, characterized in that The build server is further configured to send the installation file to a local tester, so that the local tester performs a local test on the installation file, and sends an installation file publishing request to the publishing server after the test passes.

25. The device according to claim 23, characterized in that The build server is further configured to, in response to receiving an installation file build record acquisition request sent by the publishing server, send the installation file build records of the current version and the previous version to the publishing server according to the installation file build record acquisition request.

26. The device according to claim 23, characterized in that The publishing server is further configured to verify the publishing file and, after the verification is successful, confirm that the publishing file is successfully published.

27. The device according to claim 26, characterized in that The part for verifying the published file is configured to: Confirming that the release file is successfully stored in the preset execution server; The dependency data in the release file is updated for stability, and an application file building command is sent to the build server, so that the build server builds the application file according to the updated dependency data.

28. The device according to claim 27, characterized in that The build server is further configured to receive an application file build command sent by the publishing server, build an application file according to the application file build command and the updated dependency data, and send an application file build success message to the publishing server after the application file is successfully built.

29. The device according to any one of claims 23, 27 and 28, characterized in that: The publishing server is further configured to generate a publishing file publishing report according to the publishing file building process information in response to receiving the application file building success message sent by the building server and return the publishing file publishing report to the installation file building requester.

30. An electronic device, characterized in that: comprising a memory and a processor; wherein, The memory is configured to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor to implement the method steps according to any one of claims 1 to 14.

31. A computer-readable storage medium having computer instructions stored thereon, characterized in that: When the computer instructions are executed by a processor, the method steps described in any one of claims 1 to 14 are implemented.

Images