Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor zAppBuild reporting capabilities #341

Merged
merged 14 commits into from
Apr 17, 2023

Conversation

dennis-behm
Copy link
Member

Reporting capabilities in zAppBuild were previously managed in the ImpactUtilities script. While this is a feature of zAppBuild, it does not need to be part of the ImpactUtils script.

This PR is

  • moving the the methods of the reporting capabilities to its dedicated utility script and addresses Defect with reporting of external impacts  #340 .
  • some helper methods got moved to the build utilities rather than having them in the impact utilities.


def Set<String> externalImpactList = collectionImpactsSetMap.get(cName) ?: new HashSet<String>()
// query dbb metadatastore for files with all logicalDependencies
def logicalImpactedFilesCollections = metadataStore.getImpactedFiles([cName], logicalDependencies);
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rather than querying for each individual collection name, pass the list of collections for which the filter applies.

refactor_reporting_capabilities

Conflicts:
	utilities/BuildUtilities.groovy


Signed-off-by: Dennis Behm <[email protected]>
@dennis-behm
Copy link
Member Author

@M-DLB This is read for another review. I modified the code to actually leverage the new capabilities of the API to return a list of collections carrying the impacted files.

Comment on lines 138 to 141
}else {
// debug-output
// println("$indentationMsg!* Skipped redundant analysis. $file was already or will be procceed soon.")
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you need to keep the else here, if nothing is actually done?

Copy link
Member

@M-DLB M-DLB left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That looks good to me!
Thanks @dennis-behm

@M-DLB M-DLB merged commit 3a62b76 into IBM:develop Apr 17, 2023
dennis-behm added a commit that referenced this pull request May 11, 2023
Moved the Reporting feature into in its own utilities file, and simplifying the query to check for impacted logical files across collections using DBB 2.0 APIs.

Signed-off-by: Dennis Behm <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants