|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-14461) Warnings plug... [email protected] (JIRA)
- [JIRA] (JENKINS-14461) Warnings... [email protected] (JIRA)
- [JIRA] (JENKINS-14461) Warnings... [email protected] (JIRA)
- [JIRA] (JENKINS-14461) Warnings... [email protected] (JIRA)
- [JIRA] (JENKINS-14461) Warnings... [email protected] (JIRA)
- [JIRA] (JENKINS-14461) Warnings... [email protected] (JIRA)
- [JIRA] (JENKINS-14461) Warnings... [email protected] (JIRA)
- [JIRA] (JENKINS-14461) Warnings... [email protected] (JIRA)
- [JIRA] (JENKINS-14461) Warnings... [email protected] (JIRA)
- [JIRA] (JENKINS-14461) Warnings... [email protected] (JIRA)
- [JIRA] (JENKINS-14461) Warnings... [email protected] (JIRA)
- [JIRA] (JENKINS-14461) Warnings... [email protected] (JIRA)
- [JIRA] (JENKINS-14461) Warnings... [email protected] (JIRA)

Agreed, the error is really not informative... 3.21 worked for a project that had the warnings post-build action already configured, but I've since removed it so I can't try to a build out to see. However, with 3.21 in my 1.474 installation, it now allows me to add "Scan compiler warnings" as a post-build action, but when I press "Add" to add a new parser, nothing happens, and nothing appears in the log. This is an elusive bug! I'm going to try a bunch of different versions of the plugin to see if I can get any of them working.