is there way sonarqube raise violation if files/folders found in source?
for example, specifically-named configuration files contain sensitive data (e.g. passwords) should not included in version control, , neither should ide-specific configuration directories intellij's ".idea" , eclipse's ".settings" folders.
(side-note: i'm aware these can/should part of global ignore in version control - that's not i'm asking about)
i'd sonarqube raise violation during analysis if of set of files/folders exist, preferably using regex-or-similar pattern checking.
i've read on fact sonarqube plugins can written in java, seems such simple concept (and 1 i'm sure isn't unique) i'm little surprised haven't been able find existing rules or plugins. closest i've found sonar-text-plugin, though focuses on file contents rather whether files exist @ all.
before go reinventing wheel, there pre-existing offer this?
sonarqube version 4.5.7 - upgrading option if there's no other route.
i confirm there no such built-in feature in sonarqube.
you may want write custom rule java plugin.
Comments
Post a Comment