Jenkins plugin support

[ewega]

Summary

Add Jenkins as a supported DevOps tool in the CLI. Jenkins is the most popular CI/CD server (~44% market share), providing deployment frequency and build data for DORA metrics.

Upstream Plugin

jenkins in incubator-devlake/backend/plugins/jenkins/

Property	Value
Plugin slug	jenkins
Auth	BasicAuth only (username + password/API token)
Scope type	Jobs (FullName string, path-based)
Scope ID field	fullName
Default endpoint	User-provided Jenkins server URL
Remote-scope API	Yes
Connection test	Yes

Dependencies

Blocked by:

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

Changes

• Add ConnectionDef for jenkins in connectionRegistry:
  • AuthMethod: "BasicAuth"
  • NeedsUsername: true
  • UsernamePrompt: "Jenkins username"
  • UsernameEnvVars: []string{"JENKINS_USER", "JENKINS_USERNAME"}
  • Endpoint: "" (user must provide)
  • SupportsTest: true
  • TokenPrompt: "Jenkins API token or password"
  • EnvVarNames: []string{"JENKINS_TOKEN", "JENKINS_PASSWORD"}
  • EnvFileKeys: []string{"JENKINS_TOKEN", "JENKINS_PASSWORD"}
  • ScopeIDField: "fullName"
  • ScopeFunc: scopeJenkinsHandler
• Implement scopeJenkinsHandler:
  • Use client.ListRemoteScopes("jenkins", connID, "", "") to browse job tree
  • Let user select jobs interactively or via --jobs flag
  • PUT selected jobs as scopes
• Set Available: true

Acceptance Criteria

• gh devlake configure connection add --plugin jenkins --username admin --endpoint https://jenkins.example.com creates a Jenkins connection
• Jenkins appears in interactive plugin picker
• Jenkins scopes list jobs for selection
• Connection test works
• go build ./..., go test ./..., go vet ./... pass

[ewega]

Agent Context for Implementation

This repo uses a declarative plugin registry pattern. Here's what you need to do:

1. Add ConnectionDef entry to cmd/connection_types.go

Add a new entry to connectionRegistry slice. Use the existing github entry as a template. Key fields for Jenkins:

• Plugin: "jenkins"
• DisplayName: "Jenkins"
• Available: true
• Endpoint: "" (user must provide Jenkins server URL)
• SupportsTest: true
• AuthMethod: "BasicAuth"
• NeedsUsername: true
• UsernamePrompt: "Jenkins username"
• UsernameEnvVars: []string{"JENKINS_USER", "JENKINS_USERNAME"}
• UsernameEnvFileKeys: []string{"JENKINS_USER", "JENKINS_USERNAME"}
• TokenPrompt: "Jenkins API token or password"
• EnvVarNames: []string{"JENKINS_TOKEN", "JENKINS_PASSWORD"}
• EnvFileKeys: []string{"JENKINS_TOKEN", "JENKINS_PASSWORD"}
• ScopeIDField: "fullName"
• ScopeFunc: scopeJenkinsHandler

2. Implement scopeJenkinsHandler in cmd/configure_scopes.go

Follow the pattern of scopeGitHubHandler. Use client.ListRemoteScopes("jenkins", connID, "", "") to browse the job tree. Let user select jobs interactively via prompt.SelectMulti. PUT selected jobs as scopes.

3. Key conventions

• Use doGet[T], doPost[T] generic helpers from internal/devlake/client.go — never raw HTTP
• Error wrapping: fmt.Errorf("context: %w", err)
• Terminal output: \n before emoji-prefixed steps, 3-space indent for sub-items
• Imports: stdlib → external → internal, separated by blank lines
• Tests: add entries to cmd/connection_types_test.go verifying the new registry entry
• The BasicAuth model (NeedsUsername, UsernamePrompt, etc.) was just added — the resolveUsername() function and BuildCreateRequest/BuildTestRequest already handle BasicAuth automatically based on these fields

4. Do NOT

• Add switch/case branches on plugin names outside connectionRegistry
• Modify existing plugin entries
• Change any files in internal/devlake/ unless adding new types needed for Jenkins scope responses