Reporting capabilities depend on metadata store connection / git repo in workspace

[dennis-behm]

Today, the reporting capabilities are executed if centrally turned on via their properties.

The below section should validate their prerequisites :

• Reporting of external impacts is depending on the metadata store connection
• Reporting of concurrent changes is depending on the workspace containing a git repository / other references.

These two are generally not met in a user build scenario.

dbb-zappbuild/build.groovy

Lines 643 to 659 in d177891

	// Perform analysis and build report of external impacts
	if (props.reportExternalImpacts && props.reportExternalImpacts.toBoolean()){
	if (buildSet && changedFiles) {
	println "** Perform analysis and reporting of external impacted files for the build list including changed files."
	reportingUtils.reportExternalImpacts(buildSet.plus(changedFiles))
	}
	else if(buildSet) {
	println "** Perform analysis and reporting of external impacted files for the build list."
	reportingUtils.reportExternalImpacts(buildSet)
	}
	}
	// Document and validate concurrent changes
	if (props.reportConcurrentChanges && props.reportConcurrentChanges.toBoolean()){
	println "** Calculate and document concurrent changes."
	reportingUtils.calculateConcurrentChanges(buildSet)
	}

[dennis-behm]

Delivered via zAppBuild Release 3.6.0 #456