Actions
User story #11799
open
Ensure ncf / technique consistancy when run starts
Status:
New
Priority:
N/A
Assignee:
-
Category:
Web - Config management
Target version:
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:
Description
We regularly have bugs (incomplete updates, #11682, etc) where the version of ncf does not match the version of techniques, and so we get extremely hard to understand error messages.
A solution would be to ensure that all artifacts are consistent (with a shared unique id, a list of md5 of each artifact, whatever) at the begining of the run. It would need to be done before cf-enfine starts to avoid parsing errors.
Updated by Benoît PECCATTE over 6 years ago
- Tracker changed from Bug to User story
- Target version changed from 4.1.9 to 4.3.0~beta1
Updated by Vincent MEMBRÉ about 6 years ago
- Target version changed from 4.3.0~beta1 to 4.3.0~rc1
Updated by Benoît PECCATTE about 6 years ago
- Target version changed from 4.3.0~rc1 to Ideas (not version specific)
Actions