search

microsoft / vso-agent

Visual Studio Team Services and TFS agent for Mac OSX and Linux
MIT License
132 stars 57 forks source link

Add Better Logging for a Task has no Available Execution Options #257

Closed darthtrevino closed 8 years ago

darthtrevino commented 8 years ago

For example, when I try to use the 'Report Code Coverage' build step, I get an immediate build failure in VSO with no clue as to what went wrong. Only by installing the VSO-Agent locally and seeing what was happening was I able to figure out that it required PowerShell, which is not available on our Linux build box.

This log view should display an info message about not being able to find an appropriate execution option, and what options it has available.

screen shot 2016-03-15 at 2 57 31 pm

bryanmacfarlane commented 8 years ago

The task should demand the capabilities it needs and it would never make it to the agent. I believe the agent will log but we will look at making the communication clearer here in the replacement for this agent:

https://github.com/Microsoft/vsts-agent

darthtrevino commented 8 years ago

I've only been looking at this today, but when I add my Macbook to our build pool I was able to do some log-debugging to see that the build fails when trying to report coverage because PowerShell is not an available handler. (https://github.com/Microsoft/vso-agent/blob/07e3e08a1c6f5ac574e71722dfe154bf9bd9b0fd/src/agent/job.ts#L356)

I'll keep an eye out for the replacement, thanks @bryanmacfarlane !