azuredevops-pipelines-logging

To set an output variable in Azure DevOps pipelines, use the `##vso[task.setvariable]` logging command with proper syntax and escaping in your Bash or PowerShell script. You must also configure the variable's output scope to ensure it is accessible to subsequent downstream jobs.

Azure DevOps logging commands use `##vso[...]` for script-to-agent signaling like setting variables and publishing artifacts, and `##[...]` for formatting log output. Correct command formatting and precise escaping are required in YAML pipelines to ensure reliable execution and clear log user experience.

Output variable scope issues in Azure DevOps pipelines often occur when the `task.setvariable` command lacks the proper output scope configuration. You must explicitly declare the variable as an output variable and reference it correctly in the downstream job or stage to enable cross-job communication.

To handle secrets and mask sensitive values in Azure DevOps pipeline logs, use the appropriate `##vso[task.setsecret]` logging command. This ensures the script-to-agent signaling masks the secret value in the log output, preventing accidental exposure while maintaining reliable variable passing.

Yes, you can publish log summaries and artifacts directly from a script in an Azure DevOps pipeline. By using the correct `##vso[...]` logging commands, you can append markdown summaries to the pipeline run page and upload artifacts, improving the overall log user experience.

The best way to troubleshoot Azure DevOps pipeline logging commands is to verify precise command formatting, check for escaping errors in Bash or PowerShell, and ensure the `##vso[...]` command is correctly structured for script-to-agent signaling to resolve variable passing and log output failures.