CN115421781A - Shell script-based IOS (input/output) end project automatic packaging method - Google Patents

Shell script-based IOS (input/output) end project automatic packaging method Download PDF

Info

Publication number
CN115421781A
CN115421781A CN202211373412.0A CN202211373412A CN115421781A CN 115421781 A CN115421781 A CN 115421781A CN 202211373412 A CN202211373412 A CN 202211373412A CN 115421781 A CN115421781 A CN 115421781A
Authority
CN
China
Prior art keywords
warehouse
release
sdk
script
app
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
Application number
CN202211373412.0A
Other languages
Chinese (zh)
Inventor
杜晗
白剑
黄海亮
梁瑛玮
张海林
鲁和平
李长杰
陈焕然
李乐
王浩
洪行健
冷冬
丁一
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Yifang Information Technology Co ltd
Original Assignee
Yifang Information Technology Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Yifang Information Technology Co ltd filed Critical Yifang Information Technology Co ltd
Priority to CN202211373412.0A priority Critical patent/CN115421781A/en
Publication of CN115421781A publication Critical patent/CN115421781A/en
Pending legal-status Critical Current

Links

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
    • G06F8/447—Target code generation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45504—Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
    • G06F9/45508—Runtime interpretation or emulation, e g. emulator loops, bytecode interpretation
    • G06F9/45512—Command shells

Abstract

The invention provides an IOS end project automatic packaging method based on a shell script, which comprises the steps of configuring relevant parameters of SDK and APP projects which can be issued by the script; pulling the latest configuration of the script; configuring a local path attribute value of a development warehouse, a local path attribute value of a release warehouse and a version number attribute value of a release SDK; selecting release content through a shell script; and controlling the shell script to complete the compiling, packing and releasing of the SDK project and the APP project by managing the file information. The invention achieves the purpose of controlling the shell script by rewriting the management file information, wherein the shell script can fix the operation steps of SDK and APP packaging and issuing, thereby simplifying the operation flow, improving the efficiency and reducing the threshold of issuing work.

Description

Shell script-based IOS (input/output) end project automatic packaging method
Technical Field
The invention relates to the technical field of computer software, in particular to a shell script-based IOS (input/output) end project automatic packaging method.
Background
The project at the IOS end manages codes of different SDK and APP projects through different branches of a plurality of git development warehouses, wherein when the SDK and APP are released, developers need to switch the different branches and carry out different operations according to the project flow, and obvious defects are as follows:
(1) Developers are required to know project flows and corresponding branches of different SDK and APP projects;
(2) The packaging operation process is complex, and whether the process steps are wrong or not needs to be confirmed in real time.
Disclosure of Invention
Aiming at the defects of the prior art, the invention provides an IOS end project automatic packaging method based on shell scripts, which solves the defect that when an SDK and an APP are released, developers need to know different project flows and corresponding branches, and the release efficiency is low due to the complex packaging flow.
The technical scheme of the invention is realized as follows:
an IOS end project automatic packaging method based on shell scripts comprises the following steps:
step S1: configuring related parameters of SDK and APP projects which can be issued by a script, wherein the related parameters comprise an SDK name, an APP name, a branch name corresponding to the APP, an issued SKD array attribute value and an issued APP array attribute value, and all the related parameters are recorded in a plist file;
step S2: after the configuration is finished, pushing the configured SDK and APP items to a script git warehouse through git push, and then pulling the latest configuration of the script through git pull;
and step S3: before executing the script, configuring a local path attribute value of a development warehouse, a local path attribute value of a release warehouse and a version number attribute value of an SDK in a script plist file so as to achieve the aim that the script can operate the local warehouse;
and step S4: selecting and executing the flow of the release content through the shell script instruction read-p, and continuing to execute the step S5 when the release content is selected as the SDK; when the release content is selected to be APP, skipping to execute the step S6;
step S5: when the release content is the SDK, the shell script reads and confirms local path attribute values of a development warehouse and a release warehouse, after the local path attribute values are confirmed to be not empty, the corresponding name of each SDK is obtained by reading the attribute value of the release SDK array in the plist file, the version number of the corresponding release SDK in the plist file is read through the name of each SDK, the development warehouse is compiled according to the version number of the release SDK and the shell script to obtain the SDK, and the SDK is copied to the release warehouse through the shell script to realize the package release of the SDK;
step S6: when the release content is the APP, the shell script reads and confirms the local path attribute values of the development warehouse and the release warehouse, after the local path attribute values are confirmed to be not empty, the branch names corresponding to the APPs are obtained by reading the release APP array attribute values in the plist file, corresponding branch codes in the development warehouse are pulled according to the branch names, the branch codes are compiled through the shell script, and the package release of the APPs is completed.
Further, in step S5 and step S6: and reading the local path attribute value of the development warehouse and the local path attribute value of the release warehouse in the plist file through the/usr/libexec/PlistBuddy-c.
Further, in step S5 and step S6: after reading the plist file, confirming that the local path attribute value of the development warehouse or the local path attribute value of the release warehouse is empty, prompting a developer to not configure the path attribute value through an instruction echo by the shell script, and executing an instruction exit script.
Further, in step S5: and compiling the development warehouse through the shell instruction xcodebuild to obtain the SDK.
Furthermore, in step S5, before the SDK is copied to the release warehouse, the shell script reads the dependency configuration of the files in the development warehouse and the release warehouse through the instruction, respectively, to obtain the dependency keyword and the dependency version value, and then completes the dependency replacement of the files in the release warehouse and the development warehouse through the shell instruction, thereby realizing the automatic configuration dependency.
Further, in step 6, before pulling the branch code, judging whether the development warehouse has a corresponding branch through the shell script, if not, checking whether the development warehouse pulls the corresponding branch, and if not, switching to the corresponding branch through an instruction git checkout-b.
Furthermore, in step 6, before APP packaging and releasing, developers need to upload corresponding packaging configuration plist files to a release warehouse according to different APP packaging configurations.
Compared with the prior art, the invention has the following beneficial effects: the invention discloses an IOS end project automatic packaging method based on a shell script, which achieves the purpose of controlling the shell script by rewriting management file information, wherein the shell script can fix the operation steps of SDK and APP packaging and releasing, simplifies the operation process, reduces the occurrence of low efficiency of an operator due to unfamiliarity of the process and step errors, and can operate the script to package and release the SDK and the APP only by modifying the branch name, the related parameters, the local path attribute and the version number attribute of the corresponding project without knowing the different project processes and the corresponding branches during operation, thereby improving the efficiency and reducing the threshold of the release work.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 shows a flow chart of a shell script-based IOS-side project automation packaging method.
Detailed Description
In order that the above objects, features and advantages of the embodiments of the present disclosure can be more clearly understood, embodiments of the present disclosure will be described in further detail below with reference to the accompanying drawings and detailed description. It should be noted that the embodiments and features of the embodiments of the present application may be combined with each other without conflict.
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure, however, the embodiments of the disclosure may be practiced otherwise than as described herein, and therefore the scope of the embodiments of the disclosure is not limited by the specific embodiments disclosed below.
First, the description or definition will be made with respect to terms where there are associated, where:
shell: the operating system command interpreter starts, suspends and terminates the running of programs or controls a computer by receiving shell instructions input by a user;
shell script: a file consisting of shell instructions;
IOS: an operating system of the iphone;
and (3) SDK: a Software Development Kit (Software Development Kit), a collection of Development tools for a Software engineer to build application Software for a particular Software package, software framework, hardware platform, operating system, etc.;
APP: mobile phone software (Application), mainly refers to software installed on a smart phone, and improves the defects and individuation of an original system;
git: an open-source distributed version control system can simplify the release of a source code without the support of server-side software;
branching: storing the whole flow of the modification record in a bifurcation way, wherein different branches can submit different modifications;
plist document: the attribute table file is used for storing user settings and can also be used for storing file binding information;
and (3) developing a warehouse: the system is a warehouse used for software development in developers, contains source codes of projects, and is not public;
releasing a warehouse: the method refers to a warehouse for developers to issue SDK and APP to the outside, and files in the warehouse are issued to products generated by compiling the development warehouse.
As shown in fig. 1, according to a specific embodiment of the present invention, the present invention provides a shell script-based automated packaging method for an IOS-side project, which includes the following steps:
step S1: configuring related parameters of SDK and APP projects which can be issued by a script, wherein the related parameters comprise an SDK name, an APP name, a branch name corresponding to the APP, an issued SKD array attribute value and an issued APP array attribute value, and all the related parameters are recorded in a plist file;
in the embodiment of the invention, the shell script executes the process steps of the shell script by reading the relevant parameters of the SDK and APP projects, and the manager configures the relevant parameters of the SDK project and the APP project which can be released, so that the aim of controlling the release of the SDK and the APP by the shell script is realized, the operation process is simplified, and the threshold of the release work is reduced.
Step S2: after the configuration is finished, pushing the configured SDK and APP items to a script git warehouse through git push, and then pulling the latest configuration of the script through git pull;
it can be known that the script git warehouse manages SDK and APP projects for an open-source distributed control system, the SDK and APP projects of brand-new configuration can generate new branches in the script git warehouse, the branches store modification records of management personnel for the SDK and APP projects, each modification configuration is ensured to be recorded, and developers can conveniently pull the SDK and APP projects after each modification.
And step S3: before executing the script, configuring a local path attribute value of a development warehouse, a local path attribute value of a release warehouse and a version number attribute value of an SDK in a script plist file so as to achieve the aim that the script can operate the local warehouse;
in the implementation mode of the invention, the shell script executes the issuing process of the SDK project and the APP project through the development warehouse local path attribute value and the issuing warehouse local path attribute value recorded in the plist file, wherein the development warehouse local path attribute value can enable the shell script to judge whether the SDK project and the APP project issued correspondingly in the issuing process are correct or not, a path for pulling the SDK project and the APP project code is also provided, the issuing warehouse local path attribute value is also used as the shell script to judge whether the SDK project and the APP project issued correspondingly in the issuing process are correct or not, and the path attribute value copied to the issuing warehouse by the code is also provided.
And step S4: selecting and executing the flow of the release content through the shell script instruction read-p, and continuing to execute the step S5 when the release content is selected as the SDK; when the release content is selected to be APP, skipping to execute the step S6;
in the embodiment of the invention, the release content mainly comprises an SDK project and an APP project, a developer selects the release content by executing an instruction read-p through a shell script, the shell script judges different process steps executed by the script according to a characteristic value input by the developer, and at the moment, the developer needs to input different characteristic values corresponding to different release contents, such as: inputting '1' to release a certain SDK project, inputting '2' to release a certain APP project, and exiting the shell script when inputting a non-characteristic value, thereby simplifying the operation flow of releasing the SDK project or the APP project.
Step S5: when the release content is the SDK, the shell script reads and confirms local path attribute values of a development warehouse and a release warehouse, after the local path attribute values are confirmed to be not empty, the corresponding name of each SDK is obtained by reading the attribute value of the release SDK array in the plist file, the version number of the corresponding release SDK in the plist file is read through the name of each SDK, the development warehouse is compiled according to the version number of the release SDK and the shell script to obtain the SDK, and the SDK is copied to the release warehouse through the shell script to realize the package release of the SDK;
in the embodiment of the invention, the shell script is controlled to select the release content to be the SDK, and the shell script reads the local path attribute value of the development warehouse and the local path attribute value of the release warehouse in the plist file through the instruction/usr/libexec/PlistBuddy-c.
When the local path attribute value of the development warehouse is read or the local path attribute value of the release warehouse is a null value, the shell script prompts that the local path attribute value corresponding to the distributable SDK in the development warehouse or the release warehouse is not configured through an instruction echo, then an instruction exit script is executed, and at the moment, the step S3 is required to be skipped to reconfigure the local path attribute value of the development warehouse or the local path attribute value of the release warehouse which is missing in the plist file of the distributable SDK.
Further, when the read local path attribute value of the development warehouse or the local path attribute value of the release warehouse is not a null value, reading the release SDK array attribute value in the plist file to obtain each SDK name, reading the version number of the corresponding release SDK in plist through the SDK name, compiling the local development warehouse by the shell script through the command xcodebuild to obtain each compilation product, wherein the compilation products are the release SDKs, copying the SDKs to the local release warehouse through the command copy of the shell script according to the read version number of the release SDKs, and the copying process needs to use the local path attribute value of the development warehouse and the local path attribute value of the release warehouse.
Furthermore, before the SDK is issued, the shell script reads the dependency configuration of the file in the local development warehouse line by line through an instruction sed-n-e/a keyword to obtain a dependency keyword and a dependency version value, then reads the dependency configuration of the local release warehouse file line by line through the instruction sed-n-e/the keyword to complete the dependency replacement of the local development warehouse file and the local release warehouse file through an instruction sed-i' -e to realize the automatic configuration dependency, and after the dependency configuration is completed, the shell script issues the SDK of the local release warehouse through instructions git add and git unit put.
Step S6: when the release content is the APP, the shell script reads and confirms the local path attribute values of the development warehouse and the release warehouse, after the local path attribute values are confirmed to be not empty, the branch names corresponding to the APPs are obtained by reading the release APP array attribute values in the plist file, corresponding branch codes in the development warehouse are pulled according to the branch names, the branch codes are compiled through the shell script, and the package release of the APPs is completed.
In the embodiment of the invention, the shell script is controlled to select the release content to be APP, and the shell script reads the local path attribute value of the development warehouse and the local path attribute value of the release warehouse in the plist file through the instruction/usr/libexec/PlistBuddy-c.
When the shell script reads a local path attribute value of the development warehouse or a local path attribute value of the release warehouse to be a null value, the shell script prompts that a local path attribute value corresponding to the distributable APP in the development warehouse or the release warehouse is not configured through an instruction echo, then an instruction exit script is executed, and at the moment, a step S3 is required to be skipped to reconfigure a development warehouse local path attribute value or a release warehouse local path attribute value which is missing in a plist file of the distributable APP.
Further, when the local path attribute value read by the shell script to the development warehouse or the local path attribute value of the development warehouse is not null, the shell script passes through the instruction/usr/libexec/PlistBu
Ddy-c reads the attribute value of the published APP array in the plist file capable of publishing the APP, thereby obtaining the branch name corresponding to each APP.
Further, before pulling the corresponding branch of the APP, if the branch name is wrong, the shell script executes the instruction exit script; if the branch name is correct, the shell script executes the instruction git rev-parse-abbrev-ref HEAD to judge whether a corresponding branch exists in the local warehouse or not, if the corresponding branch does not exist, the shell script checks whether the local warehouse pulls the corresponding branch or not through the instruction git rev-parse-verify, if the local warehouse already has the corresponding branch, the shell script is switched to the corresponding branch through the instruction git checkout-f, if the corresponding branch is not pulled, the shell script is switched to the corresponding branch through the instruction git checkout-b, and when the shell script confirms that the local branch is automatically switched, the shell script executes the instruction git pull to pull the branch code of the corresponding branch.
Furthermore, after the shell script automatically draws the branch code, the shell script executes an instruction xcodebuild archive to complete compiling of the branch code, and then completes packaging and issuing of the issuable APP through the instruction codebuild-exportArchive-archive-exportPath-exportoptionPlust.
Furthermore, before the APP packaging and releasing, when the shell script executes an xcodeb-export architecture-archive path-export OptionPlist instruction, the export OptionPlist indicates the address of the packaging configuration Plist file of the APP, if the packaging configuration of the APP is different, developers still need to upload the corresponding packaging configuration Plist file to a script warehouse, and judge that the compiling APP project uses the corresponding execution Plist file before packaging.
The embodiment of the invention configures parameters set by plist files in a script git warehouse, including a local path of a development warehouse, a local path of a release warehouse, a name of a release SDK, a version number of the release SDK, a name of an release APP and a branch name corresponding to the warehouse, reads related parameters in the plist files through instructions when executing shell scripts to realize the control of a script flow, wherein the controlled script flow comprises the types of script release contents, judges whether the related parameters configured by the release contents support the step of executing the script or not, confirms the packaging information of the release contents, developers and managers only need to modify the related parameters set by the plist files and upload the related parameters to the script git warehouse, when the developers and the managers need to use, the related parameters in the script git warehouse are pulled and the shell scripts are executed to realize the release of the SDK and the APP, the operation steps of the SDK and the APP packaging release can be fixed, the operation flow is simplified, the condition that the efficiency is low due to the unfamiliarity of the flow and the step of operators is reduced, the management is convenient, the release efficiency is improved, and the work threshold of the release is reduced.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.

Claims (7)

1. An IOS end project automatic packaging method based on shell script is characterized by comprising the following steps:
step S1: configuring related parameters of SDK and APP projects which can be issued by a script, wherein the related parameters comprise an SDK name, an APP name, a branch name corresponding to the APP, an issued SKD array attribute value and an issued APP array attribute value, and all the related parameters are recorded in a plist file;
step S2: after the configuration is finished, pushing the configured SDK and APP items to a script git warehouse through git push, and then pulling the latest configuration of the script through git pull;
and step S3: before executing the script, configuring a local path attribute value of a development warehouse, a local path attribute value of a release warehouse and a version number attribute value of an SDK in a script plist file so as to achieve the aim that the script can operate the local warehouse;
and step S4: selecting and executing the flow of the release content through the shell script instruction read-p, and continuing to execute the step S5 when the release content is selected as the SDK; when the release content is selected to be APP, skipping to execute the step S6;
step S5: when the release content is the SDK, the shell script reads and confirms local path attribute values of a development warehouse and a release warehouse, obtains each corresponding SDK name by reading the SDK array attribute value released in the plist file after confirming that the local path attribute values are not empty, reads the version number of the corresponding release SDK in the plist file through each SDK name, compiles the development warehouse according to the version number of the release SDK and the shell script to obtain the SDK, and copies the SDK to the release warehouse through the shell script to realize the package release of the SDK;
and S6, when the release content is the APP, the shell script reads and confirms the local path attribute values of the development warehouse and the release warehouse, after the local path attribute values are confirmed to be not empty, the branch name corresponding to the APP is obtained by reading the release APP array attribute value in the plist file, the corresponding branch code in the development warehouse is pulled according to the branch name, and the branch code is compiled through the shell script to complete the packaging and release of the APP.
2. The shell script-based IOS-side item automatic packaging method of claim 1, wherein in step S5 and step S6, the local path attribute value of the development warehouse and the local path attribute value of the release warehouse in the plist file are read through/usr/libexec/plistbudy-c.
3. The shell script-based IOS (input/output) end item automatic packaging method of claim 2, wherein in the step S5 and the step S6, after reading the plist file and confirming that the local path attribute value of the development warehouse or the local path attribute value of the release warehouse is empty, the shell script prompts a developer through an instruction echo that the path attribute value is not configured, and executes an instruction exit script.
4. The shell script-based IOS-side project automation packaging method of claim 1, wherein in the step S5, the SDK is obtained by compiling a development warehouse through a shell instruction xcodebuild.
5. The IOS-end project automation packaging method based on the shell script of claim 1, wherein in the step S5, before copying the SDK to the release warehouse, the shell script reads the dependency configuration of the files in the development warehouse and the release warehouse through an instruction, obtains the dependency keyword and the dependency version value, and completes the dependency replacement of the files in the release warehouse and the development warehouse through the shell instruction, thereby realizing the dependency of the automation configuration.
6. The shell script-based IOS-side project automation packaging method of claim 1, wherein in the step 6, before pulling the branch code, the shell script judges whether the development warehouse has a corresponding branch, if not, the development warehouse is checked whether the corresponding branch is pulled, and if not, the development warehouse is switched to the corresponding branch through an instruction git checkout-b.
7. The shell script-based IOS-end project automation packaging method of claim 1, wherein in step 6, before APP packaging release, developers need to upload corresponding packaging configuration plist files to a release warehouse according to different APP packaging configurations.
CN202211373412.0A 2022-11-04 2022-11-04 Shell script-based IOS (input/output) end project automatic packaging method Pending CN115421781A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211373412.0A CN115421781A (en) 2022-11-04 2022-11-04 Shell script-based IOS (input/output) end project automatic packaging method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211373412.0A CN115421781A (en) 2022-11-04 2022-11-04 Shell script-based IOS (input/output) end project automatic packaging method

Publications (1)

Publication Number Publication Date
CN115421781A true CN115421781A (en) 2022-12-02

Family

ID=84207367

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211373412.0A Pending CN115421781A (en) 2022-11-04 2022-11-04 Shell script-based IOS (input/output) end project automatic packaging method

Country Status (1)

Country Link
CN (1) CN115421781A (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108287694A (en) * 2017-08-08 2018-07-17 深圳壹账通智能科技有限公司 Application builds method, system, computer equipment and storage medium
CN108469957A (en) * 2018-03-08 2018-08-31 平安科技（深圳）有限公司 Using packing method for uploading, device, computer equipment and storage medium
CN108647037A (en) * 2018-04-28 2018-10-12 新疆熙菱信息技术股份有限公司 Automatically dispose method and system based on shell scripts
CN112882700A (en) * 2021-02-09 2021-06-01 京东方科技集团股份有限公司 iOS application program construction method and device, electronic equipment and storage medium
CN114239054A (en) * 2021-11-19 2022-03-25 建信金融科技有限责任公司 iOS application construction method, device, computer equipment and storage medium
CN115248700A (en) * 2021-04-25 2022-10-28 远光软件股份有限公司 Method and system for automatically constructing mobile installation package by product code

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108287694A (en) * 2017-08-08 2018-07-17 深圳壹账通智能科技有限公司 Application builds method, system, computer equipment and storage medium
CN108469957A (en) * 2018-03-08 2018-08-31 平安科技（深圳）有限公司 Using packing method for uploading, device, computer equipment and storage medium
CN108647037A (en) * 2018-04-28 2018-10-12 新疆熙菱信息技术股份有限公司 Automatically dispose method and system based on shell scripts
CN112882700A (en) * 2021-02-09 2021-06-01 京东方科技集团股份有限公司 iOS application program construction method and device, electronic equipment and storage medium
CN115248700A (en) * 2021-04-25 2022-10-28 远光软件股份有限公司 Method and system for automatically constructing mobile installation package by product code
CN114239054A (en) * 2021-11-19 2022-03-25 建信金融科技有限责任公司 iOS application construction method, device, computer equipment and storage medium

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LEWIS海: "iOS成神进阶之Shell脚本打包自动发布篇章", 《简书：HTTPS://WWW.JIANSHU.COM/P/4436FC383C0B》 *

Similar Documents

Publication Publication Date Title
US8601433B2 (en) Method and apparatus for generating virtual software platform based on component model and validating software platform architecture using the platform
US8892953B2 (en) Method and system for test suite control
CN111580832A (en) Application release system and method applied to heterogeneous multi-cloud environment
CN102279789B (en) Debugging system and debugging method for embedded system of production phase
CN108595186B (en) Multi-version software management method based on complete function on Feiteng platform
CN112965785B (en) Container-based micro-service application development method and development platform
CN108897547B (en) Software automation deployment method and device
US11288062B2 (en) Automatic source code refactoring
CN110083360A (en) A kind of Compilation Method of application code, device, equipment and storage medium
CN112882718A (en) Compiling processing method, device, equipment and storage medium
CN112379865B (en) Software development framework updating method based on Maven plug-in mechanism
CN108287720A (en) software compilation method, device, equipment and storage medium
CN105278445A (en) Secondary development method of synchronous generator excitation regulator control program
CN111176912A (en) Relay protection device hardware configuration information management system and method
CN115421781A (en) Shell script-based IOS (input/output) end project automatic packaging method
CN110688140B (en) Code management method and terminal
CN115718619A (en) Visual control logic arrangement method, equipment and medium
KR102094447B1 (en) Apparatus for generating source code of Battery Management System software and method thereof
CN112181483B (en) Plasma control system software development platform and method
CN111078531B (en) Test control system capable of being customized
CN114115890A (en) Micro-service development method and system
US20110041118A1 (en) Menu driven component based build system
CN116360779B (en) Method for constructing micro front end base based on qiankun in Vue CLI application
CN113504913B (en) Automatic Adobe Flex code conversion method
JP2012043215A (en) Debugging method

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