Using a Windows PowerShell build step (PowerShell Plugin) and calling Write-Debug with a string that has carriage returns (0x13) results in Jenkins console output that is double-spaced. This does not happen with Out-Host, however.

In Windows, the default line-ending characters ([Environment]::NewLine) are 0x13 0x10, so all Write-Debug calls that specify a multi-line message end up double-spaced.  It is just a cosmetic issue, but it is sloppy-looking, and harder to read, especially when dumping an object with many properties to Write-Debug.

Example:  Put this in a Windows PowerShell build step and run the job:

$s1 = "s1Line1" + [Environment]::NewLine + "s1Line2"
$s2 = "s2Line1`ns2Line2"
"Out-Host:" | Out-Host
$s1 | Out-Host
$s2 | Out-Host
"Write-Debug:" | Out-Host
Write-Debug $s1
Write-Debug $s2

The Jenkins console output looks like this:

Out-Host:
s1Line1
s1Line2
s2Line1
s2Line2
Write-Debug:
DEBUG: s1Line1

s1Line2
DEBUG: s2Line1
s2Line2

note the blank line after "DEBUG: s1Line1", but not after "DEBUG: s2Line1"}}{{