Methods and devices for demonstrating the dependency relationships of project artifacts

By obtaining and parsing project text from the project compilation pipeline, constructing and displaying project dependencies, the problem of users having difficulty intuitively understanding project artifact dependencies is solved, achieving intuitive display and efficient analysis of project artifact dependencies.

CN116882386BActive Publication Date: 2026-11-17QI AN XIN TECHNOLOGY GROUP INC
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202310789596.7
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-06-29
Publication Date
2026-11-17
Estimated Expiration
2043-06-29

AI Technical Summary

Technical Problem

The existing method of displaying project artifact dependencies makes it difficult for users to intuitively understand the relationships between project artifacts involved in the project compilation process and other related project artifacts, requiring manual analysis by users.

Method used

The project text is obtained from the project compilation pipeline, the project artifacts and their related other project artifacts are parsed, the project dependencies are constructed, and the output is displayed based on these relationships.

Benefits of technology

Users can directly understand the project artifacts and their dependencies involved in each compilation operation from the project dependencies, avoiding manual analysis and improving intuitiveness and efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116882386B_ABST
    Figure CN116882386B_ABST
Patent Text Reader

Abstract

This application discloses a method and apparatus for displaying project artifact dependencies, relating to the field of computer technology. The method includes: obtaining project text from a project compilation pipeline, wherein the project text represents project artifacts required during project compilation, and other project artifacts associated with each project artifact; parsing the project text and constructing project dependencies based on each project artifact and its associated other project artifacts; and performing an output operation on the project dependencies corresponding to the project artifacts, the output operation being used to display the project artifacts and their associated other project artifacts according to the project dependencies.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method and apparatus for demonstrating project artifact dependencies. Background Technology

[0002] In software or program compilation, a pipelined approach is typically used to improve efficiency. This means the entire compilation process takes place within a pipeline built on the platform or system. In this process, a software or program is usually viewed as a project. During project compilation, different functionalities may require support from other functionalities, meaning there are dependencies between them. A complete function or service can generally be considered a project artifact, and different project artifacts may have different dependencies. To ensure the accuracy of the project compilation pipeline, staff need to analyze the dependencies between project artifacts to promptly identify problematic artifacts. Therefore, clearly defining the dependencies between project artifacts is crucial for subsequent analysis and troubleshooting.

[0003] Currently, the existing method of displaying project artifact dependencies generally involves directly showing the project text generated by each compilation action in the project pipeline. This project text contains the project artifacts involved in the current compilation action and their related artifacts, meaning all project artifacts are recorded in a "one-size-fits-all" manner. This means that when users analyze the specific project artifacts involved in a particular compilation action and their relationships, they still need to manually analyze the project text to identify the project artifacts involved and their related artifacts. Consequently, it is difficult for users to intuitively understand the project artifacts involved in this compilation action and their relationships with other related artifacts. Summary of the Invention

[0004] This application provides a method and apparatus for displaying project artifact dependencies. The main purpose is to implement a method for displaying project artifact dependencies to solve the problem that users have difficulty intuitively understanding the relationships between project artifacts involved in the project compilation process and other related project artifacts from the project text.

[0005] To address the aforementioned technical problems, this application provides the following technical solutions:

[0006] Firstly, this application provides a method for displaying project artifact dependencies, including:

[0007] Obtain project text from the project compilation pipeline, wherein the project text is used to characterize the project artifacts required when compiling the project, and other project artifacts associated with each project artifact;

[0008] The project text is parsed, and project dependencies are constructed based on each project artifact and its associated other project artifacts;

[0009] An output operation is performed on the project dependencies corresponding to the project artifacts. The output operation is used to display the project artifacts and other associated project artifacts according to the project dependencies.

[0010] Optionally, obtaining the project text from the project compilation pipeline includes:

[0011] The compilation tools of the project compilation pipeline are monitored, and when compilation behavior is detected, the project text corresponding to the compilation behavior is obtained.

[0012] Optionally, the step of monitoring the compilation tools of the project compilation pipeline and obtaining the project text corresponding to the compilation behavior when compilation behavior is detected includes:

[0013] The compilation tool is monitored through a data acquisition service, and when the compilation tool is detected to be executing a target command, the project text generated by the target command is obtained.

[0014] Optionally, the project text may be at least one of tool text, mirror text, and environment text;

[0015] The tool texts mentioned here include ordinary products and their associated third-party tools;

[0016] The mirrored text includes ordinary artifacts and their associated mirrored artifacts;

[0017] The environmental text includes mirrored artifacts and their associated environmental artifacts.

[0018] Optionally, the project dependencies include a first dependency;

[0019] The step of parsing the project text and constructing project dependencies based on each project artifact and its associated other project artifacts includes:

[0020] When the project text is the tool text, the tool text is parsed through the data processing service to obtain the ordinary product and its associated third-party tool, and a first dependency relationship is constructed based on each ordinary product and its third-party tool.

[0021] Optionally, the project dependencies include second dependencies;

[0022] The step of parsing the project text and constructing project dependencies based on each project artifact and its associated other project artifacts includes:

[0023] When the project text is the mirror text, the mirror text is parsed through the data processing service to obtain the ordinary product and its associated mirror product, and a second dependency relationship is constructed based on each ordinary product and its mirror product.

[0024] Optionally, the project dependencies include third-party dependencies;

[0025] The step of parsing the project text and constructing project dependencies based on each project artifact and its associated other project artifacts includes:

[0026] When the project text is specifically the environment text, the environment text is parsed through the data processing service to obtain the image artifact and its associated environment artifact, and a third dependency relationship is constructed based on each image artifact and its environment artifact.

[0027] Optionally, before parsing the project text and constructing project dependencies based on each project artifact and its associated other project artifacts, the method further includes:

[0028] The project text is objectified using data tools and then forwarded to a message queue.

[0029] The project text is retrieved from the message queue through the preset service.

[0030] Optionally, the step of performing an output operation on the project dependencies corresponding to the project artifact includes:

[0031] The project dependencies are obtained from the message queue through the data recording service and recorded in the target storage area, wherein the target storage area includes at least one of a database and a search engine; the project dependencies are generated by the data processing service and then forwarded to the message queue.

[0032] In response to receiving an output instruction, the target project artifact is determined, and other project artifacts corresponding to the target project artifact are identified and displayed in the project dependency relationship.

[0033] Optionally, after monitoring the compilation tools of the project compilation pipeline and obtaining the project text corresponding to the compilation behavior when compilation behavior is detected, the method further includes:

[0034] Compilation information is generated based on the project text, and the compilation information is objectified and forwarded to the message queue through the data tool service. The compilation information is used to record the compilation behavior corresponding to the project text.

[0035] The compilation information corresponding to the project text is obtained from the message queue through the data recording service, and the corresponding compilation information is added to the compilation record table;

[0036] After detecting that the data recording service has the project dependency relationship, the record information is updated in the compilation record table based on the project dependency relationship.

[0037] Optionally, after monitoring the compilation tools of the project compilation pipeline and obtaining the project text corresponding to the compilation behavior when compilation behavior is detected, the method further includes:

[0038] When the compilation tool determines that the compilation behavior has been aborted, the data acquisition service generates abort information, and the data tool service performs objectification processing on the abort information and forwards it to the message queue.

[0039] The abort information is obtained from the message queue through the data tool service, and a mark is added to the record information in the compilation record table based on the abort information. The mark information includes the compilation result and time information, and the time information is used to characterize the execution time of the compilation behavior.

[0040] Secondly, this application also provides a device for displaying the dependency relationship of project artifacts, the device comprising:

[0041] The acquisition unit is configured to acquire project text from the project compilation pipeline, wherein the project text is used to characterize the project artifacts required during project compilation, and other project artifacts associated with each project artifact.

[0042] A building unit is used to parse the project text and build project dependencies based on each project artifact and its associated other project artifacts;

[0043] The output unit is used to perform an output operation on the project dependency relationship corresponding to the project artifact. The output operation is used to display the project artifact and other associated project artifacts according to the project dependency relationship.

[0044] Optionally, the acquisition unit is specifically used to monitor the compilation tools of the project compilation pipeline, and when compilation behavior is detected, to acquire the project text corresponding to the compilation behavior.

[0045] Optionally, the acquisition unit is further configured to monitor the compilation tool through a data acquisition service, and when the compilation tool is detected to be executing a target command, acquire the project text generated by the target command.

[0046] Optionally, the project text may be at least one of tool text, mirror text, and environment text;

[0047] The tool texts mentioned here include ordinary products and their associated third-party tools;

[0048] The mirrored text includes ordinary artifacts and their associated mirrored artifacts;

[0049] The environmental text includes mirrored artifacts and their associated environmental artifacts.

[0050] Optionally, the project dependencies include a first dependency;

[0051] The building unit includes:

[0052] The first construction module is used to parse the tool text through a data processing service when the project text is the tool text, to obtain the ordinary artifact and its associated third-party tool, and to construct a first dependency relationship based on each ordinary artifact and its third-party tool.

[0053] Optionally, the project dependencies include second dependencies;

[0054] The building unit includes:

[0055] The second construction module is used to parse the mirror text through a data processing service when the project text is the mirror text, to obtain the ordinary artifact and its associated mirror artifact, and to construct a second dependency relationship based on each ordinary artifact and its mirror artifact.

[0056] Optionally, the project dependencies include third-party dependencies;

[0057] The building unit further includes:

[0058] The third construction module is used to parse the environment text through a data processing service when the project text is specifically the environment text, to obtain the image artifact and its associated environment artifact, and to construct a third dependency relationship based on each image artifact and its environment artifact.

[0059] Optionally, the device further includes:

[0060] The processing unit is used to perform object-oriented processing on the project text through data tool services and forward it to a message queue;

[0061] The text acquisition unit is used to acquire the project text from the message queue through the preset service.

[0062] Optionally, the output unit includes:

[0063] A recording module is used to obtain the project dependency relationship from the message queue through a data recording service and record the project dependency relationship in a target storage area, wherein the target storage area includes at least one of a database and a search engine; the project dependency relationship is generated by a data processing service and then forwarded to the message queue;

[0064] The output module is used to respond to the received output instruction, determine the target project artifact, and determine and display other project artifacts corresponding to the target project artifact in the project dependency relationship.

[0065] Optionally, the device further includes:

[0066] A forwarding unit is used to generate compilation information based on the project text, and to perform objectification processing on the compilation information and forward it to a message queue through a data tool service. The compilation information is used to record the compilation behavior corresponding to the project text.

[0067] An adding unit is used to obtain the compilation information corresponding to the project text from the message queue through the data recording service, and add the corresponding compilation information to the compilation record table;

[0068] An update unit is used to update the record information in the compilation record table based on the project dependency after detecting that the data recording service has recorded the project dependency.

[0069] Optionally, the device further includes:

[0070] The sending unit is used to generate abort information through the data acquisition service when the compilation behavior is determined to be aborted by the compilation tool, and to forward the abort information to the message queue after performing objectification processing through the data tool service.

[0071] The tagging unit is used to obtain the abort information from the message queue through the data tool service, and add tag information to the record information in the compilation record table based on the abort information. The tag information includes compilation result and time information, and the time information is used to characterize the execution time of the compilation behavior.

[0072] Thirdly, embodiments of this application provide a storage medium including a stored program, wherein, during the execution of the program, the device where the storage medium is located executes the method for displaying the project artifact dependencies of the terminal device described in the first aspect.

[0073] Fourthly, embodiments of this application provide a device for displaying project artifact dependencies. The device includes a storage medium and one or more processors, the storage medium being coupled to the processors, the processors being configured to execute program instructions stored in the storage medium; the program instructions, when executed, perform the method for displaying project artifact dependencies of the terminal device described in the first aspect.

[0074] By employing the above-described technical solution, the technical solution provided in this application has at least the following advantages:

[0075] This application provides a method and apparatus for displaying project artifact dependencies. The method first obtains project text from the project compilation pipeline, whereby the project text represents the project artifacts required during project compilation, as well as other project artifacts associated with each project artifact. Then, the project text is parsed, and project dependencies are constructed based on each project artifact and its associated other project artifacts. Finally, an output operation is performed on the project dependencies corresponding to the project artifacts, which displays the project artifacts and their associated other project artifacts according to the project dependencies. Compared to existing technologies, this application constructs and displays project artifact dependencies based on the project text and other project artifacts that have dependencies on each project artifact. This avoids the need for users to manually analyze the relationships between other project artifacts involved in a project artifact after the project text is directly output to them. This allows users to directly determine each project artifact involved in each compilation operation and its dependent other project artifacts based on the project dependencies, eliminating the need for manual analysis and providing a clear understanding of the dependencies between project artifacts involved in each project compilation.

[0076] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, the following are specific embodiments of this application. Attached Figure Description

[0077] The above and other objects, features, and advantages of exemplary embodiments of this application will become readily understood by reading the following detailed description with reference to the accompanying drawings. In the drawings, several embodiments of this application are illustrated by way of example and not limitation, with the same or corresponding reference numerals denoteing the same or corresponding parts, wherein:

[0078] Figure 1 A flowchart illustrating a method for displaying project artifact dependencies according to an embodiment of this application is shown;

[0079] Figure 2 A flowchart illustrating another method for displaying project artifact dependencies provided in an embodiment of this application is shown;

[0080] Figure 3 A block diagram of a display device for project artifact dependencies provided in an embodiment of this application is shown;

[0081] Figure 4 A block diagram of another project artifact dependency display device provided in an embodiment of this application is shown. Detailed Implementation

[0082] Exemplary embodiments of this application will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of this application are shown in the drawings, it should be understood that this application may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided to enable a more thorough understanding of this application and to fully convey the scope of this application to those skilled in the art.

[0083] It should be noted that, unless otherwise stated, the technical or scientific terms used in this application shall have the ordinary meaning as understood by one of ordinary skill in the art to which this application pertains.

[0084] This application provides a method for displaying project artifact dependencies, applied to devices with production and development environments set up, specifically as follows: Figure 1 As shown, the method includes:

[0085] 101. Obtain project text from the project compilation pipeline.

[0086] The project text is used to characterize the project artifacts required during project compilation, as well as other project artifacts associated with each project artifact. In practical applications, the project artifacts may include ordinary artifacts, image artifacts, environment artifacts, and third-party tools.

[0087] In this embodiment, the project compilation pipeline can be understood as a pipeline-style platform or system specifically used for developing and compiling projects. Users perform compilation actions on this pipeline, generating project text during the process. This project text can be understood as text automatically recording the required project artifacts and related artifacts based on user actions during project compilation. Specifically, the project text can be in XML format. However, in practical applications, different project compilation pipelines may generate different text formats under different circumstances, which is not limited here. When project text is generated, it can be understood that the user has already performed compilation. Furthermore, in this embodiment, the ordinary artifacts, image artifacts, environment artifacts, and third-party tools are all elements required during the project compilation process and have hierarchical relationships with each other. Environment artifacts may involve multiple image artifacts, each image artifact may involve multiple ordinary artifacts, and ordinary artifacts may involve multiple third-party tools. Specifically, the number and types of the next level contained in each level are not limited and can be determined based on the actual compilation process.

[0088] 102. Parse the project text and build project dependencies based on each project artifact and its associated other project artifacts.

[0089] Since the project text actually encompasses all project artifacts targeted by the current compilation behavior, meaning that while it comprehensively records each project artifact and its related artifacts, it's essentially just a large amount of complex data being recorded, without a clear and intuitive representation of the relationships between the artifacts. Therefore, in this step, we can parse the project text based on preset services and construct project dependencies according to each project artifact and its related artifacts. This allows us to progressively determine the relationships between project artifacts within the project dependencies.

[0090] For example, the project text contains the following content: Mirror artifact a - Ordinary artifact A, Ordinary artifact B - Third-party tool 1, Environmental artifact 1 - Mirror artifact a, Ordinary artifact A - Third-party tool 2, Mirror artifact a - Ordinary artifact B.

[0091] Therefore, the project dependency relationship constructed based on the method described in this embodiment can be as follows:

[0092] Third-party tools 2 - General products A - Mirrored products a - Environmental products 1;

[0093] Third-party tools 1 - General products B - Mirror products a - Environmental products 1.

[0094] Of course, it can also be done as follows:

[0095] Environmental artifact 1: Mirror artifact a: {Ordinary artifact A: Third-party tool 2}

[0096] Common Product B: Third-Party Tool 1}

[0097] Of course, the project dependencies described in this embodiment include, but are not limited to, the methods described above, and the specific method can be selected based on the user's actual needs.

[0098] 103. Perform output operations on the project dependencies corresponding to the project artifacts.

[0099] The output operation is used to display the project artifacts and other associated project artifacts according to the project dependencies.

[0100] Once project dependencies are generated, the dependencies between regular artifacts, mirror artifacts, environment artifacts, and third-party tools are confirmed, forming a hierarchical "relationship chain." Recording this information facilitates subsequent troubleshooting and analysis. Furthermore, the project-to-dependency relationship can be displayed hierarchically based on the methods described in this step. During this process, users can select commands through the interactive interface to specify the different project artifacts they wish to view. The output will then show the project artifact and its corresponding "relationship chain," i.e., the project dependency relationship. This ensures that users can retrieve the "relationship chain" of the specific project they want to analyze, avoiding the display chaos caused by simultaneously showing other unrelated project artifacts. This allows users to more intuitively and quickly obtain the required project artifacts and their corresponding dependencies.

[0101] This application provides a method for displaying project artifact dependencies. In this embodiment, project text is first obtained from the project compilation pipeline. This project text represents the project artifacts required during project compilation, as well as other project artifacts associated with each project artifact. Then, the project text is parsed, and project dependencies are constructed based on each project artifact and its associated other project artifacts. Finally, an output operation is performed on the project dependencies corresponding to each project artifact. This output operation displays the project artifacts and their associated other project artifacts according to the project dependencies, thereby realizing the function of displaying project artifact dependencies. Compared with existing technologies, this application constructs the dependencies of each project artifact based on the project text, thus avoiding the process of users manually analyzing the relationships between other project artifacts involved in the project artifacts after directly outputting the project text. This allows users to directly determine each project artifact involved in each compilation operation and its dependent other project artifacts based on the project dependencies, eliminating the need for manual analysis and enabling users to intuitively understand the dependencies between project artifacts involved in each project compilation.

[0102] To illustrate this in more detail, the embodiments of this application provide another method for displaying project artifact dependencies, as follows: Figure 2 As shown, the method includes:

[0103] 201. Obtain project text from the project compilation pipeline.

[0104] The project text is used to represent the project artifacts required during project compilation, as well as other project artifacts associated with each project artifact; the project artifacts include ordinary artifacts, image artifacts, environment artifacts, and third-party tools.

[0105] Specifically, in this step, obtaining the project text from the project compilation pipeline includes:

[0106] The compilation tools of the project compilation pipeline are monitored, and when compilation behavior is detected, the project text corresponding to the compilation behavior is obtained.

[0107] In this embodiment, the compilation tool can be gitlab-ci.yml, which serves as the pipeline execution tool for GitLab's continuous integration services and is commonly used by users during compilation. When monitoring gitlab-ci.yml, if compilation behavior is detected, it indicates that the current user has performed a compilation on the project. This process involves operations on project artifacts, such as creation and modification, and the compilation tool will generate the corresponding project text during this process.

[0108] Furthermore, in practical applications, monitoring and data acquisition can be performed through pre-configured services, thus eliminating the need to compile the corresponding operation code every time such an operation is performed.

[0109] Based on this, in this step, monitoring the compilation tools of the project compilation pipeline and obtaining the project text corresponding to the compilation behavior when compilation behavior is detected includes:

[0110] The compilation tool is monitored through a data acquisition service, and when the compilation tool is detected to be executing a target command, the project text generated by the target command is obtained.

[0111] In this embodiment, the data acquisition service can be a Track Client, which can be pre-deployed in the compilation tool gitlab-ci.yml. When the compilation tool executes a specific instruction, the data acquisition service can be automatically triggered to acquire data, i.e., the target command described in this embodiment. Of course, the specific target command can be set according to the user's needs. This achieves the effect of monitoring and triggering the compilation tool with specific instructions through a service, thereby avoiding the need to analyze how the behavior constitutes compilation behavior, simplifying the acquisition logic. Furthermore, executing the data acquisition service through a pre-configured setup saves the amount of code required to implement the corresponding behavior during the data acquisition process, as it can be called only when needed.

[0112] 202. Perform object-oriented processing on the project text using the data tool service and forward it to the message queue.

[0113] In practical applications, the data types generated in the project compilation pipeline differ from those required for subsequent recording. Furthermore, different users may use different compilation tools or have different data formats set. This can lead to errors due to data type mismatches when analyzing project text later. Therefore, this step requires objectifying the project text using data tool services—that is, processing it into object data. Since object data has better compatibility and readability, it ensures better compatibility for subsequent parsing, recognition, and archiving based on the project text.

[0114] Simultaneously, after objectifying the project text, it needs to be forwarded to a message queue. This ensures that the project text can be sent out directly after each processing, avoiding the impact of subsequent service data congestion on the normal processing function of the current data tool service, and also ensuring decoupling when transmitting data between multiple services. Furthermore, in this embodiment, the message queue can be a Kafka queue; however, other queues can be used in practical applications, and this is not a limitation.

[0115] 203. Retrieve project text from message queue via preset service.

[0116] Once the aforementioned steps have already involved a data tool service converting the project text into object data and sending it to the message queue, the subsequent preset service needs to retrieve the project text from the message queue. By transmitting the project text through the message queue, not only is decoupling achieved between services, but it also prevents congestion even when the processing efficiency differs between the preset service and the data tool service.

[0117] 204. Parse the project text and build project dependencies based on each project artifact and its associated other project artifacts.

[0118] The project text is at least one of tool text, mirror text, and environment text;

[0119] The tool texts mentioned here include ordinary products and their associated third-party tools;

[0120] The mirrored text includes ordinary artifacts and their associated mirrored artifacts;

[0121] The environmental text includes mirrored artifacts and their associated environmental artifacts.

[0122] Since project artifacts include various types of content, such as regular artifacts, image artifacts, environment artifacts, and third-party tools, and users actually adjust and modify these project artifacts during the compilation process, the resulting project text will include information about these different types of project artifacts. In other words, the project text may involve several categories.

[0123] In one possible implementation, the project dependencies include a first dependency;

[0124] Based on this, the process of parsing the project text and constructing project dependencies based on each project artifact and its associated other project artifacts includes:

[0125] When the project text is the tool text, the tool text is parsed through the data processing service to obtain the ordinary product and its associated third-party tool, and a first dependency relationship is constructed based on each ordinary product and its third-party tool.

[0126] In this embodiment, the tool text can be a JAR package generated by the compilation tool during user operation, involving third-party tools and general artifacts. The data processing service mentioned in this embodiment can be a Track Service, a service dedicated to data processing and analysis. Based on this data processing service, the tool text can be parsed to obtain the corresponding general artifacts and the third-party tools associated with each general artifact. Since there is a dependency between the two—that is, the functionality of a general artifact requires that the associated third-party tool be correct and functioning correctly—a first dependency relationship can be established between the general artifacts and the third-party tools.

[0127] In another possible implementation, the project dependency includes a second dependency;

[0128] Based on this, the process of parsing the project text and constructing project dependencies based on each project artifact and its associated other project artifacts includes:

[0129] When the project text is the mirror text, the mirror text is parsed through the data processing service to obtain the ordinary product and its associated mirror product, and a second dependency relationship is constructed based on each ordinary product and its mirror product.

[0130] Because user adjustments and modifications to ordinary artifacts during the compilation process will also affect the parent artifacts of those artifacts, the project text between them, i.e., the mirror text described in this embodiment, is also involved. Therefore, in this step, the data processing service parses this text, and then a second dependency relationship is established between each ordinary artifact and its corresponding mirror artifact.

[0131] In another possible implementation, the project dependencies include third-party dependencies;

[0132] Based on this, the process of parsing the project text and constructing project dependencies based on each project artifact and its associated other project artifacts includes:

[0133] When the project text is specifically the environment text, the environment text is parsed through the data processing service to obtain the image artifact and its associated environment artifact, and a third dependency relationship is constructed based on each image artifact and its environment artifact.

[0134] Since environment artifacts and their corresponding image artifacts are directly related at the hierarchical level, user actions that adjust image artifacts may also involve adjustments to environment artifacts. Therefore, the resulting project text is essentially environment text containing both environment artifacts and their corresponding image artifacts. Based on this, a data processing service is used to manipulate this information to construct the relationship between environment artifacts and their corresponding image artifacts, i.e., a third dependency relationship.

[0135] Additionally, it should be noted that since there is a hierarchical relationship between third-party tools, ordinary artifacts, mirror artifacts, and environment artifacts, once the first dependency relationship, the second dependency relationship, and the third dependency relationship are obtained, the project artifact "dependency tree" or "dependency chain" as described in the previous embodiment can be determined based on the project artifacts contained in these three relationships, thereby obtaining the project dependency relationship.

[0136] 205. Perform an output operation on the project dependencies corresponding to the project artifacts.

[0137] The output operation is used to display the project artifacts and other associated project artifacts according to the project dependencies.

[0138] In this step, performing the output operation on the project dependencies corresponding to the project artifact includes:

[0139] The project dependencies are obtained from the message queue through the data recording service and recorded in the target storage area, wherein the target storage area includes at least one of a database and a search engine; the project dependencies are generated by the data processing service and then forwarded to the message queue.

[0140] In response to receiving an output instruction, the target project artifact is determined, and other project artifacts corresponding to the target project artifact are identified and displayed in the project dependency relationship.

[0141] In this embodiment, the data recording service can be a data-service, which is a service specifically designed to archive and persist received data. In other words, it can record project dependencies. The specific storage location and target storage area can be any database or search engine. Of course, in this embodiment, when the above content is entered into the database, it can be specifically stored in tables including ordinary artifacts, mirror artifacts, and environment artifacts, namely artifact_v2, dependency, and dependency_inverted. Based on this, relationships are established between the project artifacts in these three tables so that subsequent queries and displays can retrieve data from these tables.

[0142] Furthermore, in this embodiment, as described in the preceding steps, each step of acquiring and processing the project text can actually be executed based on a pre-set service. This avoids the need to compile the corresponding code each time a step is executed, allowing direct invocation based on the pre-compiled service. Simultaneously, since each compilation by the user can be recorded during the project pipeline compilation process, subsequent analysis and troubleshooting are facilitated, such as determining in which compilation action project dependencies were generated.

[0143] Based on this, after monitoring the compilation tools of the project compilation pipeline in the aforementioned steps, and obtaining the project text corresponding to the compilation behavior when compilation behavior is detected, the method further includes:

[0144] Compilation information is generated based on the project text, and the compilation information is objectified and forwarded to the message queue through the data tool service. The compilation information is used to record the compilation behavior corresponding to the project text.

[0145] The compilation information corresponding to the project text is obtained from the message queue through the data recording service, and the corresponding compilation information is added to the compilation record table;

[0146] After detecting that the data recording service has the project dependency relationship, the record information is updated in the compilation record table based on the project dependency relationship.

[0147] Specifically, this step can be implemented as follows:

[0148] The data acquisition service track client detects compilation activity in the compilation tool gitlab-ci.yml. The data acquisition service runs the command . / citrack job_start to create a record of job compilation information, which is then sent to the data tool service track service for objectification processing and pushed to the message queue Kafka. Finally, the data service reads the compilation information from the message queue Kafka and inserts a record of the corresponding job compilation information into the pipeline_job_v3 table.

[0149] Once the data tool service (track service) performs objectification processing on the second dependencies corresponding to the environment artifacts and image artifacts and pushes them to the message queue (Kafka), then, as described in this step, the data service retrieves the second dependencies from the message queue (Kafka) and stores them in the three data tables: artifact_v2, dependency, and dependency_inverted. At the same time, based on the project dependency (second dependency), the project artifact stored in the database is added to the artifacts field of the pipeline_job_v3 table, which updates the record information in the compilation record table.

[0150] Furthermore, since compilation doesn't always succeed—for example, due to design flaws or logical inconsistencies—users may abort the compilation process, or, in the case of multiple compilation attempts, stop the preceding steps by issuing a stop command at the last available step. This process necessitates marking and recording the affected project dependencies to facilitate subsequent analysis.

[0151] Based on this, after monitoring the compilation tools of the project compilation pipeline and obtaining the project text corresponding to the compilation behavior when compilation behavior is detected, the method further includes:

[0152] When the compilation tool determines that the compilation behavior has been aborted, the data acquisition service generates abort information, and the data tool service performs objectification processing on the abort information and forwards it to the message queue.

[0153] The abort information is obtained from the message queue through the data tool service, and a mark is added to the record information in the compilation record table based on the abort information. The mark information includes the compilation result and time information, and the time information is used to characterize the execution time of the compilation behavior.

[0154] Specifically, the execution process of this step can be as follows: When the completion of the compilation behavior is detected, the data acquisition service will automatically run the `. / citrack job_stop` command, generate a job termination message (i.e., termination information), and send it to the data tool service (track service). The data tool service (track service) processes the termination information into object data and pushes it to the message queue (Kafka). Finally, when the data recording service reads the termination information from the message queue (Kafka), it adds corresponding tag information to the compilation record table. The specific addition process can be as follows: If the compilation is successful: change the status field in the compilation record table to the "sucess" field and add time information (i.e., the time field duration_seconds). If the compilation fails: change the status field in the compilation record table to the "failure" field and also add the corresponding time information (i.e., the time field duration_seconds).

[0155] Furthermore, as a response to the above Figure 1 and Figure 2 In addition to the implementation of the method shown, another embodiment of this application also provides a device for displaying project artifact dependencies. This embodiment of the device for displaying project artifact dependencies corresponds to the foregoing method embodiment. For ease of reading, this embodiment of the device for displaying project artifact dependencies will not repeat the details of the foregoing method embodiment, but it should be clear that the device in this embodiment can implement all the contents of the foregoing method embodiment. Specifically, as follows... Figure 3 As shown, the demonstration device for the product dependency relationship of this project can be applied to electronic devices equipped with the Android system, including:

[0156] The acquisition unit 31 can be used to acquire project text from the project compilation pipeline, wherein the project text can be used to characterize the project artifacts required when compiling the project, as well as other project artifacts associated with each project artifact; the project artifacts include ordinary artifacts, image artifacts, environment artifacts, and third-party tools;

[0157] The construction unit 32 can be used to parse the project text and build project dependencies based on each project artifact and its associated other project artifacts;

[0158] The output unit 33 can be used to perform an output operation on the project dependency relationship corresponding to the project artifact. The output operation is used to display the project artifact and other associated project artifacts according to the project dependency relationship.

[0159] Furthermore, such as Figure 4 As shown, the acquisition unit 31 can be used to monitor the compilation tools of the project compilation pipeline, and when compilation behavior is detected, to acquire the project text corresponding to the compilation behavior.

[0160] Furthermore, such as Figure 4 As shown, the acquisition unit 31 can also be used to monitor the compilation tool through a data acquisition service, and when the compilation tool is detected to be executing a target command, to acquire the project text generated by the target command.

[0161] Furthermore, such as Figure 4 As shown, the project text is at least one of tool text, mirror text, and environment text;

[0162] The tool texts mentioned here include ordinary products and their associated third-party tools;

[0163] The mirrored text includes ordinary artifacts and their associated mirrored artifacts;

[0164] The environmental text includes mirrored artifacts and their associated environmental artifacts.

[0165] Furthermore, such as Figure 4 As shown, the project dependencies include the first dependency;

[0166] The building unit 32 includes:

[0167] The first construction module 321 can be used to parse the tool text through a data processing service when the project text is the tool text, to obtain the ordinary artifact and its associated third-party tool, and to construct a first dependency relationship based on each ordinary artifact and its third-party tool.

[0168] Furthermore, such as Figure 4 As shown, the project dependencies include a second dependency;

[0169] The building unit 32 includes:

[0170] The second construction module 322 can be used to parse the mirror text through a data processing service when the project text is the mirror text, to obtain the ordinary product and its associated mirror product, and to construct a second dependency relationship based on each ordinary product and its mirror product.

[0171] Furthermore, such as Figure 4 As shown, the project dependencies include third-party dependencies;

[0172] The building unit 32 further includes:

[0173] The third construction module 323 can be used to parse the environment text through a data processing service when the project text is specifically the environment text, to obtain the image artifact and its associated environment artifact, and to construct a third dependency relationship based on each image artifact and its environment artifact.

[0174] Furthermore, such as Figure 4 As shown, the device further includes:

[0175] Processing unit 34 can be used to perform objectification processing on the project text through data tool services and forward it to a message queue;

[0176] The text acquisition unit 35 can be used to acquire the project text from the message queue through the preset service.

[0177] Furthermore, such as Figure 4 As shown, the output unit 33 includes:

[0178] The recording module 331 can be used to obtain the project dependency relationship from the message queue through the data recording service and record the project dependency relationship in the target storage area, wherein the target storage area includes at least one of a database and a search engine; the project dependency relationship is generated by the data processing service and then forwarded to the message queue;

[0179] The output module 332 can be used to respond to receiving an output instruction, determine the target project artifact, and determine and display other project artifacts corresponding to the target project artifact in the project dependency relationship.

[0180] Furthermore, such as Figure 4 As shown, the device further includes:

[0181] Forwarding unit 36 ​​can be used to generate compilation information based on the project text, and perform objectification processing on the compilation information through data tool service and forward it to the message queue. The compilation information can be used to record the compilation behavior corresponding to the project text.

[0182] Adding unit 37 can be used to obtain the compilation information corresponding to the project text from the message queue through the data recording service, and add the corresponding compilation information to the compilation record table;

[0183] The update unit 38 can be used to update the record information in the compilation record table based on the project dependency after detecting that the data record service has recorded the project dependency.

[0184] Furthermore, such as Figure 4 As shown, the device further includes:

[0185] The sending unit 39 can be used to generate abort information through the data acquisition service when the compilation behavior is determined to be aborted by the compilation tool, and then forward the abort information to the message queue after performing objectification processing through the data tool service.

[0186] The tag adding unit 40 can be used to obtain the abort information from the message queue through the data tool service, and add tag information to the record information in the compilation record table based on the abort information. The tag information includes compilation result and time information, and the time information is used to characterize the execution time of the compilation behavior.

[0187] This application provides a method and apparatus for displaying project artifact dependencies. In this embodiment, project text is first obtained from the project compilation pipeline. This project text represents the project artifacts required during project compilation, as well as other project artifacts associated with each project artifact. Then, the project text is parsed, and project dependencies are constructed based on each project artifact and its associated other project artifacts. Finally, an output operation is performed on the project dependencies corresponding to each project artifact. This output operation displays the project artifacts and their associated other project artifacts according to the project dependencies, thereby realizing the function of displaying project artifact dependencies. Compared with the prior art, since this application constructs the dependencies of other project artifacts that have dependencies on each project artifact based on the project text, and displays them on this basis, it avoids the process where users need to manually analyze the relationships between other project artifacts involved in a project artifact after directly outputting the project text to the user. This allows users to directly determine each project artifact involved in each compilation operation and its dependent other project artifacts based on the project dependencies, eliminating the need for manual analysis and enabling users to intuitively understand the dependencies between project artifacts involved in each project compilation.

[0188] This application provides a storage medium that includes a stored program, wherein the program, when running, controls the device where the storage medium is located to execute the above-described method for displaying project artifact dependencies.

[0189] Storage media may include non-permanent memory in the form of computer-readable media, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0190] This application embodiment also provides a device for displaying project artifact dependencies. The device includes a storage medium and one or more processors. The storage medium is coupled to the processors, and the processors are configured to execute program instructions stored in the storage medium. When the program instructions are executed, they perform the project artifact dependency display method described above.

[0191] This application provides an apparatus including a processor, a memory, and a program stored in the memory and executable on the processor. When the processor executes the program, it performs the following steps: obtaining project text from a project compilation pipeline, wherein the project text is used to characterize the project artifacts required during project compilation, and other project artifacts associated with each project artifact; parsing the project text and constructing project dependencies based on each project artifact and its associated other project artifacts; and performing an output operation on the project dependencies corresponding to the project artifacts, wherein the output operation is used to display the project artifacts and their associated other project artifacts according to the project dependencies.

[0192] Furthermore, obtaining the project text from the project compilation pipeline includes:

[0193] The compilation tools of the project compilation pipeline are monitored, and when compilation behavior is detected, the project text corresponding to the compilation behavior is obtained.

[0194] Furthermore, the monitoring of the compilation tools in the project compilation pipeline, and the acquisition of the project text corresponding to the detected compilation behavior, includes:

[0195] The compilation tool is monitored through a data acquisition service, and when the compilation tool is detected to be executing a target command, the project text generated by the target command is obtained.

[0196] Furthermore, the project text is at least one of tool text, mirror text, and environment text;

[0197] The tool texts mentioned here include ordinary products and their associated third-party tools;

[0198] The mirrored text includes ordinary artifacts and their associated mirrored artifacts;

[0199] The environmental text includes mirrored artifacts and their associated environmental artifacts.

[0200] Furthermore, the project dependencies include the first dependency;

[0201] The step of parsing the project text and constructing project dependencies based on each project artifact and its associated other project artifacts includes:

[0202] When the project text is the tool text, the tool text is parsed through the data processing service to obtain the ordinary product and its associated third-party tool, and a first dependency relationship is constructed based on each ordinary product and its third-party tool.

[0203] Furthermore, the project dependencies include second dependencies;

[0204] The step of parsing the project text and constructing project dependencies based on each project artifact and its associated other project artifacts includes:

[0205] When the project text is the mirror text, the mirror text is parsed through the data processing service to obtain the ordinary product and its associated mirror product, and a second dependency relationship is constructed based on each ordinary product and its mirror product.

[0206] Furthermore, the project dependencies include third-party dependencies;

[0207] The step of parsing the project text and constructing project dependencies based on each project artifact and its associated other project artifacts includes:

[0208] When the project text is specifically the environment text, the environment text is parsed through the data processing service to obtain the image artifact and its associated environment artifact, and a third dependency relationship is constructed based on each image artifact and its environment artifact.

[0209] Furthermore, before parsing the project text and constructing project dependencies based on each project artifact and its associated other project artifacts, the method further includes:

[0210] The project text is objectified using data tools and then forwarded to a message queue.

[0211] The project text is retrieved from the message queue through the preset service.

[0212] Furthermore, the step of performing an output operation on the project dependencies corresponding to the project artifact, wherein the output operation is used to display the project artifact and other associated project artifacts according to the project dependencies, includes:

[0213] The project dependencies are obtained from the message queue through the data recording service and recorded in the target storage area, wherein the target storage area includes at least one of a database and a search engine; the project dependencies are generated by the data processing service and then forwarded to the message queue.

[0214] In response to receiving an output instruction, the target project artifact is determined, and other project artifacts corresponding to the target project artifact are identified and displayed in the project dependency relationship.

[0215] Furthermore, after monitoring the compilation tools of the project compilation pipeline and obtaining the project text corresponding to the compilation behavior when compilation behavior is detected, the method further includes:

[0216] Compilation information is generated based on the project text, and the compilation information is objectified and forwarded to the message queue through the data tool service. The compilation information is used to record the compilation behavior corresponding to the project text.

[0217] The compilation information corresponding to the project text is obtained from the message queue through the data recording service, and the corresponding compilation information is added to the compilation record table;

[0218] After detecting that the data recording service has the project dependency relationship, the record information is updated in the compilation record table based on the project dependency relationship.

[0219] Furthermore, after monitoring the compilation tools of the project compilation pipeline and obtaining the project text corresponding to the compilation behavior when compilation behavior is detected, the method further includes:

[0220] When the compilation tool determines that the compilation behavior has been aborted, the data acquisition service generates abort information, and the data tool service performs objectification processing on the abort information and forwards it to the message queue.

[0221] The abort information is obtained from the message queue through the data tool service, and a mark is added to the record information in the compilation record table based on the abort information. The mark information includes the compilation result and time information, and the time information is used to characterize the execution time of the compilation behavior.

[0222] This application also provides a computer program product, which, when executed on a data processing device, is suitable for executing program code with the following initialization method steps: obtaining project text from a project compilation pipeline, wherein the project text is used to characterize the project artifacts required during project compilation, and other project artifacts associated with each project artifact; parsing the project text, and constructing project dependencies based on each project artifact and its associated other project artifacts; performing an output operation on the project dependencies corresponding to the project artifacts, wherein the output operation is used to display the project artifacts and their associated other project artifacts according to the project dependencies, wherein the output operation is used to display the artifacts level by level according to user instructions at multiple levels, including ordinary artifacts, image artifacts, environment artifacts, and third-party tools.

[0223] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0224] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0225] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0226] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0227] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0228] Memory may include non-persistent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0229] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (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 technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0230] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0231] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0232] The above are merely embodiments of this application and are not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A method for displaying project artifact dependencies, characterized in that, include: Obtain project text from the project compilation pipeline, wherein the project text is used to characterize the project artifacts required during project compilation, and other project artifacts associated with each project artifact; the project text is at least one of tool text, mirror text, and environment text, wherein the tool text includes ordinary artifacts and their associated third-party tools, the mirror text includes ordinary artifacts and their associated mirror artifacts, and the environment text includes mirror artifacts and their associated environment artifacts. The step of obtaining project text from the project compilation pipeline includes: monitoring the compilation tools of the project compilation pipeline, and when compilation behavior is detected, obtaining the project text corresponding to the compilation behavior; The step of monitoring the compilation tools of the project compilation pipeline and obtaining the project text corresponding to the compilation behavior when compilation behavior is detected includes: monitoring the compilation tools through a data acquisition service and obtaining the project text generated by the target command when the compilation tools are detected to be executing a target command; The project text is parsed, and project dependencies are constructed based on each project artifact and its associated other project artifacts. The project dependencies include at least a first dependency. The step of parsing the project text and constructing project dependencies based on each project artifact and its associated other project artifacts includes: when the project text is the tool text, parsing the tool text through a data processing service to obtain the ordinary artifact and its associated third-party tool, and constructing the first dependency based on each ordinary artifact and its third-party tool; An output operation is performed on the project dependencies corresponding to the project artifacts. The output operation is used to display the project artifacts and other associated project artifacts according to the project dependencies.

2. The method according to claim 1, characterized in that, The project dependencies include a second dependency. The process of parsing the project text and constructing project dependencies based on each project artifact and its associated other project artifacts includes: When the project text is the mirror text, the mirror text is parsed through the data processing service to obtain the ordinary product and its associated mirror product, and a second dependency relationship is constructed based on each ordinary product and its mirror product.

3. The method according to claim 1, characterized in that, The project dependencies include third-party dependencies. The process of parsing the project text and constructing project dependencies based on each project artifact and its associated other project artifacts includes: When the project text is specifically the environment text, the environment text is parsed through the data processing service to obtain the image artifact and its associated environment artifact, and a third dependency relationship is constructed based on each image artifact and its environment artifact.

4. The method according to claim 1, characterized in that, Before parsing the project text and constructing project dependencies based on each project artifact and its associated other project artifacts, the method further includes: The project text is objectified using data tools and then forwarded to a message queue. The project text is retrieved from the message queue via a preset service.

5. The method according to claim 1, characterized in that, The step of performing an output operation on the project dependency relationship corresponding to the project artifact includes: The project dependencies are obtained from the message queue through the data recording service and recorded in the target storage area, wherein the target storage area includes at least one of a database and a search engine; the project dependencies are generated by the data processing service and then forwarded to the message queue. In response to receiving an output instruction, the target project artifact is determined, and other project artifacts corresponding to the target project artifact are identified and displayed in the project dependency relationship.

6. The method according to claim 1, characterized in that, After monitoring the compilation tools of the project compilation pipeline and obtaining the project text corresponding to the compilation behavior when compilation behavior is detected, the method further includes: Compilation information is generated based on the project text, and the compilation information is objectified and forwarded to the message queue through the data tool service. The compilation information is used to record the compilation behavior corresponding to the project text. The compilation information corresponding to the project text is obtained from the message queue through the data recording service, and the corresponding compilation information is added to the compilation record table; After detecting that the data recording service has the project dependency relationship, the record information is updated in the compilation record table based on the project dependency relationship.

7. The method according to claim 6, characterized in that, After monitoring the compilation tools of the project compilation pipeline and obtaining the project text corresponding to the compilation behavior when compilation behavior is detected, the method further includes: When the compilation tool determines that the compilation behavior has been aborted, the data acquisition service generates abort information, and the data tool service performs objectification processing on the abort information and forwards it to the message queue. The abort information is obtained from the message queue through the data tool service, and a mark is added to the record information in the compilation record table based on the abort information. The mark information includes the compilation result and time information, and the time information is used to characterize the execution time of the compilation behavior.

8. A device for displaying the dependency relationship of project products, characterized in that, The device includes: An acquisition unit is used to acquire project text from a project compilation pipeline, wherein the project text is used to characterize the project artifacts required during project compilation, and other project artifacts associated with each project artifact; the project text is at least one of tool text, mirror text, and environment text, the tool text includes ordinary artifacts and their associated third-party tools, the mirror text includes ordinary artifacts and their associated mirror artifacts, and the environment text includes mirror artifacts and their associated environment artifacts. The acquisition unit is specifically used to monitor the compilation tools of the project compilation pipeline, and when compilation behavior is detected, to acquire the project text corresponding to the compilation behavior; The acquisition unit is further specifically used to monitor the compilation tool through a data acquisition service, and when the compilation tool is detected to be executing a target command, to acquire the project text generated by the target command; A building unit is used to parse the project text and build project dependencies based on each project artifact and its associated other project artifacts, wherein the project dependencies include at least a first dependency. The construction unit includes: a first construction module, used to parse the tool text through a data processing service when the project text is the tool text, to obtain the ordinary artifact and its associated third-party tool, and to construct the first dependency relationship based on each ordinary artifact and its third-party tool; The output unit is used to perform an output operation on the project dependency relationship corresponding to the project artifact. The output operation is used to display the project artifact and other associated project artifacts according to the project dependency relationship.

9. A storage medium, characterized in that, The storage medium includes a stored program, wherein, when the program is executed, the device on which the storage medium is located is controlled to perform the method for displaying the project artifact dependencies as described in any one of claims 1 to 7.

10. A device for displaying the dependency relationship of project artifacts, characterized in that, The device includes a storage medium; and one or more processors, the storage medium being coupled to the processors, the processors being configured to execute program instructions stored in the storage medium; the program instructions, when executed, perform the method for displaying the project artifact dependencies according to any one of claims 1 to 7.

Citation Information

Patent Citations

  • Dependence relationship display method and device, storage medium and electronic equipment

    CN115185535A