19

I need logs more detailed when I run a Release Definition on VSTS. How enabled verbose logs on all Release Definition or on a task of the Release Defintion ?

Phil
  • 1,035
  • 2
  • 10
  • 17
  • Do you solve this issue by setting system.debug variable to true? (If isn't existing, add it to release definition) – starian chen-MSFT Mar 28 '18 at 03:16
  • There's a very useful Microsoft page that has many suggestions for adding tracing and troubleshooting: https://learn.microsoft.com/en-us/azure/devops/pipelines/troubleshooting?view=azure-devops – Amittai Shapira Sep 19 '19 at 12:25

1 Answers1

28

Set the system.debug variable to true in the Variables tab of the release definition; that will get you more verbose logs. Whether those logs will contain any information that's useful to you or not is another story.

Daniel Mann
  • 57,011
  • 13
  • 100
  • 120
  • 1
    This is really useful. Just add a variable called "System.debug" and set its value to "true". Helped me debug problem with calling (not a problem of the script) https://github.com/wulfland/vso-agent-tasks/blob/master/Tasks/WindowsMachineFileCopy/WindowsMachineFileCopy.ps1 – Rob Bowman Aug 14 '18 at 07:47