Application program deployment method and device, equipment, storage medium and product

By pre-configured deployment tools, signature certificates and description files independent of the development environment, updating parameter definition files and generating packaged files, the deployment difficulties of applications in different user environments are solved and development efficiency is improved.

CN119025124APending Publication Date: 2024-11-26CHINA CONSTRUCTION BANK +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411099625.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-12
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

During application development, the same set of code is difficult to deploy due to environmental changes in different user environments, which affects development efficiency.

Method used

The pre-configured deployment tool obtains the program code of the target application, determines the packaging information, and updates the parameter definition file based on the signature certificate and description file, generates the packaging file, and finally uploads it to the distribution platform for deployment, independent of the development environment.

Benefits of technology

It realizes rapid and simple deployment of applications, improves development efficiency, and solves the problems of deployment difficulties and inefficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119025124A_ABST
    Figure CN119025124A_ABST
Patent Text Reader

Abstract

The invention discloses an application program deployment method and device, equipment, a storage medium and a product. The invention relates to the technical field of computers. The method comprises the steps of obtaining a program code of a target application program, and determining packaging information of the target application program according to the program code; the deployment tool is separated from the development environment of the application program; respectively determining a target parameter and an analysis parameter matched with the target application program; updating a parameter definition file matched with the target application program according to the target parameter and the packaging information to obtain a target parameter definition file; packaging the target application program according to the target parameter definition file and each analysis parameter to obtain a packaged file; and uploading the packaged file to a distribution platform so as to deploy the target application program. According to the technical scheme, the problems that the application program is difficult to deploy and low in development efficiency are solved, the application program can be deployed quickly, simply and conveniently, and the development efficiency of the application program is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of computer technology, and in particular to a method, device, equipment, storage medium and product for deploying an application. Background Art

[0002] With the rapid development of computer technology, people's lives are increasingly dependent on mobile devices. As user needs increase, the development of applications (Application, App) also increases.

[0003] At present, in the process of application development, developers need to develop in the local environment, obtain the local dependent network and signature certificate during the building and packaging process, and then compile the code and sign and package it. In this process, the packaging process is heavily dependent on the developer's local environment. The same set of code may not be packaged and built in other user environments due to environmental changes. This not only makes it difficult to deploy the application, but also greatly affects the development efficiency. Summary of the invention

[0004] The embodiments of the present invention provide a method, apparatus, device, storage medium and product for deploying an application program, so as to solve the problems of difficult deployment of an application program and low development efficiency. The application program can be deployed quickly and easily, thereby greatly improving the development efficiency of the application program.

[0005] In a first aspect, an embodiment of the present invention provides a method for deploying an application program, the method comprising:

[0006] Acquiring the program code of the target application through a pre-configured deployment tool, and determining the packaging information of the target application according to the program code; the deployment tool is separated from the development environment of the application;

[0007] Determine the target parameters and parsing parameters that match the target application program respectively through the signature certificates and description files in the deployment tool;

[0008] Update the parameter definition file matching the target application according to the target parameter and the packaging information to obtain a target parameter definition file;

[0009] Packaging the target application according to the target parameter definition file and each of the parsing parameters to obtain a packaged file;

[0010] In response to the deployment instruction of the target application, the packaged file is uploaded to the distribution platform to deploy the target application.

[0011] In an optional implementation of this embodiment, the deployment tool is configured through the following steps:

[0012] Build the application deployment environment on the target server;

[0013] Determine at least one parameter definition file; the parameter definition file includes at least one of the following configuration information: project name, project workspace name, plan name, project unique identifier, attribute information of the distribution platform, hardening configuration file path, scan report template name, and scan vulnerability file name;

[0014] Acquire multiple signature certificates and description files, and store each of the signature certificates and each of the description files in a preset area; the signature certificates correspond to the description files one by one;

[0015] A security hardening tool and a code scanning tool are obtained, and the security hardening tool and the code scanning tool are authorized.

[0016] In an optional implementation of this embodiment, after storing each of the signature certificates and each of the description files in a preset area, the method further includes:

[0017] Determine the export options corresponding to the configuration files matching the description files, so as to export the deployed applications on demand;

[0018] The export options include at least one of: app store, development, enterprise, and temporary use.

[0019] In an optional implementation of this embodiment, determining the packaging information of the target application according to the program code includes:

[0020] Detecting the program code and determining the packaging information according to the detection result;

[0021] The packaging information includes at least one of the following: project name, code branch, code identifier, and packaging purpose.

[0022] In an optional implementation of this embodiment, after determining the packaging information according to the detection result, the method further includes:

[0023] Verify the packaging information;

[0024] If the packaging information verification fails, the deployment of the target application is stopped.

[0025] In an optional implementation of this embodiment, determining the target parameters and parsing parameters matching the target application program respectively through the signature certificates and description files in the deployment tool includes:

[0026] Parse the signature certificate and description file to obtain various reference parameters;

[0027] The reference parameters are screened to obtain the target parameters and analytical parameters respectively.

[0028] In an optional implementation of this embodiment, updating the parameter definition file matching the target application according to the target parameter and the packaging information to obtain the target parameter definition file includes:

[0029] Each of the target parameters and each of the packaging information is added to a parameter definition file that matches the target application program, to obtain a target parameter definition file that matches the target application program.

[0030] In an optional implementation of this embodiment, the target application is packaged according to the target parameter definition file and each parsed parameter value to obtain a packaged file, including:

[0031] Loading the target parameter definition file, and determining the first parameter in the target parameter definition file;

[0032] Obtaining values ​​of the first parameter and the parsing parameter;

[0033] Execute the preset script commands in sequence to obtain the packaged file.

[0034] In an optional implementation of this embodiment, after obtaining the packaged file, the method further includes:

[0035] In response to the security hardening instruction for the packaged file, the target parameter definition file is loaded, and a loading path of the security hardening configuration file is obtained;

[0036] The security reinforcement tool performs security reinforcement on the packaged file based on the loading path, and writes the reinforcement result into the reinforcement status detection file.

[0037] In an optional implementation of this embodiment, after writing the reinforcement result into the reinforcement status detection file, the method further includes:

[0038] In response to the reinforcement result detection instruction, obtaining the reinforcement status in the reinforcement status detection file;

[0039] If the reinforcement status meets the preset conditions, it is determined that the security reinforcement of the packaged file is successful;

[0040] Otherwise, continue to perform the security hardening operation on the packaged file.

[0041] In an optional implementation of this embodiment, after obtaining the packaged file, the method further includes:

[0042] In response to a code scanning instruction for the packaged file, a target operation is performed on the packaged file by a code scanning tool to complete a security scan of the packaged file;

[0043] The target operation includes at least one of the following: cache cleaning, compilation, code scanning, and code scanning report generation.

[0044] In an optional implementation of this embodiment, the uploading of the packaged file to the distribution platform in response to the deployment instruction of the target application includes:

[0045] Read the target parameter definition file to obtain relevant parameter information;

[0046] Upload the relevant parameter information and the packaged file to the distribution platform;

[0047] Receive the deployment result fed back by the distribution platform and the download link of the target application.

[0048] In a second aspect, an embodiment of the present invention further provides a device for deploying an application program, the device comprising:

[0049] A packaging information acquisition module, used to acquire the program code of the target application through a pre-configured deployment tool, and determine the packaging information of the target application according to the program code; the deployment tool is separated from the development environment of the application;

[0050] A parameter determination module, which determines target parameters and parsing parameters that match the target application program through each signature certificate and description file in the deployment tool;

[0051] A target parameter definition file determination module, used to update a parameter definition file matching the target application according to the target parameter and the packaging information to obtain a target parameter definition file;

[0052] A package file determination module, used for packaging the target application according to the target parameter definition file and each of the parsing parameters to obtain a package file;

[0053] The deployment module is used to upload the packaged file to the distribution platform in response to the deployment instruction of the target application to deploy the target application.

[0054] In a third aspect, an embodiment of the present invention further provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, a method for deploying an application as described in any one of the embodiments of the present invention is implemented.

[0055] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements a method for deploying an application as described in any one of the embodiments of the present invention.

[0056] In a fifth aspect, an embodiment of the present invention further provides a computer program product, including a computer program, which, when executed by a processor, implements a method for deploying an application as described in any one of the embodiments of the present invention.

[0057] In an embodiment of the present invention, a program code of a target application is obtained through a preconfigured deployment tool, and packaging information of the target application is determined based on the program code; target parameters and parsing parameters matching the target application are respectively determined through each signature certificate and description file in the deployment tool; a parameter definition file matching the target application is updated based on the target parameters and the packaging information to obtain a target parameter definition file; the target application is packaged based on the target parameter definition file and each of the parsing parameters to obtain a packaged file; in response to a deployment instruction of the target application, the packaged file is uploaded to a distribution platform to deploy the target application, thereby solving the problems of difficult deployment of applications and low development efficiency, allowing applications to be deployed quickly and easily, and greatly improving the development efficiency of applications.

[0058] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for use in the embodiments are briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without creative work.

[0060] Figure 1 is a flow chart of a method for deploying an application program provided according to an embodiment of the present invention;

[0061] Figure 2is a schematic diagram of a deployment process of a deployment tool provided according to an embodiment of the present invention;

[0062] Figure 3 is a flow chart of another application deployment method provided according to an embodiment of the present invention;

[0063] Figure 4 is a flowchart of another application deployment method provided according to an embodiment of the present invention

[0064] Figure 5 is a schematic diagram of the structure of a deployment device for an application program provided according to an embodiment of the present invention;

[0065] Figure 6 It is a structural diagram of an electronic device for implementing the application deployment method of an embodiment of the present invention. DETAILED DESCRIPTION

[0066] The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the present invention, rather than to limit the present invention. It should also be noted that, for ease of description, only parts related to the present invention, rather than all structures, are shown in the accompanying drawings.

[0067] It should be noted that similar numbers and letters represent similar items in the following figures. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. At the same time, in the description of the present invention, the terms "first", "second", etc. are only used to distinguish the description and cannot be understood as indicating or implying relative importance. The acquisition, storage, use, processing, etc. of data in the technical solution of this application comply with the relevant provisions of national laws and regulations. It should be noted that in the embodiments of this application, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. The purpose is only to illustrate the feasibility of the implementation of the technical solution of this application, but it does not mean that the applicant has or must use the relevant content of the solution.

[0068] Figure 1 This is a flow chart of a method for deploying an application program according to an embodiment of the present invention. This embodiment is applicable to the case where an application program is packaged and deployed using a deployment tool independent of a development environment. The method can be executed by an application program deployment device, which can be implemented in the form of hardware and / or software. The application program deployment device can be configured in electronic devices such as tablet computers, computers, or servers. Figure 1 As shown, the method includes:

[0069] Step 110: Obtain the program code of the target application through a pre-configured deployment tool, and determine the packaging information of the target application according to the program code.

[0070] Among them, the deployment tool is separated from the development environment of the application; that is, the deployment tool involved in this embodiment is deployed in a device that is not used to develop the application; illustratively, application A can be developed by computer A, and the deployment tool can be configured in computer B, that is, application A can be deployed by computer B.

[0071] It should be noted that the application involved in this embodiment may be an application developed through IOS (iPhone Operating System, a mobile operating system developed by Apple Inc.). The target application involved in this embodiment may be any application that has been developed and is to be packaged and deployed, such as a reading application, a shopping application, or a financial application, which is not limited in this embodiment.

[0072] In an optional implementation of this embodiment, after receiving a packaging instruction for the target application, the program code of the target application can be obtained through a pre-configured deployment tool, wherein the program code of the target application can be stored in different folders, and further, the packaging information of the target application contained in the obtained program code can be obtained.

[0073] The packaging information may include at least one of the following: project name, code branch, code identifier, and packaging purpose, etc., which are not limited in this embodiment.

[0074] Optionally, in this embodiment, determining the packaging information of the target application according to the program code may include: detecting the program code, and determining the packaging information according to the detection result.

[0075] In an optional implementation of this embodiment, after obtaining the program code of the target application, the obtained program code can be detected. For example, keywords, related folders or configuration files in the program code can be detected. Furthermore, the packaging information of the target application can be determined based on the detection results.

[0076] In an example of this embodiment, after obtaining the program code of application B, the configuration file in the program code can be obtained, and the key information in the configuration file, such as the program name or program function, can be traversed. Further, the packaging information of application B can be determined based on the key information obtained through the traversal.

[0077] The advantage of this setting is that the packaging information of the target application can be quickly determined, providing a basis for the subsequent packaging and deployment of the target application.

[0078] In an optional implementation of this embodiment, after determining the packaging information according to the detection result, it may also include: verifying the packaging information; if the packaging information verification fails, stopping the deployment of the target application.

[0079] Optionally, in this embodiment, after obtaining the packaging information of the target application, the packaging information of the target application can also be verified. For example, a code branch can be selected or the code can be pulled, and the pulled information can be compared with the value of the code identifier (commitID) string in the packaging information to ensure the consistency of the code. If the comparison is consistent, the verification is passed and the next step is continued; if the comparison is inconsistent, the verification fails and the deployment of the target application is stopped. The advantage of this setting is that it can ensure the effective deployment of the target application.

[0080] It should be noted that in this embodiment, the packaging information can also be verified by other methods, which are not limited in this embodiment.

[0081] Step 120: Determine target parameters and parsing parameters that match the target application program through the signature certificates and description files in the deployment tool.

[0082] It should be noted that the target parameters and parsing parameters are parameters contained in the signature certificates and description files deployed in the deployment tool. Different types of parameters in this embodiment are named separately, which is only for the purpose of explaining this embodiment and is not a limitation of this embodiment.

[0083] The signing certificate can be a P12 certificate, which is a digital certificate used for application signing and verification. It usually contains the developer's private key, public key, and other authentication information. Developers can use P12 certificates to sign their applications to ensure the integrity and credibility of the applications.

[0084] In iOS development, a provisioning profile is a security file used to manage and distribute iOS applications. The profile contains the application's signature information, device authorization information, and developer or enterprise identity authentication information. Developers need to create and manage profiles through the Developer Center, and then use them with Xcode development tools or other development tools to ensure that the application can run and be tested smoothly on iOS devices. Different types of profiles are suitable for different development and distribution needs, such as development testing, internal testing, and app store releases.

[0085] In this embodiment, the target parameters may include at least one of the following: the file path of the signing certificate (p12_file_path), the SHA1 value of the signing certificate, the description file type, the file path of the description file, the unique identifier (UUID) of the description file, etc.; the parsing parameters may include at least one of the following: CODE_SIGN_IDENTITY, PROVISIONING_PROFILE_SPECIFIER and DEVELOPMENT_TEAM, etc., which are not limited in this embodiment.

[0086] In this embodiment, during the configuration process in the deployment tool, multiple signature certificates and description files are deployed, and the signature certificates and description files are matched one by one, that is, one signature certificate corresponds to one description file.

[0087] In an optional implementation of this embodiment, after obtaining the program code of the target application, the signature certificate and description file that match the target application can be determined first, and further, the target parameters and parsing parameters that match the target application can be determined based on the signature certificate and description file.

[0088] Optionally, in this embodiment, after determining that a signing certificate and a description file that match the target application are obtained, the signing certificate and the description file can be parsed separately to determine specific information of parameters such as the file path of the signing certificate, the SHA1 value of the signing certificate, the description file type, the file path of the description file, and the unique identifier of the description file, and these parameters can be determined as target parameters that match the target application; further, specific information of parameters such as CODE_SIGN_IDENTITY, PROVISIONING_PROFILE_SPECIFIER, and DEVELOPMENT_TEAM can also be determined, and these parameters can be determined as parsing parameters.

[0089] Step 130: Update the parameter definition file matching the target application according to the target parameters and the packaging information to obtain a target parameter definition file.

[0090] In an optional implementation of this embodiment, after determining to obtain target parameters matching the target application, the parameter definition file of the target application may be updated according to the packaging information of the target application and the target parameters, thereby obtaining the target parameter definition file.

[0091] It is understandable that the target application may include multiple parameter definition files, for example, it may include aaa parameter definition.sh, bbb parameter definition.sh or ccc parameter definition.sh, etc., where "aaa", "bbb" and "ccc" represent different parameters, which are not limited in this embodiment.

[0092] Optionally, in this embodiment, updating the parameter definition file that matches the target application according to the target parameters and the packaging information to obtain the target parameter definition file may include: adding each of the target parameters and each of the packaging information to the parameter definition file that matches the target application, to obtain the target parameter definition file that matches the target application.

[0093] In an optional implementation of this embodiment, the target parameters and packaging information may be added to each parameter definition file respectively, and each parameter definition file may be updated to obtain a target parameter definition file that matches the target application.

[0094] Furthermore, you can also update the values ​​of the provisioningProfiles, signingCertificate, and teamID fields in the configuration file ExportOptions.plist; set the SHA1 value of the signing certificate P12 and the UUID of the description file to the project's engineering file; install the signing certificate P12 to the computer's keychain and set access permissions; store the description file in the computer's preset path, for example, ~ / Library / MobileDevice / ProvisioningProfiles.

[0095] The advantage of this setting is that the parameter definition file can be updated quickly, providing a basis for subsequent packaging of the application.

[0096] Step 140: Pack the target application according to the target parameter definition file and each of the parsing parameters to obtain a packaged file.

[0097] In an optional implementation of this embodiment, after obtaining the target parameter definition file of the target application, the target application may be further packaged according to the target parameter definition file of the target application and various parsing parameters to obtain a packaged file of the target application.

[0098] Optionally, in this embodiment, the target application is packaged according to the target parameter definition file and each parsing parameter value to obtain a packaged file, which may include: loading the target parameter definition file, determining the first parameter in the target parameter definition file; obtaining the values ​​of the first parameter and the parsing parameter; and sequentially executing preset script commands to obtain the packaged file.

[0099] The first parameter includes at least one of the following: workspace, scheme, configuration, exportOptionsPlist, and archivePath, etc., which are not limited in this embodiment. The parsing parameters may be CODE_SIGN_IDENTITY, PROVISIONING_PROFILE_SPECIFIER, and DEVELOPMENT_TEAM, etc., which are not limited in this embodiment. The preset script command may be xcodebuildclean, xcodebuild archive, and xcodebuild exportArchive provided by the command line tool xcodebuild, which are not limited in this embodiment.

[0100] It should be noted that the values ​​of the first parameter and the parsing parameters may be specific information of parameters such as workspace, scheme, configuration, exportOptionsPlist, archivePath, CODE_SIGN_IDENTITY, PROVISIONING_PROFILE_SPECIFIER, DEVELOPMENT_TEAM, etc., which are not numerical values ​​in the mathematical sense and are not a limitation of this embodiment.

[0101] During the process of this embodiment, the target parameter definition file can be loaded to obtain the values ​​of parameters such as workspace, scheme, configuration (the default is Release), exportOptionsPlist and archivePath; the values ​​of parameters such as CODE_SIGN_IDENTITY, PROVISIONING_PROFILE_SPECIFIER and DEVELOPMENT_TEAM after the signing certificate and description file are parsed are obtained; and the command line tool xcodebuild provided by the system is used to execute xcodebuild clean, xcodebuild archive, and xcodebuild exportArchive in sequence to complete the packaging and building of the target application.

[0102] Step 150: In response to the deployment instruction of the target application, upload the packaged file to a distribution platform to deploy the target application.

[0103] In an optional implementation of this embodiment, after the target application is packaged, if a deployment instruction for the target application is received, the packaged target application can be uploaded to a distribution platform, so that the target application can be distributed and deployed through the distribution platform.

[0104] In this embodiment, after receiving the deployment instruction for the target application, the target parameter definition file of the target application can be loaded, and the values ​​of parameters such as UPLOAD_IPA_PATH, UPLOAD_APP_KEY and PRODUCT_NAME in the target parameter definition file can be obtained; the program package is uploaded to the distribution platform; in this embodiment, the distribution platform can be a commercial distribution platform, or a distribution server can be built; further, the download address can be provided to the business end, or the deployment result can be notified in real time by email or other means.

[0105] The technical solution of this embodiment obtains the program code of the target application through a preconfigured deployment tool, and determines the packaging information of the target application according to the program code; determines the target parameters and parsing parameters matching the target application respectively through the signature certificates and description files in the deployment tool; updates the parameter definition file matching the target application according to the target parameters and the packaging information to obtain the target parameter definition file; packages the target application according to the target parameter definition file and each of the parsing parameters to obtain a packaging file; and in response to the deployment instruction of the target application, uploads the packaging file to the distribution platform to deploy the target application, thereby solving the problems of difficult deployment of applications and low development efficiency, and can quickly and easily deploy applications, greatly improving the development efficiency of applications.

[0106] In order to better understand the deployment tools of the application programs involved in this embodiment, Figure 2 is a schematic diagram of a deployment process of a deployment tool provided according to an embodiment of the present invention, such as Figure 2 As shown, the deployment tool is configured through the following steps:

[0107] Step 210: Building a deployment environment for the application on the target server.

[0108] The target server may be any electronic device or virtual machine for which application programs have not been developed, and is not limited in this embodiment.

[0109] In an example of this embodiment, the deployment environment of the application program on the target server can be: on a separate computer, install the development tool Xcode, successfully compile the project, and complete the manual packaging and building; download and install Tomcat, and execute sh startup.sh in the bin directory of Tomcat to start Tomcat; download Jenkins, and deploy the war package jenkins.war to the webapps directory of Tomcat, change its port to 8001, and visit http: / / 127.0.0.1:8001 / jenkins / ; if the login page of Jenkins can be successfully displayed, it means that the deployment environment has been downloaded successfully.

[0110] It should be noted that Jenkins is an open source, extensible web-based platform for continuous integration, delivery, and deployment. It allows continuous integration and continuous delivery of projects, regardless of the platform used, and can handle any type of build or continuous integration. After the code is submitted to the repository, Jenkins can automatically deploy the latest code in the code repository, eliminating the need for manual packaging and uploading to the server for deployment.

[0111] Step 220: Determine at least one parameter definition file.

[0112] The parameter definition file includes at least one of the following configuration information: project name, project workspace name, plan name, project unique identifier, attribute information of the distribution platform, reinforcement configuration file path, scan report template name, and scan vulnerability file name.

[0113] In this embodiment, parameter definition files can be configured for multiple projects (applications). These parameter definition files only contain entries of various configuration information, such as project name, project workspace name, plan name, project unique identifier, distribution platform attribute information, reinforcement configuration file path, scan report template name, and scan vulnerability file name. These entries can be filled in during the deployment process of the application. Please refer to other embodiments, and they will not be repeated in this embodiment.

[0114] Step 230: Acquire multiple signature certificates and description files, and store each signature certificate and each description file in a preset area.

[0115] The signing certificate corresponds to the description file one by one, that is, the signing certificate and the description file are matched one by one and need to be used together. The advantage of this setting is that it can ensure the successful signing of the application package.

[0116] In this embodiment, the signature certificate and description file can be downloaded from the development background of the application or other websites, and the downloaded signature certificate and description file can be stored in the corresponding directory of the computer. This directory is the preset area involved in this implementation, which can be any path in the computer and is not limited in this embodiment.

[0117] In an optional implementation of this embodiment, after storing each of the signing certificates and each of the description files in a preset area, it may also include: determining an export option corresponding to a configuration file matching each of the description files; so as to export each deployed application on demand; the export option includes at least one of the following: application store, development, enterprise, and temporary use.

[0118] Optionally, in this embodiment, the configuration files corresponding to different description files can be processed separately according to the timing of each application: illustratively, the export option corresponding to ExportOptions.plist can be application store (app-store); the export option corresponding to DevExportOptions.plist can be development (development); the export option corresponding to AdHocExportOptions.plist can be enterprise (ad-hoc); and the export option corresponding to EnterpriseExportOptions.plist can be temporary use (enterprise).

[0119] The advantage of this setting is that it can export on demand according to different applications, which can meet the different packaging needs of users.

[0120] Step 240: Obtain a security hardening tool and a code scanning tool, and authorize the security hardening tool and the code scanning tool.

[0121] Optionally, in this embodiment, the application deployment tool can also be configured for security hardening and code scanning; in this embodiment, the security hardening tool and the code scanning tool can be downloaded and authorized so that the application code can be subsequently security hardened and scanned during the application deployment process.

[0122] In an optional implementation of this embodiment, a security hardening tool can be obtained and installed in the calculation of the configuration and deployment tool, and an authorization file license can be imported to authorize the security hardening tool; further, hardening strategies and filtering rules for files that do not require hardening can be configured according to the actual situation of each project, and all configuration items can be written as an extensible markup language (xml) file.

[0123] In another optional implementation of this embodiment, a code scanning tool can be obtained and installed in the calculation of the configuration and deployment tool, and the code scanning tool can be authorized for use; further, scanning rules and vulnerability filtering files can be configured according to the template provided by the scanning tool based on the actual situation and development language of each project.

[0124] The solution of this embodiment, by building a deployment environment for the application on the target server; determining at least one parameter definition file; obtaining multiple signature certificates and description files, and storing each signature certificate and each description file in a preset area; obtaining a security hardening tool and a code scanning tool, and authorizing the security hardening tool and the code scanning tool, can configure the deployment tool for deploying the application in a non-development environment, providing a basis for independent deployment of the application.

[0125] Figure 3 1 is a flow chart of another application deployment method provided according to an embodiment of the present invention. This embodiment is a further refinement of the above technical solution. The technical solution in this embodiment can be combined with each optional solution in one or more of the above embodiments. Figure 3 As shown, the method includes:

[0126] Step 310: Obtain the program code of the target application through a pre-configured deployment tool, and determine the packaging information of the target application according to the program code.

[0127] Step 320: parse the signature certificate and the description file to obtain various reference parameters; filter each of the reference parameters to obtain the target parameters and parsing parameters respectively.

[0128] The reference parameters are all parameters obtained by parsing the signature certificate and the description file, which include both the target parameters involved in this embodiment and the parsing parameters.

[0129] In an optional implementation of the present embodiment, the signing certificate and the description file may be parsed to obtain reference parameters. Exemplarily, the obtained reference parameters may be: the file path (p12_file_path) of the signing certificate, the SHA1 value of the signing certificate, the description file type, the file path of the description file, the unique identifier (UUID) of the description file, CODE_SIGN_IDENTITY, PROVISIONING_PROFILE_SPECIFIER, and DEVELOPMENT_TEAM; further, the reference parameters obtained by the parsing may be screened, for example, they may be classified according to the attributes of each reference parameter to obtain the target parameters: the file path (p12_file_path) of the signing certificate, the SHA1 value of the signing certificate, the description file type, the file path of the description file, the unique identifier (UUID) of the description file; and, parsed parameters: CODE_SIGN_IDENTITY, PROVISIONING_PROFILE_SPECIFIER, and DEVELOPMENT_TEAM.

[0130] The advantage of this setting is that the target parameters and parsing parameters can be quickly determined, providing a basis for the subsequent packaging and deployment of the application.

[0131] Step 330: Update the parameter definition file that matches the target application according to the target parameters and the packaging information to obtain a target parameter definition file.

[0132] Step 340: Pack the target application according to the target parameter definition file and each of the parsing parameters to obtain a packaged file.

[0133] Step 350: In response to the security hardening instruction for the packaged file, the target parameter definition file is loaded, and the loading path of the security hardening configuration file is obtained; the security hardening tool performs security hardening on the packaged file based on the loading path, and writes the hardening result into the hardening status detection file.

[0134] In an optional implementation of the present embodiment, after obtaining the packaged file of the target application, if a security hardening instruction for the packaged file is received, the target parameter definition file of the target application can be obtained, the target parameter definition file can be parsed, and the loading path of the security hardening configuration file recorded in the target parameter definition file can be determined; further, the security hardening tool pre-deployed by the deployment tool can perform security hardening on the packaged file based on the loading path of the security hardening configuration file in the target parameter definition file, for example, using the command line calling method of the security hardening tool, passing in the loading path, and executing the hardening; further, the hardening result, i.e., the hardening status, can be written into the detection file; wherein the hardening result can be successful hardening, or unsuccessful hardening.

[0135] Optionally, in this embodiment, after the reinforcement result is written into the reinforcement status detection file, it may also include: in response to the reinforcement result detection instruction, obtaining the reinforcement status in the reinforcement status detection file; if the reinforcement status meets the preset conditions, determining that the security reinforcement of the packaged file is successful; otherwise, continuing to perform the security reinforcement operation on the packaged file.

[0136] The preset condition may be reinforcement success, or may be other forms, such as "1" (where 1 represents reinforcement success), which is not limited in this embodiment.

[0137] In an optional implementation of the present embodiment, after the security hardening tool writes the hardening result to the hardening status detection file, if it receives a hardening result detection instruction, it can obtain the hardening status in the hardening status detection file; if the hardening status meets the preset conditions, it can be determined that the security hardening of the packaged file is successful; otherwise, continue to perform the security hardening operation on the packaged file until the detection result meets the preset conditions.

[0138] In another optional implementation of this embodiment, after the security hardening tool writes the hardening results to the hardening status detection file, it can immediately detect the security hardening results to determine whether the hardening is successful; if successful, the next step can be performed; otherwise, the security hardening operation on the packaged file continues until the detection result meets the preset conditions.

[0139] The advantage of this setting is that it can ensure the security reinforcement of the packaged files, prevent the situation where the packaged files are not reinforced due to unsuccessful security reinforcement, and improve the security of the application.

[0140] Step 360: In response to the deployment instruction of the target application, upload the packaged file to the distribution platform to deploy the target application.

[0141] In an optional implementation of this embodiment, in response to the deployment instruction of the target application, uploading the packaged file to the distribution platform may include: reading the target parameter definition file to obtain each relevant parameter information; uploading each relevant parameter information and the packaged file to the distribution platform; receiving the deployment result fed back by the distribution platform, as well as the download link of the target application.

[0142] The relevant parameters may be UPLOAD_IPA_PATH, UPLOAD_APP_KEY, PRODUCT_NAME, etc.; the relevant parameter information is the specific content information of these relevant parameters. The form and content of the relevant parameter information are not limited in this embodiment.

[0143] Optionally, in this embodiment, after receiving the deployment instruction for the target application, the content information of parameters such as UPLOAD_IPA_PATH, UPLOAD_APP_KEY and PRODUCT_NAME of the target parameter definition file of the target application can be obtained; further, these parameter information and the packaged file can be sent to the distribution platform, so that the distribution platform deploys the target application according to the received parameter information and packaged file, and feeds back the deployment result to the deployment tool; further, the download link of the target application can be determined according to the fedback deployment result, and further, the download link can be provided to the business user.

[0144] The advantage of this setting is that the target application can be deployed quickly, improving the deployment efficiency of the application.

[0145] The solution of this embodiment, after obtaining the packaged file of the target application, if a security hardening instruction for the packaged file is received, the target parameter definition file of the target application can be obtained, the target parameter definition file can be parsed, and the loading path of the security hardening configuration file recorded in the target parameter definition file can be determined; further, the security hardening tool pre-deployed by the deployment tool can perform security hardening on the packaged file based on the loading path of the security hardening configuration file in the target parameter definition file, thereby realizing security hardening of the packaged file and further improving the security of the application.

[0146] Figure 4 1 is a flowchart of another application deployment method provided according to an embodiment of the present invention. This embodiment is a further refinement of the above technical solution. The technical solution in this embodiment can be combined with various optional solutions in one or more of the above embodiments. Figure 4 As shown, the method includes:

[0147] Step 410: Obtain the program code of the target application through a pre-configured deployment tool, and determine the packaging information of the target application according to the program code.

[0148] Step 420: Determine target parameters and parsing parameters that match the target application program through the signature certificates and description files in the deployment tool.

[0149] Step 430: Update the parameter definition file matching the target application according to the target parameters and the packaging information to obtain a target parameter definition file.

[0150] Step 440: Pack the target application according to the target parameter definition file and each of the parsing parameters to obtain a packaged file.

[0151] Step 450: In response to the code scanning instruction for the packaged file, a code scanning tool is used to perform a target operation on the packaged file to complete a security scan of the packaged file.

[0152] The target operation includes at least one of the following: cache cleaning, compilation, code scanning, and code scanning report generation.

[0153] In an optional implementation of this embodiment, after obtaining the packaged file of the target application, if a code scanning instruction for the packaged file is received, the code scanning tool configured in the deployment tool can be used to perform cache cleaning, compilation, code scanning, or code scanning report generation on the packaged file, thereby completing a security scan of the packaged file.

[0154] Optionally, in this embodiment, after receiving the code scanning instruction for the packaged file, the target parameter definition file of the target application can be obtained, and the content information of parameters such as BUILD_ID, SCHEME_NAME and FILTER_FILE_NAME of the target parameter definition file can be obtained; further, the content information of parameters such as CODE_SIGN_IDENTITY, PROVISIONING_PROFILE_SPECIFIER and DEVELOPMENT_TEAM after the signature certificate and description file are parsed can be obtained; the command line tool and Xcodbuild tool of the code scanning tool are used to perform cache cleaning, compilation, code scanning and code scanning report generation, thereby completing the security scan of code vulnerabilities.

[0155] Step 460: In response to the deployment instruction of the target application, upload the packaged file to the distribution platform to deploy the target application.

[0156] According to the solution of this embodiment, after obtaining the packaged file of the target application, if a code scanning instruction for the packaged file is received, the code scanning tool configured in the deployment tool can be used to perform cache cleaning, compilation, code scanning, or code scanning report generation on the packaged file, thereby completing a security scan of the packaged file. The packaged file can be security scanned and a report can be generated, so that file vulnerabilities of the packaged file can be discovered in a timely manner, thereby improving the security of the packaged file.

[0157] Figure 5 FIG. 1 is a schematic diagram of a structure of a deployment device for an application program provided according to an embodiment of the present invention. Figure 5 As shown, the device includes: a packaging information acquisition module 510, a parameter determination module 520, a target parameter definition file determination module 530, a packaging file determination module 540 and a deployment module 550.

[0158] The packaging information acquisition module 510 is used to acquire the program code of the target application through a pre-configured deployment tool, and determine the packaging information of the target application according to the program code; the deployment tool is separated from the development environment of the application;

[0159] A parameter determination module 520, which determines target parameters and parsing parameters that match the target application program through each signature certificate and description file in the deployment tool;

[0160] A target parameter definition file determination module 530 is used to update a parameter definition file matching the target application according to the target parameter and the packaging information to obtain a target parameter definition file;

[0161] A package file determination module 540 is used to package the target application according to the target parameter definition file and each of the parsing parameters to obtain a package file;

[0162] The deployment module 550 is used to upload the packaged file to the distribution platform in response to the deployment instruction of the target application to deploy the target application.

[0163] The solution of this embodiment obtains the program code of the target application through a packaging information acquisition module, and determines the packaging information of the target application according to the program code; determines the target parameters and parsing parameters matching the target application respectively through a parameter determination module; updates the parameter definition file matching the target application according to the target parameters and the packaging information through a target parameter definition file determination module to obtain a target parameter definition file; packages the target application according to the target parameter definition file and each of the parsing parameters through a packaging file determination module to obtain a packaging file; and responds to the deployment instruction of the target application through a deployment module to upload the packaging file to a distribution platform to deploy the target application, thereby solving the problems of difficult application deployment and low development efficiency, and enabling quick and easy deployment of applications, thereby improving the development efficiency of applications.

[0164] In an optional implementation of this embodiment, the application deployment device further includes a configuration module for building a deployment environment of the application on the target server;

[0165] Determine at least one parameter definition file; the parameter definition file includes at least one of the following configuration information: project name, project workspace name, plan name, project unique identifier, attribute information of the distribution platform, hardening configuration file path, scan report template name, and scan vulnerability file name;

[0166] Acquire multiple signature certificates and description files, and store each of the signature certificates and each of the description files in a preset area; the signature certificates correspond to the description files one by one;

[0167] A security hardening tool and a code scanning tool are obtained, and the security hardening tool and the code scanning tool are authorized.

[0168] In an optional implementation of this embodiment, the configuration module is further used to determine the export options corresponding to the configuration files matching the description files, so as to export the deployed applications on demand;

[0169] The export options include at least one of: app store, development, enterprise, and temporary use.

[0170] In an optional implementation of this embodiment, the packaging information acquisition module 510 is specifically used to detect the program code and determine the packaging information according to the detection result;

[0171] The packaging information includes at least one of the following: project name, code branch, code identifier, and packaging purpose.

[0172] In an optional implementation of this embodiment, the packaging information acquisition module 510 is also used to verify the packaging information;

[0173] If the packaging information verification fails, the deployment of the target application is stopped.

[0174] In an optional implementation of this embodiment, the parameter determination module 520 is specifically used to parse the signature certificate and the description file to obtain various reference parameters;

[0175] The reference parameters are screened to obtain the target parameters and analytical parameters respectively.

[0176] In an optional implementation of this embodiment, the target parameter definition file determination module 530 is specifically used to add each of the target parameters and each of the packaging information to a parameter definition file matching the target application, so as to obtain a target parameter definition file matching the target application.

[0177] In an optional implementation of this embodiment, the package file determination module 540 is specifically used to load the target parameter definition file and determine the first parameter in the target parameter definition file;

[0178] Obtaining values ​​of the first parameter and the parsing parameter;

[0179] Execute the preset script commands in sequence to obtain the packaged file.

[0180] In an optional implementation of this embodiment, the application deployment device further includes a security reinforcement module, which is used to load the target parameter definition file in response to the security reinforcement instruction for the packaged file, and obtain the loading path of the security reinforcement configuration file;

[0181] The security reinforcement tool performs security reinforcement on the packaged file based on the loading path, and writes the reinforcement result into the reinforcement status detection file.

[0182] In an optional implementation of this embodiment, the security reinforcement module is further used to obtain the reinforcement status in the reinforcement status detection file in response to the reinforcement result detection instruction;

[0183] If the reinforcement status meets the preset conditions, it is determined that the security reinforcement of the packaged file is successful;

[0184] Otherwise, continue to perform the security hardening operation on the packaged file.

[0185] In an optional implementation of this embodiment, the application deployment device further includes a code scanning module, which is used to respond to a code scanning instruction for the packaged file, perform a target operation on the packaged file through a code scanning tool, and complete a security scan of the packaged file;

[0186] The target operation includes at least one of the following: cache cleaning, compilation, code scanning, and code scanning report generation.

[0187] In an optional implementation of this embodiment, the deployment module 550 is specifically used to read the target parameter definition file to obtain relevant parameter information;

[0188] Upload the relevant parameter information and the packaged file to the distribution platform;

[0189] Receive the deployment result fed back by the distribution platform and the download link of the target application.

[0190] The application deployment device provided in the embodiment of the present invention can execute the application deployment method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0191] Figure 6A schematic diagram of the structure of an electronic device 10 that can be used to implement an embodiment of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.

[0192] like Figure 6 As shown, the electronic device 10 includes at least one processor 11, and a memory connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 to the random access memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0193] A number of components in the electronic device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0194] The processor 11 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as a method for deploying an application.

[0195] In some embodiments, the deployment method of the application program may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the deployment method of the application program described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to execute the deployment method of the application program in any other appropriate manner (e.g., by means of firmware).

[0196] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0197] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0198] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in combination with an instruction execution system, device or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0199] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0200] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0201] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

[0202] An embodiment of the present invention further provides a computer program product, including a computer program, which, when executed by a processor, implements a method for deploying an application program as provided in any embodiment of the present application.

[0203] In the process of implementation, the computer program product can be written in one or more programming languages ​​or a combination thereof to perform the computer program code of the present invention, including object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (for example, using an Internet service provider to connect through the Internet).

[0204] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0205] Note that the above are only preferred embodiments of the present invention and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A method for deploying an application, characterized in that: include: Acquiring the program code of the target application through a pre-configured deployment tool, and determining the packaging information of the target application according to the program code; the deployment tool is separated from the development environment of the application; Determine the target parameters and parsing parameters that match the target application program respectively through each signature certificate and description file in the deployment tool; Update the parameter definition file matching the target application according to the target parameter and the packaging information to obtain a target parameter definition file; Packaging the target application according to the target parameter definition file and each of the parsing parameters to obtain a packaged file; In response to the deployment instruction of the target application, the packaged file is uploaded to the distribution platform to deploy the target application.

2. The method for deploying an application according to claim 1, characterized in that: The deployment tool is configured by following the steps below: Build the application deployment environment on the target server; Determine at least one parameter definition file; the parameter definition file includes at least one of the following configuration information: project name, project workspace name, plan name, project unique identifier, attribute information of the distribution platform, hardening configuration file path, scan report template name, and scan vulnerability file name; Acquire multiple signature certificates and description files, and store each of the signature certificates and each of the description files in a preset area; the signature certificates correspond to the description files one by one; A security hardening tool and a code scanning tool are obtained, and the security hardening tool and the code scanning tool are authorized.

3. The method for deploying an application according to claim 2, characterized in that: After storing the signature certificates and the description files in a preset area, the method further includes: Determine the export options corresponding to the configuration files matching the description files, so as to export the deployed applications on demand; The export options include at least one of: app store, development, enterprise, and temporary use.

4. The method for deploying an application according to claim 1, characterized in that: The step of determining the packaging information of the target application according to the program code includes: Detecting the program code and determining the packaging information according to the detection result; The packaging information includes at least one of the following: project name, code branch, code identifier, and packaging purpose.

5. The method for deploying an application according to claim 4, characterized in that: After determining the packaging information according to the detection result, the method further includes: Verify the packaging information; If the packaging information verification fails, the deployment of the target application is stopped.

6. The method for deploying an application according to claim 4, characterized in that: The step of determining target parameters and parsing parameters that match the target application program through the signature certificates and description files in the deployment tool includes: Parse the signature certificate and description file to obtain various reference parameters; The reference parameters are screened to obtain the target parameters and analytical parameters respectively.

7. The method for deploying an application according to claim 6, characterized in that: The updating of the parameter definition file matching the target application according to the target parameter and the packaging information to obtain the target parameter definition file includes: Each of the target parameters and each of the packaging information are respectively added to a parameter definition file that matches the target application program to obtain a target parameter definition file that matches the target application program.

8. The method for deploying an application according to claim 6, characterized in that: The target application is packaged according to the target parameter definition file and each parsing parameter value to obtain a packaged file, including: Loading the target parameter definition file, and determining the first parameter in the target parameter definition file; Obtaining values ​​of the first parameter and the parsing parameter; Execute the preset script commands in sequence to obtain the packaged file.

9. The method for deploying an application according to any one of claims 1 to 8, characterized in that: After getting the package file, it also includes: In response to the security hardening instruction for the packaged file, the target parameter definition file is loaded, and a loading path of the security hardening configuration file is obtained; The security reinforcement tool performs security reinforcement on the packaged file based on the loading path, and writes the reinforcement result into the reinforcement status detection file.

10. The method for deploying an application according to claim 9, characterized in that: After the reinforcement results are written into the reinforcement status detection file, it also includes: In response to the reinforcement result detection instruction, obtaining the reinforcement status in the reinforcement status detection file; If the reinforcement status meets the preset conditions, it is determined that the security reinforcement of the packaged file is successful; Otherwise, continue to perform the security hardening operation on the packaged file.

11. The method for deploying an application according to any one of claims 1 to 8, characterized in that: After getting the package file, it also includes: In response to a code scanning instruction for the packaged file, a target operation is performed on the packaged file by a code scanning tool to complete a security scan of the packaged file; The target operation includes at least one of the following: cache cleaning, compilation, code scanning, and code scanning report generation.

12. The method for deploying an application according to claim 1, characterized in that: The step of uploading the packaged file to the distribution platform in response to the deployment instruction of the target application comprises: Read the target parameter definition file to obtain relevant parameter information; Upload the relevant parameter information and the packaged file to the distribution platform; Receive the deployment result fed back by the distribution platform and the download link of the target application.

13. A deployment device for an application, characterized in that: include: A packaging information acquisition module, used to acquire the program code of the target application through a pre-configured deployment tool, and determine the packaging information of the target application according to the program code; the deployment tool is separated from the development environment of the application; A parameter determination module, which determines target parameters and parsing parameters that match the target application program through each signature certificate and description file in the deployment tool; A target parameter definition file determination module, used to update a parameter definition file matching the target application according to the target parameter and the packaging information to obtain a target parameter definition file; A package file determination module, used for packaging the target application according to the target parameter definition file and each of the parsing parameters to obtain a package file; The deployment module is used to upload the packaged file to the distribution platform in response to the deployment instruction of the target application to deploy the target application.

14. An electronic device, characterized in that: The invention comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the method for deploying an application program as described in any one of claims 1 to 12 when executing the computer program.

15. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the program implements the method for deploying an application program as described in any one of claims 1 to 12.

16. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the computer program implements the method for deploying the application program according to any one of claims 1 to 12.