Data processing method and related equipment

By integrating data between the construction system and the change system, obtaining and statistically building information, the problem that terminal version release cannot be correlated is solved, and the code review statistics and quality observations are realized, the release risks are reduced, and data transparency and governance capabilities are improved. .

CN118939281APending Publication Date: 2024-11-12TENCENT TECHNOLOGY (SHENZHEN) CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202310527071.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-10
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

In the prior art, the changes and release of terminals cannot be associated with version construction, resulting in file changes being unable to count code review information, and there are problems such as release risks and unobservable quality.

Method used

By integrating data between the construction system and the change system, the construction information is obtained, the construction target table, the change file table and the change order table are generated, and the data is sent to the software service system for data statistics, so as to obtain the code review statistical information and report generation.

Benefits of technology

It reduces the risk of terminal version release, realizes observability of quality, opens up data correlation between changing systems, building systems and software service systems, and improves R&D data transparency and governance capabilities.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118939281A_ABST
    Figure CN118939281A_ABST
Patent Text Reader

Abstract

The invention discloses a data processing method and related equipment. The related equipment comprises a construction system, a change system and a software service system. Wherein the construction system can obtain the construction information corresponding to the current object construction; based on the construction information, performing object construction on the object, and generating a temporary construction target table; writing a construction identifier corresponding to the current object construction into an upgrading file generated by the current object construction; generating a temporary change file table based on the historical version information of the object; and sending the temporary construction target table, the upgrade file and the temporary change file table to a change system, and indicating the change system to generate a construction target table, a change file table and a change single table, so that a software service system performs data statistics based on the construction target table, the change file table and the change single table to obtain code review statistical information. According to the invention, the terminal version release risk can be reduced, and the quality observability is realized.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a data processing method and related equipment. Background Art

[0002] Currently, the build system, change system, and SOA system used in terminal construction are all independent systems and have no connection with each other. The problem brought about by such a technical solution is that the change release of the terminal cannot be associated with the version build of the terminal. Therefore, the file changes related to the terminal version build cannot count the code review information. Summary of the invention

[0003] The embodiments of the present application provide a data processing method and related equipment, which may include a data processing device, an electronic device, a computer-readable storage medium and a computer program product, which can reduce the risk of terminal version release and achieve quality observability.

[0004] The present application embodiment provides a data processing method, which is applied to build a system, including:

[0005] Get the construction information corresponding to this object construction;

[0006] Based on the construction information, construct the object and generate a temporary construction target table;

[0007] Write the build identifier corresponding to this object build into the upgrade file generated by this object build;

[0008] Generate a temporary change file table based on the historical version information of the object;

[0009] The temporary build target table, the upgrade file, and the temporary change file table are sent to the change system, instructing the change system to generate a build target table, a change file table, and a change order table, so that the software service system can perform data statistics based on the build target table, the change file table, and the change order table to obtain code review statistical information.

[0010] Accordingly, an embodiment of the present application provides a data processing device, which is applied to construct a system, including:

[0011] A first acquisition unit is used to acquire construction information corresponding to the current object construction;

[0012] A construction unit, configured to construct the object based on the construction information and generate a temporary construction target table;

[0013] A writing unit, used for writing the building identifier corresponding to the current object building into the upgrade file generated by the current object building;

[0014] A first generating unit, configured to generate a temporary change file table based on the historical version information of the object;

[0015] A sending unit is used to send the temporary build target table, the upgrade file, and the temporary change file table to the change system, instructing the change system to generate a build target table, a change file table, and a change order table, so that the software service system can perform data statistics based on the build target table, the change file table, and the change order table to obtain code review statistical information.

[0016] Optionally, in some embodiments of the present application, the first acquisition unit may also be used to receive an object construction request from a business manager, where the object construction request includes a construction configuration file; and trigger a compilation construction task based on the construction configuration file.

[0017] Optionally, in some embodiments of the present application, the writing unit can be specifically used to generate a build identifier corresponding to the current object construction based on the current object construction; generate a build product corresponding to the current object construction based on the current object construction, the build product including an upgrade file; and write the build identifier into the upgrade file.

[0018] Optionally, in some embodiments of the present application, the first generation unit can be specifically used to obtain a code change merge request list corresponding to the historical version of the object; parse the code change merge request list to obtain a change file list corresponding to each code change merge request; and generate a temporary change file table based on the change file list.

[0019] The present application embodiment provides a data processing method, which is applied to a change system, including:

[0020] Receiving a temporary build target table and a temporary change file table from a build system, wherein the temporary build target table is generated by the build system based on build information during object construction, and the temporary change file table is generated by the build system based on historical version information of the object;

[0021] Associating the upgrade files generated by the build system;

[0022] Generate a build target table, a change file table, and a change order table based on the temporary build target table, the temporary change file table, and the upgrade file;

[0023] The build target table, the change file table, and the change order table are uploaded to a software service system, and the software service system is instructed to perform data statistics to obtain code review statistical information.

[0024] Accordingly, an embodiment of the present application provides a data processing device, which is applied to a change system, including:

[0025] a receiving unit, configured to receive a temporary build target table and a temporary change file table from a build system, wherein the temporary build target table is generated by the build system based on build information during object construction, and the temporary change file table is generated by the build system based on historical version information of the object;

[0026] An associating unit, used for associating an upgrade file generated by the building system;

[0027] A second generating unit, configured to generate a build target table, a change file table, and a change order table based on the temporary build target table, the temporary change file table, and the upgrade file;

[0028] The uploading unit is used to upload the build target table, the change file table, and the change order table to the software service system, and instruct the software service system to perform data statistics to obtain code review statistical information.

[0029] Optionally, in some embodiments of the present application, the second generation unit can be specifically used to generate a build target table based on the upgrade file, the temporary build target table, and the change identifier corresponding to this object change; generate a change file table based on the upgrade file, the temporary change file table, the build identifier corresponding to this object build, and the change identifier corresponding to this object change; generate a change order table based on the upgrade file and the build identifier corresponding to this object build.

[0030] The present application embodiment provides a data processing method, which is applied to a software service system, including:

[0031] Determine data statistics rules based on business needs;

[0032] Periodically acquiring a build target table, a change file table, and a change order table from a change system, wherein the build target table, the change file table, and the change order table are generated by the change system based on a temporary build target table, a temporary change file table, and an upgrade file from the build system, wherein the temporary build target table, the temporary change file table, and the upgrade file are generated by the build system during the object build process;

[0033] Based on the data statistics rule, data statistics are performed on the build target table, the change file table, and the change order table to obtain code review statistical information.

[0034] Accordingly, an embodiment of the present application provides a data processing device, applied to a software service system, including:

[0035] A determination unit is used to determine data statistics rules based on business requirements;

[0036] a second acquisition unit, for periodically acquiring a build target table, a change file table, and a change order table from a change system, wherein the build target table, the change file table, and the change order table are generated by the change system based on a temporary build target table, a temporary change file table, and an upgrade file from the build system, wherein the temporary build target table, the temporary change file table, and the upgrade file are generated by the build system during the object construction process;

[0037] A statistical unit is used to perform data statistics on the build target table, the change file table, and the change order table based on the data statistical rules to obtain code review statistical information.

[0038] Optionally, in some embodiments of the present application, the statistical unit may also be used to display the code review statistical information.

[0039] An electronic device provided in an embodiment of the present application includes a processor and a memory, wherein the memory stores a plurality of instructions, and the processor loads the instructions to execute the steps in the data processing method provided in the embodiment of the present application.

[0040] An embodiment of the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps in the data processing method provided in the embodiment of the present application.

[0041] In addition, an embodiment of the present application also provides a computer program product, including a computer program or instructions, which, when executed by a processor, implements the steps in the data processing method provided in the embodiment of the present application.

[0042] The embodiment of the present application provides a data processing method and related equipment, including a construction system, a change system, and a software service system. Among them, the construction system can obtain the construction information corresponding to the current object construction; based on the construction information, the object is constructed and a temporary construction target table is generated; the construction identifier corresponding to the current object construction is written into the upgrade file generated by the current object construction; based on the historical version information of the object, a temporary change file table is generated; the temporary construction target table, the upgrade file, and the temporary change file table are sent to the change system, instructing the change system to generate a construction target table, a change file table, and a change order table, so that the software service system performs data statistics based on the construction target table, the change file table, and the change order table to obtain code review statistical information. The change system can receive a temporary build target table and a temporary change file table from the build system, wherein the temporary build target table is generated by the build system based on build information during object construction, and the temporary change file table is generated by the build system according to historical version information of the object; associate the upgrade file generated by the build system; generate a build target table, a change file table, and a change order table based on the temporary build target table, the temporary change file table, and the upgrade file; upload the build target table, the change file table, and the change order table to the software service system, and instruct the software service system to perform data statistics to obtain code review statistical information. The software service system can determine data statistics rules based on business needs; periodically obtain the build target table, change file table, and change order table from the change system, the build target table, change file table, and change order table are generated by the change system based on the temporary build target table, temporary change file table, and upgrade file from the build system, the temporary build target table, the temporary change file table, and the upgrade file are generated by the build system during the object construction process; based on the data statistics rules, the build target table, the change file table, and the change order table are statistically analyzed to obtain code review statistics. This application can solve the problem of whether each change in terminal SOA governance has been reviewed by the team code, connect the change system, the build system, and the software service system to complete report statistics, reduce the risk of terminal version release, and achieve quality observability. Different from the background change release in the prior art, the terminal build system and the change release are mostly not implemented on the same system, and it is difficult to count the change release review rate. This application designs a set of mechanisms to ultimately achieve data statistics and governance through data integration. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0044] Figure 1 It is a scenario schematic diagram of the data processing method provided in the embodiment of the present application;

[0045] Figure 2 is a first flow chart of the data processing method provided in an embodiment of the present application;

[0046] Figure 3 is a second flow chart of the data processing method provided in an embodiment of the present application;

[0047] Figure 4 is a third flow chart of the data processing method provided in the embodiment of the present application;

[0048] Figure 5 is a fourth flow chart of the data processing method provided in an embodiment of the present application;

[0049] Figure 6 It is a schematic diagram of a product side provided by an embodiment of the present application;

[0050] Figure 7 is a fifth flow chart of the data processing method provided in the embodiment of the present application;

[0051] Figure 8 It is a schematic diagram of triggering the construction of the data processing method provided in the embodiment of the present application;

[0052] Fig. 9 It is a schematic diagram of the execution link of the data processing method provided in the embodiment of the present application;

[0053] Fig.10 is a sixth flow chart of the data processing method provided in an embodiment of the present application;

[0054] Fig.11 is a first structural schematic diagram of a data processing device provided in an embodiment of the present application;

[0055] Fig.12 is a second structural schematic diagram of a data processing device provided in an embodiment of the present application;

[0056] Fig.13 is a third structural schematic diagram of the data processing device provided in an embodiment of the present application;

[0057] Fig.14 It is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0058] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of this application.

[0059] The embodiment of the present application provides a data processing method and related equipment, and the related equipment may include a data processing device, an electronic device, a computer-readable storage medium and a computer program product. The data processing device may be integrated in an electronic device, and the electronic device may be a terminal or a server.

[0060] It is understandable that the data processing method of this embodiment can be executed on the terminal, can be executed on the server, or can be executed by the terminal and the server together. The above examples should not be understood as limiting the present application. Among them, the terminal may include a mobile phone, an intelligent voice interaction device, an intelligent home appliance, a vehicle-mounted terminal, an aircraft, a tablet computer, a laptop, or a personal computer (PC, Personal Computer), etc. A client may also be set on the terminal, and the client may be an application client or a browser client, etc. Among them, the server may be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. The data processing method or device disclosed in this application, wherein multiple servers can be composed of a blockchain, and the server is a node on the blockchain.

[0061] like Figure 1 As shown, the data processing system provided by the embodiment of the present application includes a construction system, a change system, and a software service system. Among them, the construction system can obtain the construction information corresponding to the current object construction; based on the construction information, the object is constructed and a temporary construction target table is generated; the construction identifier corresponding to the current object construction is written into the upgrade file generated by the current object construction; based on the historical version information of the object, a temporary change file table is generated; the temporary construction target table, the upgrade file, and the temporary change file table are sent to the change system, instructing the change system to generate a construction target table, a change file table, and a change order table, so that the software service system performs data statistics based on the construction target table, the change file table, and the change order table to obtain code review statistical information.

[0062] Among them, the change system can receive a temporary build target table and a temporary change file table from the build system, wherein the temporary build target table is generated by the build system based on the build information during object construction, and the temporary change file table is generated by the build system according to the historical version information of the object; associate the upgrade file generated by the build system; generate a build target table, a change file table, and a change order table based on the temporary build target table, the temporary change file table, and the upgrade file; upload the build target table, the change file table, and the change order table to the software service system, and instruct the software service system to perform data statistics to obtain code review statistical information.

[0063] Among them, the software service system can determine data statistics rules based on business needs; periodically obtain a build target table, a change file table, and a change order table from a change system, wherein the build target table, the change file table, and the change order table are generated by the change system based on a temporary build target table, a temporary change file table, and an upgrade file from the build system, wherein the temporary build target table, the temporary change file table, and the upgrade file are generated by the build system during the object construction process; based on the data statistics rules, data statistics are performed on the build target table, the change file table, and the change order table to obtain code review statistical information.

[0064] It should be noted that the description order of the following embodiments is not intended to limit the preferred order of the embodiments.

[0065] This embodiment will be described from the perspective of a data processing device. Figure 2 As shown, the specific process of applying the data processing method to build a system can be as follows:

[0066] 201. Obtain construction information corresponding to this object construction.

[0067] Among them, Service Oriented Architecture (SOA) is a software architecture model. Its main idea is to divide the software system into multiple services, and different services can collaborate by providing and using services to each other. Each service is an independent, self-contained module that communicates and interacts through standardized interfaces. Services can be combined, reused, replaced, and upgraded. This service-oriented architecture can improve the flexibility, reusability, scalability, maintainability, and manageability of the system, help enterprises optimize business processes and maximize the use of IT resources, and promote the digital transformation of enterprises.

[0068] Among them, SOA governance is a process of managing and coordinating service-oriented architectures, which aims to ensure that services can meet business needs, have high quality and reliability, coordinate with other services, and meet security and compliance requirements. SOA governance includes managing the service life cycle, service discovery and reuse, service version control, service access control and performance management, service security and compliance, etc. Through SOA governance, organizations can achieve better service management and utilization, improve the reusability and flexibility of services, and accelerate business innovation and development.

[0069] Among them, code review (CR) is a software quality assurance activity, which mainly checks the program by viewing and reading part of the source code of the program. It is a means to check whether there are quality problems in the source code. The CR rate is used to count the version code review rate.

[0070] Among them, the code change merge request (Merge Request, MR) refers to merging the content of the developed code into the desired branch in a merge request manner. The recipient of the request is generally the project or team leader or other members.

[0071] Optionally, in one embodiment, before the step of “obtaining construction information corresponding to the current object construction”, the following may also be included:

[0072] receiving an object building request from a business owner, the object building request including a building configuration file;

[0073] Trigger the compilation and build tasks based on the build configuration file.

[0074] Among them, the function of WebHooks is to help users upload code and automatically call back a user-set address. Then according to the callback mechanism of Git WebHooks, when a specific event occurs, the Git server will send the request data to the preset URL address through an HTTP POST request, thereby triggering the corresponding operation in the external system.

[0075] Among them, git push is one of the most important functions of the Git server, which is used to send all updated commits of the local branch stored in the local system to the remote branch. Using the push command allows users to send the latest updated commits to the corresponding remote server.

[0076] For example, the business manager can send an object build request to the build system by initiating a git tag push operation. Correspondingly, the build system can receive the object build request from the business manager, where the object build request includes a build configuration file. The build system then triggers the compilation build task based on the build configuration file orange-ci.yml. After the compilation build task is triggered, according to the Git WebHooks callback mechanism, this application can generate a corresponding container based on the image in the server according to the configuration file rules carried in the build configuration file, and run the script to obtain the build information in the container environment to complete the reporting of the build information.

[0077] In one embodiment, if Figure 8 The figure below shows a diagram of triggering a compilation and build task. The business manager can use the office management system to send a git push command. After receiving the git push command, the code collaboration management system uses WebHooks to upload the code to the main server and receives the address returned by the main server. The main server will generate a corresponding container based on the image and run the corresponding script in the container environment to complete the reporting of the build information.

[0078] 202. Based on the construction information, construct the object and generate a temporary construction target table.

[0079] For example, the build system can build objects according to the build information, generate a temporary build target table, and call the http interface provided by ilogs to report the temporary build target table.

[0080] In one embodiment, if Fig. 9 The following is a schematic diagram of the execution link. The code collaboration management system can trigger the compilation and build task according to the build configuration file orange-ci.yml. After the compilation and build task is triggered, the corresponding container can be generated according to the image in the server according to the configuration file rules carried in the build configuration file, and the Python script for obtaining the build information can be run in the container environment to complete the report of the build information, and then the http interface provided by ilogs is called to report the temporary build target table.

[0081] 203. Write the build identifier corresponding to the current object build into the upgrade file generated by the current object build.

[0082] Generating build artifacts and corresponding upgrade files is a very important process in the object building process. By writing the build identifier into the upgrade file, it can ensure that the version information of each object build can be accurately recorded and transmitted, and it also facilitates subsequent version control and management.

[0083] Optionally, in one embodiment, the step of “writing the construction identifier corresponding to the current object construction into the upgrade file generated by the current object construction” may include:

[0084] Based on this object construction, generate a construction identifier corresponding to this object construction;

[0085] Based on the current object construction, a construction product corresponding to the current object construction is generated, wherein the construction product includes an upgrade file;

[0086] The build identifier is written into the upgrade file.

[0087] For example, after the compilation and build task is completed, a unique build identifier will be generated to represent the object build. The build identifier can be stored in an environment variable so that it can be referenced in the build product, that is, the build identifier is stored in a database or other persistent data storage. You can use compilation tools, packaging tools, etc. to generate build products. The build products usually include binary files, library files, configuration files, etc. The build products usually include some upgrade files, such as configuration files or upgrade script files.

[0088] By writing some script files or other tools, the build identifier can be written into the upgrade file. This process can generally be associated with a change order to record the relationship between the change order and the build identifier. By writing the build identifier into the upgrade file, the version information of the client, server, etc. can be updated. Through the above process, the build identifier can be automatically written into the upgrade file and associated with the change order during the object construction process, which will help record and find specific build versions, while improving the efficiency of version management and collaboration.

[0089] 204. Generate a temporary change file table based on the historical version information of the object.

[0090] Optionally, in one embodiment, the step of “generating a temporary change file table based on the historical version information of the object” may include:

[0091] Get the code change merge request list corresponding to the historical version of the object;

[0092] Parse the code change merge request list to obtain the list of changed files corresponding to each code change merge request;

[0093] Generate a temporary change file table based on the change file list.

[0094] For example, Fig.10As shown, you can obtain the build information and build according to this tag at the same time. The script will execute the corresponding API to obtain the code change merge request list directly related to the last released version, and then parse the code change merge request list to obtain the list of changed files brought by each code change merge request, and call the http interface provided by the general ilogs to report the temporary change file table.

[0095] 205. Send the temporary build target table, the upgrade file, and the temporary change file table to the change system.

[0096] For example, a temporary build target table, upgrade file, and temporary change file table can be sent to the change system to instruct the change system to generate a build target table, a change file table, and a change order table based on the temporary build target table, upgrade file, and temporary change file table, so that the software service system can perform data statistics based on the build target table, change file table, and change order table to obtain code review statistical information.

[0097] In one embodiment, the technical solution of the present application can also be used to design a research and development management system. The terminal version product must be triggered by each change to trigger a build. A change order table identifier is first generated, and then the object build is triggered to generate a build identifier, and then the change file list is calculated, thereby completing the connection of the entire research and development process.

[0098] The core design of the technical solution of this application solves the problem that SOA governance cannot be carried out in the terminal field. It obtains build information in the build system, triggers the build system to build a version, obtains the list of code change merge requests between the two versions in the build system container environment, and queries the list of change files based on each code change merge request. At this stage, the data collection and storage of build objects and change files are completed. The build system will write the build identifier to the upgrade file, and the product will associate the upgrade file generated by the front-end environment when the change system releases the change. This solves the problem of the relationship between the change system, the build system, and the change file, and ultimately the data of the build target table, the change file table, and the change order table can be landed in the database. The SOA system can calculate the code review statistics of all code change merge requests of the terminal according to preset rules.

[0099] This application splits the R&D data generated by different systems, designs a build target table, a change file table, and a change order table, and combines the existing R&D process to design an algorithm to obtain the code change merge request list and change file list released by the terminal. The change order table and the build object are associated through the build identifier, which opens up the data association between the three systems and makes them no longer isolated, thereby improving the transparency of terminal R&D data and achieving data governance.

[0100] As can be seen from the above, this embodiment is applied to the construction system, and the construction system can obtain the construction information corresponding to the current object construction; based on the construction information, the object is constructed and a temporary construction target table is generated; the construction identifier corresponding to the current object construction is written into the upgrade file generated by the current object construction; based on the historical version information of the object, a temporary change file table is generated; the temporary construction target table, the upgrade file, and the temporary change file table are sent to the change system, instructing the change system to generate a construction target table, a change file table, and a change order table, so that the software service system can perform data statistics based on the construction target table, the change file table, and the change order table to obtain code review statistics. This application can solve the problem of whether each change in terminal SOA governance has been reviewed by the team code, connect the change system, the construction system, and the software service system to complete report statistics, reduce the risk of terminal version release, and achieve quality observability. Different from the background change release in the prior art, the terminal construction system and the change release are mostly not implemented on the same system, and it is difficult to count the change release review rate. This application designs a set of mechanisms to ultimately achieve data statistics and governance through data integration.

[0101] This embodiment will be described from the perspective of a data processing device. Figure 3 As shown, the specific process of applying the data processing method to the change system can be as follows:

[0102] 301. Receive a temporary build target table and a temporary change file table from a build system.

[0103] For example, the change system can receive a temporary build target table and a temporary change file table from the build system, wherein the temporary build target table is generated by the build system based on the build information during object construction, and the temporary change file table is generated by the build system based on the historical version information of the object.

[0104] 302. Associate the upgrade files generated by the build system.

[0105] For example, when the build system initiates a change release, it is necessary to upload the associated upgrade files. The build step in the CI / CD process can be used to upload the files. CI / CD is a method of frequently delivering applications to customers by introducing automation in the application development phase. That is, use relevant plug-ins or APIs to upload the upgrade files to a cloud repository, such as Amazon S3, OSS, etc. The uploaded relevant information needs to be written to the database for subsequent management.

[0106] 303. Generate a build target table, a change file table, and a change order table based on the temporary build target table, the temporary change file table, and the upgrade file.

[0107] Optionally, in one embodiment, the step of “generating a build target table, a change file table, and a change order table based on the temporary build target table, the temporary change file table, and the upgrade file” may include:

[0108] Generate a build target table based on the upgrade file, the temporary build target table, and the change identifier corresponding to this object change;

[0109] Generate a change file table based on the upgrade file, the temporary change file table, the build identifier corresponding to the current object build, and the change identifier corresponding to the current object change;

[0110] Generate a change order table based on the upgrade file and the build identifier corresponding to this object build.

[0111] For example, Figure 7 As shown, after the change system associates the upgrade file generated by the build system and obtains the temporary build target table and the temporary change file table from the build system, the build target table can be generated according to the upgrade file, the temporary build target table, and the change identifier corresponding to this object change, wherein the build target table can be as shown in Table 1:

[0112]

[0113] Table 1

[0114] The change system may generate a change file table according to the upgrade file, the temporary change file table, the build identifier corresponding to the current object build, and the change identifier corresponding to the current object change, wherein the change file table may be as shown in Table 2:

[0115]

[0116]

[0117]

[0118] Table 2

[0119] The change system may generate a change order table according to the upgrade file and the build identifier corresponding to the current object build, wherein the change order table may be as shown in Table 3:

[0120]

[0121]

[0122]

[0123] Table 3

[0124] 304. Upload the build target table, the change file table, and the change order table to the software service system.

[0125] For example, the change system may upload the build target table, the change file table, and the change order table to the software service system, and instruct the software service system to perform data statistics to obtain code review statistical information.

[0126] In one embodiment, for example, after the change is approved, the change order table needs to be uploaded. Specifically, a database, a connection library, or an SQL statement can be used to upload the change order table data to a cloud storage repository or service, such as MySQL, PostgreSQL, MongoDB, etc.

[0127] For example, you can create a review rate table for data warehouses and changes in the database, which contains key information about data warehouses and changes, such as data warehouse name, change ID, review end time, etc. Then, during data processing and statistics, the processed warehouse and change review rate data is written into the database table, which can be implemented using relevant SQL statements or data connection libraries. The final data will be stored in the data warehouse, and the SOA system can count the warehouse and code change review rates according to the rules.

[0128] In one embodiment, the uploaded upgrade files and change list data need to be version controlled and backed up for subsequent management and backtracking. Among them, tools such as Git and SVN can be used for version control, and cloud storage services can be used for data backup.

[0129] In addition, since the uploaded upgrade files and change order table data may contain sensitive company information, security encryption and access control are required. Encryption algorithms can be used to encrypt data, perform certificate authentication and session management to ensure that only authorized users can access and operate data.

[0130] The core design of the technical solution of this application solves the problem that SOA governance cannot be carried out in the terminal field. It obtains build information in the build system, triggers the build system to build a version, obtains the list of code change merge requests between the two versions in the build system container environment, and queries the list of change files based on each code change merge request. At this stage, the data collection and storage of build objects and change files are completed. The build system will write the build identifier to the upgrade file, and the product will associate the upgrade file generated by the front-end environment when the change system releases the change. This solves the problem of the relationship between the change system, the build system, and the change file, and ultimately the data of the build target table, the change file table, and the change order table can be landed in the database. The SOA system can calculate the code review statistics of all code change merge requests of the terminal according to preset rules.

[0131] This application splits the R&D data generated by different systems, designs a build target table, a change file table, and a change order table, and combines the existing R&D process to design an algorithm to obtain the code change merge request list and change file list released by the terminal. The change order table and the build object are associated through the build identifier, which opens up the data association between the three systems and makes them no longer isolated, thereby improving the transparency of terminal R&D data and achieving data governance.

[0132] As can be seen from the above, this embodiment is applied to the change system, and the change system can receive a temporary build target table and a temporary change file table from the build system, wherein the temporary build target table is generated by the build system based on the build information in the object construction, and the temporary change file table is generated by the build system according to the historical version information of the object; associate the upgrade file generated by the build system; generate a build target table, a change file table, and a change order table based on the temporary build target table, the temporary change file table, and the upgrade file; upload the build target table, the change file table, and the change order table to the software service system, and instruct the software service system to perform data statistics to obtain code review statistics. This application can solve the problem of counting whether each change in terminal SOA governance has been reviewed by the team code, connect the change system, the build system, and the software service system to complete report statistics, reduce the risk of terminal version release, and achieve quality observability. Different from the background change release in the prior art, the terminal build system and the change release are mostly not implemented on one system, and it is difficult to count the change release review rate. This application designs a set of mechanisms to ultimately achieve data statistics and governance through data integration.

[0133] This embodiment will be described from the perspective of a data processing device. Figure 4 As shown, the specific process of applying the data processing method to the software service system can be as follows:

[0134] 401. Determine data statistics rules based on business needs.

[0135] For example, the software service system can design rules and algorithms for the SOA system according to business needs, realize statistical and analytical calculations of the review rates of warehouses and changes, and can be implemented based on big data technologies such as MapReduce, Spark, and Hadoop.

[0136] In one embodiment, the data statistics rule can be set as follows: if the data warehouse or change order table has no directly dependent change files, it is ignored; if the data warehouse or change order table has directly dependent change files, and all directly dependent change files have corresponding code change merge requests, and all these code change merge requests have been reviewed, then the number of change orders reviewed by each person in charge who participated in the review is increased by one; if the data warehouse or change order table has directly dependent change files, and all directly dependent files have corresponding code change merge requests, and all these code change merge requests have not been reviewed by the person in charge, then the total number of change order tables that the person in charge of the change order table submitter needs to review is increased by one. The final statistics are: the review rate of each person in charge = the number of reviewed change orders / the total number of change order tables that need to be reviewed.

[0137] 402. Periodically obtain a build target table, a change file table, and a change order table from a change system.

[0138] For example, the software service system can periodically obtain the build target table, change file table, and change order table from the change system. The build target table, change file table, and change order table are generated by the change system based on the temporary build target table, temporary change file table, and upgrade file from the build system. The temporary build target table, temporary change file table, and upgrade file are generated by the build system during the object construction process. That is, the SOA system needs to periodically collect the review data in the database and calculate the review rate of each warehouse and change through the above-mentioned rules and algorithms.

[0139] 403. Based on the data statistics rules, data statistics are performed on the build target table, the change file table, and the change order table to obtain code review statistical information.

[0140] Optionally, in one embodiment, after the step of “based on the data statistics rules, performing data statistics on the build target table, the change file table, and the change order table to obtain code review statistical information”, the following may also be included:

[0141] Displays code review statistics.

[0142] For example, the SOA system can present the calculated review rate results to relevant project teams and managers through web pages or data visualization tools. Figure 6The figure shows a schematic diagram of code review statistics. The figure includes a filter bar, which includes a drop-down box for selecting a month, a drop-down box for TeamLeader, a drop-down box for center leader, a query button, etc. The figure also includes a header bar, which includes TeamLeader, the number of team members, center leader, total review rate, total number of GitMRs, the number of MRs in which TL participated, the number of MRs in which TL did not participate, etc. The figure also includes table data rows, which correspond to the data displayed by the statistics in the header.

[0143] The core design of the technical solution of this application solves the problem that SOA governance cannot be carried out in the terminal field. It obtains build information in the build system, triggers the build system to build a version, obtains the list of code change merge requests between the two versions in the build system container environment, and queries the list of change files based on each code change merge request. At this stage, the data collection and storage of build objects and change files are completed. The build system will write the build identifier to the upgrade file, and the product will associate the upgrade file generated by the front-end environment when the change system releases the change. This solves the problem of the relationship between the change system, the build system, and the change file, and ultimately the data of the build target table, the change file table, and the change order table can be landed in the database. The SOA system can calculate the code review statistics of all code change merge requests of the terminal according to preset rules.

[0144] This application splits the R&D data generated by different systems, designs a build target table, a change file table, and a change order table, and combines the existing R&D process to design an algorithm to obtain the code change merge request list and change file list released by the terminal. The change order table and the build object are associated through the build identifier, which opens up the data association between the three systems and makes them no longer isolated, thereby improving the transparency of terminal R&D data and achieving data governance.

[0145] As can be seen from the above, this embodiment is applied to the software service system. The software service system can determine the data statistics rules based on business needs; periodically obtain the build target table, change file table, and change order table from the change system. The build target table, change file table, and change order table are generated by the change system based on the temporary build target table, temporary change file table, and upgrade file from the build system. The temporary build target table, the temporary change file table, and the upgrade file are generated by the build system during the object construction process; based on the data statistics rules, the build target table, the change file table, and the change order table are statistically analyzed to obtain code review statistics. This application can solve the problem of whether each change in terminal SOA governance has been reviewed by the team code, connect the change system, the build system, and the software service system to complete the report statistics, reduce the risk of terminal version release, and achieve quality observability. Different from the background change release in the prior art, the terminal build system and the change release are mostly not implemented on one system, and it is difficult to statistically analyze the change release review rate. This application designs a set of mechanisms to ultimately achieve data statistics and governance through data integration.

[0146] According to the method described in the previous embodiment, the data processing device will be further described in detail below by taking the example of being specifically integrated into an electronic device.

[0147] The present application embodiment provides a data processing method, such as Figure 5 As shown, the specific process of the data processing method can be as follows:

[0148] 501. The build system obtains build information to build an object and generates a temporary build target table.

[0149] For example, the business manager initiates a git tag push operation, and the build system triggers the compilation and build task according to the build configuration file orange-ci.yml, runs the script to obtain the build information in the container, and calls the http interface provided by ilogs to report the temporary build target table. This step can complete the data reporting of the first table. The trigger principle diagram of the build configuration file orange-ci push is as follows Figure 8 shown.

[0150] Among them, based on the Git WebHooks callback mechanism, when a specific event occurs, the Git server will send the request data to the preset URL address through an HTTP POST request, thereby triggering the corresponding operation in the external system. The technical solution of this application will be based on the configuration file rules. For example, the git push operation will trigger the oci build. Each build will generate a corresponding container in the server according to the image (mirror), and will run the corresponding script in the container environment to complete the reporting of the build information. Its execution chain is as follows Fig. 9 shown.

[0151] 502. The build system generates a temporary change file table based on the code change merge request list directly from the last released version of the object.

[0152] For example, when obtaining the build information, based on the current tag build, the script will execute the corresponding API to obtain the MR List (code change merge request list) directly related to the last released version, and then parse the MR List to obtain the list of changed files brought by each MR (code change merge request), and generally call the http interface provided by ilogs to report the temporary change file table. This step completes the data reporting of the second table. The complete process is as follows Fig.10 shown.

[0153] 503. The build system writes the build identifier into the upgrade file.

[0154] Among them, in the build process, generating build products and corresponding upgrade files is a very important process. By writing the build ID (build identifier) ​​into the upgrade file, it can ensure that the version information of each build can be accurately recorded and transmitted, and it is also convenient for subsequent version control and management.

[0155] Here is the build process and how to write the build ID to the upgrade file:

[0156] 1. Get the build ID: When the compilation process is completed, a unique build ID will be generated to identify this build. The build ID can be stored in an environment variable for reference in the build product.

[0157] 2. Generate build products: Use compilation tools, packaging tools, etc. to generate build products. Build products usually include binary files, library files, configuration files, etc. Note that the build ID needs to be stored in a database or other persistent data storage.

[0158] 3. Generate upgrade files: The build product usually contains some upgrade files, such as configuration files or upgrade script files. By writing the build ID into the upgrade file, the version information of the client, server, etc. can be updated.

[0159] 4. Write the build ID: By writing some script files or other tools, the build ID can be written into the upgrade file. This process can generally be associated with the change order table to record the relationship between the change order table and the build ID.

[0160] Through the above process, the build ID can be automatically written to the upgrade file during the build process and associated with the change order table. This will help record and find specific build versions, while improving the efficiency of version management and collaboration.

[0161] 504. The change system receives the temporary build target table and the temporary change file table from the build system, and associates the upgrade file.

[0162] 505. The change system generates a build target table, a change file table, and a change order table according to the temporary build target table, the temporary change file table, and the upgrade file.

[0163] For example, when the build system initiates a change release, it will upload the upgrade file associated with the local release. After the change is approved, the change order table data will be uploaded. Here, the data reporting of the third table is completed. The detailed technical details are as follows:

[0164] 1. Upload associated upgrade files: When initiating a change release, you need to upload the associated upgrade files. You can use the build step in the CI / CD process to upload the upgrade files to a cloud repository, such as Amazon S3, OSS, etc., using related plug-ins or APIs. The uploaded related information needs to be written into the database for subsequent management.

[0165] 2. Upload the change order table data after the change is approved: After the change is approved, the change order table data needs to be uploaded. The specific implementation method can use a database connection library or SQL statement to upload the change order table data to a cloud repository or service, such as MySQL, PostgreSQL, MongoDB, etc.

[0166] 3. Version control and backup: Uploaded upgrade files and change order table data need to be version controlled and backed up for subsequent management and backtracking. You can use tools such as Git and SVN for version control and use cloud storage services for data backup.

[0167] 4. Security encryption and access control: The uploaded upgrade files and change order table data may contain sensitive information of the company, which requires security encryption and access control. Encryption algorithms can be used to encrypt data; certificate authentication and session management can be performed to ensure that only authorized users can access and operate data.

[0168] 506. The SOA system determines data statistics rules based on business needs.

[0169] For example, the data statistics rules can be as follows:

[0170] 1. If the data warehouse or change order table has no directly dependent change files, it is ignored.

[0171] 2. If the data warehouse or change order table has directly dependent change files, and all directly dependent files have corresponding MergeRequests (code change merge requests), and all these MergeRequests have been reviewed by the TL (team leader), the number of change orders reviewed by each TL participating in the review will be increased by one.

[0172] 3. If the data warehouse or change order table has directly dependent change files, all directly dependent files have corresponding MergeRequests, and all these MergeRequests have not been reviewed by the TL, then the total number of change orders that the TL of the change order submitter needs to review will be increased by one.

[0173] The final statistic is that the review rate of each TL = the number of change order forms reviewed / the total number of change orders that need to be reviewed.

[0174] 507. The SOA system periodically obtains the build target table, the change file table, and the change order table from the change system.

[0175] 508. The SOA system performs data statistics on the build target table, the change file table, and the change order table according to the data statistics rules to obtain code review statistics information.

[0176] For example, the final data will be stored in the database table, and the SOA system will record the review rate of the data warehouse and changes according to the rules. The detailed technical details are as follows:

[0177] 1. Create database tables: Create review rate tables for data warehouses and changes in the database, which contain key information about the data warehouse and changes, such as warehouse name, change ID (change identifier), review end time, etc.

[0178] 2. Write data into the database table: During the data processing and statistical process, write the processed data warehouse and the changed review rate data into the database table. This can be achieved using relevant SQL statements or data connection libraries.

[0179] 3. Design data statistics rules for the SOA system: Based on business needs, design rules and algorithms for the SOA system to implement statistics and analytical calculations on the review rate of data warehouses and changes. This can be achieved based on big data technologies such as MapReduce, Spark, and Hadoop.

[0180] 4. Data collection and calculation: The SOA system needs to periodically collect review data from the database and calculate the review rate of each data warehouse and change through the above-mentioned rules and algorithms.

[0181] 5. Provide visual results: SOA system can present the calculated review rate results to relevant project teams and managers through web pages or data visualization tools. Figure 6 The figure shows the UI diagram of the MR TL review rate of the product-side data warehouse, where the filter bar includes a drop-down box for selecting the month, a drop-down box for TeamLeader, a drop-down box for center leader, and a query button; the header bar includes TeamLeader, number of team members, center leader, total review rate, total number of GitMRs, number of MRs in which TL participated, and number of MRs in which TL did not participate; the table data rows correspond to the data displayed in the header statistics.

[0182] In one embodiment, the present application can also design a research and development management system. The terminal version product triggers the build through each change. It will first generate a change order table ID, then trigger the tag build to generate the build ID, and then calculate the change file list, thereby completing the connection of the entire research and development process.

[0183] As can be seen from the above, this embodiment can obtain construction information through the construction system to construct the object and generate a temporary construction target table. The construction system generates a temporary change file table based on the code change merge request list directly from the last released version of the object. The construction system writes the construction identifier into the upgrade file. The change system receives the temporary construction target table and the temporary change file table from the construction system, and associates the upgrade file. The change system generates a construction target table, a change file table, and a change order table based on the temporary construction target table, the temporary change file table, and the upgrade file. The SOA system determines the data statistics rules based on business needs. The SOA system periodically obtains the construction target table, the change file table, and the change order table from the change system. The SOA system performs data statistics on the construction target table, the change file table, and the change order table according to the data statistics rules to obtain code review statistics information. This application can solve the problem of whether each change in terminal SOA governance has been reviewed by the team code, open up the change system, the construction system, and the software service system to complete the report statistics, reduce the risk of terminal version release, and achieve quality observability. Different from the background change release in the existing technology, the terminal construction system and change release are mostly not implemented on the same system, and it is difficult to count the change release review rate. This application designs a mechanism to ultimately achieve data statistics and governance through data integration.

[0184] In order to better implement the above method, the embodiment of the present application also provides a data processing device, which is used to construct a system such as Fig.11 As shown, the data processing device may include a first acquisition unit 1101, a construction unit 1102, a writing unit 1103, a first generation unit 1104, and a sending unit 1105, as follows:

[0185] The first acquisition unit 1101 is used to acquire the construction information corresponding to the current object construction;

[0186] A construction unit 1102, configured to perform object construction on the object based on the construction information and generate a temporary construction target table;

[0187] The writing unit 1103 is used to write the construction identifier corresponding to the current object construction into the upgrade file generated by the current object construction;

[0188] A first generating unit 1104 is used to generate a temporary change file table based on the historical version information of the object;

[0189] The sending unit 1105 is used to send the temporary build target table, the upgrade file, and the temporary change file table to the change system, instructing the change system to generate a build target table, a change file table, and a change order table, so that the software service system can perform data statistics based on the build target table, the change file table, and the change order table to obtain code review statistical information.

[0190] Optionally, in some embodiments of the present application, the first acquisition unit may also be used to receive an object construction request from a business manager, where the object construction request includes a construction configuration file; and trigger a compilation construction task based on the construction configuration file.

[0191] Optionally, in some embodiments of the present application, the writing unit can be specifically used to generate a build identifier corresponding to the current object construction based on the current object construction; generate a build product corresponding to the current object construction based on the current object construction, the build product including an upgrade file; and write the build identifier into the upgrade file.

[0192] Optionally, in some embodiments of the present application, the first generation unit can be specifically used to obtain a code change merge request list corresponding to the historical version of the object; parse the code change merge request list to obtain a change file list corresponding to each code change merge request; and generate a temporary change file table based on the change file list.

[0193] The present application also provides a data processing device, which is applied to a change system, such as Fig.12 As shown, the data processing device may include a receiving unit 1201, an associating unit 1202, a second generating unit 1203, and an uploading unit 1204, as follows:

[0194] The receiving unit 1201 is used to receive a temporary build target table and a temporary change file table from a build system, wherein the temporary build target table is generated by the build system based on the build information during the object construction, and the temporary change file table is generated by the build system based on the historical version information of the object;

[0195] An associating unit 1202 is used to associate the upgrade file generated by the building system;

[0196] A second generating unit 1203 is used to generate a build target table, a change file table, and a change order table based on the temporary build target table, the temporary change file table, and the upgrade file;

[0197] The uploading unit 1204 is used to upload the build target table, the change file table, and the change order table to the software service system, and instruct the software service system to perform data statistics to obtain code review statistical information.

[0198] Optionally, in some embodiments of the present application, the second generation unit can be specifically used to generate a build target table based on the upgrade file, the temporary build target table, and the change identifier corresponding to this object change; generate a change file table based on the upgrade file, the temporary change file table, the build identifier corresponding to this object build, and the change identifier corresponding to this object change; generate a change order table based on the upgrade file and the build identifier corresponding to this object build.

[0199] The present application also provides a data processing device, which is applied to a software service system, such as Fig.13 As shown, the data processing device may include a determining unit 1301, a second obtaining unit 1302, and a statistical unit 1303, as follows:

[0200] The determining unit 1301 is used to determine data statistics rules based on business requirements;

[0201] A second acquisition unit 1302 is used to periodically acquire a build target table, a change file table, and a change order table from the change system, wherein the build target table, the change file table, and the change order table are generated by the change system based on a temporary build target table, a temporary change file table, and an upgrade file from the build system, wherein the temporary build target table, the temporary change file table, and the upgrade file are generated by the build system during the object construction process;

[0202] The statistical unit 1303 is used to perform data statistics on the build target table, the change file table, and the change order table based on the data statistical rules to obtain code review statistical information.

[0203] Optionally, in some embodiments of the present application, the statistical unit may also be used to display the code review statistical information.

[0204] As can be seen from the above, this embodiment is applied to the construction system, and the construction system can obtain the construction information corresponding to the current object construction through the first acquisition unit; the construction unit can construct the object based on the construction information and generate a temporary construction target table; the writing unit writes the construction identifier corresponding to the current object construction into the upgrade file generated by the current object construction; the first generation unit generates a temporary change file table based on the historical version information of the object; the sending unit sends the temporary construction target table, the upgrade file, and the temporary change file table to the change system, instructing the change system to generate a construction target table, a change file table, and a change order table, so that the software service system can perform data statistics based on the construction target table, the change file table, and the change order table to obtain code review statistics. This application can solve the problem of whether each change in terminal SOA governance has been reviewed by the team code, connect the change system, the construction system, and the software service system to complete report statistics, reduce the risk of terminal version release, and achieve quality observability. Different from the background change release in the existing technology, the terminal construction system and change release are mostly not implemented on the same system, and it is difficult to count the change release review rate. This application designs a mechanism to ultimately achieve data statistics and governance through data integration.

[0205] The present application also provides an electronic device, such as Fig.14 As shown, it shows a schematic diagram of the structure of an electronic device involved in an embodiment of the present application, and the electronic device may be a terminal or a server, etc. Specifically:

[0206] The electronic device may include components such as a processor 1401 with one or more processing cores, a memory 1402 with one or more computer-readable storage media, a power supply 1403, and an input unit 1404. Those skilled in the art will appreciate that Fig.14 The electronic device structure shown in the figure does not constitute a limitation on the electronic device, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0207] The processor 1401 is the control center of the electronic device, which uses various interfaces and lines to connect various parts of the entire electronic device, and executes various functions of the electronic device and processes data by running or executing software programs and / or modules stored in the memory 1402, and calling data stored in the memory 1402. Optionally, the processor 1401 may include one or more processing cores; preferably, the processor 1401 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 1401.

[0208] The memory 1402 can be used to store software programs and modules. The processor 1401 executes various functional applications and data processing by running the software programs and modules stored in the memory 1402. The memory 1402 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc.; the data storage area may store data created according to the use of the electronic device, etc. In addition, the memory 1402 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices. Accordingly, the memory 1402 may also include a memory controller to provide the processor 1401 with access to the memory 1402.

[0209] The electronic device also includes a power supply 1403 for supplying power to each component. Preferably, the power supply 1403 can be logically connected to the processor 1401 through a power management system, so as to manage charging, discharging, and power consumption through the power management system. The power supply 1403 can also include any components such as one or more DC or AC power supplies, recharging systems, power failure detection circuits, power converters or inverters, and power status indicators.

[0210] The electronic device may further include an input unit 1404, which may be used to receive input digital or character information and generate keyboard, mouse, joystick, optical or trackball signal input related to user settings and function control.

[0211] Although not shown, the electronic device may also include a display unit, etc., which will not be described in detail here. Specifically in this embodiment, the processor 1401 in the electronic device will load the executable files corresponding to the processes of one or more application programs into the memory 1402 according to the following instructions, and the processor 1401 will run the application programs stored in the memory 1402 to implement various functions, as follows:

[0212] The construction system can obtain the construction information corresponding to this object construction; based on the construction information, perform object construction on the object and generate a temporary construction object table; write the construction identifier corresponding to this object construction into the upgrade file generated by this object construction; based on the historical version information of the object, generate a temporary change file table; send the temporary construction object table, the upgrade file, and the temporary change file table to the change system, instructing the change system to generate a construction object table, a change file table, and a change order table, so that the software service system can perform data statistics based on the construction object table, the change file table, and the change order table to obtain code review statistical information.

[0213] The specific implementation of the above operations can be found in the previous embodiments, which will not be described in detail here.

[0214] As can be seen from the above, this embodiment can obtain the construction information corresponding to the current object construction through the construction system; based on the construction information, the object is constructed and a temporary construction object table is generated; the construction identifier corresponding to the current object construction is written into the upgrade file generated by the current object construction; based on the historical version information of the object, a temporary change file table is generated; the temporary construction object table, the upgrade file, and the temporary change file table are sent to the change system, instructing the change system to generate a construction object table, a change file table, and a change order table, so that the software service system can perform data statistics based on the construction object table, the change file table, and the change order table to obtain code review statistics. This application can solve the problem of whether each change in terminal SOA governance has been reviewed by the team code, connect the change system, the construction system, and the software service system to complete report statistics, reduce the risk of terminal version release, and achieve quality observability. Different from the background change release in the prior art, the terminal construction system and the change release are mostly not implemented on the same system, and it is difficult to count the change release review rate. This application designs a set of mechanisms to ultimately achieve data statistics and governance through data integration.

[0215] A person of ordinary skill in the art will appreciate that all or part of the steps in the various methods of the above embodiments may be completed by instructions, or by controlling related hardware through instructions. The instructions may be stored in a computer-readable storage medium and loaded and executed by a processor.

[0216] To this end, an embodiment of the present application provides a computer-readable storage medium, in which a plurality of instructions are stored, and the instructions can be loaded by a processor to execute the steps in any data processing method provided in the embodiment of the present application. For example, the instructions can execute the following steps:

[0217] The construction system can obtain the construction information corresponding to this object construction; based on the construction information, perform object construction on the object and generate a temporary construction object table; write the construction identifier corresponding to this object construction into the upgrade file generated by this object construction; based on the historical version information of the object, generate a temporary change file table; send the temporary construction object table, the upgrade file, and the temporary change file table to the change system, instructing the change system to generate a construction object table, a change file table, and a change order table, so that the software service system can perform data statistics based on the construction object table, the change file table, and the change order table to obtain code review statistical information.

[0218] The specific implementation of the above operations can be found in the previous embodiments, which will not be described in detail here.

[0219] The computer-readable storage medium may include: a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0220] Since the instructions stored in the computer-readable storage medium can execute the steps in any data processing method provided in the embodiments of the present application, the beneficial effects that can be achieved by any data processing method provided in the embodiments of the present application can be achieved. Please refer to the previous embodiments for details and will not be repeated here.

[0221] According to one aspect of the present application, a computer program product or a computer program is provided, the computer program product or the computer program comprising computer instructions, the computer instructions being stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the method provided in various optional implementations of the above-mentioned data processing aspects.

[0222] The above is a detailed introduction to a data processing method and related equipment provided in an embodiment of the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for technical personnel in this field, according to the idea of ​​the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A data processing method, characterized in that: Used to build systems, including: Get the construction information corresponding to this object construction; Based on the construction information, construct the object and generate a temporary construction target table; Write the build identifier corresponding to this object build into the upgrade file generated by this object build; Generate a temporary change file table based on the historical version information of the object; The temporary build target table, the upgrade file, and the temporary change file table are sent to the change system, instructing the change system to generate a build target table, a change file table, and a change order table, so that the software service system can perform data statistics based on the build target table, the change file table, and the change order table to obtain code review statistical information.

2. The data processing method according to claim 1, characterized in that: Before obtaining the construction information corresponding to the current object construction, the method further includes: receiving an object construction request from a business person in charge, wherein the object construction request includes a construction configuration file; Based on the build configuration file, a compilation build task is triggered.

3. The data processing method according to claim 1, characterized in that: The construction identifier corresponding to the current object construction is written into the upgrade file generated by the current object construction, including: Based on this object construction, generate a construction identifier corresponding to this object construction; Based on the current object construction, a construction product corresponding to the current object construction is generated, wherein the construction product includes an upgrade file; The build identifier is written into the upgrade file.

4. The data processing method according to claim 1, characterized in that: The step of generating a temporary change file table based on the historical version information of the object includes: Obtain a list of code change merge requests corresponding to historical versions of the object; Parse the code change merge request list to obtain a list of changed files corresponding to each code change merge request; Based on the changed file list, a temporary changed file table is generated.

5. A data processing method, characterized in that: Applied to change the system, including: Receiving a temporary build target table and a temporary change file table from a build system, wherein the temporary build target table is generated by the build system based on build information during object construction, and the temporary change file table is generated by the build system based on historical version information of the object; Associating the upgrade files generated by the build system; Generate a build target table, a change file table, and a change order table based on the temporary build target table, the temporary change file table, and the upgrade file; The build target table, the change file table, and the change order table are uploaded to a software service system, and the software service system is instructed to perform data statistics to obtain code review statistical information.

6. The data processing method according to claim 5, characterized in that: The generating of the build target table, the change file table, and the change order table based on the temporary build target table, the temporary change file table, and the upgrade file comprises: Generate a build target table based on the upgrade file, the temporary build target table, and the change identifier corresponding to the current object change; Generate a change file table based on the upgrade file, the temporary change file table, the build identifier corresponding to the current object build, and the change identifier corresponding to the current object change; A change order table is generated based on the upgrade file and the build identifier corresponding to this object build.

7. A data processing method, characterized in that: Applied to software service systems, including: Determine data statistics rules based on business needs; Periodically acquiring a build target table, a change file table, and a change order table from a change system, wherein the build target table, the change file table, and the change order table are generated by the change system based on a temporary build target table, a temporary change file table, and an upgrade file from the build system, wherein the temporary build target table, the temporary change file table, and the upgrade file are generated by the build system during the object build process; Based on the data statistics rule, data statistics are performed on the build target table, the change file table, and the change order table to obtain code review statistical information.

8. The data processing method according to claim 7, characterized in that: After performing data statistics on the build target table, the change file table, and the change order table based on the data statistics rule to obtain code review statistical information, the method further includes: Displays the code review statistics.

9. A data processing device, characterized in that: Used to build systems, including: A first acquisition unit is used to acquire construction information corresponding to the current object construction; A construction unit, configured to construct the object based on the construction information and generate a temporary construction target table; A writing unit, used for writing the building identifier corresponding to the current object building into the upgrade file generated by the current object building; A first generating unit, configured to generate a temporary change file table based on the historical version information of the object; A sending unit is used to send the temporary build target table, the upgrade file, and the temporary change file table to the change system, instructing the change system to generate a build target table, a change file table, and a change order table, so that the software service system can perform data statistics based on the build target table, the change file table, and the change order table to obtain code review statistical information.

10. A data processing device, characterized in that: Applied to change the system, including: a receiving unit, configured to receive a temporary build target table and a temporary change file table from a build system, wherein the temporary build target table is generated by the build system based on build information during object construction, and the temporary change file table is generated by the build system based on historical version information of the object; An associating unit, used for associating an upgrade file generated by the building system; A second generating unit, configured to generate a build target table, a change file table, and a change order table based on the temporary build target table, the temporary change file table, and the upgrade file; The uploading unit is used to upload the build target table, the change file table, and the change order table to the software service system, and instruct the software service system to perform data statistics to obtain code review statistical information.

11. A data processing device, characterized in that: Applied to software service systems, including: A determination unit is used to determine data statistics rules based on business requirements; a second acquisition unit, for periodically acquiring a build target table, a change file table, and a change order table from a change system, wherein the build target table, the change file table, and the change order table are generated by the change system based on a temporary build target table, a temporary change file table, and an upgrade file from the build system, wherein the temporary build target table, the temporary change file table, and the upgrade file are generated by the build system during the object construction process; A statistical unit is used to perform data statistics on the build target table, the change file table, and the change order table based on the data statistical rules to obtain code review statistical information.

12. An electronic device, characterized in that: It comprises a memory and a processor; the memory stores an application program, and the processor is used to run the application program in the memory to execute the operations in the data processing method according to any one of claims 1 to 8.

13. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor to execute the steps in the data processing method according to any one of claims 1 to 8.

14. A computer program product comprising a computer program or instructions, characterized in that When the computer program or instruction is executed by a processor, the steps of the data processing method according to any one of claims 1 to 8 are implemented.