Add integration with issue trackers and other tools

[nettle]

Integration with other tools is indispensably essential! The issue tacking systems are the first candidate for the integration: Jira, Redmine etc The other tools to integrate with: code review systems (Gerrit etc), collaboration/ChatOps (Slack, Teams, Mattermost etc).

Some of scenarios are the following:

• A number of issues are found and should be assigned for review+fix to particular developers or/and teams. It has a sense to create one (or many) ticket at issue/task tracking system to assign issues and track the progress.
• A new issue is found and should be automatically assigned to particular developers or/and teams via issue tracking system
• An issue is fixed and should be referred to from Commit Message
• An issue or issues are mentioned in Slack chat

[gyorb]

Hi,

Yes we know that integrations are important but our resources are limited. We are focusing right now to support the storage of other static analyzer reports and to port CodeChecker to python3.

We discussed some ticketing system integration but flooding a ticketing system with a lot of new tickets for each analysis report might not be the best solution. On the other hand one simple CI job could query the database daily and filter for the high priority reports and create/update a jira ticket with the jenkins jira plugin. This could be done in jenkins. There are notification plugins in jenkins for multiple services like Slack, Mattermost... so this approach could work there too. The CodeChecker cmd command is very flexible and and you can query a lot of information from the database, or you can use the CodeChecker parse command to process local analysis reports.

We have user guides and helper scripts how to integrate to gerrit and how to support different CI workflows like daily analysis or to check if any new report was introduced by a developer.

Contributions are welcome!