CN109766128A - Project aggregation report generation method and device and storage medium - Google Patents

Abstract

The invention discloses a method for generating a project aggregation report, comprising: obtaining at least one project, determining at least one first project according to the at least one project; adding the at least one first project to a preset second project; The second project to which the at least one first project is added is used as a target project, and the source code of the target project is aggregated to obtain a project aggregation report for the at least one first project. The invention also discloses an item aggregation report generating device and a computer-readable storage medium.

Description

Method, device and storage medium for generating project aggregation report

technical field

The present invention relates to Internet information technology, and in particular, to a method, device and computer-readable storage medium for generating an item aggregation report.

Background technique

Under the microservice architecture, a technical team usually manages multiple projects, each of which belongs to a different distributed version control system (Git) repository. In order to generate a quality report, continuous integration of each project is generally performed on Jenkins, and finally a project aggregation report is manually aggregated. The Jenkins is a continuous integration tool, which can regularly compile, run the corresponding code, run integration tests, and display the running results as a project aggregation report. The obtained project aggregation report refers to the code quality report generated by some static checking tools and compilation tools during the continuous integration process of the software project; the generated code quality report may include code quantity, defect rate, test coverage, Compile quality data such as packaging results.

Due to the fine-grained splitting of each project under the microservice architecture, a technical team may need to manage dozens to dozens of projects at the same time. Using the above-mentioned project aggregation report generation method requires technicians to manually aggregate reports corresponding to multiple projects. , the generation efficiency of the project aggregation report is low.

SUMMARY OF THE INVENTION

In view of this, the main purpose of the present invention is to provide a method, apparatus and computer-readable storage medium for generating an item aggregation report.

In order to achieve the above object, the technical scheme of the present invention is achieved in this way:

An embodiment of the present invention provides a method for generating an item aggregation report, the method comprising:

obtaining at least one project, and determining at least one first project according to the at least one project; adding the at least one first project to a preset second project;

The second project to which the at least one first project is added is used as a target project, and the source code of the target project is aggregated to obtain a project aggregation report for the at least one first project.

In the above solution, before adding the at least one first project to the preset second project, the method further includes:

In the configuration file of the second project, add a description of the parent dependency of the at least one first project to the second project;

According to the parent dependency description, a parent-child dependency relationship between the at least one first project and the second project is established.

In the above solution, before the source code of the target project is aggregated, the method includes:

Determine at least one first jar package required by the first project; the first jar package is a jar package that the first project cannot obtain through the underlying public package;

A dependency description for the at least one first jar package is added to the configuration file of the second project, and the first project acquires the at least one first jar package according to the dependency description in the configuration file.

In the above solution, before the source code of the target project is aggregated, the method includes:

When it is determined that the at least one first project contains a public project and the public project depends on the second jar package, modify the dependency description for the jar package in the configuration file of the public project to cancel the public project's effect on the Dependency of the second jar package; the second jar package is a third-party jar package except the jar package included in the maven private repository where the second project is deployed.

In the above solution, before the source code of the target project is aggregated, the method further includes:

Obtain the source code of the second project and save it in the root directory;

Obtain the source code of the at least one first project in turn, and create at least one subdirectory under the root directory; one of the subdirectories corresponds to save a source code of the first project;

A tree-like directory is obtained from the root directory and the at least one subdirectory.

In the above solution, the source code of the target project is aggregated to obtain a project aggregation report for the at least one first project, including:

The source code of the target project is aggregated layer by layer according to the tree-like directory, and a project aggregation report for the at least one first project is obtained according to the aggregation result.

An embodiment of the present invention provides an apparatus for generating an item aggregation report, the apparatus includes: a first processing module and a second processing module; wherein,

The first processing module is configured to obtain at least one project, and determine at least one first project according to the at least one project; add the at least one first project to a preset second project;

The second processing module is configured to use the second project added with the at least one first project as a target project, aggregate the source code of the target project, and obtain a project aggregation report for the at least one first project .

In the above solution, the second processing module is specifically configured to obtain the source code of the second project and save it in the root directory before aggregating the source code of the target project; sequentially obtain the source code of the at least one first project , create at least one subdirectory under the root directory; one of the subdirectories corresponds to save a source code of the first project; obtain a tree-like directory according to the root directory and the at least one subdirectory; according to the tree The source code of the target project is aggregated layer by layer in the state directory, and a project aggregation report for the at least one first project is obtained according to the aggregation result.

An embodiment of the present invention provides an apparatus for generating an item aggregation report, the apparatus includes: a processor and a memory for storing a computer program that can be executed on the processor; wherein,

The processor is configured to execute the steps of any one of the above-mentioned methods for generating an item aggregation report when running the computer program.

Embodiments of the present invention further provide a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, implements the steps of any of the foregoing methods for generating an item aggregation report.

The method, device, and computer-readable storage medium for generating a project aggregation report provided by the embodiments of the present invention obtain at least one project, determine at least one first project according to the at least one project; add the at least one first project to A preset second project; taking the second project added with the at least one first project as a target project, and aggregating the source code of the target project to obtain a project aggregation report for the at least one first project. In the embodiment of the present invention, a target project with a hierarchical relationship is established according to each first project and the second project, so that the relationship between each first project can be determined; according to the relationship between each first project, the relationship between each project can be determined, so that Jenkins can check multiple first projects at one time to generate a project aggregation report for multiple projects, which improves the generation efficiency of the project aggregation report.

Description of drawings

1 is a schematic flowchart of a method for generating a project aggregation report according to an embodiment of the present invention;

2 is a schematic flowchart of another method for generating a project aggregation report according to an embodiment of the present invention;

3 is a schematic structural diagram of an apparatus for generating an item aggregation report according to an embodiment of the present invention;

FIG. 4 is a schematic structural diagram of another device for generating an item aggregation report according to an embodiment of the present invention.

Detailed ways

In various embodiments of the present invention, at least one project is obtained, at least one first project is determined according to the at least one project; the at least one first project is added to a preset second project; A second project of at least one first project is used as a target project, and the source code of the target project is aggregated to obtain a project aggregation report for the at least one first project.

The present invention will be described in further detail below in conjunction with the embodiments.

FIG. 1 is a schematic flowchart of a method for generating a project aggregation report according to an embodiment of the present invention; the method can be applied to a server; as shown in FIG. 1 , the method includes:

Step 101: Obtain at least one project, and determine at least one first project according to the at least one project; add the at least one first project to a preset second project.

Here, each first project may belong to different projects, and the projects may belong to different Git repositories, that is, each first project may belong to different Git repositories. The Git is an open source distributed version control system that can handle version management of projects ranging from very small to very large efficiently and at high speed.

Here, for each item, one or more first projects may be determined.

The determining at least one first project according to at least one project includes: determining at least one first project according to each of the at least one project.

Specifically, before the step 101, the method includes: acquiring a preset second project.

Here, the second project may be an empty project; that is, the second project is neither used for storing business data nor performing business operations.

The acquiring a preset second project includes: creating an empty project, adding a tool for performing quality inspection to obtain a project aggregation report in the project; and using the project after adding the tool as the second project.

Here, the tool is a quality check tool required for generating a project aggregation report, which can be specifically used for static check and coverage check. The quality checking tool can use existing tools, so it will not be repeated here. Specifically, the quality inspection report tool can be added by writing the code corresponding to the quality inspection tool or writing the description of the quality inspection tool in the configuration file (POM, Project Object Model) file of the project. to the said project.

Here, the POM file is a configuration file in an Extensible Markup Language (XML, Extensible Markup Language) format; each project corresponds to its POM file. The POM file is used to describe the basic information of the maven project corresponding to the project, such as groupId, artifactId, version, etc., and can also configure the maven private repository, packaging form, dependencies, and the like.

Specifically, the adding the at least one first project to the preset second project includes:

In the configuration file of the second project, that is, the POM file, add a description of the parent dependency of each first project in the at least one first project to the second project;

According to the parent dependency description, a parent-child dependency relationship between each first project in the at least one first project and the second project is established. After the dependencies are established, each first project can be added to the second project.

Here, a parent dependency description for the second project may also be added to the POM file of each first project, and the parent dependency description may be the same configuration description, thereby reducing the workload of separate configuration.

By adding a parent dependency description, the first project corresponding to each project in multiple Git repositories under the Jenkins architecture is added as a sub-project to the second project, that is, the second project is used as the parent of the first project project.

The step 101 further includes: after adding each first project to the second project, deploying the second project to a maven private repository, so that each first project can be referenced when generating a project aggregation report.

It should be noted that since the above second project itself is an empty project, that is, a project without the spring bootmain function (such as a public project as a basic service), an error may be reported when deploying it to the maven private repository: Unable to find main class. Therefore, in order to deploy the second project into the maven private repository, the configuration file of the second project is modified. Specifically, the configuration file of the second project can be modified by adding relevant configurations to the maven plug-in in the second project, and adding relevant configurations to the maven plug-in in the second project includes: maven in the second project Add the layout node: <configuration> node to the spring-boot-maven-plugin sub-plugin in the plug-in, and add the layout configuration to this node: <layout>NONE</layout>.

Step 102: Use the second project added with the at least one first project as a target project, and aggregate the source code of the target project to obtain a project aggregation report for the at least one first project.

Specifically, before the aggregating the source code of the target project, the method includes:

Determine at least one first jar package required by each first project in the at least one first project; the first jar package is a jar package that the first project cannot obtain through the underlying public package;

A dependency description for the at least one first jar package is added to the configuration file of the second project, so that each first project in the at least one first project is based on the dependency description in the configuration file of the second project Obtain the at least one first jar package.

Here, the first jar package is a jar package that cannot be obtained by the first project through the underlying public package, such as a jar package that depends on compilation time, and the jar package that depends on compile time may include: lombok, junit, and the like. In this embodiment, the dependency description in the public package can be added to the POM file of the second project, that is, the parent project, for example, the dependency configuration can be added through the subordinate <dependency> tag, and the <scope>compile</scope> tag can be used to add the dependency configuration. The first jar package is configured as a compile-time dependency, so as to implement dependency modification on the jar package that cannot be obtained through the underlying public package.

Through the above steps, the dependency of the jar package that cannot be obtained through the underlying public package is modified, so that the jar package that cannot be obtained through the underlying public package can be referenced by the compilation tool when the first project, that is, the subproject, is compiled.

The jar package is an archive file with an extension of ".jar", which is not only used for data compression and distribution, but also for deploying encapsulated libraries, components and plug-in programs, and can be directly used by tools such as compilers. use.

In this embodiment, considering the project packaging (Package), also known as the release package, the third-party jar package it depends on is usually introduced into the final project jar package, that is, the jar package of the target project, so as to pass the java- jar runs. However, when there is a public project in the subproject, the public project will also introduce the third-party jar package it depends on into its own jar package, and then be depended on by the final project jar package. This packaging method will cause the jar package obtained by packaging the public project to be too large, which is inconvenient to be used in the projects corresponding to other sub-projects and the project corresponding to the parent project. It is necessary to support the third-party jar not to be imported when the public package is packaged. Bag.

Specifically, before the aggregating the source code of the target project, the method includes:

When it is determined that the at least one first project contains a public project and the public project depends on the second jar package, modify the dependency description for the jar package in the configuration file of the public project to cancel the public project's effect on the Dependency of the second jar package; the second jar package is a third-party jar package except the jar package included in the maven private repository where the second project is deployed.

For example, in this embodiment, the packaging process can be modified by adding a configuration description of repackage (repackage) to the POM file of the public project. Specifically, you can add the execution <execution> node in the spring-boot-maven-plugin plug-in, and add the <goal>repackage</goal> configuration to the node to complete the addition of the repackage configuration to the POM file of the public project.

Specifically, before the aggregating the source code of the target project, the method further includes:

Obtain the source code of the second project and save it in the root directory;

Obtain the source code of each first project in the at least one first project in turn, and create at least one subdirectory under the root directory; one of the subdirectories corresponds to save the source code of one of the first projects;

A tree-like directory is obtained from the root directory and the at least one subdirectory.

Specifically, the aggregating the source code of the target project to obtain a project aggregation report for the at least one first project, including:

The source code of the target project is aggregated layer by layer according to the tree-like directory, and a project aggregation report for the at least one first project is obtained according to the aggregation result.

Specifically, when aggregating the source code (specifically Git source code) of multiple first projects in the target project on Jenkins, you can first download the source code of the parent project, that is, the second project; and then use the multiple-scms plug-in of the parent project. Create at least one subdirectory in the same directory, download the source code of each subproject to the newly created corresponding subdirectory, and save the source code of a subproject in a subdirectory; thus obtain a tree-like directory containing the source code of the parent and child projects (specifically The application process can be displayed in the workspace root directory of Jenkins).

After obtaining the tree-like directory, execute the inspection command under the tree-like directory (that is, the workspace root directory), that is, execute the command of the quality inspection tool in the configuration file of the second project, and obtain sub-layers layer by layer during the execution process. The source code of the project (ie, the first project) is aggregated layer by layer, and finally a project aggregation report containing the inspection results of all sub-projects can be generated.

It should be noted that, considering the exclusivity of the source code download, only one source code is allowed to be downloaded in the same directory, that is, if the source code of the subproject is downloaded first, the source code of the subproject will be deleted when the source code of the parent project is downloaded. Therefore, in this embodiment, the source code of the subproject will be deleted. First download the parent project as the top-level directory, and then create a subdirectory in the same directory through the multiple-scms plugin, and the name of the created subdirectory is the same as the name of the subproject node in the parent project configuration file, so that Jenkins can download the downloaded Subdirectories are checked as subprojects.

The above method provided in this embodiment does not require handwritten scripts or excessive modifications to the projects corresponding to each project, less intrusion into the project, and convenient automatic inspection; and supports the inspection of the parent and child projects in different Git repositories, which is convenient for the parent and child projects to do separately. Permission management and branch management.

FIG. 2 is a schematic flowchart of another method for generating an item aggregation report according to an embodiment of the present invention; as shown in FIG. 2 , the method includes:

Step 201: Acquire a preset parent project.

Here, the parent project, that is, the second project described in FIG. 1 , may be an empty project, that is, the parent project is neither used for storing business data nor performing business operations.

Before the step 201, it includes: adding a parent project. Specifically, it includes: writing a corresponding configuration file, that is, a POM file, for the parent project, and writing a quality inspection tool required for generating a project aggregation report into the POM file of the parent project when writing the POM file.

It should be noted that since the above parent project itself is an empty project, that is, a project without a spring boot main function (such as a public project as a basic service), an error may be reported when deploying it to the maven private repository: Unable to find main class. Therefore, in order to deploy the parent project into the maven private repository, the POM file of the parent project is modified. Specifically, the POM file of the parent project can be modified by adding relevant configurations to the maven plug-in in the parent project, and adding relevant configurations to the maven plug-in in the parent project, including: spring in the maven plug-in in the parent project Add a layout node to the -boot-maven-plugin sub-plugin: <configuration> node, and add a layout configuration to this node: <layout>NONE</layout>.

Step 202: Add at least one first project to the parent project as a child project of the parent project.

Specifically, the first project is a project corresponding to projects in multiple Git repositories under the Jenkins architecture, which is added to the parent project as a sub-project. And deploy the parent project to the maven private repository so that the child project can be referenced when generating the Jenkins project aggregation report.

The adding at least one first project to the parent project includes: in the POM file of the parent project, adding a parent dependency description of each first project in the at least one first project to the parent project; According to the parent dependency description, a parent-child dependency relationship between each first project and the parent project is established; after the dependency relationship is established, each first project can be added to the parent project.

Alternatively, a parent dependency description specifying the parent project may be added to the POM files of multiple first projects, and the same dependency description is uniformly used in each first project, thereby reducing the workload of separate configuration.

Step 203 , modify the dependency of the jar package that cannot be obtained through the underlying public package.

Specifically, after adding the parent project and sub-project, considering that some jar packages cannot be obtained through the underlying public package, it is necessary to modify the dependencies of the jar package that cannot be obtained through the underlying public package, so that the jar package can be compiled in the sub-project. is referenced by the compilation tools.

Specifically, before the source code of the target project is aggregated, the method includes:

Determine at least one first jar package required by each first project; the first jar package is a jar package that cannot be obtained by the first project through the underlying public package; in the POM file of the parent project The dependency description of at least one first jar package, and the at least one first project obtains the at least one first jar package according to the dependency description in the POM file of the parent project.

For example, when modifying the dependencies of a jar package that cannot be obtained through the underlying public package, you can add the dependency description in the public package to the POM file of the parent project, such as adding dependency configuration through the <dependency> tag, And configure the jar package as a compile-time dependency through the <scope>compile</scope> tag.

Step 204: Modify the packaging process.

Considering that when a microservice project is packaged, the dependent third-party jar package is usually introduced into the final project jar package so that it can be run through java-jar. However, when there is a public project in the subproject, the public project will also introduce the third-party jar package it depends on into its own jar package, and then be depended on by the final project jar package. This packaging method will cause the jar package obtained by packaging the public project to be too large, which is inconvenient to be used in the projects corresponding to other sub-projects and the project corresponding to the parent project. It is necessary to support the third-party jar not to be imported when the public package is packaged. Bag.

Specifically, before the aggregating the source code of the target project, the method includes:

When it is determined that the at least one first project contains a public project and the public project depends on the second jar package, modify the dependency description for the jar package in the POM file of the public project to cancel the public project's influence on the Dependency of the second jar package; the second jar package is a third-party jar package except the jar package included in the maven private repository where the second project is deployed.

For example, in this embodiment, the packaging process can be modified by adding a configuration description of repackage (repackage) to the POM file of the public project. Specifically, you can add the execution <execution> node in the spring-boot-maven-plugin plug-in, and add the <goal>repackage</goal> configuration to the node to complete the addition of the repackage configuration to the POM file of the public project.

Step 205: Use the parent project to which the at least one first project is added as a target project, and aggregate the source code of the target project to obtain a project aggregation report for the at least one first project.

Specifically, the step 205 includes: downloading the source code of the parent project; then creating a subdirectory under the same directory through the multiple-scms plug-in, and then downloading the source code of the subproject, that is, each first project, to the newly created corresponding subdirectory Then, a complete tree-like directory containing the source code of the parent and child projects is generated in the workspace root directory of Jenkins, ready for a comprehensive inspection;

After obtaining the tree-like directory, execute the inspection command in the tree-like directory, that is, the above-mentioned workspace directory, execute the command of the quality inspection tool configured in the POM file of the parent project, and obtain the source code of the subproject layer by layer during the execution process. And aggregate it layer by layer, and finally generate a project aggregation report that includes the inspection results of all sub-projects at the same time.

It should be noted that, considering the exclusivity of Git source code download, only one source code is allowed to be downloaded in the same directory, that is, if the source code of the subproject is downloaded first, the source code of the subproject will be deleted when the source code of the parent project is downloaded. Therefore, this embodiment First download the parent project as the top-level directory, and then create a subdirectory in the same directory through the multiple-scms plugin, and the name of the created subdirectory is the same as the name of the subproject node in the POM file of the parent project, so that Jenkins can Downloaded subdirectories are checked as subprojects.

FIG. 3 is a schematic structural diagram of an apparatus for generating an item aggregation report according to an embodiment of the present invention; as shown in FIG. 3 , the apparatus includes: a first processing module 301 and a second processing module 302 .

The first processing module 301 is configured to obtain at least one project, determine at least one first project according to the at least one project, and add the at least one first project to a preset second project.

The second processing module 302 is configured to use the second project added with the at least one first project as a target project, and aggregate the source code of the target project to obtain a project aggregation for the at least one first project Report.

Specifically, the first processing module 301 is configured to, before adding the at least one first project to a preset second project, add the at least one first project in the configuration file of the second project A parent dependency description for the second project; according to the parent dependency description, establish a parent-child dependency relationship between the at least one first project and the second project.

Specifically, the second processing module 302 is configured to determine at least one first jar package required by the first project before aggregating the source code of the target project; the first jar package is the first jar package. A jar package that cannot be obtained through the underlying public package for a project; a dependency description for the at least one first jar package is added to the configuration file of the second project, and the first project is based on the dependency description in the configuration file. Obtain the at least one first jar package.

Specifically, the second processing module 302 is configured to, before aggregating the source code of the target project, determine that the at least one first project includes a public project and the public project depends on the second jar package, modify the The dependency description for the jar package in the configuration file of the public project, so as to cancel the dependency of the public project on the second jar package; the second jar package is private except for the maven in which the second project is deployed. A third-party jar package other than the jar package contained in the repository.

Specifically, the second processing module 302 is configured to obtain the source code of the second project and save it in the root directory before aggregating the source code of the target project; sequentially obtain the source code of the at least one first project, At least one subdirectory is created under the root directory; one of the subdirectories corresponds to save a source code of the first project; a tree-like directory is obtained according to the root directory and the at least one subdirectory.

Specifically, the second processing module 302 is configured to perform layer-by-layer aggregation of the source code of the target project according to the tree-like directory, and obtain a project aggregation report for the at least one first project according to the aggregation result.

It should be noted that when the device for generating an item aggregation report provided by the above embodiment performs the method for generating an item aggregation report, only the division of the above program modules is used as an example for illustration. In practical applications, the above processing may be allocated as required. It is completed by different program modules, that is, the internal structure of the device is divided into different program modules, so as to complete all or part of the processing described above. In addition, the device for generating an item aggregation report provided by the above embodiment and the embodiment of the method for generating an item aggregation report belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.

FIG. 4 is a schematic structural diagram of another device for generating an item aggregation report according to an embodiment of the present invention. The apparatus 40 includes: a processor 401 and a memory 402 for storing a computer program that can be executed on the processor; wherein, the processor 401 is configured to, when running the computer program, execute: obtain at least one item , determine at least one first project according to the at least one project; add the at least one first project to a preset second project; take the second project to which the at least one first project is added as a target project, The source code of the target project is aggregated to obtain a project aggregation report for the at least one first project.

In one embodiment, the processor 401 is further configured to, when running the computer program, execute: before adding the at least one first project to a preset second project, in the configuration file of the second project , adding a parent dependency description of the at least one first project to the second project; and establishing a parent-child dependency relationship between the at least one first project and the second project according to the parent dependency description.

In one embodiment, the processor 401 is further configured to, when running the computer program, execute: before aggregating the source code of the target project, determine at least one first jar package required by the first project; The first jar package is a jar package that the first project cannot obtain through the underlying public package; a dependency description for the at least one first jar package is added to the configuration file of the second project, and the first jar package is The project obtains the at least one first jar package according to the dependency description in the configuration file.

In one embodiment, the processor 401 is further configured to, when running the computer program, execute: before aggregating the source code of the target project, determine that the at least one first project includes a public project, and the When the public project depends on the second jar package, modify the dependency description for the jar package in the configuration file of the public project to cancel the public project's dependency on the second jar package; A third-party jar package other than the jar package contained in the maven private repository of the second project is deployed.

In one embodiment, the processor 401 is further configured to, when running the computer program, execute: before aggregating the source code of the target project, obtain the source code of the second project and save it in the root directory; obtain the source code in sequence; For the source code of the at least one first project, create at least one subdirectory under the root directory; one of the subdirectories corresponds to save the source code of the first project; according to the root directory and the at least one subdirectory Get a tree-like directory.

In one embodiment, the processor 401 is further configured to perform, when running the computer program: perform layer-by-layer aggregation on the source code of the target project according to the tree-like directory, and obtain the at least one target project according to the aggregation result. Project aggregation report of the first project.

It should be noted that the device for generating an item aggregation report provided by the above embodiment and the embodiment of the method for generating an item aggregation report belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.

In practical application, the apparatus 40 may further include: at least one network interface 403 . The various components in the generating device 40 of the project aggregation report are coupled together by a bus system 404 . It will be appreciated that the bus system 404 is used to implement the connection communication between these components. In addition to the data bus, the bus system 404 also includes a power bus, a control bus, and a status signal bus. However, for clarity of illustration, the various buses are labeled as bus system 404 in FIG. 4 . The number of the processors 404 may be at least one. The network interface 403 is used for wired or wireless communication between the item aggregation report generating apparatus 40 and other devices.

The memory 402 in the embodiment of the present invention is used for storing various types of data to support the operation of the generating apparatus 40 for the item aggregation report.

The methods disclosed in the above embodiments of the present invention may be applied to the processor 401 or implemented by the processor 401 . The processor 401 may be an integrated circuit chip with signal processing capability. In the implementation process, each step of the above-mentioned method can be completed by an integrated logic circuit of hardware in the processor 401 or an instruction in the form of software. The above-mentioned processor 401 may be a general-purpose processor, a digital signal processor (DSP, DiGital Signal Processor), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. The processor 401 may implement or execute the methods, steps, and logical block diagrams disclosed in the embodiments of the present invention. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in combination with the embodiments of the present invention can be directly embodied as being executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium, and the storage medium is located in the memory 402, and the processor 401 reads the information in the memory 402, and completes the steps of the foregoing method in combination with its hardware.

In an exemplary embodiment, the generating device 40 of the item aggregation report may be implemented by one or more application-specific integrated circuits (ASIC, Application Specific Integrated Circuit), DSP, Programmable Logic Device (PLD, Programmable Logic Device), complex programmable Logic Device (CPLD, Complex Programmable LogicDevice), Field Programmable Gate Array (FPGA, Field-Programmable Gate Array), General Purpose Processor, Controller, Microcontroller (MCU, Micro Controller Unit), Microprocessor (Microprocessor), or other electronic components to implement the aforementioned method.

Embodiments of the present invention further provide a computer-readable storage medium, on which a computer program is stored, and when the computer program is run by a processor, execute: obtain at least one item, and determine at least one first item according to the at least one item project; adding the at least one first project to a preset second project; taking the second project to which the at least one first project is added as a target project, and aggregating the source code of the target project to obtain A project aggregation report describing at least one first project.

In one embodiment, when the computer program is run by the processor, execute: before adding the at least one first project to a preset second project, in the configuration file of the second project, add the A parent dependency description of at least one first project on the second project; and a parent-child dependency relationship between the at least one first project and the second project is established according to the parent dependency description.

In one embodiment, when the computer program is run by the processor, execute: before aggregating the source code of the target project, determine at least one first jar package required by the first project; the first jar The package is a jar package that the first project cannot obtain through the underlying public package; a dependency description for the at least one first jar package is added to the configuration file of the second project, and the first project is based on the configuration The dependency description in the file obtains the at least one first jar package.

In one embodiment, when the computer program is run by the processor, execute: before aggregating the source code of the target project, determine that the at least one first project includes a public project, and the public project depends on the second project. jar package, modify the dependency description for the jar package in the configuration file of the public project to cancel the dependency of the public project on the second jar package; The third-party jar package outside the jar package contained in the maven private repository of the second project.

In one embodiment, when the computer program is run by the processor, execute: before aggregating the source code of the target project, obtain the source code of the second project and save it in the root directory; sequentially obtain the at least one first project. For the source code of a project, at least one subdirectory is created under the root directory; one of the subdirectories correspondingly stores a source code of the first project; a tree-like directory is obtained according to the root directory and the at least one subdirectory.

In one embodiment, when the computer program is run by the processor, execute: perform layer-by-layer aggregation on the source code of the target project according to the tree-like directory, and obtain a project for the at least one first project according to the aggregation result Aggregated reports.

In the several embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other manners. The device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined, or Can be integrated into another system, or some features can be ignored, or not implemented. In addition, the coupling, or direct coupling, or communication connection between the components shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be electrical, mechanical or other forms. of.

The unit described above as a separate component may or may not be physically separated, and the component displayed as a unit may or may not be a physical unit, that is, it may be located in one place or distributed to multiple network units; Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present invention may all be integrated into one processing unit, or each unit may be separately used as a unit, or two or more units may be integrated into one unit; the above-mentioned integration The unit can be implemented either in the form of hardware or in the form of hardware plus software functional units.

Those of ordinary skill in the art can understand that all or part of the steps of implementing the above method embodiments can be completed by program instructions related to hardware, the aforementioned program can be stored in a computer-readable storage medium, and when the program is executed, execute Including the steps of the above-mentioned method embodiment; and the aforementioned storage medium includes: a mobile storage device, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk and other various A medium on which program code can be stored.

Alternatively, if the above-mentioned integrated unit of the present invention is implemented in the form of a software function module and sold or used as an independent product, it may also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of the present invention may be embodied in the form of software products in essence or the parts that make contributions to the prior art. The computer software products are stored in a storage medium and include several instructions for A computer device (which may be a personal computer, a server, or a network device, etc.) is caused to execute all or part of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes: a removable storage device, a ROM, a RAM, a magnetic disk or an optical disk and other mediums that can store program codes.

The above are only preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention. Any modifications, equivalent replacements and improvements made within the spirit and principles of the present invention shall be included in the within the protection scope of the present invention.

Claims (10)

1. a generation method of project aggregation report, is characterized in that, described method comprises: obtaining at least one project, and determining at least one first project according to the at least one project; adding the at least one first project to a preset second project; The second project to which the at least one first project is added is used as a target project, and the source code of the target project is aggregated to obtain a project aggregation report for the at least one first project. 2. The method according to claim 1, wherein, before the adding the at least one first project to the preset second project, the method further comprises: In the configuration file of the second project, add a description of the parent dependency of the at least one first project to the second project; According to the parent dependency description, a parent-child dependency relationship between the at least one first project and the second project is established. 3. The method according to claim 1, wherein, before the source code of the target project is aggregated, the method comprises: Determine at least one first jar package required by the first project; the first jar package is a jar package that the first project cannot obtain through the underlying public package; A dependency description for the at least one first jar package is added to the configuration file of the second project, and the first project acquires the at least one first jar package according to the dependency description in the configuration file. 4. The method according to claim 1, wherein before the source code of the target project is aggregated, the method comprises: When it is determined that the at least one first project contains a public project and the public project depends on the second jar package, modify the dependency description for the jar package in the configuration file of the public project to cancel the public project's effect on the Dependency of the second jar package; the second jar package is a third-party jar package except the jar package included in the maven private repository where the second project is deployed. 5. The method according to claim 1, wherein before the source code of the target project is aggregated, the method further comprises: Obtain the source code of the second project and save it in the root directory; Obtain the source code of the at least one first project in turn, and create at least one subdirectory under the root directory; one of the subdirectories corresponds to save a source code of the first project; A tree-like directory is obtained from the root directory and the at least one subdirectory. 6. The method according to claim 5, wherein the aggregating the source code of the target project to obtain a project aggregation report for the at least one first project, comprising: The source code of the target project is aggregated layer by layer according to the tree-like directory, and a project aggregation report for the at least one first project is obtained according to the aggregation result. 7. An apparatus for generating an item aggregation report, wherein the apparatus comprises: a first processing module and a second processing module; wherein, The first processing module is configured to obtain at least one project, and determine at least one first project according to the at least one project; add the at least one first project to a preset second project; The second processing module is configured to use the second project added with the at least one first project as a target project, aggregate the source code of the target project, and obtain a project aggregation report for the at least one first project . 8. The device according to claim 7, wherein the second processing module is specifically configured to obtain the source code of the second project and save it in the root directory before aggregating the source code of the target project; Obtain the source code of the at least one first project in turn, and create at least one subdirectory under the root directory; one of the subdirectories corresponds to save the source code of one of the first projects; according to the root directory and the at least one A tree-like directory is obtained from the sub-directory; the source code of the target project is aggregated layer by layer according to the tree-like directory, and a project aggregation report for the at least one first project is obtained according to the aggregation result. 9. An apparatus for generating an item aggregation report, wherein the apparatus comprises: a processor and a memory for storing a computer program that can be run on the processor; wherein, When the processor is configured to run the computer program, the steps of the method according to any one of claims 1 to 6 are executed. 10. A computer-readable storage medium on which a computer program is stored, characterized in that, when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.