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
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.
Comments
Spencer Murata
FORUM MODERATOR / JAZZ DEVELOPER Feb 14 '13, 1:51 p.m.Is an error given? You should be able to save the step...
Thomas Dunnigan
Feb 14 '13, 2:13 p.m.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.
Spencer Murata
FORUM MODERATOR / JAZZ DEVELOPER Feb 15 '13, 3:28 p.m.I would probably enter it as a defect, although I am not able to reproduce on 7.1.3.3.