Hello Lucene/Solr folks, During Lucene development CI is used for build and unit tests to gate merges. The CI doesn't yet include any analysis tools though, but their use has been discussed [1]. I fixed some issues flagged by Facebook's Infer and was prompted to bring up the topic here [2].
The recent PR fixed some low-hanging fruit that was reported when I ran Muse [3] - a github app that is a platform for static analysis tools. Muse's platform bundles the most useful analysis tools, all open source with many of them developed by FANG, and triggers analysis on PRs then delivers results as comments. Because of the PR-centric workflow you only see issues related to the changes in the pull request. This means that even a project where tools give a daunting list of issues can still have quiet day-to-day operation. Muse also has options to configure individual tools and turn tools or warnings off entirely. If there are concerns in addition to noise and added mental tax on development then I'd really like to hear those thoughts. Would you be up for running Muse on the lucene-solr repo? Let me know, and I hope to hear your thoughts on analysis tools either way. -Tom [1] https://issues.apache.org/jira/projects/LUCENE/issues/LUCENE-8847 [2] https://issues.apache.org/jira/projects/SOLR/issues/SOLR-14819 [3] Muse result on Lucene: https://console.muse.dev/result/TomMD/lucene-solr/01EH5WXS6C1RH1NFYHP6ATXTZ9?tab=results Muse app link: https://github.com/apps/muse-dev [4] https://github.com/TomMD/lucene-solr/pulls [5] Example of muse commenting on an issue https://github.com/TomMD/shiro/pull/2
