Automatic environment deployment method, electronic equipment and readable storage medium

Abstract

The invention discloses an automatic environment deployment method, electronic equipment and a readable storage medium, and belongs to the technical field of computers. The method comprises the steps that an environment deployment request is received, and the environment deployment request is used for requesting deployment of a running environment of a target application program; obtaining a plurality of remote code warehouses corresponding to the target application program from a multi-warehouse relation table included in the management configuration file; and according to the plurality of remote code warehouses, performing automatic environment deployment by calling a target framework.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of computer technologies, and particularly to an environment automatic deployment method, an electronic device, and a readable storage medium. Background Art

[0002] Currently, code management for the same product usually adopts a decentralized management method. In decentralized management, a product includes multiple modules, and each module can have at least one code repository. This requires using different tools and processes to manage the code in multiple code repositories. Each repository can use an independent Git as the version control system and is maintained by different teams. As a result, when deploying the operating environment of the product, the deployment complexity is high and the deployment efficiency is low. Summary of the Invention

[0003] The embodiments of the present application provide an environment automatic deployment method, an electronic device, and a readable storage medium, which can solve the problem of low environment deployment efficiency in a multi-repository environment.

[0004] To solve the above technical problems, the present application is implemented as follows:

[0005] In a first aspect, an environment automatic deployment method is provided. The method includes: receiving an environment deployment request, where the environment deployment request is used to request the deployment of the operating environment of a target application; obtaining a plurality of remote code repositories corresponding to the target application from a multi-repository relationship table included in a management configuration file; and performing automatic environment deployment by calling a target framework according to the plurality of remote code repositories.

[0006] In a second aspect, an electronic device is provided, including a processor and a memory. The memory stores a program or instruction that can run on the processor. When the program or instruction is executed by the processor, the method described in the first aspect is implemented.

[0007] In a third aspect, a readable storage medium is provided. At least one computer program is stored in the readable storage medium. When the computer program is loaded and executed by a processor, the method described in the first aspect is implemented.

[0008] In a fourth aspect, a computer program product is provided. The computer program product includes at least one computer program. When the computer program is loaded and executed by a processor, the method described in the first aspect is implemented.

[0009] In an embodiment of the present application, by receiving a request to deploy the operating environment of a target application, then obtaining multiple remote code repositories corresponding to the target application from the multi-repository relationship table included in the management configuration file, and then performing automated environment deployment by calling a target framework based on the multiple remote code repositories, an efficient operation of completing environment deployment based on a single request is achieved, reducing the complexity of deployment; at the same time, since the multi-repository relationship table uniformly manages the correspondence between each application and multiple remote code repositories, all remote code repositories corresponding to the target application can be directly obtained from the multi-repository relationship table, realizing the unified management of multiple remote code repositories, thereby simplifying the deployment process and improving the deployment efficiency.

[0010] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present application. Brief Description of the Drawings

[0011] The drawings herein are incorporated into the specification and constitute a part of this specification, showing embodiments consistent with the present application, and are used together with the specification to explain the principles of the present application.

[0012] Figure 1 It shows a schematic diagram of an environment automated deployment method provided by an exemplary embodiment of the present application;

[0013] Figure 2 It shows another schematic diagram of an environment automated deployment method provided by an exemplary embodiment of the present application;

[0014] Figure 3 It shows yet another schematic diagram of an environment automated deployment method provided by an exemplary embodiment of the present application;

[0015] Figure 4 It shows still another schematic diagram of an environment automated deployment method provided by an exemplary embodiment of the present application;

[0016] Figure 5 It shows a schematic diagram of the structure of a version control and build environment management system provided by an exemplary embodiment of the present application;

[0017] Figure 6 It shows a schematic diagram of the structure of an electronic device provided by an exemplary embodiment of the present application. Detailed Embodiments

[0018] Exemplary embodiments will be described in detail herein, and examples thereof are shown in the accompanying drawings. When the following description refers to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. On the contrary, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0019] Figure 1 FIG. 4 shows a schematic flowchart of an environment automatic deployment method provided by an exemplary embodiment of the present application. This method can be executed by an electronic device, and the electronic device can include: a terminal device or a network-side device. In other words, this method can be executed by software or hardware installed in the electronic device. This method can include the following steps:

[0020] S110: Receive an environment deployment request.

[0021] Wherein, the environment deployment request is used to request to deploy the running environment of the target application program.

[0022] It can be understood that this running environment includes a build environment and a development environment.

[0023] Exemplarily, when a user needs to deploy the running environment of a certain application program, the user can click the deployment button on the corresponding interface, and the electronic device can receive the environment deployment request sent by the user. Wherein, the environment deployment request can carry the application identifier of the target application program, and the application identifier can uniquely identify the target application program.

[0024] S120: Obtain multiple remote code repositories corresponding to the target application program from the multi-repository relationship table included in the management configuration file.

[0025] Wherein, the multiple remote code repositories refer to the storage locations of the source code of the target application program.

[0026] It can be understood that the management configuration file stores detailed configuration information related to each application program. The detailed configuration information includes a multi-repository relationship table. The multi-repository relationship table includes multiple preset program identifiers and multiple remote code repositories corresponding to each preset program identifier. That is to say, according to the target application program specified in the environment deployment request, multiple remote code repositories corresponding to the target application program can be obtained from the multi-repository relationship table.

[0027] Optionally, the multi-repository relationship table further includes the association relationships corresponding to the multiple remote code repositories. The association relationships include the path associations between the local code repository and the multiple remote code repositories in terms of physical files and directory structures, and the logical associations between the local code repository and the multiple remote code repositories in terms of code branches and version tags.

[0028] It should be noted that the multi-repository relationship table in the management configuration file is updated regularly to ensure the accuracy and timeliness of the configuration information.

[0029] In another implementation, the method further includes: when the multiple remote code repositories corresponding to the target application cannot be obtained from the multi-repository relationship table, outputting a prompt message to reject the environment deployment request. It can be understood that if the user specifies a non-existent application, the deployment process will terminate immediately and a corresponding reminder will be returned, thus avoiding possible incorrect operations.

[0030] S130: Perform automated environment deployment by calling a target framework according to the multiple remote code repositories.

[0031] It can be understood that during the deployment process, the code in the multiple remote code repositories needs to be pulled to the local. Therefore, after receiving the environment deployment request, the corresponding multiple remote code repositories can be automatically obtained from the multi-repository relationship table according to the target application specified in the environment deployment request, and then passed to the target framework. In this way, the target framework can accurately obtain the source code from the specified location for accurate environment deployment.

[0032] Optionally, the target framework can be the repo framework, and the repo framework can effectively manage multiple associated remote code repositories.

[0033] In the embodiments of the present application, by receiving a request to deploy the running environment of the target application, then obtaining the multiple remote code repositories corresponding to the target application from the multi-repository relationship table included in the management configuration file, and then performing automated environment deployment by calling the target framework according to the multiple remote code repositories, the efficient operation of completing the environment deployment based on one request is realized, and the complexity of the deployment is reduced; at the same time, since the multi-repository relationship table uniformly manages the corresponding relationships between each application and the multiple remote code repositories, all the remote code repositories corresponding to the target application can be directly obtained from the multi-repository relationship table, realizing the unified management of the multiple remote code repositories, thereby simplifying the deployment process and improving the deployment efficiency.

[0034] Next, through Figure 2 a schematic illustration of the embodiments corresponding to the above environment deployment request will be given, such as Figure 2As shown in the figure, it includes the following steps:

[0035] S210: Receive a user request.

[0036] S220: Process the user request.

[0037] Among them, the processing process is to obtain the target application identifier from the user request, and the target application identifier is the program identifier of the target application.

[0038] S230: Determine whether the target application identifier exists in the multi-warehouse relationship table.

[0039] If it exists, go to step S240; if not, go to step S270.

[0040] S240: Obtain multiple remote code repositories corresponding to the target application identifier.

[0041] S250: Pass the multiple remote code repositories corresponding to the target application identifier into the repo framework.

[0042] S260: The repo framework performs local deployment of multiple remote code repositories.

[0043] S270: End the deployment.

[0044] In this embodiment, centralized configuration information management reduces the complexity of maintenance work, reduces the error rate, makes the relationship between each application and the corresponding remote code repository easier to manage and maintain. At the same time, through automated environment configuration, the consistency of the development environment is ensured, the compatibility issues caused by environment differences are reduced, and moreover, the automated environment configuration significantly reduces the need for manual operations and improves the deployment efficiency.

[0045] In one implementation, after the automated environment deployment by calling the target framework, the method further includes: when receiving a release request for the target application, obtaining the target version number and the target release method corresponding to the target application from the release request; generating a to-be-released file package according to the release method, where the package name of the to-be-released file package is composed of the target version number.

[0046] It is understandable that the release request is used to indicate pushing the target application to the production environment. Among them, the release request carries the target version number and the target release method corresponding to the target application. The target version number is used to indicate the unique identifier of the specific version or update to be released. The format of the target version number can be: major version number.minor version number.revision version number. For example, 1.0.0. Among them, the major version number usually refers to major updates or functional changes to the application, the minor version number refers to some minor functional updates or improvements, and the revision version number refers to bug fixes or minor improvements. The use of the target version number can ensure that each file package to be released is unique and can avoid confusion between file packages to be released under the same application. The release method is used to indicate the strategy for introducing the target version of the target application into the production environment. The release method includes but is not limited to source code release and patch release. After determining the release method, a file package to be released is generated according to the release method. The package name of the file package to be released is composed of the target version number. Exemplarily, assuming that the name of the target application is AA and its target version number is 7.2.0, then its package name can be: AA7.2.0. In this way, users can judge whether the application is the latest or whether there are available updates through the package name, which helps to improve user satisfaction.

[0047] It should be noted that after the user receives the release request, if the environment has not been deployed yet, then first deploy the environment according to the Figure 1 corresponding embodiment. After the environment deployment is completed, execute the release process.

[0048] In one implementation, after obtaining the target version number and the target release method corresponding to the target application from the release request, the method further includes: obtaining multiple remote code repositories corresponding to the target application from the multi-repository relationship table; calling the target framework to execute a target command, where the target command is used to add a target version number tag to each of the remote code repositories, and the target version number tag is used to uniquely identify the target version corresponding to the target application in the multiple remote code repositories.

[0049] It is understandable that when a target application needs to be released, a tag can be created in the version control system. Usually, this tag corresponds to the version number of the target application, that is, it is used to identify the target version. For example, if the target version of the target application is 1.2.3, the target version number tag corresponding to this version can be "v1.2.3". When creating target version number tags for multiple remote code repositories, the version pointed to by this target version number tag can be considered stable and releasable. This helps to avoid pushing untested or unstable programs to users, and at the same time can ensure that the code versions in the relevant remote code repositories are consistent when releasing, avoiding version inconsistencies caused by the same module in different remote code repositories, thus affecting the release.

[0050] In this implementation method, the remote code repositories corresponding to the target application are obtained from the multi-repository relationship table, which improves the accuracy of version control. At the same time, by calling the target framework to execute the command to add target version number tags to each of the remote code repositories, it helps to simplify version control management and release management, and optimizes the version release process.

[0051] In one implementation method, when the release method includes source code release, generating the file package to be released according to the release method includes: obtaining the source code files corresponding to the target version number tag from the multiple remote code repositories; and packing the source code files according to the local path relationship of the multiple remote code repositories to obtain the file package to be released.

[0052] Among them, source code release means packing and releasing the source code corresponding to the target version, which involves the release of new functions. Exemplarily, the target version numbers corresponding to source code release can be 1.0.0 or 1.2.0.

[0053] It is understandable that since the version pointed to by the target version number tag can be considered stable and releasable, when generating the file package to be released, the packed version is a verified and stable version. Therefore, the source code corresponding to the target version can be retrieved from multiple remote code repositories by using the already created target version number tags in the code repository, so as to generate the file package to be released. In addition, since the target application may include multiple modules, and each module may correspond to at least one remote code repository, then the target application corresponds to multiple remote code repositories. By packing the code according to the local path relationship of the multiple remote code repositories, the code of each module can be correctly integrated into the file package to be released, which can ensure the integrity and normal operation of the target application.

[0054] In another implementation, when the release method includes patch release, generating the file package to be released according to the release method includes: generating a code difference patch from the target version number tag to the historical version number tag, where the historical version number tag is the version number tag of the previous version corresponding to the target application; and obtaining the file package to be released by packaging the code difference patch according to the local path relationship of the multiple remote code repositories.

[0055] It can be understood that patch release corresponds to problem fixing or minor improvement, rather than introducing new features. Exemplarily, the target version number corresponding to patch release can be 1.0.1 or 1.2.2. That is to say, patch release usually increases the revision number based on the major version number or minor version number, for example, from 1.0.1 to 1.0.2. Therefore, patch release needs to generate a code difference patch from the target version number tag to the historical version number tag, that is, a code difference patch from 1.0.2 to 1.0.1. To ensure that this code difference patch can be correctly applied to the target application and avoid patch installation failure or abnormal operation of the target application due to path mismatch, it is necessary to align the code difference patch with the local paths of multiple remote code repositories, that is, package it according to the local path relationship of the multiple remote code repositories.

[0056] Next, Figure 3 a schematic illustration of the embodiment corresponding to the above release request is given. As Figure 3 shown, it includes the following steps:

[0057] S310: Receive a user request.

[0058] Wherein, the user request is a release request.

[0059] S320: Process the user request.

[0060] Wherein, the processing process is to obtain the target application identifier from the user request, and the target application identifier is the program identifier of the target application.

[0061] S330: Determine whether the target application identifier exists in the multi-repository relationship table.

[0062] If it exists, go to step S340; if not, go to step S393.

[0063] S340: Obtain multiple remote code repositories corresponding to the target application identifier.

[0064] S350: Pass the multiple remote code repositories corresponding to the target application identifier into the repo framework.

[0065] S360: The repo framework performs local deployment of multiple remote code repositories.

[0066] Among them, the specific content of the environment deployment involved in the above S320 - S360 can be referred to Figure 1 the embodiments shown, and will not be elaborated here.

[0067] S370: Create version number tags for multiple remote code repositories.

[0068] S380: Determine the release method.

[0069] Among them, in the case where the release method is source code release, go to step S381; in the case where the release method is patch release, go to step S391.

[0070] S381: Obtain the code differences of each repository from the target version number tag to the historical version number tag.

[0071] S382: Generate a code difference patch according to the code differences.

[0072] S383: Package the code difference patch according to the local path relationship of multiple remote code repositories.

[0073] S391: Determine the code corresponding to the target version according to the target version number tag.

[0074] S392: Package the code corresponding to the target version according to the local path relationship of multiple remote code repositories.

[0075] S393: End the release.

[0076] In this embodiment, the complexity of maintenance work is reduced through centralized configuration information management, the error rate is reduced, making the relationship between each application and the corresponding remote code repository easier to manage and maintain. At the same time, the automated label creation and version control functions enable the latest code to be quickly deployed to the production environment, shortening the solution time for security vulnerabilities and performance issues.

[0077] In one implementation, the management configuration file further includes a compilation dependency file; after the automated environment deployment is performed according to the multiple remote code repositories by calling a target framework, the method further includes: when receiving a build request for the target application, obtaining preset compilation parameters corresponding to the target application from the compilation dependency file, where the build request is used to request the compilation of the target application; and calling a target build framework for automated compilation according to the preset compilation parameters.

[0078] It can be understood that the compilation dependency files refer to various preset compilation parameters required during the compilation process. The preset compilation parameters can include various files or configuration information, and these files or configuration information can include specific types corresponding to each application, kernel configuration files, configuration files of the target build framework, compilation methods, or other necessary files or configuration information. After receiving the build request, the preset compilation parameters corresponding to the target application will be automatically obtained, and then the preset compilation parameters will be passed into the target build framework to achieve automated building, which helps to simplify build management and optimize the build process.

[0079] Optionally, the target build framework can be the yocto compilation framework.

[0080] It should be noted that after the user receives the build request, if the environment has not been deployed yet, the environment will be deployed first according to Figure 1 the corresponding embodiment, and after the environment deployment is completed, the build process will be executed.

[0081] Next, the embodiments corresponding to the above build request will be schematically described through Figure 4 as follows. As shown in Figure 4 , it can include the following steps:

[0082] S410: Receive the user request.

[0083] Among them, the user request is a build request.

[0084] S420: Process the user request.

[0085] Among them, the processing process is to obtain the target application identifier from the user request, and the target application identifier is the program identifier of the target application.

[0086] S430: Determine whether the target application identifier exists in the multi-repository relationship table.

[0087] If it exists, go to step S440; if it does not exist, go to step S490.

[0088] S440: Obtain multiple remote code repositories corresponding to the target application identifier.

[0089] S450: Pass the multiple remote code repositories corresponding to the target application identifier into the repo framework.

[0090] S460: The repo framework performs local deployment of multiple remote code repositories.

[0091] Among them, the specific content of the environment deployment involved in the above S420 - S460 can refer to Figure 1 the embodiments shown, and will not be elaborated here.

[0092] S470: Match the preset compilation parameters corresponding to the target application.

[0093] S480: Call the target build framework for automated compilation according to the preset compilation parameters.

[0094] S490: End the compilation.

[0095] In this embodiment, the complexity of maintenance work is reduced through centralized configuration information management, the error rate is decreased, making the relationship between each application and the corresponding remote code repository easier to manage and maintain. At the same time, through the automated build process, the consistency of the development environment is ensured, compatibility issues caused by environmental differences are reduced, and manual operations are decreased, improving the build efficiency.

[0096] As Figure 5 shown, the embodiment of the present application further provides a version control and build environment management system, including: a request submission module 510, a deployment request processing module 520, a release request processing module 530, a build request processing module 540, a multi-repository deployment module 550, a release module 560, and a build module 570.

[0097] Among them, when the user submits a deployment request through the request submission module 510, the deployment request processing module 520 will parse the user's request and accordingly call the multi-repository deployment module 550 to obtain multiple independent code repositories corresponding to the target application according to the content required by the user, and based on the relationship table between repositories recorded in the configuration management module, call the repo multi-repository management framework to deploy to the local, so as to achieve precise deployment of the environment. If the user submits a release request through the request submission module 510, the release request processing module 530 will parse the request. After the command parsing is completed, it will first call the multi-repository deployment module 550 to deploy multiple independent code repositories to the local according to the relationship table between repositories recorded in the configuration management module according to the content of the user's request, and then call the release module 560 to enter the release process. In this call to the release module 560, according to the content of the user's request, by implementing steps such as unified tagging, version switching, packaging, or patch generation of multiple independent repositories, a file package to be released will be finally generated. If the user submits a build request through the request submission module 510, the build request processing module 540 will parse the user's build request, call the multi-repository deployment module 550 to deploy the build environment first, and then call the build module 570 to perform a build according to the content of the user's request, thereby generating a build product.

[0098] In this embodiment, through an automated environment deployment and construction process, the consistency of the development environment is ensured, compatibility issues caused by environmental differences are reduced, and the integration efficiency between different modules is improved; moreover, through automated dependency management and environment configuration, the need for manual operations is significantly reduced, and the development cycle is shortened; moreover, through centralized configuration information management, the complexity of maintenance work is reduced, the error rate is decreased, and the system is made easier to manage and maintain; moreover, through a centralized security management mechanism, it helps to protect sensitive information, prevent unauthorized access, and enhance the security of the entire system; moreover, through automated label creation and version control functions, the latest code can be quickly deployed to the production environment, shortening the time to resolve security vulnerabilities and performance issues; moreover, through a centralized management framework, the problem tracking and debugging process across repositories is simplified, and the efficiency of problem solving is improved; moreover, through a design that supports parallel management and independent configuration of multiple applications, the system can flexibly adapt to new technologies and market changes and has high scalability.

[0099] As Figure 6 shown, an embodiment of the present application further provides an electronic device 600, including a processor 610 and a memory 620. A program or instruction that can run on the processor 610 is stored on the memory 620. When the program or instruction is executed by the processor 610, it implements the above Figures 1 to 5 shown embodiment processes, and can achieve the same technical effects. To avoid repetition, it will not be elaborated here.

[0100] An embodiment of the present application further provides a readable storage medium. A program or instruction is stored on the readable storage medium. When the program or instruction is executed by a processor, it implements the above Figures 1 to 5 shown embodiment processes, and can achieve the same technical effects. To avoid repetition, it will not be elaborated here.

[0101] Among them, the processor is the processor in the terminal described in the above embodiment. The readable storage medium includes computer-readable storage media, such as computer read-only memory ROM, random access memory RAM, magnetic disks, or optical discs, etc. In some examples, the readable storage medium can be a non-transitory readable storage medium.

[0102] Another embodiment of the present application provides a chip. The chip includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run a program or instruction to implement the above Figures 1 to 5 shown embodiment processes, and can achieve the same technical effects. To avoid repetition, it will not be elaborated here.

[0103] It should be understood that the chip mentioned in the embodiment of the present application can also be referred to as a system-on-chip, system chip, chip system, or system-on-chip.

[0104] Another embodiment of the present application provides a computer program / program product. The computer program / program product is stored in a storage medium and is executed by at least one processor to implement the above Figures 1 to 5 each process of the illustrated embodiment, and can achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0105] It should be noted that in this article, the term "including", "comprising" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed, or further includes elements inherent to such process, method, article or device. Without more limitations, the element defined by the statement "including one..." does not exclude the existence of additional identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in a reverse order according to the functions involved. For example, the described methods may be performed in an order different from that described, and various steps may be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0106] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-described embodiment methods can be implemented by means of a computer software product plus a necessary general hardware platform, and of course, can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disc, etc.) and includes several instructions for causing a terminal or a network-side device to execute the methods described in various embodiments of the present application.

[0107] The embodiments of the present application have been described above in conjunction with the accompanying drawings. However, the present application is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not restrictive. Under the inspiration of the present application, those of ordinary skill in the art can also make many forms of embodiments without departing from the purpose of the present application and the scope protected by the claims. These embodiments are all within the protection scope of the present application.

Claims

1. An environmental automatic deployment method, characterized in that, The method includes: Receiving an environment deployment request, where the environment deployment request is used to request the deployment of the running environment of a target application; Obtaining multiple remote code repositories corresponding to the target application from a multi-repository relationship table included in a management configuration file; Performing automated environment deployment by calling a target framework according to the multiple remote code repositories.

2. The method according to claim 1, wherein After performing the automated environment deployment by calling the target framework, the method further includes: When receiving a release request for the target application, obtaining a target version number and a target release method corresponding to the target application from the release request; Generating a to-be-released file package according to the release method, where the package name of the to-be-released file package is composed of the target version number.

3. The method according to claim 2, wherein After obtaining the target version number and the target release method corresponding to the target application from the release request, the method further includes: Obtaining multiple remote code repositories corresponding to the target application from the multi-repository relationship table; Calling the target framework to execute a target command, where the target command is used to add a target version number label to each of the remote code repositories, and the target version number label is used to uniquely identify the target version corresponding to the target application in the multiple remote code repositories.

4. The method according to claim 3, wherein When the release method includes source code release, generating the to-be-released file package according to the release method includes: Obtaining source code files corresponding to the target version number label from the multiple remote code repositories; Packaging the source code files according to the local path relationship of the multiple remote code repositories to obtain the to-be-released file package.

5. The method according to claim 3, characterized in that When the release method includes patch release, generating the to-be-released file package according to the release method includes: Generating a code difference patch from the target version number label to a historical version number label, where the historical version number label is the version number label of the previous version corresponding to the target application; Packaging the code difference patch according to the local path relationship of the multiple remote code repositories to obtain the to-be-released file package.

6. The method according to claim 1, wherein The management configuration file further includes a compilation dependency file; After performing the automated environment deployment by calling the target framework according to the multiple remote code repositories, the method further includes: When receiving a build request for the target application, obtaining preset compilation parameters corresponding to the target application from the compilation dependency file, where the build request is used to request the compilation of the target application; Performing automated compilation by calling a target build framework according to the preset compilation parameters.

7. The method according to claim 1, wherein The method further includes: When unable to obtain multiple remote code repositories corresponding to the target application from the multi-repository relationship table, outputting a prompt message for rejecting the environment deployment request.

8. An electronic device, characterized in that, It includes a processor, a memory, and programs or instructions stored on the memory and executable on the processor. When the programs or instructions are executed by the processor, the steps of the environment automatic deployment method according to any one of claims 1-7 are implemented.

9. A readable storage medium, characterized in that, Programs or instructions are stored on the readable storage medium. When the programs or instructions are executed by the processor, the steps of the environment automatic deployment method according to any one of claims 1-7 are implemented.

10. A computer program product, the computer program product includes a computer program stored on a non-transitory computer-readable storage medium, the computer program includes program instructions, when the program instructions are executed by a computer, the computer is caused to implement the steps of the environment automatic deployment method according to any one of claims 1-7 when executed.

Images