Sonarqube set leak period to specific version other than previous version
Evaluating Sonarqube (Version 5.4), we want to migrate our current workflow using another Audit tool, which works like that : The current version that runs in production is our reference version. A new development version is checked out from GIT, a diff process calculates the new and modified files vs. the reference version and starts the audit for these files. There's also a slightly different handling of legacy code (components that already existed in 2012) and new components (after 2012). The build breaks if : Blocker issues in changed files (those files already existing in 2012) from