You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a number of places I output all the variables or all the files in a folder or some such thing, to help figure out where things are or what state things are in while I'm developing. They're harmless, other than they show some state of the machine, but there's no reason for it to be there all the time. Those "debug" steps should only be run when the system.debug variable is true (can be set when running a build manually from the web, or presumably as a defined variable in the azure-pipelines.yml
The text was updated successfully, but these errors were encountered:
In a number of places I output all the variables or all the files in a folder or some such thing, to help figure out where things are or what state things are in while I'm developing. They're harmless, other than they show some state of the machine, but there's no reason for it to be there all the time. Those "debug" steps should only be run when the system.debug variable is true (can be set when running a build manually from the web, or presumably as a defined variable in the azure-pipelines.yml
The text was updated successfully, but these errors were encountered: