-
Bug
-
Resolution: Unresolved
-
Major
-
None
When inheritance project contains promoted build configuration, i.e Promoted build plugin is installed and "Promote builds when..." is configured on a project, then subsequent modifications to "Promote builds when..." subsection is not immediately visible and no new version is saved.
This is because promoted builds plugin stores only references to promotion processes in the config files, i.e. :
<properties>
<hudson.plugins.promoted__builds.JobPropertyImpl plugin="promoted-builds@2.20-SNAPSHOT">
<activeProcessNames>
<string>zupa</string>
</activeProcessNames>
</hudson.plugins.promoted__builds.JobPropertyImpl>
</properties>
And the configuration of promotions processes themselves are stored under "promotions" subdirectory.
Because VersionedObjectStore.areIdentical 's implementation compares configuration strings:
Jenkins.XSTREAM2.toXMLUTF8(o1, os1);
Jenkins.XSTREAM2.toXMLUTF8(o2, os2);
It will not detect changes and store a new version.
The way promoted builds plugin stores configuration breaks versioning in inheritance plugin.
This bug consists of two parts:
1. Provide short term workaround to get Promoted builds configuration working, even sacrificing versioning, i.e. always the latest version of promoted builds configuration is used.
2. Create bug to solve problem completely, i.e. COS: versioning is working even with changes made only to the promotion processes.