Details
-
Type:
Improvement
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: config-rotator-plugin
-
Labels:None
-
Environment:Every
-
Similar Issues:
Description
When setting config-rotator up for an invalid clear case configuration, eg. including the same component twice, the logs is very verbose and does not hint what is wrong.
The build is also started.
Attachments
Activity
We have implemented to levels of check of configuration. The first check is if configuration is loadable in ClearCase. The second level of check is if the configuration added make sense in a context of configuration rotation. Eg. config-rotator does not allow the same component more the once.
Polling check the first level, and abort polling if check is not passed.
Builds do both checks and fail if not passed.
Bue Petersen
added a comment - We have implemented to levels of check of configuration. The first check is if configuration is loadable in ClearCase. The second level of check is if the configuration added make sense in a context of configuration rotation. Eg. config-rotator does not allow the same component more the once.
Polling check the first level, and abort polling if check is not passed.
Builds do both checks and fail if not passed. 
If configuration is not valid, and there is no existing build we can not prevent the build from being started by the poller.
We will do a simple check of configuration by checking if same component is included more than once. Checks can later be improved or extended. At the moment it can not be done during configuration as we have no workspace there.