CN112445513A - Installation package processing method and device - Google Patents
Installation package processing method and device Download PDFInfo
- Publication number
- CN112445513A CN112445513A CN201910808955.2A CN201910808955A CN112445513A CN 112445513 A CN112445513 A CN 112445513A CN 201910808955 A CN201910808955 A CN 201910808955A CN 112445513 A CN112445513 A CN 112445513A
- Authority
- CN
- China
- Prior art keywords
- installation package
- uploading
- target
- file
- certificate
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000009434 installation Methods 0.000 title claims abstract description 224
- 238000003672 processing method Methods 0.000 title claims abstract description 13
- 238000011161 development Methods 0.000 claims abstract description 88
- 238000012545 processing Methods 0.000 claims abstract description 52
- 238000000034 method Methods 0.000 claims abstract description 35
- 238000004806 packaging method and process Methods 0.000 claims abstract description 35
- 230000003068 static effect Effects 0.000 claims abstract description 9
- 238000012360 testing method Methods 0.000 claims description 67
- 238000010276 construction Methods 0.000 claims description 8
- 238000005538 encapsulation Methods 0.000 claims description 5
- 238000004883 computer application Methods 0.000 abstract description 2
- 238000012858 packaging process Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 230000003203 everyday effect Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000010606 normalization Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000003860 storage Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
- G06F8/44—Encoding
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
Abstract
The embodiment of the application provides an installation package processing method and device, and relates to the technical field of computer application. The method comprises the steps that in response to an installation package processing instruction, project source codes uploaded by a user are obtained by using an integrated development tool; performing static compilation on the project source code to obtain an executable file; configuring a target certificate and a target description file according to a developer account added in the integrated development tool; and packaging the executable file, the target certificate and the target description file to obtain an installation package. The technical scheme provided by the embodiment of the application improves the generation efficiency of the installation package.
Description
Technical Field
The embodiment of the application relates to the technical field of computer application, in particular to an installation package processing method and device.
Background
In the release process of an APP (application), related files including executable files need to be packaged and packaged to obtain an installation package, and then the installation package is uploaded to a public platform for a user to download and install. The installation package is subjected to different processing, such as release or debugging, and a certificate and a description file of a corresponding function need to be configured, for example, when the installation package is released, the installation package can be uploaded to a public platform so that a user can download and install the installation package, a release certificate and a release description file need to be configured, wherein the release certificate, namely equipment used by an authentication developer, has the authority of releasing an APP; the release description file identifies that a certain device has the right to install the APP, and records an IMEI (International Mobile Equipment Identity) number where the APP can be installed. At present, the operation of packaging and packaging the iOS platform to obtain the installation package is manually completed, that is, a developer is required to download a certificate and a description file of a corresponding function from a developer website, and the certificate and the description file are packaged and packaged together with an executable file to obtain the installation package. However, with the iteration and normalization of the project, the way of manually packaging and packaging to obtain the installation package is complicated and inefficient.
Disclosure of Invention
The embodiment of the application provides an installation package processing method and device, and aims to solve the problem that an installation package packaging mode in the prior art is complex.
In a first aspect, an embodiment of the present application provides an installation package processing method, including:
responding to the installation package processing instruction, and acquiring a project source code uploaded by a user by using an integrated development tool;
performing static compilation on the project source code to obtain an executable file;
configuring a target certificate and a target description file according to a developer account added in the integrated development tool;
and packaging the executable file, the target certificate and the target description file to obtain an installation package.
In a second aspect, an embodiment of the present application provides an installation package processing apparatus, including:
the acquisition module is used for responding to the installation package processing instruction and acquiring the project source code uploaded by the user by using the integrated development tool;
the obtaining module is used for performing static compiling on the project source code to obtain an executable file;
the configuration module is used for configuring a target certificate and a target description file according to a developer account added in the integrated development tool;
and the packaging module is used for packaging the executable file, the target certificate and the target description file to obtain an installation package.
In the embodiment of the application, in response to an installation package processing instruction, an integrated development tool is utilized to obtain a project source code uploaded by a user; performing static compilation on the project source code to obtain an executable file; configuring a target certificate and a target description file according to a developer account added in the integrated development tool; and packaging the executable file, the target certificate and the target description file to obtain an installation package. The executable file, the target certificate and the target description file are obtained through the integrated development tool and are packaged to obtain the installation package, the problem that the mode for obtaining the installation package through manual packaging in the existing mode is complex and tedious is solved, and the efficiency for obtaining the installation package through packaging is improved.
These and other aspects of the present application will be more readily apparent from the following description of the embodiments.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative efforts.
FIG. 1 is a flow chart illustrating one embodiment of an installation package processing method provided by the present application;
FIG. 2 is a flow chart illustrating another embodiment of an installation package processing method provided by the present application;
FIG. 3 is a schematic structural diagram illustrating an embodiment of an installation package processing apparatus provided in the present application;
fig. 4 shows a schematic structural diagram of another embodiment of an installation package processing apparatus provided in the present application.
Detailed Description
In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application.
In some of the flows described in the specification and claims of this application and in the above-described figures, a number of operations are included that occur in a particular order, but it should be clearly understood that these operations may be performed out of order or in parallel as they occur herein, the number of operations, e.g., 101, 102, etc., merely being used to distinguish between various operations, and the number itself does not represent any order of performance. Additionally, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel. It should be noted that, the descriptions of "first", "second", etc. in this document are used for distinguishing different messages, devices, modules, etc., and do not represent a sequential order, nor limit the types of "first" and "second" to be different.
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Fig. 1 is a flowchart of an embodiment of an installation package processing method provided in an embodiment of the present application, where the method is implemented in an integrated development tool, and the method may include the following steps:
101: and responding to the installation package processing instruction, and acquiring the project source code uploaded by the user by utilizing the integrated development tool.
The installation package processing instruction may be a processing instruction set by the user at a specific time, such as a processing instruction set by the user to process the installation package at a certain fixed time every day. And acquiring the project source code uploaded by the user by utilizing the integrated development tool at the fixed time in response to the installation package processing instruction.
Alternatively, the installation package processing instruction may also be a processing instruction generated when an update of the item source code uploaded by the user is detected. And responding to the installation package processing instruction, and acquiring the updated project source code uploaded by the user by using the integrated development tool.
In addition, the installation package processing instruction can also be a processing instruction generated when a user clicks a processing control provided by the integrated development tool based on the processing requirement of the user on the installation package.
The source code of the project refers to a source code of an application program to be developed, the source code of the project uploaded by the user may be a source code uploaded to a remote repository of the project by the user, and the remote repository may refer to a remote repository for storing the source code of the application program. The source code in the remote repository can participate in the packaging process to obtain the installation package, and the update code which is not uploaded to the project remote repository does not participate in the packaging process. In other words, in response to the installation package processing instruction, the latest project source code uploaded to the remote warehouse by the user is acquired by using the integrated development tool for processing.
The integrated development tool can be an application program for providing a program development environment, and has a plurality of functions such as a code compiling function, an analysis function, a debugging function and a packaging uploading function. For IOS applications, the integrated development tool may be, for example, xcodeserver.
102: and statically compiling the project source code to obtain an executable file.
103: and configuring a target certificate and a target description file according to the added developer account in the integrated development tool.
And the developer account is used for real machine debugging and certificate signing in the development process of the developer, and the installation package is uploaded to the account used on the public platform or the test platform.
All certificates and corresponding description files can be obtained according to the account number of the developer. Among them, the certificate can be divided into a development certificate and an issue certificate. The development certificate can also be called as a test certificate, the equipment used by the authentication developer has the authority to develop the application program, and the development certificate is required to be used when the real machine debugging is required in the development process; the issuing certificate can also be called as a production certificate, the device used by the authentication developer has the authority of issuing the application program, and the issuing certificate is required to be used when the application program needs to be issued online in the later stage of the development process.
The description file may also be divided into a development description file and a release description file. The development description file can identify that a certain device has the right to install and debug the application program; the release profile may then identify that a device has the right to install and use the application. The development description file corresponds to a development certificate, and the issue description file corresponds to an issue certificate.
The installation package processing instruction may include a processing type, the processing type may include real machine debugging and online publishing, and based on the processing type, a corresponding target certificate and a target description file may be directly configured. For example, when the processing type is true machine debugging, the target certificate is a development certificate, the target description file is a development description file, and when the processing type is online publishing, the target certificate is a publishing certificate, and the target description file is a publishing description file.
Therefore, optionally, step 103 may specifically configure the publishing certificate and the publishing description file in response to the installation package uploading instruction according to the developer account added in the integrated development tool.
In practical application, according to a developer account added in the integrated development tool and according to the processing type in the installation package processing instruction, configuring a target certificate and a target description file of a corresponding function.
104: and packaging the executable file, the target certificate and the target description file to obtain an installation package.
And packaging the executable file and the corresponding target certificate and target description file to obtain an installation package so as to carry out processing operations such as debugging or uploading on the installation package.
In the embodiment, based on the integrated development tool, in response to the installation package processing instruction, the integrated development tool is used for acquiring a project source code uploaded by a user, and static compiling is performed on the project source code to acquire an executable file which can be loaded and executed by an operating system; and configuring a target certificate and a target description file of a corresponding function for the executable file according to a developer account added in the integrated development tool. And then, the target certificate, the target description file and the executable file are packaged to obtain the installation package, so that the subsequent processing operations such as issuing and the like are performed on the installation package. By the technical scheme, based on the integrated development tool, the corresponding target certificate and the target description file can be automatically configured, and the operation of obtaining the installation package by packaging the target certificate and the target description file with the executable file can be realized. The automatic packaging process of the installation package is realized, the mode that in the prior art, the certificate and the description file need to be obtained through manual downloading and the installation package is obtained through manual packaging is improved, and the generation efficiency of the installation package is improved.
In some embodiments, the method of configuring the target certificate and the target description file according to the added developer account in the integrated development tool may include:
creating a Bundle ID (application identifier) according to the developer account added in the integrated development tool;
and configuring a target certificate and a target description file according to the bundle ID.
The Bundle ID is an identifier of an application program corresponding to the project source code, and may also be referred to as an application ID, and is a globally unique identifier of each application program. Each time a new application is developed, a bundle ID corresponding to the application needs to be created. The bundle ID of the application program may be created according to the developer account, and each developer account may create a plurality of bundle IDs.
A certificate, which is used as a certificate for authenticating that a device used by a developer has a right to develop or issue an application, needs to be created according to a developer account. The certificate created by each developer account is limited, that is, the same certificate can be used by a plurality of bundle IDs. The description file is used as an identifier for a device having an authority to install an application program, describes a correspondence between the application program and a certificate, and needs to be created according to the bundle ID and the certificate. Each bundle ID corresponds to one description file, that is, each developer account may have multiple description files. The development description file needs to be created according to the bundle ID, the development certificate and the test equipment, and is used for identifying that the test equipment has the permission to test the application program; the release description file needs to be created according to the bundle ID and the release certificate, and the device does not need to be selected because the application program which is formally released does not need to be limited to install the device.
Creating a bundle ID according to the added developer account in the integrated development tool, and configuring a target certificate and a target description file of a corresponding function according to the processing type in the installation package processing instruction and in combination with the bundle ID.
The integrated development tool integrates the functionality of a developer account. Based on the integrated development tool, the bundle ID can be automatically created according to the account number and the password of the developer, and the corresponding target certificate and the target description file can be automatically created. The user does not need to manually download and obtain the certificate and the description file from the developer website, the time for configuring the target certificate and the target description file is saved, and the processing efficiency of the installation package is improved.
In practical applications, the development of an application program is not completed by a developer, and for an application program developed by a company, the development team usually develops the application program cooperatively. The developer account may be a company account under which individual developer accounts of multiple developers may be added. Each developer can use the own developer account to create a development certificate, and a team manager creates a development description file according to the development certificates of the developers. And the issuing certificate and the issuing description are created according to the company account.
Therefore, when the installation package for the real-machine debugging is obtained based on the integrated development tool, the description file containing the bundle ID can be identified according to the bundle ID, the corresponding development certificate and the corresponding development description file are matched according to the developer account of the developer, and the installation package for the real-machine debugging is obtained through encapsulation. And when the installation package for uploading and publishing is obtained based on the integrated development tool, the description file containing the bundle ID can be identified according to the bundle ID, the publishing certificate and the corresponding publishing description file are matched according to the function name, and the installation package for uploading and publishing is obtained by packaging.
In the embodiment of the application, the function of the account of the developer is integrated through the integrated development tool, the target certificate and the target description file corresponding to the function are automatically created and identified in response to different processing instructions of the installation package, the operation of automatically packaging and obtaining the installation package is realized, the problem that in the prior art, the target certificate and the target description file corresponding to the function need to be manually created and identified by a user, the mode of manually packaging and obtaining the installation package is complex is solved, and the processing efficiency of the installation package is improved.
In some embodiments, after obtaining the installation package based on the integrated development tool package, the method may further comprise:
and uploading the installation package.
The installation package can be uploaded to a plurality of platforms, and the installation package can be uploaded in various modes.
As an optional manner, the method for uploading the installation package may include:
acquiring an uploading path provided by a user;
and uploading the installation package to a package management platform corresponding to the uploading path according to the uploading path so as to download and install the installation package from the package management platform.
The package management platform can be an application installation package management platform used by a company development team and used for storing installation packages of various applications so as to facilitate downloading and installing the installation packages by team members.
In the process of uploading to the packet management platform, an upload path may be recorded, and the upload path may include IP address information. The uploading paths of installation packages of different versions are different.
In practical application, based on an integrated development tool, in response to an instruction for uploading an installation package to a package management platform, the integrated development tool is used for packaging to obtain the installation package, an uploading path is obtained, the installation package can be uploaded to the package management platform corresponding to the uploading path according to the uploading path, so that the installation package can be downloaded and installed from the package management platform, and information such as the uploading path and an IP address is recorded. By recording information such as an uploading path and the like, the process of automatically uploading the installation package to the package management platform by using the integrated development tool is realized, manual operation of a user is not needed, and the efficiency of uploading the installation package to the package management platform is improved.
As another optional mode, the method for uploading the installation package may further include:
logging in a test platform by using the developer account;
uploading the installation package to a test platform so that the test platform can test the installation package;
and if the installation package passes the test, uploading the installation package to a public platform so as to be convenient for downloading and installing the installation package from the public platform.
When the installation package is the IOS installation package, the test platform can be testflight, namely, the IOS officially releases the application program of the test edition. Before the application program is formally uploaded to the public platform for release, a series of test processes need to be carried out, the test is passed and can be uploaded to the public platform for release, so that the installation package can be downloaded from the public platform conveniently, and various functions of the application program can be used. The public platform can be an application program mall APP store, and the user can download the installation package from the APP store.
In practical application, in response to a processing instruction for uploading an installation package to a test platform, the corresponding target certificate and the target description file are configured by using the integrated development tool, and the target certificate and the target description file are packaged with the executable file to obtain the installation package. The test platform can carry out real machine debugging and issue to a public platform, so the target certificate can be a development certificate or an issue certificate; the object description file may also be a development description file and a release description file. And logging in the test platform by using the account number and the password of the developer, and uploading the installation package to the test platform so that the test platform can test the installation package. If the installation package passes the test, the installation package can be uploaded to the APP store, so that a user can download and install the installation package from the APP store conveniently, wherein the installation package uploaded to the APP store needs to be configured with an issuing certificate and an issuing description file.
If the installation package fails to pass the test, modifying and debugging the installation package again, repeating the test process until the test passes, and uploading the installation package passing the test to the APP store for release.
In some embodiments, the method of uploading the installation package to a test platform may include:
exporting the installation package and saving the installation package to the local;
and calling a construction tool plug-in to upload the installation package to a test platform.
The construction tool plug-in can be fastlane, and the fastlane is an automatic construction tool constructed by developers and has the functions of packaging, uploading and the like. The building tool plug-in can locally search the target certificate and the target description file contained in the installation package to be uploaded, so that the corresponding installation package is uploaded to the test platform.
In practical application, based on the integrated development tool, in response to an instruction for uploading an installation package to a test platform, the integrated development tool is used for packaging and obtaining the installation package, exporting and storing the installation package to the local, and a construction tool plug-in is called to automatically identify a target certificate and a target description file of the installation package to be uploaded, which are stored in the local, so that the installation package containing the target certificate and the target description file is uploaded to the test platform, and the test platform can test the installation package conveniently.
The test platform logs in by using a developer account, and if historical uploading information including the developer account exists, namely pre-configuration information exists, the pre-configuration information is read, and logging uploading is achieved; if the pre-configuration information does not exist, the user is required to manually input the pre-configuration information, and the method is suitable for uploading the installation package to the test platform for the first time.
In the embodiment of the application, the installation package is obtained by utilizing the integrated development tool for encapsulation, exported and stored locally, the certificate and the description file in the installation package are identified by calling the construction tool plug-in, and uploaded to the test platform, so that the operation of automatically uploading the installation package to the test platform is realized, the mode that the installation package needs to be manually identified locally and uploaded to the test platform in the prior art is improved, and the method is simple, convenient and efficient.
Fig. 2 is a flowchart of another embodiment of an installation package processing method provided in an embodiment of the present application, where the method is implemented based on an integrated development tool, and the method may include the following steps:
201: and responding to the installation package processing instruction, and acquiring the project source code uploaded by the user by utilizing the integrated development tool.
202: and statically compiling the project source code to obtain an executable file.
203: and configuring a target certificate and a target description file according to the added developer account in the integrated development tool.
204: and generating a configuration file based on the target function configuration requirement provided by the user.
205: packaging the configuration file, the executable file, the target certificate, the target description file and the resources required by operation to obtain an installation package; the configuration file is used for providing the target function when the installation package operates.
The above 201 to 203 refer to the corresponding contents in embodiment 1, and are not described herein again.
In 204, the target function configuration may be a personalized configuration added to the application by a developer, and the target function configuration requirement may be a function that needs to be implemented based on the personalized configuration when the installation package runs. The personalized configuration may be specifically version type configuration of the application program, new characteristics issued by the application program, screenshot in the application program, and the like. The version type configuration may specifically include a debug version and a release version. The installation package of the debugging version is the installation package containing debugging information, so that a developer can conveniently debug in the subsequent testing process; the installation package of the release version is the installation package which does not contain the debugging information, and various optimization is carried out, so that the installation package is convenient for a user to use well. The personalized configurations are contained within the item source code.
Because the integrated development tool does not recognize the personalized configuration content contained in the project source code, and the part of the content needs to be updated and adjusted in time, for example, when the version of the application program is updated, information such as new use characteristics and the like needs to be added, a configuration file which is different from an executable file and can be recognized by the integrated development tool can be created according to the project source code containing the personalized configuration, so that the configuration file and the executable file are packaged together to obtain an installation package, and the personalized configuration can be realized when the installation package runs.
The configuration file may be a plist (Property List file) file, which is typically used to store user settings, and may also be used to store bundled information. Here, the plist file may specifically include personalized configuration information.
In the above 205, the plist file, the executable file, the target certificate, the target description file, and the resource required for operation are encapsulated together by using an integrated development tool to obtain an installation package containing a personalized configuration, where the plist file may be used to provide a corresponding function when the installation package is operated. For example, if a developer wants to obtain an installation package for installation and debugging, the developer may first obtain a plist file including debugging version configuration information by manually packaging a source code, and then package the plist file to obtain the installation package with the personalized debugging version type.
In practical application, based on an integrated development tool, when an installation package processing instruction is responded, when a project source code uploaded by a user is acquired by using the integrated development tool, firstly, the personalized configuration of the project source code is manually packaged to obtain a plist file, and then the plist file, an executable file, a target certificate, a target description file and a resource file required by application program operation are packaged together to obtain a specific version type installation package with personalized configuration.
In this embodiment, in consideration of the fact that the integrated development tool xcodeserver does not recognize the personalized configuration content included in the source code, the source code including the personalized configuration is manually packaged to obtain a plist file that can be recognized by the integrated development tool, and then the plist file is packaged with the executable file, the target certificate, the target description file and the resource file required for operation by using the integrated development tool to obtain an installation package with personalized configuration, so that the personalized configuration of the installation package is realized at higher efficiency.
When uploading the installation package with the personalized configuration, various modes can be provided.
As an implementation manner, the installation package with personalized configuration may be uploaded to a package management platform, different version types correspond to different uploading paths, the uploading path corresponding to the installation package of a specific version type is recorded, and simultaneously, the version number and version type information may be recorded.
As another implementation manner, the installation package with the personalized configuration may be uploaded to a test platform, and a build tool plug-in may be used to identify a target certificate, a target description file, a plist file, and personalized configuration information included in a local installation package, and upload a corresponding installation package to the test platform. When the test platform is uploaded, screenshots of the application programs, descriptions of the application programs and all resource information required by the release of the application programs can be uploaded.
In practical application, when an installation package is obtained based on the integrated development tool package, whether the installation package is a debugging version type installation package or a release version type installation package can be judged according to a plist file obtained by manually packaging a source code. When the installation package is uploaded to a test platform for testing, the debugging version type installation package can be uploaded so that a tester can conveniently start various service monitoring errors in the test process, find bugs and timely modify the errors. Meanwhile, the release version type installation package can be uploaded, and the fact that the test condition is considered in the release version type installation package state is the real condition of use of a user. Therefore, the test of the release version type installation package is more helpful to ensure the user experience.
If the installation package uploaded to the test platform passes the test, the release version type installation package can be uploaded to the public platform APP store, so that the release version type installation package can be downloaded and installed conveniently, various functions of the application program can be used better, and debugging is not needed.
Fig. 3 is a flowchart of an embodiment of an installation package processing apparatus provided in an embodiment of the present application, where the apparatus may include:
the first obtaining module 301 is configured to obtain, by using an integrated development tool, a project source code uploaded by a user in response to an installation package processing instruction;
a first obtaining module 302, configured to perform static compilation on the project source code to obtain an executable file;
a first configuration module 303, configured to configure a target certificate and a target description file according to a developer account added in the integrated development tool;
a first packaging module 304, configured to package the executable file, the target certificate, and the target description file to obtain an installation package.
In some embodiments, the configuration module may include:
the first creating unit is used for creating an application identifier bundle ID according to the developer account added in the integrated development tool;
and the second creating unit is used for creating a target certificate and a target description file according to the bundle ID.
In some embodiments, the apparatus may further comprise:
and the uploading module is used for uploading the installation package.
In some embodiments, the upload module may include:
the acquisition unit is used for acquiring an uploading path provided by a user;
and the first uploading unit is used for uploading the installation package to a package management platform corresponding to the uploading path according to the uploading path so as to be convenient for downloading and installing the installation package from the package management platform.
In some embodiments, the upload module may further include:
the login unit is used for logging in a test platform by utilizing the developer account;
the second uploading unit is used for uploading the installation package to a test platform so that the test platform can test the installation package;
and the third uploading unit is used for uploading the installation package to a public platform if the installation package passes the test, so that the installation package is downloaded and installed from the public platform conveniently.
In some embodiments, the second uploading unit may include:
the export subunit is used for exporting the installation package and saving the installation package to the local;
and the uploading subunit is used for calling the construction tool plug-in to upload the installation package to the test platform.
In some embodiments, the encapsulation module may include:
the generating unit is used for generating a configuration file based on the target function configuration requirement provided by the user;
the packaging unit is used for packaging the configuration file, the executable file, the target certificate, the target description file and the resources required by operation to obtain an installation package; the configuration file is used for providing the target function when the installation package operates.
The installation package processing apparatus shown in fig. 3 may execute the installation package processing method shown in the embodiment shown in fig. 1, and the implementation principle and the technical effect are not described again. The specific manner in which each module and unit of the installation package processing apparatus in the above embodiments perform operations has been described in detail in the embodiments related to the method, and will not be described in detail here.
Fig. 4 is a flowchart of another embodiment of an installation package processing apparatus according to an embodiment of the present application, where the apparatus may include:
a second obtaining module 401, configured to obtain, by using an integrated development tool, a project source code uploaded by a user in response to an installation package processing instruction;
a second obtaining module 402, configured to perform static compilation on the project source code to obtain an executable file;
a second configuration module 403, configured to configure a target certificate and a target description file according to a developer account added in the integrated development tool;
a generating module 404, configured to generate a configuration file based on a target function configuration requirement provided by a user;
a second encapsulation module 405, configured to encapsulate the configuration file, the executable file, the target certificate, the target description file, and the resource required by operation to obtain an installation package; the configuration file is used for providing the target function when the installation package operates.
The installation package processing apparatus shown in fig. 4 may execute the installation package processing method shown in the embodiment shown in fig. 2, and the implementation principle and the technical effect are not described again. The specific manner in which each module and unit of the installation package processing apparatus in the above embodiments perform operations has been described in detail in the embodiments related to the method, and will not be described in detail here.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware. With this understanding in mind, the above-described technical solutions may be embodied in the form of a software product, which can be stored in a computer-readable storage medium such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.
Claims (14)
1. An installation package processing method is characterized by comprising the following steps:
responding to the installation package processing instruction, and acquiring a project source code uploaded by a user by using an integrated development tool;
performing static compilation on the project source code to obtain an executable file;
configuring a target certificate and a target description file according to a developer account added in the integrated development tool;
and packaging the executable file, the target certificate and the target description file to obtain an installation package.
2. The method of claim 1, wherein configuring a target certificate and a target description file according to a developer account added in the integrated development tool comprises:
creating an application identifier bundle ID according to the added developer account in the integrated development tool;
and creating a target certificate and a target description file according to the bundle ID.
3. The method of claim 1, further comprising:
and uploading the installation package.
4. The method of claim 3, wherein uploading the installation package comprises:
acquiring an uploading path provided by a user;
and uploading the installation package to a package management platform corresponding to the uploading path according to the uploading path so as to download and install the installation package from the package management platform.
5. The method of claim 3, wherein uploading the installation package comprises:
logging in a test platform by using the developer account;
uploading the installation package to a test platform so that the test platform can test the installation package;
and if the installation package passes the test, uploading the installation package to a public platform so as to be convenient for downloading and installing the installation package from the public platform.
6. The method of claim 5, wherein uploading the installation package to a test platform comprises:
exporting the installation package and saving the installation package to the local;
and calling a construction tool plug-in to upload the installation package to a test platform.
7. The method of claim 1, wherein encapsulating the executable file, the target certificate, and the target description file to obtain an installation package comprises:
generating a configuration file based on target function configuration requirements provided by a user;
packaging the configuration file, the executable file, the target certificate, the target description file and the resources required by operation to obtain an installation package; the configuration file is used for providing the target function when the installation package operates.
8. An installation package processing apparatus, comprising:
the acquisition module is used for responding to the installation package processing instruction and acquiring the project source code uploaded by the user by using the integrated development tool;
the obtaining module is used for performing static compiling on the project source code to obtain an executable file;
the configuration module is used for configuring a target certificate and a target description file according to a developer account added in the integrated development tool;
and the packaging module is used for packaging the executable file, the target certificate and the target description file to obtain an installation package.
9. The apparatus of claim 8, wherein the configuration module comprises:
the first creating unit is used for creating an application identifier bundle ID according to the developer account added in the integrated development tool;
and the second creating unit is used for creating a target certificate and a target description file according to the bundle ID.
10. The apparatus of claim 8, further comprising:
and the uploading module is used for uploading the installation package.
11. The apparatus of claim 10, wherein the upload module comprises:
the acquisition unit is used for acquiring an uploading path provided by a user;
and the first uploading unit is used for uploading the installation package to a package management platform corresponding to the uploading path according to the uploading path so as to be convenient for downloading and installing the installation package from the package management platform.
12. The apparatus of claim 10, wherein the upload module comprises:
the login unit is used for logging in a test platform by utilizing the developer account;
the second uploading unit is used for uploading the installation package to a test platform so that the test platform can test the installation package;
and the third uploading unit is used for uploading the installation package to a public platform if the installation package passes the test, so that the installation package is downloaded and installed from the public platform conveniently.
13. The apparatus of claim 12, wherein the second uploading unit comprises:
the export subunit is used for exporting the installation package and saving the installation package to the local;
and the uploading subunit is used for calling the construction tool plug-in to upload the installation package to the test platform.
14. The apparatus of claim 9, wherein the encapsulation module comprises:
the generating unit is used for generating a configuration file based on the target function configuration requirement provided by the user;
the packaging unit is used for packaging the configuration file, the executable file, the target certificate, the target description file and the resources required by operation to obtain an installation package; the configuration file is used for providing the target function when the installation package operates.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910808955.2A CN112445513A (en) | 2019-08-29 | 2019-08-29 | Installation package processing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910808955.2A CN112445513A (en) | 2019-08-29 | 2019-08-29 | Installation package processing method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112445513A true CN112445513A (en) | 2021-03-05 |
Family
ID=74741298
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910808955.2A Pending CN112445513A (en) | 2019-08-29 | 2019-08-29 | Installation package processing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112445513A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113849845A (en) * | 2021-11-29 | 2021-12-28 | 统信软件技术有限公司 | Method and device for packaging plug-in file, computing device and readable storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104572237A (en) * | 2015-01-19 | 2015-04-29 | 上海动联信息技术股份有限公司 | Automatic quick generation system and method for UKey installation package |
| US20160170712A1 (en) * | 2014-12-15 | 2016-06-16 | Beijing Jinher Software Co., Ltd | Method for integrally implementing development and release of APP |
| CN106155751A (en) * | 2016-08-02 | 2016-11-23 | 传线网络科技（上海）有限公司 | Application packing and issuing method and device |
| CN108469957A (en) * | 2018-03-08 | 2018-08-31 | 平安科技（深圳）有限公司 | Using packing method for uploading, device, computer equipment and storage medium |
| CN109783129A (en) * | 2018-12-15 | 2019-05-21 | 深圳壹账通智能科技有限公司 | Applied program processing method, device, computer equipment and storage medium |
-
2019
- 2019-08-29 CN CN201910808955.2A patent/CN112445513A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160170712A1 (en) * | 2014-12-15 | 2016-06-16 | Beijing Jinher Software Co., Ltd | Method for integrally implementing development and release of APP |
| CN104572237A (en) * | 2015-01-19 | 2015-04-29 | 上海动联信息技术股份有限公司 | Automatic quick generation system and method for UKey installation package |
| CN106155751A (en) * | 2016-08-02 | 2016-11-23 | 传线网络科技（上海）有限公司 | Application packing and issuing method and device |
| CN108469957A (en) * | 2018-03-08 | 2018-08-31 | 平安科技（深圳）有限公司 | Using packing method for uploading, device, computer equipment and storage medium |
| CN109783129A (en) * | 2018-12-15 | 2019-05-21 | 深圳壹账通智能科技有限公司 | Applied program processing method, device, computer equipment and storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113849845A (en) * | 2021-11-29 | 2021-12-28 | 统信软件技术有限公司 | Method and device for packaging plug-in file, computing device and readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8612947B2 (en) | System and method for remotely compiling multi-platform native applications for mobile devices | |
| CN105512029B (en) | A kind of method, server and system for testing intelligent terminal | |
| US8918760B2 (en) | Test script generation for application image validation | |
| CN106933609B (en) | Android application program installation package generation method and device | |
| CN107704238B (en) | Method and device for packaging items | |
| CN107896244B (en) | Version file distribution method, client and server | |
| US9823909B1 (en) | Program code conversion for cross-platform compatibility | |
| CN110096424B (en) | Test processing method and device, electronic equipment and storage medium | |
| CN107632829A (en) | A kind of App automation continuous integration systems and method based under iOS system | |
| US10452435B2 (en) | Dynamic build pipeline execution | |
| CN111078278A (en) | Automatic packaging method supporting Flutter and iOS mixed editing project | |
| CN105389263A (en) | Method, system and equipment for monitoring application software permissions | |
| CA2772228A1 (en) | Single development test environment | |
| CN115904959A (en) | Software integration and deployment method and software development management system | |
| CN113064630A (en) | Mobile terminal APP automatic packaging method and system, electronic device and storage medium | |
| CN115080060A (en) | Application program distribution method, device, equipment, storage medium and program product | |
| Jenkins et al. | Jenkins | |
| CN110727575B (en) | Information processing method, system, device and storage medium | |
| CN109726104B (en) | Test packet generation method of mobile terminal, test terminal and storage medium | |
| CN112445513A (en) | Installation package processing method and device | |
| CN108170588B (en) | Test environment construction method and device | |
| CN104965719A (en) | Method and apparatus for generating an application installation file | |
| CA2772225A1 (en) | Version numbering in single development and test environment | |
| CN112685048A (en) | Application program packaging method, electronic device and storage medium | |
| CN105068796A (en) | Pushing method for patch program set and pushing system for patch program set |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |