"echo on" doesn't work
When a Build Forge agent is running under Windows, "echo on" is the
default value but it does not appear to have any effect. Any idea why not? One thought I had was that Build Forge was stripping everything that looked like a command echo, but that appears not to be the case. -- Tim McDaniel, tmcd@panix.com |
One answer
When a Build Forge agent is running under Windows, "echo on" is the Hi Tim, By default the Build Forge Agent will use the /Q switch when invoking cmd.exe, and this disables echoing completely, even if an "echo on" command is issued. The "shell" setting in BFAgent.conf could be changed to override this, but it may have strange side-effects, such as having the command text show up as part of the value during collector run commands and possibly breaking variable expansion in some instances. This is some information about the shell setting from the documentation. shell shell_name Your best solution may be to override the shell only within those steps where you wish to explicitly control echo. For example: #!cmd.exe /c @echo off not_echoed not_echoed @echo on echoed @not_echoed echoed echoed bju |
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.