Aspire CLI output uses fixed column width on Jenkins

[lvde0]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I am not sure if this is an issue with my setup or Aspires internal Spectre-based console logger, but for some reason it defaults to a column width of 80 when running on Jenkins. Other tools like the dotnet CLI work just fine.

Possibly related issue: spectreconsole/spectre.console#216
Some project managed to work around this bug: criticalmanufacturing/cli@e421ef0

Maybe Aspire could something similar?

(Originally posted on Discord)

Expected Behavior

It should use the available space.

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version info

No response

Anything else?

No response

[joperezr]

As part of triage cleanup ahead of the 13.3 release, this issue is being moved to the Backlog milestone. If you believe it should remain in 13.3, feel free to re-add to the milestone and leave a comment here why it should not be punted.

[adamint]

Faithful repro is blocked for me because I don't have a Jenkins console in this environment. I did run a local non-TTY Jenkins-shaped check on macOS 26.6 (JENKINS_URL=... COLUMNS=80/160/240 aspire publish -?) against 13.4.6 and current main. The wrapping did not change with COLUMNS, but that is not enough to validate the Jenkins screenshot; this still needs a real Jenkins run or captured console metadata.