[JIRA] (JENKINS-38215) msbuild compiler warning not detected / extracted
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38215 Re: msbuild compiler warning not detected / extracted Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/warnings/parser/MsBuildParser.java http://jenkins-ci.org/commit/warnings-plugin/5e3f481071b86ba45b666413978ea9f53bdc1790 Log: Improved fix for JENKINS-38215. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
[JIRA] (JENKINS-38215) msbuild compiler warning not detected / extracted
Title: Message Title Dirk Thomas commented on JENKINS-38215 Re: msbuild compiler warning not detected / extracted Thank you very much for addressing this. I am looking forward for the next release to use it. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
[JIRA] (JENKINS-38215) msbuild compiler warning not detected / extracted
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-38215 msbuild compiler warning not detected / extracted Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
[JIRA] (JENKINS-38215) msbuild compiler warning not detected / extracted
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38215 Re: msbuild compiler warning not detected / extracted Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/warnings/parser/MsBuildParser.java src/test/java/hudson/plugins/warnings/parser/MsBuildParserTest.java src/test/resources/hudson/plugins/warnings/parser/issue38215.txt http://jenkins-ci.org/commit/warnings-plugin/4834ebc22697bf682b0024ba0aa1c03d4f07a542 Log: [FIXED JENKINS-38215] Detect MSBuild command line warnings. Compare: https://github.com/jenkinsci/warnings-plugin/compare/01a54cc79a4a...4834ebc22697 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
[JIRA] (JENKINS-38215) msbuild compiler warning not detected / extracted
Title: Message Title Dirk Thomas commented on JENKINS-38215 Re: msbuild compiler warning not detected / extracted Yes, that is the only warning not being recognized (the same warning appears twice in the console log). In contrast to the cases in your test which are all file specific these ones are warning for the command line arguments. Therefore it doesn't start with a filename / row / column but just with `Command line warning ...`. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
[JIRA] (JENKINS-38215) msbuild compiler warning not detected / extracted
Title: Message Title Ulli Hafner commented on JENKINS-38215 Re: msbuild compiler warning not detected / extracted This warning totally looks different, here is an example from my tests: https://github.com/jenkinsci/warnings-plugin/blob/master/src/test/resources/hudson/plugins/warnings/parser/msbuild.txt Is this the only warning that is not parsed? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
[JIRA] (JENKINS-38215) msbuild compiler warning not detected / extracted
Title: Message Title Dirk Thomas created an issue Jenkins / JENKINS-38215 msbuild compiler warning not detected / extracted Issue Type: Bug Assignee: Ulli Hafner Components: warnings-plugin Created: 2016/Sep/14 8:23 PM Environment: Jenkins 2.7.1, Warnings Plug-in 4.56, Master is an Ubuntu 14.04 system, Slave is a Windows 10 system Priority: Minor Reporter: Dirk Thomas The console out of the job http://ci.ros2.org/job/ci_windows/1651/consoleFull shows the following compiler warning: (ClCompile target) -> cl : Command line warning D9002: ignoring unknown option '-std=c++11' but the result says: "MSBuild Warnings: 0 warnings". I am happy to provide more information if necessary and/or try a from-source build to check if it makes any difference. Add Comment
