Bitbucket Cloud plugin support

[ewega]

Summary

Add Bitbucket Cloud as a supported DevOps tool in the CLI. Bitbucket is the third most popular Git platform, especially prevalent in Atlassian/Jira shops.

Upstream Plugin

bitbucket in incubator-devlake/backend/plugins/bitbucket/

Property	Value
Plugin slug	bitbucket
Auth	BasicAuth (username + app password)
Scope type	Repositories (BitbucketId string = full_name)
Scope ID field	bitbucketId
Default endpoint	https://api.bitbucket.org/2.0/
Remote-scope API	Yes
Connection test	Yes
Extra field	usesApiToken bool

Dependencies

Blocked by:

• Generalize auth model for multi-plugin support #85 — Auth generalization (Bitbucket requires BasicAuth with username + app password)
• Generic scope ID extraction and remote-scope API client #86 — Scope ID extraction (bitbucketId needs ScopeIDField)

Changes

• Add ConnectionDef for bitbucket in connectionRegistry:
  • AuthMethod: "BasicAuth"
  • NeedsUsername: true
  • UsernamePrompt: "Bitbucket username"
  • UsernameEnvVars: []string{"BITBUCKET_USER", "BITBUCKET_USERNAME"}
  • Endpoint: "https://api.bitbucket.org/2.0/"
  • SupportsTest: true
  • TokenPrompt: "Bitbucket app password"
  • EnvVarNames: []string{"BITBUCKET_TOKEN", "BITBUCKET_APP_PASSWORD"}
  • EnvFileKeys: []string{"BITBUCKET_TOKEN", "BITBUCKET_APP_PASSWORD"}
  • ScopeIDField: "bitbucketId"
  • HasRepoScopes: true
  • ScopeFunc: scopeBitbucketHandler
• Implement scopeBitbucketHandler:
  • Use client.ListRemoteScopes("bitbucket", connID, "", "") to list workspaces, then repos
  • Let user select repos interactively
  • PUT selected repos as scopes
• Set Available: true

Acceptance Criteria

• gh devlake configure connection add --plugin bitbucket --username myuser creates a Bitbucket connection
• Bitbucket appears in interactive plugin picker
• Bitbucket scopes list repos for selection
• Connection test works
• go build ./..., go test ./..., go vet ./... pass

[ewega]

@copilot This issue is still open with no PR. Please resume from latest main. Blockers #85 and #86 are already merged. Implement Bitbucket support using registry-driven BasicAuth fields and ScopeFunc, avoid hardcoded plugin switches outside connectionRegistry, add tests, update README/docs, run go build ./..., go test ./..., and go vet ./..., and open a PR that closes #89.

[ewega]

@codex[agent] Backup pass: Copilot still has not produced a PR for this issue. Please take a fresh pass from latest main, implement Bitbucket Cloud support with BasicAuth + username fields via connectionRegistry and remote-scope handling, add tests/docs, and open a PR that closes #89.

[ewega]

Implemented and merged. The Bitbucket Cloud plugin is now fully available in the CLI.

Merged PRs:

• PR feat: Add Bitbucket Cloud plugin support #129 — feat: Add Bitbucket Cloud plugin support (primary implementation: ConnectionDef, scopeBitbucketHandler, BitbucketRepoScope type, BasicAuth with NeedsUsername, tests)
• PR Addressing PR comments #130, Addressing PR comments #131 — review follow-ups
• PR Add robust Bitbucket Cloud scope handling and coverage #138 — hardened scope handling, error propagation, docs

All acceptance criteria satisfied: --plugin bitbucket connection creation, interactive plugin picker, workspace/repo scope browsing, connection test, and CI gates pass.