WO2019028992A1 - Procédé de construction de relation de dépendance de version multi-module, dispositif, serveur et support de stockage - Google Patents

Procédé de construction de relation de dépendance de version multi-module, dispositif, serveur et support de stockage Download PDF

Info

Publication number
WO2019028992A1
WO2019028992A1 PCT/CN2017/104629 CN2017104629W WO2019028992A1 WO 2019028992 A1 WO2019028992 A1 WO 2019028992A1 CN 2017104629 W CN2017104629 W CN 2017104629W WO 2019028992 A1 WO2019028992 A1 WO 2019028992A1
Authority
WO
WIPO (PCT)
Prior art keywords
version
module
dependency
directed edge
modification
Prior art date
Application number
PCT/CN2017/104629
Other languages
English (en)
Chinese (zh)
Inventor
张玉强
Original Assignee
上海壹账通金融科技有限公司
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 上海壹账通金融科技有限公司 filed Critical 上海壹账通金融科技有限公司
Publication of WO2019028992A1 publication Critical patent/WO2019028992A1/fr

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

Definitions

  • the present application relates to the field of computer technology, and in particular, to a multi-module version dependency construction method, apparatus, server, and storage medium.
  • APP applications In order to continuously meet the needs of the market and users, APP applications also need to be continuously upgraded to enhance the performance of the APP by continuously adding new features and modules. Inevitably, there will be dependencies between different functional modules. For example, the implementation of the function of the A module needs to call the interface of the B module, and the A module depends on the B module. When the module is upgraded, it is very likely that the active or passively associated code program changes, which may cause the other modules of the associated module to be paralyzed, that is, the interface does not match, and the functions do not match.
  • a multi-module version dependency construction method comprising:
  • version information uploaded by a plurality of module terminals, where the version information includes a module version identifier, a dependency relationship with a module version identifier of another module, and dependency detail information corresponding to the dependency relationship;
  • Each module is an independent node, and each of the independent nodes includes at least one child node, and each of the child nodes corresponds to one of the module version identifiers, and the dependency relationship between the module version identifiers is a directed edge.
  • the build version depends on the network map, wherein the directed edge associates the corresponding dependency detail information;
  • a multi-module version dependency building device comprising:
  • An information receiving module configured to receive version information uploaded by a plurality of module terminals, where the version information includes a module version identifier, a dependency relationship with a module version identifier of another module, and dependency detail information corresponding to the dependency relationship;
  • each module is an independent node
  • each of the independent nodes includes at least one child node
  • each of the child nodes corresponds to one of the module version identifiers, and is identified by the module version.
  • the dependency relationship is a version dependent network graph for the directed edge, wherein the directed edge associates the corresponding dependency detail information;
  • a dynamic monitoring module configured to monitor a version update dynamics issued by the module terminal, and extract version revision description information carried in the version update dynamics
  • Relying on the detailed information searching module configured to determine, in the version dependent network map, an independent node that dynamically corresponds to the version update, find all the directed edges connected to the independent node, and obtain the searched Dependency details corresponding to the side;
  • a policy generation module configured to generate a directed edge modification policy by comparing the obtained dependency detail information with the version modification description information
  • Relying on a network map update and push module configured to update the version dependent network map according to the directed edge modification policy, and push the updated version dependent network map to the module terminal related to the current modification.
  • a server comprising a memory and a processor, the memory storing computer readable instructions, the computer readable instructions being executed by the processor such that the processor performs the following steps:
  • version information uploaded by a plurality of module terminals, where the version information includes a module version identifier, a dependency relationship with a module version identifier of another module, and dependency detail information corresponding to the dependency relationship;
  • Each module is an independent node, and each of the independent nodes includes at least one child node, and each of the child nodes corresponds to one of the module version identifiers, and the dependency relationship between the module version identifiers is a directed edge.
  • the build version depends on the network map, wherein the directed edge associates the corresponding dependency detail information;
  • One or more computer readable non-volatile storage media storing computer readable instructions, when executed by one or more processors, cause one or more processors to perform the steps of:
  • version information uploaded by a plurality of module terminals, where the version information includes a module version identifier, a dependency relationship with a module version identifier of another module, and dependency detail information corresponding to the dependency relationship;
  • Each module is an independent node, and each of the independent nodes includes at least one child node, and each of the child nodes corresponds to one of the module version identifiers, and the dependency relationship between the module version identifiers is a directed edge.
  • the build version depends on the network map, wherein the directed edge associates the corresponding dependency detail information;
  • 1 is an application environment diagram of a multi-module version dependency construction method in an embodiment
  • FIG. 2 is a schematic diagram showing the internal structure of a server in an embodiment
  • FIG. 3 is a flow chart of a method for constructing a multi-module version dependency in an embodiment
  • FIG. 4 is a schematic diagram of a version dependent network diagram in an embodiment
  • FIG. 5 is a flow chart of a method for constructing a multi-module version dependency relationship in another embodiment
  • FIG. 6 is a schematic diagram of an independent node in an embodiment
  • FIG. 7 is a structural block diagram of a multi-module version dependency relationship constructing apparatus in an embodiment
  • FIG. 8 is a structural block diagram of a multi-module version dependency relationship constructing apparatus in another embodiment
  • FIG. 9 is a structural block diagram of a multi-module version dependency relationship constructing apparatus in still another embodiment.
  • FIG. 10 is a structural block diagram of a multi-module version dependency relationship constructing apparatus in still another embodiment.
  • an application environment diagram of a multi-module version dependency construction method includes a module terminal 110 and a server 120.
  • Module terminal 110 can communicate with server 120 over a network.
  • the module terminal 110 may be at least one of a smartphone, a tablet, and a notebook, but is not limited thereto.
  • the server 120 may be an independent physical server or a server cluster composed of a plurality of physical servers.
  • a server includes a processor coupled via a system bus, a non-volatile storage medium, an internal memory, and a network interface.
  • the non-volatile storage medium of the server 120 stores an operating system and computer executable instructions for implementing a multi-module version dependency construction method applicable to the server 120 when executed by the processor.
  • This processor is used to provide computing and control capabilities to support the operation of the entire server.
  • the internal memory in the server 120 provides an environment for the operation of the operating system and computer executable instructions in the non-volatile storage medium, the network interface of the server 120 being used for End 110 performs network communication.
  • FIG. 2 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the server to which the solution of the present application is applied.
  • the specific server may It includes more or fewer components than those shown in the figures, or some components are combined, or have different component arrangements.
  • FIG. 3 is a schematic flow chart of a method according to an embodiment of the present application. It should be understood that although the various steps in the flowchart of FIG. 3 are sequentially displayed as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Except as explicitly stated herein, the execution of these steps is not strictly limited, and may be performed in other sequences. Moreover, at least some of the steps in FIG. 3 may include a plurality of sub-steps or stages, which are not necessarily performed at the same time, but may be executed at different times, and the order of execution thereof is not necessarily This may be performed in sequence, but may be performed alternately or alternately with other steps or at least a portion of the sub-steps or stages of the other steps.
  • a multi-module version dependency construction method is provided.
  • the method is applied to the server shown in FIG. 2 as an example, and specifically includes the following steps:
  • Step S202 Receive version information uploaded by a plurality of module terminals, where the version information includes a module version identifier, a dependency relationship with a module version identifier of another module, and dependency detail information corresponding to the dependency relationship.
  • the embodiment relates to a multi-module version dependency construction method for managing each module version upgrade of a multi-module APP system, and the essence thereof is to construct a visual version-dependent network diagram.
  • the APP system includes a plurality of modules, each of which is compiled independently, and each module corresponds to one module terminal.
  • the module terminal is used to count the version information of the corresponding module, and upload the statistical version information to the server.
  • the version information here includes the module version identifiers that the module has published at the historical moment, the dependencies between each module version and other module versions, and the dependency details.
  • the above module version identifier includes the module identifier and version number, such as A1.0, A for module A, and 1.0 for version number.
  • the dependency between different module versions is the calling relationship between different modules.
  • A1.0 calls one or more function interfaces of B1.0 (such as payment interface) when implementing the corresponding function of the module
  • A1.0 depends on B1.0, and the called interface is between two modules. Associated interface.
  • Dependent on detailed information that is, detailed record of dependency information between two module versions with dependencies, including dependent content (such as associated interfaces), dependent content on active relying parties (such as A1.0 above) and passive relying parties Any description of the positional relationship between the versions of each module, such as the position description in B1.0 above.
  • Step S204 Each module is an independent node, each independent node includes at least one child node, each child node corresponds to a module version identifier, and a dependency-dependent network diagram is constructed for the directed edge by the dependency relationship between the module version identifiers. Wherein, the directed edge associates the corresponding dependency detail information.
  • the server first constructs a corresponding independent node for each module according to the version information of each module received, and constructs a child node for multiple module versions under the module, such as A1.0, A1.1, A2.0. Then, according to the dependency relationship between each module version, a directed edge is generated, and the directed edge connects two mutually dependent module versions, and the directed edge arrow points to the active relying party, for example, A1.0 ⁇ B1.0 indicates that B1.0 depends on A1. .0. Finally, the generated directed edges are associated with the corresponding detail information, such as the directed edge between A1.0 and B1.0, and the dependency details information between A1.0 and B1.0 is associated, thereby completing the version dependent network.
  • the construction of the graph is shown in Figure 4. It should be noted that the dependencies between versions are not limited to those shown in the figure, and all reasonable dependencies can be displayed in the form of a version-dependent network diagram in the above manner.
  • the dependency details corresponding to the directed edge will be displayed.
  • Step S206 Monitor the version update dynamics issued by the module terminal, and extract the version modification description information carried in the version update dynamics.
  • the server dynamically monitors the version update of each module terminal and dynamically obtains the version modification description information according to the version update of the module terminal.
  • the server can obtain the version update dynamics of the module terminal in the following two ways. One is that the server grasps the version modification document of the module terminal periodically updated according to the set path, and parses the document to obtain Take the version modification description information. The second is that the server obtains the version update dynamic uploaded by the module terminal to obtain the corresponding version modification description information.
  • the version modification description information includes a description of the modification of the existing version and a description of the new version of the release.
  • the corresponding version modification content includes the modified module version identifier, the modified content, and the modification description.
  • the corresponding version modification description information is a modified version and a modified description of the new version relative to the closest historical version, and a description of the added function and the added function.
  • Step S208 Determine, in the version dependent network map, an independent node that dynamically corresponds to the version update, find all directed edges connected to the independent node, and obtain dependency detail information corresponding to the directed directed edge.
  • the server may determine the module for which the version update dynamic is determined by extracting the module update identifier of the release version update, or modify the description information according to the version and modify the modified version identifier related to the description information, such as A1.2, and further confirm the obtained version.
  • Update the module for which the dynamic is targeted and then locate the corresponding independent node in the version dependent network graph.
  • the server obtains all directed edges elicited by the independent node and dependency details corresponding to the directed edges.
  • the module terminal A issues a version update dynamic about the module A, such as modifying the module version A1.1 or releasing the upgrade version A1.2.
  • the module that the server locates is the A module.
  • the B2.0 depends on the directed edge of A1.1, C1. .0 and C1.2 depend on the directed edges of A1.1.
  • the directed edge of the connection it can be confirmed that the module having the associated relationship with the current version update has the module B and the module C.
  • Step S210 Compare the acquired dependency detail information with the version modification description information to generate a directed edge modification policy.
  • the version modification description information is sequentially compared with the dependent detail information of each directed edge connected by the independent node, to determine whether the modification involved in the modification description information has a modification to the original dependent portion, and if so, according to the comparison.
  • deleting the directed edge information or modifying the dependent detail information corresponding to the existing directed edge, or deleting one or more existing directed edges according to the comparison result modify the dependency details information corresponding to other directed edges. For example, if the modification deletes the call to the associated interface, the corresponding directed edge and its corresponding dependency detail information are deleted.
  • the modified B2.0 removes the call to the original associated interface of module A1.1, and deletes the directed edge between B2.0 and A1.1. And delete the dependency details corresponding to the directed edge. Modifying the strategy also includes generating new directed edges.
  • the modified module version involves modification of the dependent part
  • the corresponding dependency of the directed edge is unstable.
  • the function of the active relying party may not be related to the dependent part. achieve. That is, the dependency relationship cannot guarantee the normal operation of the module function, and the reminder information is sent to the corresponding module terminal, and the reminder information includes the modified description information of the current modification and the related information of the directed edge identifier.
  • module terminal A modifies module A1.1 and modifies the associated interface a called by module C1.0.
  • the modification is recorded in the version modification description information.
  • version modification description information is compared with the related information of the directed edge between A1.1 and C1.0, it is confirmed that the dependent partial modification occurs, and then A1.1 is performed.
  • the directed edge between C1.0 and C1.0 is identified and the corresponding modified description is associated with the directed edge.
  • the C module terminal receives the updated version depending on the network map, it can click the directed edge of the identifier to know the interface mismatch caused by the modification, and timely handle the corresponding processing.
  • the server will further determine whether the deprecated modification will affect other modules, and make corresponding modification strategies through information comparison until the entire version depends on the network map to reach a stable state.
  • the corresponding A module terminal can also know the interface mismatch caused by the dependency in this modification in time, so as to further confirm the modification.
  • Step S212 Update the version dependent network map according to the directed edge modification policy, and push the updated version dependent network map to the module terminal related to the current modification.
  • the server compares the obtained dependency details with the version involved in this release update. Modify the description information to confirm whether it is necessary to modify the existing directed edge or whether to add a new directed edge to generate a modification policy according to the comparison result, and update the version dependent network map according to the modification policy.
  • the updated version relies on the network map to be pushed to the relevant module terminal display.
  • the related module terminal here includes a module terminal that releases the version update dynamics and other module terminals associated with the current modification, and the module terminals associated with the version update of the A module are the module terminal B and the module terminal C.
  • the dependent version information in the version dependency information and the dependency information in the version dependency graph are used to determine the change of the dependency relationship caused by the current version upgrade or the generation of the new directed edge to continuously update the visual version dependency.
  • the relationship diagram is displayed, and the updated version dependency map is pushed to the module terminal that is associated with the update, so that the corresponding module terminal can know the version change of the associated module in a timely and clear manner, and the corresponding time is made accordingly. Confirmation and processing.
  • the automatic management of the dependencies between the modules is realized, the management efficiency is higher, the linkage real-time between the modules is stronger, and the mismatch caused by the dependencies is largely less.
  • step S210 after comparing the acquired dependency detail information and the version modification description information to generate the directed edge modification policy, further comprising step S211: modifying the generated directed edge modification strategy Pushing to the module terminal that releases the version update dynamics, so that the module terminal confirms the generated directed edge modification policy; after receiving the determination instruction sent by the module terminal, performing step S212: modifying the version update network according to the directed edge Figure and push the updated version dependent network map to the module terminal associated with this modification.
  • increasing the confirmation link of the module terminal may make the modification of the version-dependent network map more reliable, and increase the reliability of the generated version-dependent network diagram.
  • the version update dynamically includes a change dynamic of an existing version or an update version release dynamic, wherein the upgrade version release dynamic includes an upgrade version identifier.
  • the update dynamics of the module terminal acquired by the server is dynamic for the upgrade version
  • the method for dynamically updating the build version according to the version update depends on the network map: determining the dynamic corresponding to the upgrade version release in the version dependency network map An independent node, and add a child node corresponding to the upgrade version identifier at the determined independent node.
  • the version modification description information corresponding to the dynamic version of the upgrade version is compared with the dependent detail information of the directed edge connected to the independent node, and if the modification does not involve the modification of the related dependent part, the low version dependency is It can be copied to the higher version of the release. If the C module releases C2.0, C2.0 does not modify the dependency of C1.0 on A1.1. C2.0 also calls the associated interface in A1.1, then C2.0 and A1.1. There is also the same dependency as C1.0. The directed edges between C1.0 and A1.1 and the corresponding dependency details can be copied to C2.0. In one embodiment, a lower version of the directed edge that repeats with the higher version of the directed edge may also be deleted to simplify the dependency network map.
  • the directional is directional.
  • the side and the corresponding dependency details are deleted.
  • the update of the version dependent network map is only to add a new child node.
  • the version upgrade description information includes an improved description of the new version relative to the closest historical version, a connection edge can be generated between the new version and the closest historical version, and an association relationship between the connection edge and the improved description is established.
  • a corresponding improved description is displayed, as shown in FIG.
  • the version of each module is continuously upgraded, and the version of the built-in version depends on the network map.
  • the version between the server and the module terminal depends on the transmission and storage of the network map. Both occupy large resources, and it is time-consuming and laborious for the module terminal to find the dependencies related to itself in the huge version dependency network diagram. In this embodiment, the above problem is solved.
  • the dependency subgraph of each module is generated according to the updated version dependency network diagram, and the generated dependency subgraph is pushed to the corresponding The module terminal display, wherein the generated module dependency subgraph includes an independent node corresponding to the module, a separate node directly connected to the independent node, and a directed edge of the independent node and the directly connected independent node and the directed edges Corresponding dependency details.
  • the dependency graph of the module may further include an independent node spaced apart from the independent node of the corresponding module, the number of independent nodes being no more than a set number of independent nodes.
  • the number of independent nodes is not more than one, including the directly connected independent nodes (the number of intervals is 0) and the independent nodes connected to the directly connected independent nodes (the number of intervals is 1).
  • the module related to the update is confirmed, only the dependency sub-graph of the related module is generated, and the generated dependency sub-map is pushed to the corresponding The relevant module in the terminal.
  • a multi-module version dependency construction apparatus includes:
  • the information receiving module 302 is configured to receive version information uploaded by the plurality of module terminals, where the version information includes a module version identifier, a dependency relationship with the module version identifier of the other module, and dependency detail information corresponding to the dependency relationship.
  • the network diagram construction module 304 is configured to use each module as an independent node, each independent node includes at least one child node, each child node corresponds to a module version identifier, and the dependency relationship between the module version identifiers is a directed edge.
  • the build version relies on a network map in which the directed edges are associated with corresponding dependency details.
  • the dynamic monitoring module 306 is configured to monitor the version update dynamics issued by the module terminal, and extract version revision description information carried in the version update dynamics.
  • the dependency detail information searching module 308 is configured to determine, in the version dependent network map, an independent node that dynamically corresponds to the version update, find all directed edges connected to the independent node, and obtain dependency detail information corresponding to the directed directed edge.
  • the modification policy generation module 310 is configured to generate a directed edge modification policy by comparing the obtained dependency detail information with the version modification description information.
  • the network map update and push module 312 is configured to modify the version dependent network map according to the directed edge modification and push the updated version dependent network map to the module terminal related to the current modification.
  • the multi-module version dependency relationship building device further includes:
  • the terminal confirmation module 311 is configured to push the generated directed edge modification policy to the module terminal that releases the version update dynamic, so that the module terminal confirms the generated directed edge modification policy.
  • the network map update and push module 312 After receiving the determination command sent by the module terminal, the network map update and push module 312 is entered.
  • the multi-module version dependency relationship building device further includes:
  • the upgrade version sub-node adding module 402 is configured to determine whether the version modification description information carries the upgrade version identifier, and if yes, add the child node corresponding to the upgrade version identifier to the corresponding independent node in the version dependency network diagram.
  • the modification policy generation module 310 is further configured to compare the version modification description information with the dependency detail information corresponding to each directed edge of the search, and determine whether the current modification involves recording in the dependency detail information.
  • Dependent part of the modification if it is, according to the comparison result delete the existing directed edge or modify the existing directed edge corresponding to the details of the information; and determine whether the modification of the existing directed edge makes the existing directed edge corresponding to the dependence The relationship is unstable, and if so, the reminder information is sent to the module terminal corresponding to the unstable directed edge;
  • a new directed edge and corresponding dependency details are generated based on the comparison result.
  • the multi-module version dependency construction apparatus further includes: a dependency sub-graph generation module 502, configured to generate a dependency sub-graph of each module according to the version dependency map, and generate The dependency subgraph is pushed to the corresponding module terminal display.
  • a dependency sub-graph generation module 502 configured to generate a dependency sub-graph of each module according to the version dependency map, and generate The dependency subgraph is pushed to the corresponding module terminal display.
  • a server comprising a memory and a processor, wherein the memory stores computer readable instructions, and when the computer readable instructions are executed by the processor, the processor performs the following steps: receiving a plurality of module terminal uploads Version information, the version information includes the module version identifier, the dependency relationship with the module version identifier of other modules, and the dependency detail letter corresponding to the dependency relationship.
  • Each module is an independent node, each independent node includes at least one child node, each child node corresponds to a module version identifier, and a dependency-dependent network diagram is constructed for the directed edge by the dependency relationship between the module version identifiers, wherein And the related details information of the directed edge association; monitoring the version update dynamics issued by the terminal, extracting the version modification description information carried in the version update dynamic; determining the independent node corresponding to the version update dynamic in the version dependent network map, searching and All the directed edges connected to the independent node and obtain the dependency details information corresponding to the directed directed edge; compare the obtained dependency detail information and the version modification description information to generate a directed edge modification strategy; and modify the policy update version according to the directed edge Depends on the network map and pushes the updated version dependent network map to the module terminal associated with this modification.
  • the processor after comparing the acquired dependency detail information and the version modification description information to generate a directed edge modification policy, the processor further performs the following steps:
  • the processor further performs the following steps: determining whether the version modification description information carries the upgrade version identifier, and if yes, adding the child node corresponding to the upgrade version identifier to the corresponding independent node in the version dependency network diagram .
  • the step of comparing the acquired dependency detail information and the version modification description information performed by the processor to generate the directed edge modification policy includes:
  • the version modification description information is sequentially compared with the dependency detail information corresponding to each directed edge of the search, and it is determined whether the modification involves modification of the dependent portion recorded in the dependency detail information, and if so, the deletion is already performed according to the comparison result.
  • the module terminal sends the reminder information; according to the comparison result, a new directed edge and corresponding dependency detail information are generated.
  • the processor further performs the steps of: generating a dependency subgraph of each module based on the version dependency graph and pushing the generated dependency subgraph to the corresponding module terminal display.
  • one or more computer readable non-volatile storage media having computer readable instructions, when executed by one or more processors, causing one or more processors The following steps are performed: receiving version information uploaded by multiple module terminals, where the version information includes a module version identifier, a dependency relationship with a module version identifier of another module, and dependency detail information corresponding to the dependency relationship; each module is an independent node.
  • Each of the independent nodes includes at least one child node, and each child node corresponds to a module version identifier, and a version dependent network map is constructed for the directed edge by the dependency relationship between the module version identifiers, wherein the directed edge association corresponds to the corresponding dependency information.
  • the processor after comparing the acquired dependency detail information and the version modification description information to generate a directed edge modification policy, the processor further performs the following steps:
  • the processor further performs the following steps: determining whether the version modification description information carries the upgrade version identifier, and if yes, adding the child node corresponding to the upgrade version identifier to the corresponding independent node in the version dependency network diagram .
  • the step of comparing the acquired dependency detail information and the version modification description information performed by the processor to generate the directed edge modification policy includes:
  • the version modification description information is sequentially compared with the dependency detail information corresponding to each directed edge of the search, and it is determined whether the modification involves modification of the dependent portion recorded in the dependency detail information, and if so, the deletion is already performed according to the comparison result.
  • a new directed edge and corresponding dependency details are generated based on the comparison result.
  • the processor further performs the steps of: generating a dependency subgraph of each module based on the version dependency graph and pushing the generated dependency subgraph to the corresponding module terminal display.
  • the storage medium may be a non-volatile storage medium such as a magnetic disk, an optical disk, or a read-only memory (ROM).

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

L'invention concerne un procédé de construction de relation de dépendance de version multi-module qui consiste : à recevoir des informations de version téléchargées en amont par une pluralité de terminaux de module ; à établir un graphe de réseau de dépendance de version utilisant chaque module en tant que nœud indépendant et une relation de dépendance entre des identifiants de version de module en tant que bord dirigé, chaque nœud indépendant comprenant au moins un sous-nœud, et le bord dirigé étant associé à des informations de détail de dépendance correspondantes ; à surveiller la dynamique de mise à jour de version libérée par les terminaux de module, et à extraire des informations de description de modification de version ; à déterminer les nœuds indépendants correspondant à la dynamique de mise à jour de version dans le graphe de réseau de dépendance de version, et à rechercher les informations de détail de dépendance de tous les bords dirigés connectés aux nœuds indépendants ; à comparer les informations de détail de dépendance obtenues aux informations de description de modification de version, et à générer une politique de modification de bord dirigé ; à mettre à jour le graphe de réseau de dépendance de version selon la politique de modification de bord dirigé, et à pousser le graphe de réseau de dépendance de version mis à jour vers les terminaux de module.
PCT/CN2017/104629 2017-08-09 2017-09-29 Procédé de construction de relation de dépendance de version multi-module, dispositif, serveur et support de stockage WO2019028992A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710674839.7A CN107678776A (zh) 2017-08-09 2017-08-09 多模块版本依赖关系构建方法、装置、服务器和存储介质
CN201710674839.7 2017-08-09

Publications (1)

Publication Number Publication Date
WO2019028992A1 true WO2019028992A1 (fr) 2019-02-14

Family

ID=61135167

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/104629 WO2019028992A1 (fr) 2017-08-09 2017-09-29 Procédé de construction de relation de dépendance de version multi-module, dispositif, serveur et support de stockage

Country Status (2)

Country Link
CN (1) CN107678776A (fr)
WO (1) WO2019028992A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111142931A (zh) * 2020-01-02 2020-05-12 中国银行股份有限公司 一种基线信息确定方法、装置、服务器及存储介质
CN111522579A (zh) * 2020-06-22 2020-08-11 上海通联金融服务有限公司 一种版本环境进程检测方法、设备及存储介质
CN117112011A (zh) * 2023-08-16 2023-11-24 北京冠群信息技术股份有限公司 一种版本管理方法及装置

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108363587B (zh) * 2018-03-07 2022-02-01 平安普惠企业管理有限公司 应用程序运行监控方法、装置、计算机设备和存储介质
CN109117143A (zh) * 2018-06-11 2019-01-01 阿里巴巴集团控股有限公司 一种应用部署方法及系统
US10873604B1 (en) 2018-06-19 2020-12-22 Architecture Technology Corporation Methods and systems for reconfiguring network devices
CN109144980A (zh) * 2018-08-21 2019-01-04 成都四方伟业软件股份有限公司 元数据管理方法、装置及电子设备
CN109241672A (zh) * 2018-10-15 2019-01-18 中冶赛迪技术研究中心有限公司 一种物流仿真软件的模型版本升级系统及方法
CN110162477B (zh) * 2019-05-28 2022-11-22 山东财经大学 一种第三方库版本升级的异常自动调试系统及方法
CN110704062A (zh) * 2019-09-27 2020-01-17 天津五八到家科技有限公司 依赖管理方法、数据获取方法、装置及设备
CN111090835B (zh) * 2019-12-06 2022-04-19 支付宝(杭州)信息技术有限公司 一种文件衍生图的构建方法及装置
CN111176723B (zh) * 2019-12-31 2020-11-06 上海道客网络科技有限公司 基于服务网格和链路版本的服务多版本发布系统与方法
CN111274271A (zh) * 2020-01-13 2020-06-12 北京奇艺世纪科技有限公司 一种信息管理装置、方法、电子设备及存储介质
CN111399898B (zh) * 2020-03-04 2023-09-05 平安科技（深圳）有限公司 多模块系统代码版本的管理方法、装置和计算机设备
CN114090032A (zh) * 2020-08-05 2022-02-25 福建天泉教育科技有限公司 一种通过即时通讯工具进行版本更新消息推送的方法及系统
CN112286545B (zh) * 2020-09-21 2023-05-05 长沙市到家悠享网络科技有限公司 数据更新方法、装置、设备和存储介质
CN112256318B (zh) * 2020-10-26 2022-12-27 上海云轴信息科技有限公司 一种用于依赖产品的构建方法及设备
CN112363756B (zh) * 2020-12-04 2022-06-21 四川长虹电器股份有限公司 一种可动态切换bom版本的方法
CN112632957A (zh) * 2020-12-18 2021-04-09 湖南特能博世科技有限公司 电力图纸管理方法、装置、终端设备及服务器
CN112947896B (zh) * 2021-03-26 2023-10-27 中国航空无线电电子研究所 一种基于有向图的组件依赖分析方法
CN115794196B (zh) * 2023-02-13 2023-06-30 中科南京软件技术研究院 EdgeX的关键软件识别方法、装置、设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104765620A (zh) * 2014-01-02 2015-07-08 国际商业机器公司 一种程序模块部署的方法和系统
US20150227363A1 (en) * 2014-02-13 2015-08-13 Linkedln Corporation Systems and methods for software dependency management
CN106648563A (zh) * 2015-10-30 2017-05-10 阿里巴巴集团控股有限公司 应用程序中共享模块的依赖解耦处理方法和装置
CN106874031A (zh) * 2017-01-03 2017-06-20 青岛海信电器股份有限公司 一种终端设备系统程序的启动方法及装置

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10157172B2 (en) * 2008-08-27 2018-12-18 International Business Machines Corporation Property dependency visualization
CN102073582A (zh) * 2010-07-30 2011-05-25 兰雨晴 基于冲突的软件包依赖关系检查方法
CN102109991A (zh) * 2010-07-30 2011-06-29 兰雨晴 软件包依赖关系建模方法
CN102880466B (zh) * 2012-09-04 2016-03-16 中标软件有限公司 一种Linux操作系统软件包依赖关系检测方法
CN106371838B (zh) * 2016-08-31 2019-10-18 福建联迪商用设备有限公司 一种维护软件包依赖关系的方法及系统
CN106886410B (zh) * 2017-01-06 2018-06-19 深圳云天励飞技术有限公司 一种软件版本管理系统
CN106970788B (zh) * 2017-02-24 2018-08-07 中国人民解放军海军大连舰艇学院 一种基于时态的对象依赖关系发现方法和系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104765620A (zh) * 2014-01-02 2015-07-08 国际商业机器公司 一种程序模块部署的方法和系统
US20150227363A1 (en) * 2014-02-13 2015-08-13 Linkedln Corporation Systems and methods for software dependency management
CN106648563A (zh) * 2015-10-30 2017-05-10 阿里巴巴集团控股有限公司 应用程序中共享模块的依赖解耦处理方法和装置
CN106874031A (zh) * 2017-01-03 2017-06-20 青岛海信电器股份有限公司 一种终端设备系统程序的启动方法及装置

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111142931A (zh) * 2020-01-02 2020-05-12 中国银行股份有限公司 一种基线信息确定方法、装置、服务器及存储介质
CN111142931B (zh) * 2020-01-02 2023-03-21 中国银行股份有限公司 一种基线信息确定方法、装置、服务器及存储介质
CN111522579A (zh) * 2020-06-22 2020-08-11 上海通联金融服务有限公司 一种版本环境进程检测方法、设备及存储介质
CN117112011A (zh) * 2023-08-16 2023-11-24 北京冠群信息技术股份有限公司 一种版本管理方法及装置

Also Published As

Publication number Publication date
CN107678776A (zh) 2018-02-09

Similar Documents

Publication Publication Date Title
WO2019028992A1 (fr) Procédé de construction de relation de dépendance de version multi-module, dispositif, serveur et support de stockage
US10776104B2 (en) Systems and methods for tracking configuration file changes
CN112118565B (zh) 多租户服务灰度发布方法、装置、计算机设备和存储介质
CN109976667B (zh) 一种镜像管理方法、装置及系统
CN108566290B (zh) 服务配置管理方法、系统、存储介质和服务器
US10380103B2 (en) Object data updating method and apparatus in an object storage system
CN106888233B (zh) 数据更新系统及方法
US9971787B2 (en) Unified file and object data storage
WO2017143844A1 (fr) Procédé d'opération de données et serveur de gestion de données
US11159390B2 (en) Systems and methods for service-aware mapping of a system infrastructure
JP6325001B2 (ja) 階層データ構造のノードにおいて再帰的イベントリスナを用いる方法およびシステム
US11171994B2 (en) Tag-based security policy creation in a distributed computing environment
CN112685499B (zh) 一种工作业务流的流程数据同步方法、装置及设备
WO2017148326A1 (fr) Procédé et dispositif de gestion de ressource
US20190114163A1 (en) Systems and methods for peer-to-peer build sharing
CN109729121A (zh) 一种云存储系统及用于云存储系统中实现自定义数据处理的方法
CN111880832A (zh) 一种基于docker容器化技术的镜像管理方法
CN108536447B (zh) 运维管理方法
CN110798358B (zh) 分布式服务标识方法、装置、计算机可读介质及电子设备
CN112395339A (zh) 系统间数据准入校验方法、装置、计算机设备和存储介质
CN116048609A (zh) 配置文件更新方法、装置、计算机设备和存储介质
CN112711466B (zh) 悬挂事务巡检方法和装置、电子设备和存储介质
US11153388B2 (en) Workflow engine framework for cross-domain extension
CN113760487B (zh) 一种业务处理方法和装置
CN115220992A (zh) 接口变更监控方法、装置、计算机设备和存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17921379

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 25.06.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 17921379

Country of ref document: EP

Kind code of ref document: A1