CN110187888A - A kind of Pod dissemination method, storage medium, electronic equipment and system - Google Patents
A kind of Pod dissemination method, storage medium, electronic equipment and system Download PDFInfo
- Publication number
- CN110187888A CN110187888A CN201810155323.6A CN201810155323A CN110187888A CN 110187888 A CN110187888 A CN 110187888A CN 201810155323 A CN201810155323 A CN 201810155323A CN 110187888 A CN110187888 A CN 110187888A
- Authority
- CN
- China
- Prior art keywords
- pod
- spec
- component
- jenkins
- parameter
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- 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
Abstract
The invention discloses a kind of Pod dissemination method, storage medium, electronic equipment and systems, are related to field of software development, and this method includes the Jenkins task created in Jenkins tool for carrying out Pod publication；Jenkins parameter is set in the Jenkins task of creation, and the Jenkins parameter is for being arranged component name and version number that spec file to be released corresponds to component；Pod publication script is added into the Jenkins task of creation, Pod publication script is verified for upgrading the local warehouse spec with the locally significant property to spec file to be released, and after being updated based on version number information of the version number of setting to spec file to be released by spec file push to be released into the privately owned warehouse spec.The present invention uses script mode, realizes the automation publication of pod publication, improves developer's development efficiency.
Description
Technical field
The present invention relates to field of software development, and in particular to a kind of Pod dissemination method, storage medium, electronic equipment and is
System.
Background technique
In the exploitation of iOS software, the module of some functional independences is usually packaged into a component, is then write pair
The spec file answered, spec file are the description files of pod, include the letters such as author, description, type, dynamic/static library dependence
It ceases, each dependence packet is known as pod in cocoapods tool, cocoapods tool is opening based on the exploitation of ruby scripting language
Source iOS relies on packet management tool；The spec file write is published to the privately owned warehouse spec by cocoapods tool, by group
The process in the spec file distribution of part to the privately owned warehouse spec is exactly the publication of pod.
Be usually using the process that cocoapods tool carries out the publication of pod: the upgrading of operation related command is local first
The warehouse spec, the related command that reruns carry out the validity check of pod, the validity inspection of pod if component engineering is complex
Looking into step will be extremely time-consuming, to be checked to beat tag to component warehouse to component warehouse operation git tag order by rear, then transport
Component changing push to the long-range warehouse git is finally run pod repo push order component is corresponding by row git push order
Spec file push to the privately owned warehouse spec, if component comparison between projects are complicated, this same step will be very time-consuming.The above step
Rapid manual operations carries out step by step, and needs just to can be carried out further work after waiting each step to be finished, and works as certain
One walks out of existing mistake, then needs to repeat relevant operation, time-consuming and laborious, significantly reduces software development efficiency.
Summary of the invention
In view of the deficiencies in the prior art, the purpose of the present invention is to provide a kind of Pod dissemination methods, using script
Mode realizes the automation publication of pod publication, improves developer's development efficiency.
To achieve the above objectives, the technical solution adopted by the present invention is that, comprising:
The Jenkins task for carrying out Pod publication is created in Jenkins tool；
Jenkins parameter is set in the Jenkins task of creation, and the Jenkins parameter is to be released for being arranged
Spec file corresponds to component name and the version number of component；
Pod publication script is added into the Jenkins task of creation, the Pod publication script is for upgrading local spec
Warehouse is verified with the locally significant property to spec file to be released, and based on the version number of setting to spec file to be released
Version number information be updated after by spec file push to be released into the privately owned warehouse spec.
Based on the above technical solution,
The process in the spec file distribution of component to the privately owned warehouse spec is Pod publication；
The component by iOS develop in multiple functional independence modules encapsulate.
Based on the above technical solution,
The Jenkins parameter includes SPEC_NAME parameter and POD_VERSION parameter；
The SPEC_NAME parameter is for being arranged the component name that spec file to be released corresponds to component, and the SPEC_
NAME parameter is character string type, no default parameter value；
The POD_VERSION parameter is for being arranged the version number that spec file to be released corresponds to component, and the POD_
VERSION parameter is character string type, and default parameter value is -1.
Based on the above technical solution, the Pod publication script executes Pod before upgrading the local warehouse spec
Script is issued to execute following steps:
A: setting in the Jenkins task of creation, the ground in the component name splicing component warehouse based on setting
Location；
B: the address of the component warehouse based on splicing downloads spec file to be released and corresponds to the component code of component extremely
Under the working space catalogue of Jenkins task；
C: whether the parameter value for checking the POD_VERSION parameter of setting is -1, if then exiting holding for Pod publication script
Row, if it is not, then going to step D；
D: the version number of the component code judgement setting based on downloading whether there is, and then exit Pod publication script if it exists
Execution, if it is not, then going to step E；
E: judging that download component code corresponds to the spec file of component and whether there is, and then exits Pod publication foot if it does not exist
This execution, if it is not, then carrying out the upgrading in the local warehouse spec.
Based on the above technical solution,
The version number of updated spec file to be released is the version number using POD_VERSION parameter setting；
After version number's modification information of spec file to be released is committed to component warehouse, tag is beaten to component warehouse and by tag
Remote component warehouse is pushed to, by spec file push to be released into the privately owned warehouse spec.
The present invention also provides a kind of storage medium, computer program, the computer program are stored on the storage medium
Method described above is realized when being executed by processor.
The present invention also provides a kind of electronic equipment, including memory and processor, stored on a processor on memory
The computer program of operation, the processor realize method described above when executing the computer program.
The present invention also provides a kind of Pod delivery systems, comprising:
Creation module is used to create the Jenkins task for carrying out Pod publication in Jenkins tool；
Setup module, is used to be arranged in the Jenkins task of creation Jenkins parameter, and the Jenkins parameter is used
Component name and the version number of component are corresponded in setting spec file to be released；
Execution module is used to add Pod publication script into the Jenkins task of creation, and the Pod publication script is used
It is verified in the upgrading local warehouse spec with the validity to spec file to be released, and based on the version number of setting to pending
The version number information of cloth spec file be updated after by spec file push to be released into the privately owned warehouse spec.
Based on the above technical solution, the process in the spec file distribution of component to the privately owned warehouse spec is Pod hair
Cloth；The component by iOS develop in multiple functional independence modules encapsulate.
Based on the above technical solution,
The Jenkins parameter includes SPEC_NAME parameter and POD_VERSION parameter；
The SPEC_NAME parameter is for being arranged the component name that spec file to be released corresponds to component, and the SPEC_
NAME parameter is character string type, no default parameter value；
The POD_VERSION parameter is for being arranged the version number that spec file to be released corresponds to component, and the POD_
VERSION parameter is character string type, and default parameter value is -1.
Compared with the prior art, the advantages of the present invention are as follows: it is based on Jenkins tool, is created in Jenkins tool
Pod issues relevant Jenkins task, and then using the mechanism of Pod publication script, the version number of spec file to be released is believed
Breath is pushed in the privately owned warehouse spec after being updated, and completes the automatic publication of Pod publication, without artificially being intervened, entirely
Issuing process is simple and automatic, effectively improves developer for the development efficiency of software.
Detailed description of the invention
Fig. 1 is a kind of flow chart of Pod dissemination method in the embodiment of the present invention；
Fig. 2 is the structural schematic diagram of a kind of electronic equipment of the embodiment of the present invention.
Specific embodiment
Invention is further described in detail with reference to the accompanying drawings and embodiments.
Shown in Figure 1, the embodiment of the present invention provides a kind of Pod dissemination method, is based on Jenkins tool, for realizing
Exploitation to iOS software, Jenkins tool are a kind of continuous integrating tools based on java language development, are continued for monitoring
Duplicate work, is an open source software project, and the embodiment of the present invention realizes Pod hair on the basis of being based on Jenkins tool
The automatical and efficient completion of cloth.The Pod dissemination method of the embodiment of the present invention specifically includes:
S1: the Jenkins task for carrying out Pod publication is created in Jenkins tool.Pod is issued, component
The process in spec file distribution to the privately owned warehouse spec is Pod publication.Component by iOS develop in multiple functional independence modules seal
It fills, in the prior art, the exploitation for iOS software generally uses modular development scheme, uses in exploitation
It include the module of functional independence in module.Creation for Jenkins task, specifically:
S101: grassroot project is selected in Jenkins tool；
S102: selection " software project of one free style of building "；
S103: Pod_Repo_Push is inputted in task title bar；
S104: clicking creation, that is, creates one for carrying out the Jenkins task of Pod publication, so that subsequent can be with base
The publication of Pod is carried out in Jenkins tool.
S2: Jenkins parameter is set in the Jenkins task of creation, and Jenkins parameter is for being arranged spec to be released
File corresponds to component name and the version number of component.Specifically, Jenkins parameter includes SPEC_NAME parameter and POD_VERSION
Parameter, wherein SPEC_NAME parameter is for being arranged the component name that spec file to be released corresponds to component, and SPEC_NAME parameter
For character string type, no default parameter value；POD_VERSION parameter is for being arranged the version that spec file to be released corresponds to component
Number, and POD_VERSION parameter is character string type, default parameter value is -1.By being arranged in Jenkins task
Jenkins parameter, that is, the form of input parameter, carries out component name and version number that spec file to be released corresponds to component
Input, spec file to be released is corresponded into the component name of component and version number is input in Jenkins tool, in order to subsequent
Operation.
S3: in the Jenkins task of addition Pod publication script to creation, Pod publication script is for upgrading the local storehouse spec
Library is verified with the locally significant property to spec file to be released, and based on the version number of setting to spec file to be released
Version number information be updated after by spec file push to be released into the privately owned warehouse spec, the process specifically: operation
Then " podupdate " order upgrading local warehouse spec runs the local that " pod lib lint " order carries out spec file
Validation verification, exits the execution of Pod publication script if authentication failed, otherwise runs " sed " order to spec text to be released
The version number information of part is updated, and then runs " pod repo push " order for spec file push to the privately owned storehouse spec
In library, the privately owned warehouse spec is the warehouse spec that software supplier uses intra-company git service tray, and the warehouse spec is to use
Come the warehouse git of trustship spec file, git is a free, open source distributed version control system.
In one embodiment, Pod issue script before upgrade the local warehouse spec, execution Pod issue script with
Execute following steps:
A: operation " export LANG=en_US.UTF-8&&export LANGUAGE=en_US.UTF-8&&export
LC_ALL=en_US.UTF-8 " sets in the Jenkins task of creation, because cocoapods tool is to use
The exploitation of ruby scripting language, it is therefore desirable to which character set is set, and otherwise Pod order can be executed and be reported an error, and be then based on the group of setting
The address in part name splicing component warehouse；
B: the address of the component warehouse based on splicing, operation " git clone " command download spec file to be released are corresponding
Under the component code of component to the working space catalogue of Jenkins task；
C: whether the parameter value for checking the POD_VERSION parameter of setting is -1, is moved back if then running order " exit 1 "
Pod issues the execution of script out, and prints " parameter error ", if it is not, then going to step D；
D: operation " tag=$ (echo`/usr/bin/git tag | grep $ POD_VERSION`) " order, to be based on down
The version number of the component code judgement setting of load whether there is, and then runs order " exit 1 " if it exists and exits Pod publication script
Execution, and " version number is existing " is printed, if it is not, then going to step E；
E: operation " if [！- f " $ SPEC_NAME.podspec "] " command determination download component code corresponds to the spec of component
File whether there is, and then runs order " exit 1 " if it does not exist and exits the execution of Pod publication script, and prints " parameter mistake
Accidentally ", if it is not, then carrying out the upgrading in the local warehouse spec.
Above-mentioned steps, which are equivalent to, joined fault tolerance judgment mechanism before upgrading the local warehouse spec, guarantee Pod publication
The generation that certain faulty operations are also prevented while efficiently progress is further ensured that the high efficiency of Pod publication automation carries out,
Promote the software development efficiency of software developer.
The version number of updated spec file to be released is the version number using POD_VERSION parameter setting；It is pending
After version number's modification information of cloth spec file is committed to component warehouse, tag is beaten to component warehouse and tag is pushed to long-range group
Part warehouse, by spec file push to be released into the privately owned warehouse spec, version number's modification information of spec file to be released is
Show the information that the version number of spec file to be released has changed, the version of component warehouse spec file to be released is informed with this
It number has changed.Tag is beaten to be usually used in that version is marked.
Certainly, it after spec file push to be released is into the privately owned warehouse spec, is added in Jenkins tool
Jenkins is operated after executing, and Jenkins mail notification is arranged, and Jenkins tool provides the mechanism operated after a kind of execution,
By this mechanism, Jenkins task execution can be allowed to execute a customized operation again after finishing, therefore postal can be added
Part notice operation, specifically: addition mail notification inbox, it can be logical to mail hair mail after Jenkins task execution is complete
Know；Add email template；Add mail trigger event, add successfully and unsuccessfully two events.By email notice mechanism,
Developer can be made to receive the notice of Pod publication success or failure in time, without waiting the execution of task always, to mention
Rise the working efficiency of developer.
The principle of the Pod dissemination method of the embodiment of the present invention is, is based on Jenkins tool, creates in Jenkins tool
It builds Pod and issues relevant Jenkins task, then using the mechanism of Pod publication script, by the version number of spec file to be released
Information is pushed in the privately owned warehouse spec after being updated, and completes the automatic publication of Pod publication, whole without artificially being intervened
A issuing process is simple and automatic, effectively improves developer for the development efficiency of software.
In addition, corresponding above-mentioned Pod dissemination method is stored with meter the present invention also provides a kind of storage medium on storage medium
Calculation machine program, when computer program is executed by processor the step of Pod dissemination method described in realization the various embodiments described above.It needs
Illustrate, the storage medium includes USB flash disk, mobile hard disk, ROM (Read-Only Memory, read-only memory), RAM
Various Jie that can store program code such as (Random Access Memory, random access memory), magnetic or disk
Matter.
It is shown in Figure 2, corresponding above-mentioned Pod dissemination method, the present invention also provides a kind of electronic equipment, including memory and
Processor, the computer program run on a processor is stored on memory, and processor is realized when executing computer program
State the Pod dissemination method of each embodiment.
The embodiment of the present invention also provides a kind of Pod delivery system based on above-mentioned Pod dissemination method, including creation module,
Setup module and execution module.
Creation module is used to create the Jenkins task for carrying out Pod publication in Jenkins tool；Setup module
For Jenkins parameter to be arranged in the Jenkins task of creation, the Jenkins parameter is for being arranged spec text to be released
Part corresponds to component name and the version number of component；Execution module is used to add Pod publication script into the Jenkins task of creation,
Pod publication script is verified for upgrading the local warehouse spec with the validity to spec file to be released, and based on setting
Version number the version number information of spec file to be released is updated after by spec file push to be released to privately owned spec
In warehouse.
The process in the spec file distribution of component to the privately owned warehouse spec is Pod publication；The component by iOS develop in it is more
A functional independence module encapsulates.The Jenkins parameter includes SPEC_NAME parameter and POD_VERSION parameter；
SPEC_NAME parameter is for being arranged the component name that spec file to be released corresponds to component, and SPEC_NAME parameter is character string class
Type, no default parameter value；POD_VERSION parameter is for being arranged the version number that spec file to be released corresponds to component, and POD_
VERSION parameter is character string type, and default parameter value is -1.
The version number of updated spec file to be released is the version number using POD_VERSION parameter setting；It is pending
After version number's modification information of cloth spec file is committed to component warehouse, tag is beaten to component warehouse and tag is pushed to long-range group
Part warehouse, by spec file push to be released into the privately owned warehouse spec.
The principle of the Pod delivery system of the embodiment of the present invention is that creation module is based on Jenkins tool, in Jenkins
Pod is created in tool and issues relevant Jenkins task, and then execution module, will be to be released using the mechanism of Pod publication script
The version number information of spec file is pushed in the privately owned warehouse spec after being updated, and is completed the automatic publication of Pod publication, is not necessarily to
Artificially intervened, entire issuing process is simple and automatic, effectively improves developer for the development efficiency of software.
The present invention is not limited to the above-described embodiments, for those skilled in the art, is not departing from
Under the premise of the principle of the invention, several improvements and modifications can also be made, these improvements and modifications are also considered as protection of the invention
Within the scope of.The content being not described in detail in this specification belongs to the prior art well known to professional and technical personnel in the field.
Claims (10)
1. a kind of Pod dissemination method is based on Jenkins tool characterized by comprising
The Jenkins task for carrying out Pod publication is created in Jenkins tool；
Jenkins parameter is set in the Jenkins task of creation, and the Jenkins parameter is for being arranged spec text to be released
Part corresponds to component name and the version number of component；
Pod publication script is added into the Jenkins task of creation, the Pod publication script is for upgrading the local warehouse spec
It is verified with the locally significant property to spec file to be released, and based on the version number of setting to the version of spec file to be released
This number information be updated after by spec file push to be released into the privately owned warehouse spec.
2. a kind of Pod dissemination method as described in claim 1, it is characterised in that:
The process in the spec file distribution of component to the privately owned warehouse spec is Pod publication；
The component by iOS develop in multiple functional independence modules encapsulate.
3. a kind of Pod dissemination method as described in claim 1, it is characterised in that:
The Jenkins parameter includes SPEC_NAME parameter and POD_VERSION parameter；
The SPEC_NAME parameter is for being arranged the component name that spec file to be released corresponds to component, and the SPEC_NAME joins
Number is character string type, no default parameter value；
The POD_VERSION parameter is for being arranged the version number that spec file to be released corresponds to component, and the POD_
VERSION parameter is character string type, and default parameter value is -1.
4. a kind of Pod dissemination method as claimed in claim 3, it is characterised in that: the Pod publication script is local in upgrading
Before the warehouse spec, Pod publication script is executed to execute following steps:
A: setting in the Jenkins task of creation, the address in the component name splicing component warehouse based on setting；
B: the address of the component warehouse based on splicing downloads spec file to be released and corresponds to the component code of component to Jenkins
Under the working space catalogue of task；
C: whether the parameter value for checking the POD_VERSION parameter of setting is -1, if then exiting the execution of Pod publication script,
If it is not, then going to step D；
D: the version number of the component code judgement setting based on downloading whether there is, and then exit holding for Pod publication script if it exists
Row, if it is not, then going to step E；
E: judging that download component code corresponds to the spec file of component and whether there is, and then exits Pod publication script if it does not exist
It executes, if it is not, then carrying out the upgrading in the local warehouse spec.
5. a kind of Pod dissemination method as claimed in claim 4, it is characterised in that:
The version number of updated spec file to be released is the version number using POD_VERSION parameter setting；
After version number's modification information of spec file to be released is committed to component warehouse, tag is beaten to component warehouse and pushes tag
To remote component warehouse, by spec file push to be released into the privately owned warehouse spec.
6. a kind of storage medium, computer program is stored on the storage medium, it is characterised in that: the computer program is located
Reason device realizes method described in any one of claim 1 to 5 when executing.
7. a kind of electronic equipment, including memory and processor, the computer journey run on a processor is stored on memory
Sequence, it is characterised in that: the processor realizes method described in any one of claim 1 to 5 when executing the computer program.
8. a kind of Pod delivery system characterized by comprising
Creation module is used to create the Jenkins task for carrying out Pod publication in Jenkins tool；
Setup module is used to be arranged in the Jenkins task of creation Jenkins parameter, and the Jenkins parameter is for setting
Set component name and version number that spec file to be released corresponds to component；
Execution module is used to add Pod publication script into the Jenkins task of creation, and the Pod publication script is for rising
The grade local warehouse spec is verified with the validity to spec file to be released, and based on the version number of setting to be released
The version number information of spec file be updated after by spec file push to be released into the privately owned warehouse spec.
9. a kind of Pod delivery system as claimed in claim 8, it is characterised in that: the spec file distribution of component is to privately owned
The process in the warehouse spec is Pod publication；The component by iOS develop in multiple functional independence modules encapsulate.
10. a kind of Pod delivery system as claimed in claim 8, it is characterised in that:
The Jenkins parameter includes SPEC_NAME parameter and POD_VERSION parameter；
The SPEC_NAME parameter is for being arranged the component name that spec file to be released corresponds to component, and the SPEC_NAME joins
Number is character string type, no default parameter value；
The POD_VERSION parameter is for being arranged the version number that spec file to be released corresponds to component, and the SPEC_NAME
Parameter is character string type, and default parameter value is -1.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810155323.6A CN110187888A (en) | 2018-02-23 | 2018-02-23 | A kind of Pod dissemination method, storage medium, electronic equipment and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810155323.6A CN110187888A (en) | 2018-02-23 | 2018-02-23 | A kind of Pod dissemination method, storage medium, electronic equipment and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110187888A true CN110187888A (en) | 2019-08-30 |
Family
ID=67713418
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810155323.6A Pending CN110187888A (en) | 2018-02-23 | 2018-02-23 | A kind of Pod dissemination method, storage medium, electronic equipment and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110187888A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111399810A (en) * | 2020-03-11 | 2020-07-10 | 杭州涂鸦信息技术有限公司 | iOS application program dynamic componentization development method, system and equipment thereof |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106254491A (en) * | 2016-08-17 | 2016-12-21 | 成都聚美优品科技有限公司 | A kind of stable IOS client framework model efficiently |
| CN107391968A (en) * | 2017-08-18 | 2017-11-24 | 武汉斗鱼网络科技有限公司 | A kind of method and device for realizing privately owned pod issues control of authority |
-
2018
- 2018-02-23 CN CN201810155323.6A patent/CN110187888A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106254491A (en) * | 2016-08-17 | 2016-12-21 | 成都聚美优品科技有限公司 | A kind of stable IOS client framework model efficiently |
| CN107391968A (en) * | 2017-08-18 | 2017-11-24 | 武汉斗鱼网络科技有限公司 | A kind of method and device for realizing privately owned pod issues control of authority |
Non-Patent Citations (2)
| Title |
|---|
| JY.C: "iOS+Jenkins+CocoaPods 管理私有库", 《HTTPS://WWW.CNBLOGS.COM/EN815/P/8243599.HTML》 * |
| RIPPERHE: "一行命令发布 Pod 框架", 《HTTPS://JUEJIN.CN/POST/6844903472320495629/》 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111399810A (en) * | 2020-03-11 | 2020-07-10 | 杭州涂鸦信息技术有限公司 | iOS application program dynamic componentization development method, system and equipment thereof |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107577469B (en) | software packaging and publishing management method | |
| CN101876943B (en) | Systems and methods for identifying a relationship between multiple interrelated applications in a mainframe environment | |
| Tsai et al. | End-to-end integration testing design | |
| CN106777101B (en) | Data processing engine | |
| US20180253296A1 (en) | Software kit release management | |
| CN111428431B (en) | Automatic test and recording method and system supporting EDA software | |
| US9658842B2 (en) | Application runtime expert for deployment of an application on multiple computer systems | |
| CN103164328A (en) | Method and device and system for regression testing of service function | |
| US11138097B2 (en) | Automated web testing framework for generating and maintaining test scripts | |
| CN103646104A (en) | Hard real-time fault diagnosis method and system | |
| CN103279419A (en) | Automation version verifying method and system based on B/S structural system | |
| CN111897566A (en) | Software development continuous integration method, device, equipment and medium | |
| CN109725906A (en) | A kind of code compiling method and corresponding continuous integration system | |
| CN112561370A (en) | Software version management method and device, computer equipment and storage medium | |
| CN111190814A (en) | Software test case generation method and device, storage medium and terminal | |
| CN111124642A (en) | Automatic flow method and system allowing cloud management platform to be customized | |
| CN104484275A (en) | Method and system capable of remotely testing smart cards | |
| CN110187888A (en) | A kind of Pod dissemination method, storage medium, electronic equipment and system | |
| CN112527312B (en) | Test method and test device for embedded system | |
| CN110851516B (en) | Host operation control system and method | |
| US11301246B2 (en) | Automatically generating continuous integration pipelines | |
| CN114281367A (en) | Big data platform deployment method and system for trust and creation environment | |
| CN112783653A (en) | Resource scheduling method and device based on containerization | |
| CN112269776A (en) | Database operation and maintenance management platform | |
| CN116795378B (en) | Method and device for arranging and executing process based on code dynamic compiling |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20190830 |