|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
You can use Batch or Powershell or pretty much anything that can access Environment variables.
For example if you put his into a Windows batch script and run it you'll get the values for all the WARNINGS variables.
SET WARNINGS
That will list them out in Jenkins console for the build.
Or you can use the Jenkins tokens in a build Email and email them to yourself.
To test I just used both, ${WARNINGS_COUNT} and ${ENV,var="WARNING_COUNT"} with a text tag before each one and then just waited for an email.
Of course you also need something to have Warnings in it.
I used a previous build log that had MSBuild warnings in it. Then set the Warnings scanner to use the file instead of the workspace.