Why doesn't a semicolon work in a build forge step? (BF 7.1.3.2)
The following command in a step disallows the step from being saved in BF 7.1.3.2
plink servename "cd $HOME/%COMPUTERNAME%/my/directory/path;sh myScript.sh" However if the double quotes are removed ", then the step can be saved. plink servename cd $$HOME/%COMPUTERNAME%/my/directory/path;sh myScript.sh |
One answer
The only time I have seen issues like this is when the browser is accessing the console through some sort of active intrusion detection system that inspects packets. In those cases, request that IT except your console from the ID appliance, or if that is not possible due to security policy, running through https on the console will eliminate this problem.
To test if this is the problem, try to access the project through https or through a system in the lab on the same subnet as your console system.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
Is an error given? You should be able to save the step...
No error, it just does nothing. When selecting another step after not saving it prompts you that you will lose your changes. It appears to be the combination of double quotes and semicolon.
I would probably enter it as a defect, although I am not able to reproduce on 7.1.3.3.