|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
Use case:
New warnings can be detected by Jenkins-plugin, but then its too late; new warnings should be detected as early as possible in the development cycle. They should be fixed even prior the check-in. This is especially a challenge in an environment with very much warnings, including much false positive warnings. (my interest: PC-Lint / MISRA)
(static-checker-manager: project manager.)
http://www.robertgamble.net/2011/09/incremental-linting-with-flexelint.html -> contextual method.
The use case is outside of Jenkins, so I would not be disappointed if this issue would be rejected. Maybe a gist would be a more appropriate hosting-solution, but I’d like to keep it nearer to the original sources.
The java solution seems to be a bit slow, maybe I’ll do a rewrite in c.
I can manage this all by myself, no effort for You.