We recommend you listen only to agent traffic. Set the VSTS_AGENT_HTTPTRACE environment variable before you launch the agent.listener. If your agent is version 2.114.0 or newer, you can trace the HTTP traffic headers and write them into the diagnostic log. HTTP traces and trace files can contain passwords and other secrets. Use full HTTP tracing - macOS and Linux.
The capabilities.txt file provides a clean way to see all capabilities installed on the build machine We continually add to this data to make it more useful. This includes information like what tasks are run, whether or not the firewall is enabled, PowerShell version info, and some other items. The environment.txt file has various information about the environment within which your build ran. Inside the diagnostic logs you will find environment.txt and capabilities.txt. Shows when each job was run, and how it completedīoth logs show how the agent capabilities were detected and set. This log:Ĭannot be opened until the process is terminated.Īttempts to connect to your Azure DevOps organization or Team Foundation Server. The log file generated when you ran run.cmd.
Includes this line near the top: Adding Command: configure The log file generated when you ran config.cmd. Agent diagnostic logsĪgent diagnostic logs provide a record of how the agent was configured and what happened when it ran. Look for the worker log file that has the date and time stamp of your completed build. You can get the diagnostic log of the completed build that was generated by the worker process on the build agent. In addition to the pipeline diagnostic logs, the following specialized log types are available, and may contain information to help you troubleshoot. To download all logs, navigate to the build results for the run, choose Download all logs as zip.
0 kommentar(er)
