Sonar Scanner Windows:
Version: 1.8 (build 1574)
GitHub Authentication for SonarQube:
Version: 1.5 (build 870)
Our organization uses gitflow workflow for our projects and we consider develop and master to be long-lived branches. Develop is promoted to master periodically depending on when we are releasing our product in order for stabilizing work to be completed in master ahead of release. Ideally we could have both develop and master scanned in SonarQube and analyzed as long-lived branches. Unfortunately when I submitted develop initially I forgot to change the regex and it showed up as a short-lived branch. I tried deleting the branch, changing the regex in the “Detection of long lived branches” section to “(develop|master)”, and then resubmitting the scan but it still showed up as a short-lived branch. I then tried changing the branch name to “alpha” as a test and changed the regex to “(develop|master|alpha)” to see if it was because of my accidental submission of develop initially, but alpha still showed up as a short-lived branch.
I saw this post (Having multiple long-lived branches on GitHub) where someone said “I think issue is that SonarQube project was created after Develop branch existed, and thus updating the RegEx does not have an impact on its status as long-lived, unfortunately.” Is it because my project in SonarQube was created before the regex was changed? If so do I need to delete my project in SonarQube and recreate it? Or am I missing something?