Actions
Bug #14891
closed
Rtf can not launch ncf tests on non-released major rudder version
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
It always try to execute ncf-setup with a "cf-engine version" arg based on latest rudder released version, matching the ncf version given.
But, if there are no release yet, ncf-setup can not find the proper rudder repo and fail to find which cfengine agent to use...
Moreover, ncf-setup can no longer support the nightly syntax for 5.1 since it wronlgy parse the rudder version.
Also, rtf should run ncf-setup on master branch instead of the given version if this one does not exists (for 5.1 for instance)
Updated by Félix DALLIDET almost 5 years ago
- Status changed from New to In progress
- Assignee set to Félix DALLIDET
Updated by Félix DALLIDET almost 5 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Félix DALLIDET to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-tools/pull/479
Updated by Félix DALLIDET almost 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-tools|577d35ebf70435ad62dc1b26700d05aa89942960.
Updated by Benoît PECCATTE over 4 years ago
- Status changed from Pending release to Released
Actions