CN112256318B - Construction method and equipment for dependent product - Google Patents
Construction method and equipment for dependent product Download PDFInfo
- Publication number
- CN112256318B CN112256318B CN202011158920.8A CN202011158920A CN112256318B CN 112256318 B CN112256318 B CN 112256318B CN 202011158920 A CN202011158920 A CN 202011158920A CN 112256318 B CN112256318 B CN 112256318B
- Authority
- CN
- China
- Prior art keywords
- information
- construction
- description information
- product
- dependency
- 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.)
- Active
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/43—Checking; Contextual analysis
- G06F8/433—Dependency analysis; Data or control flow analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Abstract
The method comprises the steps of obtaining existing dependency relationship description information of a dependent product from a local database; preprocessing the acquired dependency relationship description information to obtain code information to be compared; updating the construction mark number of the dependent product according to the code information to be compared and adding updated identification information to obtain new dependency relationship description information according to the updated construction mark number and the updated identification information; and triggering the script to execute a construction task based on the new dependency description information. The method can be automatically built through remodeling, starts from the updating demand source of the interdependent product, and rebuilds the task through the dependency relationship description information, so that the pain point problem of automatic updating of the follow-up building of the interdependent product updating is solved, and the serialized production of the product with a plurality of dependency relationships can be completed through one-time building.
Description
Technical Field
The present application relates to the field of computers, and in particular, to a method and an apparatus for building a dependent product.
Background
The continuous construction is a technology which is emerging in recent years, can realize the updating of unattended automatic monitoring codes, and automatically constructs products required by testers. In practical applications, more than one product is required to be continuously constructed, and some of them have interdependent relationship. The traditional construction process usually only focuses on the construction of one product, and cannot well solve the problem of reference of the latest version in the construction process among interdependent products. At present, the dependent products with the dependency relationship can only be updated by manually triggering the construction of the dependent products. Aiming at the construction problem of the interdependent products, a complete and convenient tool is not provided for solving the problem, if the referenced products have subsequent references, the construction of a long subsequent string of products is required to be triggered again, and the construction becomes a pain point of a continuous construction system.
Disclosure of Invention
An object of the present application is to provide a method and an apparatus for building dependent products, which solve the problem of the prior art that the latest version of the building process between interdependent products cannot be solved well.
According to an aspect of the present application, there is provided a method for building a dependent product, the method comprising:
obtaining the existing dependency relationship description information of the dependent product from a local database;
preprocessing the acquired dependency relationship description information to obtain code information to be compared;
updating the construction mark number of the dependent product according to the code information to be compared and adding updating identification information so as to obtain new dependency relationship description information according to the updated construction mark number and the updating identification information;
and triggering the script to execute a construction task based on the new dependency relationship description information.
Further, before obtaining the existing dependency description information of the dependent product from the local database, the method includes:
and acquiring a yaml file which is input into a local database by a user and used for constructing the dependency description information of the dependent product.
Further, preprocessing the acquired dependency description information to obtain code information to be compared, including:
extracting code information to be compared in the acquired dependency relationship description information, and putting the code information to be compared into a comparison list, wherein the code information to be compared comprises self source codes and bin information of the dependent product.
Further, updating the building mark number of the dependent product according to the code information to be compared and adding updated mark information, including:
delivering the code information to be compared to a source code warehouse through an engine to judge whether dependency description information corresponding to the code information to be compared needs to be updated or not;
and if so, adding the updating identification information and updating the construction mark number of the dependent product.
Further, the method comprises:
and adding a construction mark into the dependency relationship description information, judging whether the construction mark is updated, and if so, updating the construction mark of a subsequent product having a dependency relationship with the dependent product.
Further, before triggering the script to execute the construction task based on the new dependency description information, the method includes:
and periodically triggering and continuously constructing an integrated checking task by a script built in a calling engine, and comparing the dependency description information through the checking task to call the triggering script based on the comparison result.
Further, based on the new dependency description information, triggering a script to execute a construction task, including:
inquiring keyword information carried in new dependency relationship description information in the local database based on the trigger script, wherein the keyword information comprises updating identification information;
acquiring parameter information required by constructing a task according to the keyword information, wherein the required parameter information comprises product-dependent information and corresponding input parameter information;
and performing a reorganization construction task based on the required parameter information.
Further, performing a reorganization and construction task based on the required parameter information includes:
and transmitting the required parameter information to subsequent construction tasks, sequentially connecting the subsequent tasks with the changed dependency relationship in series based on the transmitted parameter information, and sequentially performing the construction tasks according to the serial sequence.
According to yet another aspect of the present application, there is also provided an apparatus for dependent product construction, the apparatus comprising:
one or more processors; and
a memory storing computer readable instructions that, when executed, cause the processor to perform the operations of the method as previously described.
According to yet another aspect of the present application, there is also provided a computer readable medium having computer readable instructions stored thereon, the computer readable instructions being executable by a processor to implement the method as described above.
Compared with the prior art, the method and the system have the advantages that the existing dependency relationship description information of the dependent product is obtained from the local database; preprocessing the acquired dependency relationship description information to obtain code information to be compared; updating the construction mark number of the dependent product according to the code information to be compared and adding updating identification information so as to obtain new dependency relationship description information according to the updated construction mark number and the updating identification information; and triggering the script to execute a construction task based on the new dependency relationship description information. The method can be automatically built through remodeling, starts from the updating demand source of the interdependent product, and rebuilds the task through the dependency relationship description information, so that the pain point problem of automatic updating of the follow-up building of the interdependent product updating is solved, and the serialized production of the product with a plurality of dependency relationships can be completed through one-time building.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:
FIG. 1 illustrates a flow diagram of a build method for a dependent product provided in accordance with an aspect of the subject application;
FIG. 2 is a schematic diagram illustrating a topology between dependent products in an embodiment of the present application;
fig. 3 shows a code diagram of dependency description information in an embodiment of the present application.
The same or similar reference numbers in the drawings identify the same or similar elements.
Detailed Description
The present application is described in further detail below with reference to the attached figures.
In a typical configuration of the present application, the terminal, the device serving the network, and the trusted party each include one or more processors (e.g., central Processing Units (CPUs)), input/output interfaces, network interfaces, and memory.
The Memory may include volatile Memory in a computer readable medium, random Access Memory (RAM), and/or nonvolatile Memory such as Read Only Memory (ROM) or flash Memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both permanent and non-permanent, removable and non-removable media, may implement the information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase-Change RAM (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read-Only Memory (EEPROM), flash Memory or other Memory technology, compact Disc Read-Only Memory (CD-ROM), digital Versatile Disc (DVD) or other optical storage, magnetic cassette tape, magnetic tape storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include non-transitory computer readable media (transient media), such as modulated data signals and carrier waves.
FIG. 1 illustrates a flow diagram of a method for building a dependent product, provided according to an aspect of the present application, the method comprising: from step S11 to step S14,
in step S11, the existing dependency description information of the dependent product is obtained from the local database; here, existing dependency description information of the dependent products is stored in a local Database (DB), and the dependency description information is used to describe a dependency between the dependent products, for example, two product bins and an ISO system, where the ISO system depends on a bin and the two product bins have a dependency, and the dependency description information between the products is obtained from the local database, so as to perform subsequent continuous construction by using the dependency description information, where the dependency description information may be a topology file having a dependency.
In step S12, preprocessing the acquired dependency description information to obtain code information to be compared; and then, the code information to be compared is obtained by carrying out subsequent comparison to judge whether the version of the product is updated, and the code information to be compared is the source code information depending on the product in the source warehouse.
In step S13, updating the building mark number of the dependent product according to the code information to be compared and adding the updated identification information, so as to obtain new dependency description information according to the updated building mark number and the updated identification information; here, whether the dependent product is updated is judged according to the extracted code information to be compared, so that the build mark number (build number) of the dependent product is updated and the update identification information is added, that is, the build number is updated and an update mark of the dependent product, such as "updated", is added to the dependency description information @ ", thereby obtaining new dependency description information.
In step S14, the script is triggered to execute the building task based on the new dependency description information. Here, when the dependency description information is updated, the script is triggered to execute a construction task, and the construction task is to automatically construct subsequent products by using the dependency of the dependent products after the dependent products are sequentially constructed. Therefore, the serialized production of products with a plurality of dependency relationships can be completed by one-time construction, and when the dependent products are updated, the subsequent quoted products can be continuously constructed by using the quoted update information of the dependent products.
In an embodiment of the present application, before obtaining existing dependency description information of a dependent product from a local database, a yaml file, which is input by a user into the local database and used for constructing the dependency description information of the dependent product, may be obtained. Here, the user inputs a yaml file describing the dependency relationship of the constructed product into the local database, the yaml file is a file capable of describing the topology structure of the dependency relationship, the dependent product can be marked by using the yaml file, and therefore marking when the dependent product is updated is completed by using the yaml file.
In an embodiment of the present application, in step S12, to-be-compared code information in the acquired dependency description information is extracted, and the to-be-compared code information is placed in a comparison list, where the to-be-compared code information includes a source code and bin information of a dependent product. Here, the dependency relationship information is stored in the yaml file, and the self-source code and bin information of the dependent product are extracted from the yaml file and are put into the comparison list, so as to determine whether the information in the comparison list is updated or not and determine whether the dependent product is updated or not. According to the topological structure shown in FIG. 2, bin updating only depends on the source code of bin, ISO construction depends on the source codes of bin and ISO, image1 and image2 construction depends on ISO, image1 and image2 are mirror images and are a product of automatic construction. The description information in the topology shown in fig. 2 is specifically shown in fig. 3, and several components are described inside by a yaml file, including a source of monitoring used by a bin, two warehouses (zstack and premium in fig. 3) on which the construction of the bin depends, both of which are trigger sources of "trigger", ISO depends on the latest bin and also on the update of its own source code, both the update of the bin and the update of its own source code trigger the update of ISO, an image includes two image constructions and depends on the construction of ISO, and when there is an update of ISO, the image triggers the construction of the image after the ISO construction is completed, and 2 build files at a time, that is, 2 images are constructed at a time.
Specifically, the code information to be compared may be processed by an engineDelivering the code information to a source code warehouse to judge whether the dependency description information corresponding to the code information to be compared needs to be updated; and if so, adding the updating identification information and updating the construction mark number of the dependent product. Here, the engine submits the comparison list of the code information to be compared to the source code warehouse, and performs the check logic, i.e. automatically processes the input comparison list, automatically pulls the warehouse content in the comparison list, and compares whether the remote end record is consistent with the local record, i.e. judges whether the remote end and the local dependency description information are consistent, more specifically, compares the source code information of the dependent product contained in the description information, i.e. pulls a section of code to compare whether the code is consistent, if not, it indicates that the product needs to be updated, and adds "updated", and if not, it indicates that the product needs to be updated @ "identify and update the build tag number of the dependent product. The comparison can be carried out based on the commit numbers obtained from the yaml structure, the commit numbers are numbers which are automatically generated in a version management tool when software version control, namely management is carried out, each patch is uploaded, the number has uniqueness, the number can be used for representing the patch subsequently, and when a new patch exists, the commit numbers change, so that if the commit numbers of the pulled new codes are inconsistent, the new pulled codes are updated.
Specifically, a construction mark is added to the dependency relationship description information, whether the construction mark is updated or not is judged, and if yes, the construction mark of a subsequent product having a dependency relationship with the dependent product is updated. Here, when the alignment is inconsistent, an update is required, and the mark is updated by adding an updated mark, such as "updated" to yaml @ If the build tag number (build number) of the dependent product is updated, and the dependent product is also dependent on the subsequent product, the subsequent product re-tags the updated tag, updates the commit information, and writes the updated commit information back to the yaml structure corresponding to the local database.
In an embodiment of the present application, before triggering a script to execute a build task based on the new dependency description information, a script built in an invocation engine periodically triggers a continuous build integrated check task, and the trigger script is invoked based on a comparison result by comparing the dependency description information through the check task. Here, yaml1 and yaml2 may be already in the local database, the present application may perform simultaneous monitoring of multiple continuous building tasks, and a continuous integration tool (e.g., jenkins) may be used to provide an agent to periodically perform a certain set task. The checking task (Jenkins checker Job) of the continuous integration tool is triggered once every 5 minutes, and the Job calls a script built in an engine to execute the processes of data preprocessing, information comparison and triggering subsequent construction tasks. Jenkins checker Job checks whether the triggered script is called immediately after the completion of the comparison.
Specifically, keyword information carried in new dependency relationship description information in the local database is queried based on the trigger script, wherein the keyword information includes update identification information; acquiring parameter information required by constructing a task according to the keyword information, wherein the required parameter information comprises product-dependent information and corresponding input parameter information; and carrying out recombination construction tasks based on the required parameter information. Here, the trigger script determines whether the previous check result is updated based on the keyword information in the database, where the keyword information is a previous keyword mark, such as "updated @ ", obtaining all parameters needed by build according to the keyword information, including dependent products and all input parameters thereof, such as adding updated before the corresponding field in the updated yaml file @ The key word, if bin has update, added updated before commit number @ All input parameters include updated corresponding commit @ XXX and bin information, warehouse information, dependency information, and the like; and then, carrying out a recombination construction task by using the acquired required parameter information, wherein the recombination construction task refers to the construction task of the dependent product and the subsequent product which are recombined and then constructed in sequence. And describing the dependency relationship among the constructed products in a way of yaml custom key words, and whether the description information such as construction, type and the like is triggered.
Specifically, the required parameter information is transmitted to subsequent construction tasks, the subsequent tasks with the changed dependency relationship are sequentially connected in series based on the transmitted parameter information, and the construction tasks are sequentially performed according to the serial order. All required parameters are sorted, the parameters are transmitted to a subsequent Jenkins built Job, the Jenkins built Job can realize hosting and building tasks and can realize parameter-based sequential building, the build tasks are recombined based on the transmitted parameters required by the build, the subsequent tasks which depend on updating are connected together in series, and the sequence is built one by one, for example, if the source code of the ISO is updated, the ISO and 2 images behind the ISO are updated, the bin cannot be updated, and the bin quoted in the ISO cannot be updated; the method comprises the steps that building is carried out when updating is detected, the latest ISO is built when the ISO is detected to have the updating, the trigger definition in the image comprises the ISO, the image is marked to be rebuilt once the ISO is updated, and the image does not need to be rebuilt when the bin is not updated in the whole process. The build-by-order is dependent on the order between products, such as ISO dependent bin, and image dependent ISO, then the build-by-order is to build bin first, then ISO, and finally 2 images, thus ensuring that each product is valid.
According to the method, the topological relation of dependence can be described through the yaml file from the update demand source of the interdependent products through remodeling automatic construction, and then the problem of pain points of automatic update of subsequent construction of the dependence product update is solved through re-sequencing and construction of the engine for analyzing the relation, so that the serialized production of the products with a plurality of dependence relations can be completed through one-time construction.
In addition, the embodiment of the present application also provides a computer readable medium, on which computer readable instructions are stored, and the computer readable instructions can be executed by a processor to implement the aforementioned building method for dependent products.
In an embodiment of the present application, there is also provided an apparatus for relying on the building of a product, the apparatus comprising:
one or more processors; and
a memory storing computer readable instructions that, when executed, cause the processor to perform the operations of the method as previously described.
For example, the computer readable instructions, when executed, cause the one or more processors to:
obtaining the existing dependency relationship description information of the dependent product from a local database;
preprocessing the acquired dependency description information to obtain code information to be compared;
updating the construction mark number of the dependent product according to the code information to be compared and adding updating identification information so as to obtain new dependency relationship description information according to the updated construction mark number and the updating identification information;
and triggering the script to execute a construction task based on the new dependency relationship description information.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.
It should be noted that the present application may be implemented in software and/or a combination of software and hardware, for example, implemented using Application Specific Integrated Circuits (ASICs), general purpose computers or any other similar hardware devices. In one embodiment, the software programs of the present application may be executed by a processor to implement the steps or functions described above. Likewise, the software programs (including associated data structures) of the present application may be stored in a computer readable recording medium, such as RAM memory, magnetic or optical drive or diskette and the like. Further, some of the steps or functions of the present application may be implemented in hardware, for example, as circuitry that cooperates with the processor to perform various steps or functions.
In addition, some of the present application may be implemented as a computer program product, such as computer program instructions, which when executed by a computer, may invoke or provide methods and/or techniques in accordance with the present application through the operation of the computer. Program instructions which invoke the methods of the present application may be stored on a fixed or removable recording medium and/or transmitted via a data stream on a broadcast or other signal-bearing medium and/or stored within a working memory of a computer device operating in accordance with the program instructions. An embodiment according to the present application comprises an apparatus comprising a memory for storing computer program instructions and a processor for executing the program instructions, wherein the computer program instructions, when executed by the processor, trigger the apparatus to perform a method and/or a solution according to the aforementioned embodiments of the present application.
It will be evident to those skilled in the art that the present application is not limited to the details of the foregoing illustrative embodiments, and that the present application may be embodied in other specific forms without departing from the spirit or essential attributes thereof. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the application being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned. Furthermore, it will be obvious that the term "comprising" does not exclude other elements or steps, and the singular does not exclude the plural. The terms first, second, etc. are used to denote names, but not to denote any particular order.
Claims (9)
1. A build method for a dependent product, the method comprising:
acquiring the existing dependency relationship description information of the dependent product from a local database;
preprocessing the acquired dependency description information to obtain code information to be compared;
updating the construction mark number of the dependent product according to the code information to be compared and adding updated identification information to obtain new dependency relationship description information according to the updated construction mark number and the updated identification information;
triggering a script to execute a construction task based on the new dependency relationship description information;
and triggering a script to execute a construction task based on the new dependency relationship description information, wherein the construction task comprises the following steps:
inquiring keyword information carried in new dependency description information in the local database based on the trigger script, wherein the keyword information comprises updating identification information;
acquiring parameter information required by constructing tasks according to the keyword information, wherein the required parameter information comprises product-dependent information and corresponding input parameter information;
and performing a reorganization construction task based on the required parameter information.
2. The method of claim 1, wherein before obtaining the existing dependency description information of the dependent product from the local database, the method comprises:
and acquiring a yaml file which is input into a local database by a user and used for constructing the dependency description information of the dependent product.
3. The method according to claim 1 or 2, wherein preprocessing the acquired dependency description information to obtain code information to be compared includes:
extracting code information to be compared in the acquired dependency relationship description information, and putting the code information to be compared into a comparison list, wherein the code information to be compared comprises a self source code and bin information of a dependent product.
4. The method of claim 1, wherein updating the building identifier of the dependent product and adding the updated identifier according to the code information to be compared comprises:
delivering the code information to be compared to a source code warehouse through an engine to judge whether dependency description information corresponding to the code information to be compared needs to be updated or not;
and if so, adding the updated identification information and updating the construction mark number of the dependent product.
5. The method according to claim 1, characterized in that it comprises:
and adding a construction mark into the dependency relationship description information, judging whether the construction mark is updated, and if so, updating the construction mark of a subsequent product having a dependency relationship with the dependent product.
6. The method of claim 1, wherein before triggering the script to execute the build task based on the new dependency description information, the method comprises:
and periodically triggering and continuously constructing an integrated checking task by a script built in a calling engine, and comparing the dependency description information through the checking task to call the triggering script based on the comparison result.
7. The method of claim 1, wherein performing a reorganization construction task based on the required parameter information comprises:
and transmitting the required parameter information to subsequent construction tasks, sequentially connecting the subsequent tasks with the changed dependency relationship in series based on the transmitted parameter information, and sequentially performing the construction tasks according to the serial sequence.
8. An apparatus for building a dependent product, the apparatus comprising:
one or more processors; and
a memory storing computer readable instructions that, when executed, cause the processor to perform the operations of the method of any of claims 1 to 7.
9. A computer readable medium having computer readable instructions stored thereon which are executable by a processor to implement the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011158920.8A CN112256318B (en) | 2020-10-26 | 2020-10-26 | Construction method and equipment for dependent product |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011158920.8A CN112256318B (en) | 2020-10-26 | 2020-10-26 | Construction method and equipment for dependent product |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112256318A CN112256318A (en) | 2021-01-22 |
| CN112256318B true CN112256318B (en) | 2022-12-27 |
Family
ID=74261603
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011158920.8A Active CN112256318B (en) | 2020-10-26 | 2020-10-26 | Construction method and equipment for dependent product |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112256318B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113407226B (en) * | 2021-06-29 | 2022-08-19 | 中电金信软件有限公司 | Management method and device of component information and electronic equipment |
| CN113687818A (en) * | 2021-08-17 | 2021-11-23 | 北京市商汤科技开发有限公司 | Task execution method, device, equipment and computer readable storage medium |
| CN116088968A (en) * | 2023-04-10 | 2023-05-09 | 北京渲光科技有限公司 | Graphic engine management method, device, terminal and storage medium |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106777299A (en) * | 2016-12-30 | 2017-05-31 | 深圳市彬讯科技有限公司 | The project dependence solution of operation management instrument and static data warehouse |
| CN107239269A (en) * | 2016-03-29 | 2017-10-10 | 中兴通讯股份有限公司 | A kind of software delta upgrade method, device and OSS |
| CN107491329A (en) * | 2017-08-04 | 2017-12-19 | 上海携程商务有限公司 | Docker mirror images construction method, equipment, storage medium and electronic installation |
| CN107678776A (en) * | 2017-08-09 | 2018-02-09 | 上海壹账通金融科技有限公司 | Multimode version dependence construction method, device, server and storage medium |
| CN108363587A (en) * | 2018-03-07 | 2018-08-03 | 平安普惠企业管理有限公司 | Application program operation and monitoring method, device, computer equipment and storage medium |
| CN108762769A (en) * | 2018-06-04 | 2018-11-06 | 万惠投资管理有限公司 | Micro services application layout and dispositions method, device and terminal |
| CN108958721A (en) * | 2018-07-09 | 2018-12-07 | 中国科学院软件研究所 | A kind of intelligence continuous integrating with persistently dispose pipelining technique and system |
| CN110162332A (en) * | 2019-05-20 | 2019-08-23 | 深圳前海微众银行股份有限公司 | A kind of construction method and system of RN project |
| CN110377334A (en) * | 2019-07-25 | 2019-10-25 | 北京奇艺世纪科技有限公司 | Continuous integrating method and apparatus |
| US10481893B1 (en) * | 2015-08-10 | 2019-11-19 | American Megatrends International, Llc | Identifying and resolving firmware component dependencies |
| CN110704062A (en) * | 2019-09-27 | 2020-01-17 | 天津五八到家科技有限公司 | Dependency management method, data acquisition method, device and equipment |
| CN111124454A (en) * | 2019-12-25 | 2020-05-08 | 南京医康科技有限公司 | Mirror image construction method and device, electronic equipment and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10324708B2 (en) * | 2017-11-14 | 2019-06-18 | Red Hat, Inc. | Managing updates to container images |
-
2020
- 2020-10-26 CN CN202011158920.8A patent/CN112256318B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10481893B1 (en) * | 2015-08-10 | 2019-11-19 | American Megatrends International, Llc | Identifying and resolving firmware component dependencies |
| CN107239269A (en) * | 2016-03-29 | 2017-10-10 | 中兴通讯股份有限公司 | A kind of software delta upgrade method, device and OSS |
| CN106777299A (en) * | 2016-12-30 | 2017-05-31 | 深圳市彬讯科技有限公司 | The project dependence solution of operation management instrument and static data warehouse |
| CN107491329A (en) * | 2017-08-04 | 2017-12-19 | 上海携程商务有限公司 | Docker mirror images construction method, equipment, storage medium and electronic installation |
| CN107678776A (en) * | 2017-08-09 | 2018-02-09 | 上海壹账通金融科技有限公司 | Multimode version dependence construction method, device, server and storage medium |
| CN108363587A (en) * | 2018-03-07 | 2018-08-03 | 平安普惠企业管理有限公司 | Application program operation and monitoring method, device, computer equipment and storage medium |
| CN108762769A (en) * | 2018-06-04 | 2018-11-06 | 万惠投资管理有限公司 | Micro services application layout and dispositions method, device and terminal |
| CN108958721A (en) * | 2018-07-09 | 2018-12-07 | 中国科学院软件研究所 | A kind of intelligence continuous integrating with persistently dispose pipelining technique and system |
| CN110162332A (en) * | 2019-05-20 | 2019-08-23 | 深圳前海微众银行股份有限公司 | A kind of construction method and system of RN project |
| CN110377334A (en) * | 2019-07-25 | 2019-10-25 | 北京奇艺世纪科技有限公司 | Continuous integrating method and apparatus |
| CN110704062A (en) * | 2019-09-27 | 2020-01-17 | 天津五八到家科技有限公司 | Dependency management method, data acquisition method, device and equipment |
| CN111124454A (en) * | 2019-12-25 | 2020-05-08 | 南京医康科技有限公司 | Mirror image construction method and device, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112256318A (en) | 2021-01-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112256318B (en) | Construction method and equipment for dependent product | |
| CN106656536B (en) | Method and equipment for processing service calling information | |
| CN112148509A (en) | Data processing method, device, server and computer readable storage medium | |
| US20180173808A1 (en) | Intent and bot based query guidance | |
| CN110019754B (en) | Knowledge base building method, device and equipment | |
| CN113448862B (en) | Software version testing method and device and computer equipment | |
| CN113157315A (en) | Method, device, equipment and medium for identifying difference information of different versions of software | |
| CN112650688A (en) | Automated regression testing method, associated device and computer program product | |
| CN112783760A (en) | Test case processing method and device and storage medium | |
| CN112328631A (en) | Production fault analysis method and device, electronic equipment and storage medium | |
| CN113918437A (en) | User behavior data analysis method and device, computer equipment and storage medium | |
| CN110716804A (en) | Method and device for automatically deleting useless resources, storage medium and electronic equipment | |
| CN112052157B (en) | Method, device and system for constructing test message | |
| CN109672608B (en) | Method for transmitting messages according to time | |
| CN109871593B (en) | Information inheritance method and device based on BIM platform and storage device | |
| CN115329759B (en) | Information processing method, device, equipment and storage medium | |
| CN115062084B (en) | Method and device for constructing API (application programming interface) based on database metadata | |
| US20160173591A1 (en) | Data replication among portable electronic devices | |
| CN115237422A (en) | Code compiling method, device, computer equipment and storage medium | |
| CN114329128A (en) | Method and device for acquiring marking data, computer equipment and storage medium | |
| CN110221952B (en) | Service data processing method and device and service data processing system | |
| CN111538651A (en) | Interface testing method, device, server and storage medium | |
| CN114595159B (en) | Test data generation method, device, equipment and storage medium | |
| CN113741956B (en) | Method and device for transplanting version management function, version management method and device | |
| CN112882922B (en) | Test method and related device |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |