ImpactBuild should be triggered for Properties Changes about dbb-zappbuild HOT 3 CLOSED

@bala-azha Thanks for bringing this up to our attention. This sounds like a very interesting enhancement, which was also raised by other users.

It took us a while to think how we could support this in zAppBuild. With the LogicalFiles with its LogicalDependencies , which are captured within the collection, we have a lot of flexibility. We would be actually be able to add any other logical dependency to an logical file. Our current thinking is to add logicalDependencies for Build Property (with it's own dependency category) based on list of properties, which should be considered in an impactBuild scenario.

Currently, we think about the Compiler Version, Compile Options and Link Options. Do you see any other build properties, which you would like to include?

from dbb-zappbuild.

@bala-azha @drbruce-git

I developed a prototype for this enhancement. When scanning the files, it adds LogicalDependencies for the build properties to the LogicalFile: https://github.com/dennis-behm/dbb-zappbuild/blob/properties/utilities/ImpactUtilities.groovy#L354-L366

It detects the change of the property file and passes control to a new gitUtil method to understand the actual change. I pass it to a Java Properties object for validation before returning all the modified build properties to the impact calculation.

After the impact analysis phase, there is a new calculation of impacted files for the list of changed properties:

You can browse my fork at https://github.com/dennis-behm/dbb-zappbuild/tree/properties

I need to do some housekeeping, while I used the new test framework, which I modified to my needs.

from dbb-zappbuild.

While this is delivered, I am closing the issue.

from dbb-zappbuild.