Skip to content

Variability: Check if update propagations of configuration's __hash and __updateHash properties can be avoided #1582

@kbirken

Description

@kbirken

When a configuration references a sub-configuration (and this again referencing an sub-configuration, ...), a change in a leaf configuration will be propagated in opposite direction of the reference relation. This will usually change the hash values __hash and '__updateHash' in the referencing configurations.

Although for these hash properties VCS hints have been implemented, the collision check in platforms like github or gitlab or bitbucket will not be able to execute the VCS hints. Thus, collisions will be reported by the git platform quite often, especially for central configurations which refer to many sub-configurations.

In order to reduce these "false" conflicts, it should be assessed if the frequent updates of central hash values can be reduced.

Metadata

Metadata

Assignees

Labels

variabilityVariability-related tickets

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions