As an enterprise DevOps engineer, we apply metadata to our SCM repositories because these attributes allow teams to manage scale of tens of thousands of repos.
I would like SonarQube to import GitHub’s Custom Properties to SonarQube. Note that Customer Properties are key-value while SonarQube tags are just values.
Our specific use case is that these attributes in the SCM can be used to create SonarQube Portfolios.
Hi Peter,
Thanks for sharing this, the use case makes sense.
I understand the ask as wanting SonarQube to reuse GitHub custom properties as project tags, so teams can drive portfolio creation from metadata they already manage in GitHub instead of maintaining it again manually in SonarQube.
Today, portfolios can already be built dynamically by tags, regex, or organization, but we do not currently support importing GitHub custom properties directly into SonarQube project tags.
We’ve already captured this internally as product feedback, so it is on our radar, but no exact timing yet, but if you’re open to it, do you have any examples of the properties you’d want synced and whether you need a one-time import, continuous sync, or both?
This would help us evaluate the right solution shape.
Appreciate your time.
Best,
Victor
An application may consist of one or more repositories (the polyrepo paradigm). In this case, a SQ portfolio would represent an application view. Our team tags every single repository with an “application ID” sourced from a CMDB.
Applications are owned by business units. Repositories are may also be tagged with this value. This allows the creation of SQ portfolios scoped around a logical grouping of ownership/responsibility.