Project

General

Profile

Actions
Copy link

Bug #14891

closed

Rtf can not launch ncf tests on non-released major rudder version

Added by Félix DALLIDET over 5 years ago. Updated over 5 years ago.

Status:
Released
Priority:
N/A
Assignee:
Benoît PECCATTE
Category:
Rudder tests
Target version:
master
Pull Request:
https://github.com/Normation/rudder-t...
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)

Subtasks 1 (0 open — 1 closed)

Bug #14892: rtf should run ncf-setup on master branch instead of the given version if this one does not existsReleasedBenoît PECCATTEActions
Actions
Copy link

Also available in: Atom PDF