slug: jenkins
provider: Jenkins
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 2
edges:
- tag: Jobs
  spec_file: jenkins-jobs-api-openapi.yml
  capability_id: BC-4210.10
  capability_id_l1: BC-4210
  capability_name: Continuous Integration Management
  confidence: 0.85
  evidence: POST /job/{jobName}/build triggerBuild 'Trigger a build for a parameterless job'; GET /job/{jobName}/{buildNumber}/api/json
    'Get information about a specific build'
  reason: Operations trigger and inspect builds on an automation server described as enabling developers
    to 'reliably build, test, and deploy software' — this is continuous integration build pipeline management.
- tag: Queue
  spec_file: jenkins-queue-api-openapi.yml
  capability_id: BC-4210.10
  capability_id_l1: BC-4210
  capability_name: Continuous Integration Management
  confidence: 0.7
  evidence: GET /queue/api/json getQueue 'Get the current build queue'
  reason: Reading the pending build queue is part of CI build pipeline operation, though it is a single
    read-only status call so confidence is moderate.