Must-share information (formatted with Markdown):
which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
- Enterprise Edition - Version 7.9.1 (build 27448)
what are you trying to achieve
- We are scanning updated cobol files from endevor check-ins, which is working well. Yet, we are trying to figure baseline status as we are only scanning the files within the change-set. We cannot scan all 10k+ cobol files to get a “baseline”. Therefore we are wondering how we should go about getting baselines on individual files or something like that.
This is all automated via Topaz workbench, CA Endevor, Gitlab, ZOWE, etc.
- what have you tried so far to achieve this
- As I said, currently, we are just scanning all the files within the endevor change-set, and thus each scan looks like a new file each time even if the file has been scanned before, and has no scan history. If we try to keep history, files that were scanned in one pipeline may or may not be a part of the next change-set, when they are missing Sonar treats them like they have been removed. Consequently, we are not building update history of our cobol components