For example, I have a build step the executes a "Command Line" runner type. Per the build log, the script is executed from a .cmd file on the build server, but this file goes away as soon as the build finishes. My problem is that some of these commands are failing for me on the build server, but not locally. But given the dynamic-created nature of the commands (using Build Properties), it time-consuming to figure out what, exactly, was being executed. Not to mention reconstructing manaully is prone to human error.
Is there a way to capture the contents of the .cmd file and see them somewhere? In a detailed log? Or a way to keep them around after the build finishes?