How to Report on GCs that have Component Skew?
![]()
Hello,
I need some guidance for reporting with JRS based on LQE.
Context:
we still have a lot of teams that are in the process of adopting GCs and are rather fresh in the topic.
to support them we have a small expert team that tries to proactively find issues in the GCs the product teams create and offer to help them remove issues.
Question:
I would like to create a report that lists al GCs on our Server that currently have Component Skew in their hierarchy.
Is this possible?
If yes, how?
Thank you.
|
Accepted answer
![]()
Thomas,
Even with a finite set of optional traceabiliy links, this is not possible. If you traverse configuration -contributions-> configuration -component-> component, and then count the number of configurations, a count greater than 1 would indicate component skew directly within that configuration. But it would not detect component skew in a hierarchy where the skew occurred across multiple different children. I do not think it is possible to do what you want in Report Builder with generated SPARQL.
If one ignores the correct handling of overriding contributions from change sets (DNG does not currently publish them to TRS), one might be able to write custom SPARQL to do this. I have never tried to do this. The relevant properties in such a query are:
Best regards,
David Thomas Kirstätter selected this answer as the correct answer
|
2 other answers
![]() Hi Thomas,
When creating JRS report, you need to focus/select single GC and therefore, such report is not possible. This is an example what can be done https://www.ibm.com/docs/en/elm/7.0.2?topic=builder-finding-all-versions-artifact.
Regards,
Fariz Saracevic
Comments
Hi Fariz, thanks for the hint. But I can report on GCs and the GC tree structure itself when using "Lifecycle Query Engine" instead of "Lifecycle Query Engine with Configuration". So, as I can in principle report the complete content of a GC Tree (all Global and Local Contributions) I thought, I could as well somehow detect Component Skew....
The link you shared seems to me rather to help detect artifact Overlap between components, not Component Skew in a GC tree.
|