Márton Csordás
Márton Csordás
When running CodeChecker with the `CodeChecker --makefile` generation mode, it should be possible to detect which analysis action was run successfully and which failed.
CodeChecker will contain a view to show the source directories and files and indicate the number of findings grouped per source code directory and files.
If the serer has a huge number of products (for example 100), it's not effective to get and show all the runs. We need to extend the `getProducts` API function...
We are using the `getRunHistoryTagCounts` API function to get report filter items for baseline and newcheck run tags: https://github.com/Ericsson/codechecker/blob/76947debcf9f6be8b1fd106f545ca11d6bfab533/web/api/report_server.thrift#L587-L589 Unfortunatelly we cannot filter the resuts by tag names but only...
Write analyzer statistics information to the `metada.json` file when using report-converter so the server will be able to store these information alongside the run.
CodeChecker changes the past on the following scenario (introduce reports with same report hashes): - Start a web server with the master branch. - Analyze and store the following source...
This is a rolling ticket and it's purpose is to create a new section for the current release on the new features page. This page needs to be extended https://codechecker-demo.eastus.cloudapp.azure.com/new-features...
> Closes #3450
Introduce markdownlint (https://github.com/markdownlint/markdownlint) to the CodeChecker repository's docs folder and fix the warnings.