Code execution method and device

[0001] This is a continuation of International Patent Application No. PCT/CN2021/086711 filed on Apr. 12, 2021, which claims priority to Chinese Patent Application No. 202010337776.8 filed on Apr. 26, 2020. The disclosures of all of the aforementioned patent applications are hereby incorporated by reference in their entireties.

[0002] This application relates to the field of software development technologies, and in particular, to a code execution method and a device.

[0003] Tools such as compilation and building and code check are indispensable during software package creation. These tools are executed and operated based on a specific version of code. To use these tools, the code of the specific version needs to be obtained. The obtaining process has a critical impact on execution efficiency of these tools.

[0004] In the conventional technology, a user selects, in a compilation and building system, a code version on which compilation and building are to be performed. A download machine in the compilation and building system downloads corresponding code from a code version control system based on the code version selected by the user, and then distributes the downloaded code to each executor based on a dependency relationship, so that each executor can complete a compilation and execution operation.

[0005] However, for some relatively large software products, hundreds or thousands of executors may be required to simultaneously initiate download actions from a code hosting platform. Therefore, a download process may take a relatively long time, and compilation and building completion efficiency may be low.

[0006] This application provides a code execution method and a device, to improve efficiency of completing a code processing process such as compilation and building, code check, and code analysis.

[0007] According to a first aspect, this application provides a code execution method, and the method is applied to a code execution system. The code execution system includes a pre-preparation service module, a storage cluster, and an executor. The method includes: the pre-preparation service module obtains a pre-preparation policy set by a user; the pre-preparation service module downloads, based on the pre-preparation policy, an updated code file included in an updated code version from a code hosting platform to the storage cluster; the pre-preparation service module receives a code execution request, and determines, based on the code execution request, a storage address of code content corresponding to the code execution request in the storage cluster; the pre-preparation service module sends the storage address to the executor; the executor obtains the code content based on the received storage address; and the executor executes the obtained code content.

[0008] In a possible design, that the pre-preparation service module downloads, based on the pre-preparation policy, an updated code file included in an updated code version from a code hosting platform to the storage cluster includes: the pre-preparation service module receives a code version update notification sent by the code hosting platform; the pre-preparation service module determines, based on the code version update notification and the pre-preparation policy, whether the updated code version complies with the pre-preparation policy; and if the updated code version complies with the pre-preparation policy, the pre-preparation service module downloads the updated code file included in the updated code version from the code hosting platform to the storage cluster.

[0009] In a possible design, the pre-preparation policy includes a first commit type, and the code version update notification includes a commit type corresponding to the updated code version.

[0010] That the pre-preparation service determines, based on the code version update notification and the pre-preparation policy, whether the updated code version complies with the pre-preparation policy includes: determining, based on the commit type corresponding to the updated code version, whether the commit type corresponding to the updated code version and the first commit type are a same commit type; and if the commit type corresponding to the updated code version and the first commit type are a same commit type, determining that the updated code version complies with the pre-preparation policy.

[0011] In a possible design, the pre-preparation policy includes a first code branch, and the code version update notification includes information about a code branch in which the updated code version is located.

[0012] That the pre-preparation service determines, based on the code version update notification and the pre-preparation policy, whether the updated code version complies with the pre-preparation policy includes: determining, based on the information about the code branch in which the updated code version is located, whether the code branch in which the updated code version is located and the first code branch are a same code branch; and if the code branch in which the updated code version is located and the first code branch are a same code branch, determining that the updated code version complies with the pre-preparation policy.

[0013] In a possible design, the code version update notification further includes an identifier of the updated code version, and the method further includes: the pre-preparation service module determines, based on the identifier of the updated code version, M code files corresponding to the updated code version, where M is a positive integer; the pre-preparation service module obtains a storage address of code content of each code file in the M code files in the storage cluster; and the pre-preparation service module generates, based on the identifier of the updated code version, the M code files, and the storage address of the code content of each code file in the M code files in the storage cluster, a file tree object corresponding to the updated code version.

[0014] In a possible design, the code execution request carries information about at least one code version that the user requests to execute.

[0015] That the pre-preparation service module determines, based on the code execution request, a storage address of code content corresponding to the code execution request in the storage cluster includes: the pre-preparation service module determines, based on the information about the at least one code version and the file tree object, a storage address of code content corresponding to each code version in the at least one code version.

[0016] That the executor obtains the code content based on the received storage address includes: the executor determines to-be-read storage addresses based on the received storage address of the code content corresponding to each code version in the at least one code version, where storage addresses included in the to-be-read storage addresses are different from each other; and the executor reads the code content from the storage cluster based on the to-be-read storage addresses.

[0017] According to a second aspect, this application provides a code execution apparatus, including: a pre-preparation service module, configured to: obtain a pre-preparation policy set by a user; download, based on the pre-preparation policy, an updated code file included in an updated code version from a code hosting platform to a storage cluster; receive a code execution request, and determine, based on the code execution request, a storage address of code content corresponding to the code execution request in the storage cluster; and send the storage address to an executor; and an execution module, configured to: obtain the code content based on the received storage address; and execute the obtained code content.

[0018] In a possible design, the pre-preparing service module is specifically configured to: receive a code version update notification sent by the code hosting platform; determine, based on the code version update notification and the pre-preparation policy, whether the updated code version complies with the pre-preparation policy; and if the updated code version complies with the pre-preparation policy, download the updated code file included in the updated code version from the code hosting platform to the storage cluster.

[0019] In a possible design, the pre-preparation policy includes a first commit type, and the code version update notification includes a commit type corresponding to the updated code version; and the pre-preparation service module is specifically configured to: determine, based on the commit type corresponding to the updated code version, whether the commit type corresponding to the updated code version and the first commit type are a same commit type; and if the commit type corresponding to the updated code version and the first commit type are a same commit type, determine that the updated code version complies with the pre-preparation policy.

[0020] In a possible design, the pre-preparation policy includes a first code branch, and the code version update notification includes information about a code branch in which the updated code version is located; and the pre-preparation service module is specifically configured to: determine, based on the information about the code branch in which the updated code version is located, whether the code branch in which the updated code version is located and the first code branch are a same code branch; and if the code branch in which the updated code version is located and the first code branch are a same code branch, determine that the updated code version complies with the pre-preparation policy.

[0021] In a possible design, the pre-preparation service module is further configured to: determine, based on an identifier of the updated code version, M code files corresponding to the updated code version, where M is a positive integer; obtain a storage address of code content of each code file in the M code files in the storage cluster; and generate, based on the identifier of the updated code version, the M code files, and the storage address of the code content of each code file in the M code files in the storage cluster, a file tree object corresponding to the updated code version.

[0022] In a possible design, the code execution request carries information about at least one code version that the user requests to execute; and the pre-preparation service module is specifically configured to: determine, based on the information about the at least one code version and the file tree object, a storage address of code content corresponding to each code version in the at least one code version; and correspondingly, the execution module is specifically configured to: determine to-be-read storage addresses based on the received storage address of the code content corresponding to each code version in the at least one code version, where storage addresses included in the to-be-read storage addresses are different from each other; and read the code content from the storage cluster based on the to-be-read storage addresses.

[0023] According to a third aspect, this application provides a readable storage medium. The readable storage medium stores a computer program. When the computer program is executed, the foregoing code execution method is implemented.

[0024] According to a fourth aspect, this application provides an electronic device, including a memory and a processor.

[0025] The memory is configured to store program instructions, and the processor is configured to invoke the program instructions in the memory to perform the foregoing code execution method.

[0026] According to the code execution method and the device provided in this embodiment, a user is allowed to set a pre-preparation policy. A pre-preparation service module may obtain, in advance based on the pre-preparation policy, a code version that complies with the policy and store the code version in a storage cluster. When the user triggers a code execution request, code content can be directly obtained from the storage cluster. In this way, a problem of low compilation and building completion efficiency caused by a relatively long time occupied by a download action can be avoided. In addition, after receiving a plurality of storage addresses, an executor filters out duplicate storage addresses, to obtain to-be-read storage addresses. Because storage addresses included in the to-be-read storage addresses are different, a problem of repeated reading can be avoided, and this further resolves a problem in the conventional technology that a code file is repeatedly downloaded when execution tasks received by an executor overlap.

[0035] To make the objectives, technical solutions, and advantages of this application clearer, the following clearly describes the technical solutions in this application with reference to accompanying drawings in this application. It is clearly that described embodiments are a part rather than all of embodiments of this application. All other embodiments obtained by persons of ordinary skill in the art based on embodiments of this application without creative efforts shall fall within the protection scope of this application.

[0036] In this application, it should be explained that terms such as “first” and “second” are merely intended for a purpose of description, and shall not be understood as an indication or implication of relative importance. In addition, “at least one” means one or more, and “a plurality of” means two or more. The term “and/or” describes an association relationship between associated objects and may indicate three relationships. For example, A and/or B may indicate the following cases: Only A exists, both A and B exist, and only B exists. A and B may be singular or plural. The character “/” generally indicates a kind of “or” relationship between the associated objects. “At least one of the following items (pieces)” or a similar expression thereof means any combination of these items, including a single item (piece) or any combination of a plurality of items (pieces). For example, at least one item (piece) of a, b, or c may indicate: a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c may be singular or plural.

[0037] For the same software product, many code versions are generated when R&D personnel continuously improve functions and fix vulnerabilities. In a process of creating a software package of a code version, tools such as compilation and building, code check, and code analysis are used. A compilation and building tool is used as an example. As shown in FIG. 1, a compilation and building process in the conventional technology is as follows: A user selects a code version on which compilation and building are to be performed. A distribution module in a compilation and building system determines, based on the code version selected by the user, a plurality of code files corresponding to the code version, and then delivers an execution task to each executor based on a dependency relationship between these code files. After receiving the execution task, the executor first downloads the corresponding code file from a code hosting platform, and then performs a compilation and building operation. For example, if the code version selected by the user is version A, the distribution module may determine that code files corresponding to version A include a file 1, a file 2, a file 3, and a file 4, where the file 1 and the file 3 have a dependency relationship, the file 2 and the file 4 have a dependency relationship, and the file 2 and the file 3 have a dependency relationship. In this case, based on the foregoing dependency relationships, the file 1 and the file 3 may be used as one execution task, the file 2 and the file 4 may be used as one execution task, the file 2 and the file 3 may be used as one execution task, and the three execution tasks may be delivered to the three executors shown in FIG. 1. After receiving the execution tasks, the executors first download the corresponding code files from the code hosting platform, and then perform a compilation and building operation on code content in the downloaded code files.

[0038] However, for some relatively large software products, hundreds or thousands of executors may be required to simultaneously initiate download actions from the code hosting platform, and a download process takes a relatively long time, so that compilation and building completion efficiency is low. In addition, when the user needs to build a plurality of code versions, if the execution tasks received by the executor overlap, a code file may be repeatedly downloaded. For example, if a user needs to build a code version A and a code version B, an execution task corresponding to the code version A received by an executor includes a file 1 and a file 2, and an execution task corresponding to the code version B includes the file 1 and a file 3. In this case, the execution tasks received by the executor overlap, and the executor needs to repeatedly download the file 1, and this causes a waste of download resources.

[0039] It should be noted that the foregoing description is provided by using a compilation and building tool as an example. A code check tool and a code analysis tool are similar to the compilation and building tool in terms of obtaining a code version, and are both implemented by executors directly downloading code files from a code hosting platform. Therefore, for the two tools, problems similar to those in compilation and building also exist, that is, low code check efficiency and low code analysis efficiency.

[0040] Due to the foregoing technical problems in the conventional technology, this application provides a code execution method. The method may be implemented based on a code execution system shown in FIG. 2. The code execution system shown in FIG. 2 includes a pre-preparation service module, a storage cluster, and an executor cluster. The executor cluster includes a plurality of executors. The pre-preparation service module may be integrated in the code execution system, or may be an independent module. FIG. 2 shows an example in which the pre-preparation service module is integrated in the code execution system. A user can configure a pre-preparation policy of a code version by using the pre-preparation service module.

[0041] It should be noted that when the code execution method provided in this application is applied to a compilation and building scenario, the code execution system may be a compilation and building system; when the code execution method provided in this application is applied to a code check scenario, the code execution system may be a code check system; or when the code execution method provided in this application is applied to a code analysis scenario, the code execution system may be a code analysis system.

[0042] In the conventional technology, it takes a relatively long time for an executor to download a corresponding code file from a code hosting platform, and this results in low compilation and building completion efficiency. In view of this, the foregoing pre-preparation service module is added in this application. A user may configure a pre-preparation policy of a code version by using the pre-preparation service module. When the code version is updated on a code hosting platform, the pre-preparation service module may download, based on the foregoing pre-preparation policy, an updated code file included in an updated code version from the code hosting platform to a storage cluster, so that the storage cluster stores all code versions that comply with the pre-preparation policy set by the user. When the user needs to perform compilation and building on one or more of the code versions, the user triggers a code execution request. After receiving the code execution request, the pre-preparation service module first determines, based on the code execution request, a storage address of code content corresponding to the code execution request in the storage cluster. Then, the storage address is sent to an executor, so that the executor can obtain the code content based on the storage address, and further execute the obtained code content.

[0043] It can be learned that the code execution method provided in this application allows a user to set a pre-preparation policy. A pre-preparation service module may obtain, in advance based on the pre-preparation policy, a code version that complies with the policy and store the code version in a storage cluster. When the user triggers a code execution request, code content can be directly obtained from the storage cluster. Therefore, a problem of low compilation and building completion efficiency caused by a relatively long time occupied by a download action can be avoided.

[0044] The following describes in detail the code execution method provided in this application by using specific embodiments. Based on the system shown in FIG. 2, FIG. 3 is a schematic flowchart of an embodiment of a code execution method according to this application. As shown in FIG. 3, the code execution method provided in this application includes the following steps.

[0045] S301: A pre-preparation service module obtains a pre-preparation policy set by a user.

[0046] In a possible implementation, the code execution system shown in FIG. 2 provides a user interaction interface, and the user may configure the pre-preparation policy by using the user interaction interface.

[0047] Optionally, the pre-preparation policy may be a code branch, or may be a commit type.

[0048] S302: The pre-preparation service module downloads, based on the pre-preparation policy, an updated code file included in an updated code version from a code hosting platform to a storage cluster.

[0049] In a possible implementation, this step may further include the following steps.

[0050] Step A: The pre-preparation service module receives a code version update notification sent by the code hosting platform.

[0051] Specifically, when detecting that there is an updated code version, the code hosting platform sends the code version update notification to the pre-preparation service module. The code version update notification may include: an identifier of the updated code version, information about a code branch in which the updated code version is located, a commit type corresponding to the updated code version, and/or information about the updated code file included in the updated code version.

[0052] The following describes the meanings of the code branch, the code version, and the code file on the code hosting platform.

[0053] As shown in FIG. 4, it is assumed that a basic version of a software product is a version 0. A new code version may be further developed based on the version 0 for purposes such as function optimization and vulnerability fixing of the product. A plurality of code branches may be designed based on different development purposes. R&D personnel may update a code version on a corresponding code branch. Each code version is a version further developed based on a previous code version on a same code branch. The submission of each code version corresponds to a time point. Therefore, each code version also corresponds to a time point. Each code version includes one or more code repositories, and each code repository includes a plurality of code files.

[0054] In a possible implementation, when a user submits a new code version, the code hosting platform may determine that there is a code version update, and may use the code version submitted by the user as the updated code version. The code hosting platform may further obtain a modified code file submitted by the user this time, and use the code file as the updated code file included in the updated code version.

[0055] For example, it is assumed that a user modifies a file 110 included in a version 11 on a code branch 1, to obtain a file 120, and after the file 120 is submitted, a version 12 is obtained. The code hosting platform may use the version 12 as an updated code version. The file 120 may be used as the updated code file included in the version 12.

[0056] Step B: The pre-preparation service module determines, based on the code version update notification and the pre-preparation policy, whether the updated code version complies with the pre-preparation policy.

[0057] In a possible implementation, the pre-preparation policy set by the user includes a first commit type. In this case, whether the updated code version complies with the pre-preparation policy may be determined in the following manner: determining, based on the commit type corresponding to the updated code version, whether the commit type corresponding to the updated code version and the first commit type are a same commit type; and if the commit type corresponding to the updated code version and the first commit type are a same commit type, determining that the updated code version complies with the pre-preparation policy.

[0058] Following the example in the step A, the code version update notification sent by the code hosting platform includes an identifier of the version 12, information about a code branch in which the version 12 is located, a commit type corresponding to the version 12, and/or information about the updated code file 120 included in the version 12. Whether the commit type corresponding to the version 12 and the first commit type are a same commit type may be determined based on the commit type corresponding to the version 12. If the commit type corresponding to the version 12 and the first commit type are a same commit type, it is determined that the version 12 complies with the foregoing pre-preparation policy. For example, if the first commit type is code result rectification, and the commit type corresponding to the version 12 is also code result rectification, it may be determined that the version 12 complies with the foregoing pre-preparation policy.

[0059] In another possible implementation, the pre-preparation policy set by the user includes a first code branch. In this case, whether the updated code version complies with the pre-preparation policy may be determined in the following manner: determining, based on the information about the code branch in which the updated code version is located, whether the code branch in which the updated code version is located and the first code branch are a same code branch; and if the code branch in which the updated code version is located and the first code branch are a same code branch, determining that the updated code version complies with the pre-preparation policy.

[0060] Following the example in the step A, the code version update notification sent by the code hosting platform includes the identifier of the version 12, the information about the code branch in which the version 12 is located, the commit type corresponding to the version 12, and/or information about the updated code file 120 included in the version 12. Whether the code branch in which the version 12 is located and the first code branch are a same code branch may be determined based on the information about the code branch in which the version 12 is located. If the code branch in which the version 12 is located and the first code branch are a same code branch, it is determined that the version 12 complies with the pre-preparation policy.

[0061] Step C: If the updated code version complies with the pre-preparation policy, download the updated code file included in the updated code version from the code hosting platform to the storage cluster.

[0062] In a possible implementation, referring to the foregoing description, the code version update notification sent by the code hosting platform may include the information about the updated code file included in the updated code version. Therefore, a corresponding file may be downloaded from the code hosting platform to the storage cluster based on the information about the updated code file included in the updated code version.

[0063] In a possible implementation, the pre-preparation service module may further determine whether code files included in the updated code version stored in the storage cluster are complete in addition to the updated code file. If the code files are incomplete, when downloading the updated code file from the code hosting platform, the pre-preparation service module further needs to download the missing code file to the storage cluster.

[0064] In a possible implementation, the method provided in this embodiment may further include: The pre-preparation service module determines, based on the identifier of the updated code version, M code files corresponding to the updated code version, where M is a positive integer; the pre-preparation service module obtains a storage address of code content of each code file in the M code files in the storage cluster; and the pre-preparation service module generates, based on the identifier of the updated code version, the M code files, and the storage address of the code content of each code file in the M code files in the storage cluster, a file tree object corresponding to the updated code version. The file tree object may alternatively be stored in the storage cluster. A file tree object shown in FIG. 5 can be obtained by performing this operation on all updated code versions.

[0065] S303: The pre-preparation service module receives a code execution request, and determines, based on the code execution request, a storage address of code content corresponding to the code execution request in the storage cluster.

[0066] The following describes an implementation in which the user triggers the code execution request.

[0067] The code execution request carries information about at least one code version that the user requests to execute, information about each code version may include an identifier of the code version and description information of the code version, and the description information of the code version may be used to indicate a commit type corresponding to the code version.

[0068] In a possible implementation, the user may trigger the code execution request by selecting an option box in FIG. 6. Each option box in FIG. 6 corresponds to two types of information. Information on the left is an identifier of the code version, and information on the right is description information of the code version. In this case, the code version that the user requests to execute is a code version corresponding to the option box selected by the user, and the information about the code version that the user requests to execute includes: information about the code version corresponding to the option box selected by the user. For example, if the user selects a first option box, an identifier of the code version that the user requests to execute is 4358ca2e, and description information of the code version that the user requests to execute is Fix #code result rectification.

[0069] In another possible implementation, the user may first select an option box in FIG. 6 to select a code version that the user currently requests to execute, and then trigger a code execution button to trigger the code execution request. Similarly, in this case, the code version that the user requests to execute is a code version corresponding to the option box selected by the user, and the information about the code version that the user requests to execute is information about the code version corresponding to the option box selected by the user.

[0070] In a possible implementation, after receiving the code execution request triggered by the user, the pre-preparation service module determines, based on the information about the at least one code version and the file tree object, a storage address of code content corresponding to each code version in the at least one code version. The pre-preparation service module sends, to the executor, the storage address of the code content corresponding to each code version in the at least one code version.

[0071] Descriptions are provided below by using examples.

[0072] As shown in FIG. 5, it is assumed that a storage cluster stores n file tree objects, including a file tree object 1, a file tree object 2, . . . , and a file tree object n. Each file tree object corresponds to one code version. It is assumed that an identifier of a code version corresponding to the file tree object 1 is 4358ca2e, an identifier of a code version corresponding to the file tree object 2 is 17bfab15, an identifier of a code version corresponding to the file tree object 3 is 1405fe59, an identifier of a code version corresponding to the file tree object 4 is f4d598e2, an identifier of a code version corresponding to the file tree object 5 is 04ad141a, an identifier of a code version corresponding to the file tree object 6 is d32df9a5, and an identifier of a code version corresponding to the file tree object n is version n. After a code execution request triggered by a user is received, it is assumed that the code execution request carries information about two code versions. Based on the information about the two code versions, it may be determined that identifiers of the two code versions are 4358ca2e and f4d598e2. Based on the relationship between the file tree object and the code version, it may be determined that the file tree object corresponding to 4358ca2e is the file tree object 1. Because the code files corresponding to the file tree object 1 include a file 1 and a file 4, it may be determined that 4358ca2e includes the file 1 and the file 4, a storage address of the file 1 is an address 1, and a storage address of the file 4 is an address 4. The file tree object corresponding to f4d598e2 is the file tree object 4. Because the code files corresponding to the file tree object 4 include the file 1 and a file 5, it may be determined that f4d598e2 includes the file 1 and the file 5, a storage address of the file 1 is the address 1, and a storage address of the file 5 is an address 5.

[0073] S304: The pre-preparation service module sends the storage address to the executor.

[0074] Following the example in step S303, it may be determined, in S303, that storage addresses of code content corresponding to 4358ca2e are the address 1 and the address 4, and storage addresses of code content corresponding to f4d598e2 are the address 1 and the address 5. In this case, the pre-preparation service module sends, to the executor, the address 1 and the address 4 that correspond to 4358ca2e, and the address 1 and the address 5 that correspond to f4d598e2.

[0075] S305: The executor obtains the code content based on the received storage address.

[0076] S306: The executor executes the obtained code content.

[0077] In a possible implementation, after receiving the storage address of the code content corresponding to each code version in the at least one code version, the executor filters out duplicate storage addresses, to determine to-be-read storage addresses, and reads code content from the storage cluster based on the to-be-read storage addresses. For example, storage addresses of the code content corresponding to the version A received by the executor include an address 1 and an address 2, and storage addresses of the code content corresponding to the version B include the address 1 and an address 3. The address 1 is repeated, so that the redundant address 1 is filtered out, to obtain the to-be-read storage addresses, including the address 1, the address 2, and the address 3. Further, the code content is read from the storage cluster based on the three storage addresses. This avoids a problem in the conventional technology that a code file is repeatedly downloaded when execution tasks received by an executor overlap.

[0078] According to the code execution method provided in this embodiment, a user is allowed to set a pre-preparation policy. A pre-preparation service module may obtain, in advance based on the pre-preparation policy, a code version that complies with the policy and store the code version in a storage cluster. When the user triggers a code execution request, code content can be directly obtained from the storage cluster. In this way, a problem of low compilation and building completion efficiency caused by a relatively long time occupied by a download action can be avoided. In addition, after receiving a plurality of storage addresses, an executor filters out duplicate storage addresses, to obtain to-be-read storage addresses. Because storage addresses included in the to-be-read storage addresses are different from each other, a problem of repeated reading can be avoided, and this further resolves a problem in the conventional technology that a code file is repeatedly downloaded when execution tasks received by an executor overlap.

[0079] FIG. 7 is a schematic diagram of a structure of a code execution apparatus 700 according to this application. As shown in FIG. 7, the code execution apparatus 700 provided in this application includes a pre-preparation service module 701 and an execution module 702. The pre-preparation service module 701 is configured to: obtain a pre-preparation policy set by a user; download, based on the pre-preparation policy, an updated code file included in an updated code version from a code hosting platform to a storage cluster; receive a code execution request, and determine, based on the code execution request, a storage address of code content corresponding to the code execution request in the storage cluster; and send the storage address to an executor. The execution module 702 is configured to: obtain the code content based on the received storage address; and execute the obtained code content.

[0080] Optionally, the pre-preparation service module 701 is specifically configured to: receive a code version update notification sent by the code hosting platform; determine, based on the code version update notification and the pre-preparation policy, whether the updated code version complies with the pre-preparation policy; and if the updated code version complies with the pre-preparation policy, download the updated code file included in the updated code version from the code hosting platform to the storage cluster.

[0081] Optionally, the pre-preparation policy includes a first commit type. The code version update notification includes a commit type corresponding to the updated code version. The pre-preparation service module 701 is specifically configured to: determine, based on the commit type corresponding to the updated code version, whether the commit type corresponding to the updated code version and the first commit type are a same commit type; and if the commit type corresponding to the updated code version and the first commit type are a same commit type, determine that the updated code version complies with the pre-preparation policy.

[0082] Optionally, the pre-preparation policy includes a first code branch. The code version update notification includes information about a code branch in which the updated code version is located. The pre-preparation service module 701 is specifically configured to: determine, based on the information about the code branch in which the updated code version is located, whether the code branch in which the updated code version is located and the first code branch are a same code branch; and if the code branch in which the updated code version is located and the first code branch are a same code branch, determine that the updated code version complies with the pre-preparation policy.

[0083] Optionally, the pre-preparation service module 701 is further configured to: determine, based on an identifier of the updated code version, M code files corresponding to the updated code version, where M is a positive integer; obtain a storage address of code content of each code file in the M code files in the storage cluster; and generate, based on the identifier of the updated code version, the M code files, and the storage address of the code content of each code file in the M code files in the storage cluster, a file tree object corresponding to the updated code version.

[0084] Optionally, the code execution request carries information about at least one code version that the user requests to execute. The pre-preparation service module 701 is specifically configured to determine, based on the information about the at least one code version and the file tree object, a storage address of code content corresponding to each code version in the at least one code version. Correspondingly, the execution module 702 is specifically configured to: determine to-be-read storage addresses based on the storage address of code content corresponding to each code version in the at least one code version, where storage addresses included in the to-be-read storage addresses are different from each other; and read code content from the storage cluster based on the to-be-read storage addresses.

[0085] The foregoing code execution apparatus provided in this application may perform the steps in the foregoing method embodiment. Implementation principles and technical effects are similar, and details are not described herein again.

[0086] FIG. 8 is a schematic diagram of a hardware structure of an electronic device 800 according to this application. As shown in FIG. 8, the electronic device 800 includes a memory 801 and at least one processor 802. The memory 801 is configured to store program instructions, and the at least one processor 802 is configured to invoke the program instructions in the memory 801 to perform the steps in the foregoing method embodiment. Implementation principles and technical effects are similar, and details are not described herein again.

[0087] This application further provides a readable storage medium. The readable storage medium stores executable instructions. When executing the executable instructions, the at least one processor 802 of the electronic device implements the steps in the foregoing method embodiment. Implementation principles and technical effects are similar, and details are not described herein again.

[0088] This application further provides a program product. The program product includes computer programs (namely, executable instructions). The computer programs are stored in a readable storage medium. At least one processor 802 of an electronic device may read the computer program from the readable storage medium, and the at least one processor 802 executes the computer program, so that the electronic device implements the foregoing code execution method.

[0089] In the several embodiments provided in this application, it should be understood that the disclosed device and method may be implemented in other manners. For example, the described device embodiment is merely an example. For example, division into modules is merely logical function division. During actual implementation, there may be another division manner. For example, a plurality of modules may be combined or integrated into another system, or some features may be ignored or not performed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections may be implemented by using some interfaces. The indirect couplings or communication connections between the apparatuses or units may be implemented in electrical, mechanical, or other forms.

[0090] Modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical units, may be located in one position, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual requirements to achieve the objectives of the solutions in the embodiments of this application.

[0091] In addition, functional modules in embodiments of this application may be integrated into one processing unit, or each of the modules may exist alone physically, or two or more modules are integrated into one unit. The unit formed by the modules may be implemented in a form of hardware, or may be implemented in a form of hardware in addition to a software functional unit.

[0092] When the foregoing integrated module is implemented in a form of a software functional module, the integrated unit may be stored in a computer-readable storage medium. The software function module is stored in a storage medium and includes several instructions to enable a computer device (which may be a personal computer, a server, or a network device) or a processor to perform some steps of the methods in the embodiments of this application.

[0093] It should be understood that the processor may be a central processing unit (CPU), or may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or the like. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor or the like. The steps of the methods disclosed with reference to the present disclosure may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and a software module in a processor.

[0094] The memory may include a high-speed RAM memory, or may include a non-volatile memory NVM such as at least one magnetic disk memory, or may include a USB flash drive, a removable hard disk, a read-only memory, a magnetic disk, an optical disc, or the like.

[0095] The bus may be an industry standard architecture (ISA) bus, a peripheral component interconnect (peripheral component, PCI) bus, an extended industry standard architecture (EISA) bus, or the like. Buses may be classified into an address bus, a data bus, a control bus, and the like. For ease of representation, the bus in the accompanying drawings in this application is not limited to only one bus or only one type of bus.

[0096] All or a part of the foregoing embodiments may be implemented by software, hardware, firmware, or any combination thereof. When software is configured to implement the embodiments, the embodiments may be implemented entirely or partially in a form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or some of the procedures or functions according to embodiments of this application are generated. The computer may be a general-purpose computer, a dedicated computer, a computer network, or another programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or may be transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center in a wired (for example, a coaxial cable, an optical fiber, or a digital subscriber line (DSL)) or wireless (for example, infrared, radio, or microwave) manner. The computer-readable storage medium may be any usable medium accessible by a computer, or a data storage device, such as a server or a data center, integrating one or more usable media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk drive, or a magnetic tape), an optical medium (for example, a digital versatile disc (DVD)), a semiconductor medium (for example, a solid state drive (solid state disk, SSD)), or the like.