I run FBCMD from Hudson so that Hudson can dynamically display the output of the log during the build and developers can quickly search through the text based output of a log for what they want.
I've noticed that when running looping actions that perform actions that include other FinalBuilder projects, that the log indents a couple spaces to the right each time the included action is called and returned to the calling script. We have a large log and after a couple of hundred loops, that log is fairly difficult to navigate and use because of significant scrolling and unnecessary white space, etc.
I've found FBCMD's /XL and /H options which help modify the log so that the indentation doesn't occur, but in the case of the /XL it's kind of nice to get all the information in the log so you know which Action Lists activity occurred, and in the case of the /H, it's kind of nice to get the indentation that actually does occur so that it's obvious to see when things were included or action lists in the main script were entered.
Could the indentation be corrected?
I've attached a set of sample scripts that can demo the problem (using FB6 build 2004).
We've experienced a new problem with indentation, but closely related to the original issue. We started using an async action that calls other action lists and includes other projects, which include action lists, etc. and we rapidly ran into a problem with the log filling up with indentations which causes all sort of readability problems as well as some really, really huge log files. :-)
I think the problem might be that after calling an action list to do some work, the script continues to intent after coming back to the original action list/tab. With all the action list work we have scripted that iterates through chains of action lists, all that work exacerbates the issue. The async action might only have helped us notice an indentation issue that much faster.
We are using FB 6.3.2172 - FBCMD with Hudson. We use the /XL option to show some identation in our logging, because we find it is helpful over /H to see the indentation in the log when grouped under action groups. I've updated the sample scripts to help show the problem. I also confirmed the issue exists for us in FB 7.0.0.1065.