Is it possible to raise and display build warnings from build steps using TFS 2015?

Background

The questions below relate to TFS 2015 on-premise.

It is possible to fail a build step by returning a non-zero exit code from, for example, a PowerShell or Command Line step. The build logs also capture anything written to the standard output stream. It is also possible to fail a Command Line step if anything is written to the standard error stream.

Question 1

Is it possible to raise build warnings via PowerShell and Command Line steps so that they’re displayed on the build summary page under Issues? For example, in the same way that the Visual Studio Build / MSBuild steps are raised and displayed?

Question 2

I notice in the build logs for the Command Line step the following lines:

2015-09-22T12:29:21.0696320Z Executing the following commandline. (workingFolder = C:\Builds\_work\dacceaf2\Repo)
2015-09-22T12:29:21.0696320Z C:\Builds\_work\dacceaf2\Repo\tools\Test\bin\Release\Test.exe .\src\Web\Content\Images\ C:\Builds\_work\dacceaf2\staging\Web\Content\Images\
2015-09-22T12:29:21.0696320Z Error message highlight pattern: 
2015-09-22T12:29:21.0706314Z Warning message highlight pattern: 

Is there any way to set these highlight patterns for the step?

[mattbrooks2010]

@pascalberger OK thanks — tried emitting the output below from a PowerShell step and got the desired result on the build summary page:

Write-Host "##vso[task.logissue type=warning;]Test warning"
Write-Host "##vso[task.logissue type=error;]Test error"

Is there currently a generic way of teaching the build system what forms of existing tool output should be considered as warnings though — as per question 2 above?

Additionally are there any built-in generic conventions (other than the logging commands) for triggering a ‘partially succeeded’ step rather than a ‘failed’ step?

I’m happy the logging commands will work for us but they are proprietary — existing build logic will need updating.

[pascalberger]

You should be able to return warnings and errors from your script using logging commands.