Difference between revisions of "Continuous Integration: Dependency Walker Jenkins Pipeline"
From Gcube Wiki
Manuele.simi (Talk | contribs) (Created page with "The Dependency Walker pipeline allows to navigate the dependencies among projects in Jenkins. Given the name of a Jenkins project (P): * navigate the maven modules built by...") |
Manuele.simi (Talk | contribs) |
||
| Line 2: | Line 2: | ||
Given the name of a Jenkins project (P): | Given the name of a Jenkins project (P): | ||
| − | + | * navigate the maven modules built by P | |
| − | + | * recursively analyze the module's dependencies and their Jenkins projects | |
| − | + | * generate the list of projects that have modules depending on each maven module in P | |
| − | + | * print a formatted report of the information extracted from the analysis. | |
| + | |||
| + | = Interface = | ||
| + | |||
| + | = Report = | ||
| + | |||
| + | == Sample Report == | ||
Revision as of 02:33, 13 March 2020
The Dependency Walker pipeline allows to navigate the dependencies among projects in Jenkins.
Given the name of a Jenkins project (P):
- navigate the maven modules built by P
- recursively analyze the module's dependencies and their Jenkins projects
- generate the list of projects that have modules depending on each maven module in P
- print a formatted report of the information extracted from the analysis.
