SonarQube plugin support

[ewega]

Summary

Add SonarQube as a supported DevOps tool in the CLI. SonarQube is the most popular code quality platform (~40% adoption), providing code coverage, code smells, and quality gate data complementary to DORA metrics.

Upstream Plugin

sonarqube in incubator-devlake/backend/plugins/sonarqube/

Property	Value
Plugin slug	sonarqube
Auth	AccessToken (SonarQube token; DevLake backend handles base64 encoding internally)
Scope type	Projects (ProjectKey string)
Scope ID field	projectKey
Default endpoint	User-provided SonarQube instance URL
Remote-scope API	Yes
Connection test	Yes
Extra field	Optional organization

Dependencies

Blocked by:

• Generic scope ID extraction and remote-scope API client #86 — Scope ID extraction (projectKey needs ScopeIDField)

Not blocked by #85 — SonarQube uses AccessToken, compatible with current auth model.

Changes

• Add ConnectionDef for sonarqube in connectionRegistry:
  • AuthMethod: "AccessToken" (or empty, defaults to AccessToken)
  • Endpoint: "" (user must provide)
  • SupportsTest: true
  • TokenPrompt: "SonarQube token"
  • EnvVarNames: []string{"SONARQUBE_TOKEN", "SONAR_TOKEN"}
  • EnvFileKeys: []string{"SONARQUBE_TOKEN", "SONAR_TOKEN"}
  • ScopeIDField: "projectKey"
  • ScopeFunc: scopeSonarQubeHandler
• Implement scopeSonarQubeHandler:
  • Use client.ListRemoteScopes("sonarqube", connID, "", "") to list projects
  • Let user select projects interactively or via --projects flag
  • PUT selected projects as scopes
• Set Available: true

Acceptance Criteria

• gh devlake configure connection add --plugin sonarqube --endpoint https://sonar.example.com creates a SonarQube connection
• SonarQube appears in interactive plugin picker
• SonarQube scopes list projects for selection
• Connection test works
• go build ./..., go test ./..., go vet ./... pass

[ewega]

Agent Context for Implementation

IMPORTANT conventions from Wave 1 learnings:

• Use literal emoji characters (📋, 📝, ✅, ⚠️), NOT Unicode escapes (\U0001f50e)
• Do NOT change line endings (CRLF/LF) in existing files — only add your new code
• Set AuthMethod: "AccessToken" explicitly (don't rely on default)
• In tests, skip plugins without scopes using if len(def.RequiredScopes) == 0 { continue }
• Clear RequiredScopes: []string{} and ScopeHint: "" if the plugin doesn't use OAuth/PAT scopes
• Add a row to the README Supported Plugins table

1. Add ConnectionDef entry to cmd/connection_types.go

Add a new entry to connectionRegistry slice. Follow existing entries (github, gitlab, jira, jenkins) as templates. Key fields for SonarQube:

• Plugin: "sonarqube"
• DisplayName: "SonarQube"
• Available: true
• Endpoint: "" (user must provide SonarQube instance URL)
• SupportsTest: true
• AuthMethod: "AccessToken"
• TokenPrompt: "SonarQube token"
• EnvVarNames: []string{"SONARQUBE_TOKEN", "SONAR_TOKEN"}
• EnvFileKeys: []string{"SONARQUBE_TOKEN", "SONAR_TOKEN"}
• ScopeIDField: "projectKey"
• ScopeFunc: scopeSonarQubeHandler

2. Implement scopeSonarQubeHandler in cmd/configure_scopes.go

Follow the pattern of existing handlers. Use client.ListRemoteScopes("sonarqube", connID, "", "") to list projects. Handle pagination (loop on NextPageToken). Let user select projects interactively via prompt.SelectMulti. PUT selected projects as scopes.

3. Tests

Add TestConnectionRegistry_SonarQube in cmd/connection_types_test.go verifying registry fields.

4. Do NOT

• Add switch/case branches on plugin names outside connectionRegistry
• Modify existing plugin entries
• Change line endings in existing files

[ewega]

@claude[agent] This issue is still open with no PR. Please resume from latest main. Blocker #86 is already merged. Implement SonarQube support via ConnectionDef + scope handler using remote scopes, keep behavior registry-driven, add tests, update README/docs, run go build ./..., go test ./..., and go vet ./..., and open a PR that closes #90.

[ewega]

@codex[agent] Backup pass: Claude still has not produced a PR for this issue. Please take a fresh pass from latest main, implement SonarQube support with a registry entry and remote-scope handler, add tests/docs, and open a PR that closes #90.

[ewega]

Implemented and merged. SonarQube is now a fully available plugin in the CLI.

Merged PR:

• PR Add SonarQube remote scope flag and selection support #139 — Add SonarQube remote scope flag and selection support: sonarqube ConnectionDef with Available: true, ScopeIDField: "projectKey", --projects non-interactive flag, remote project scope listing/validation, tests

All acceptance criteria satisfied: --plugin sonarqube connection creation, interactive plugin picker, project scope browsing, connection test, and CI gates pass.