Jenkins
Builds, stages, agents, queue and control operations — without opening Jenkins.
Delivery → Jenkins brings build status into AccelerUp.
Setup
Settings → Datasources → Jenkins. URL, user, API token.
Auto-mapping
Jobs are mapped to services by regex rules, not one at a time.
There is no per-job configuration and no Jenkinsfile change required. A new
job matching an existing rule is mapped automatically — which is the only way
this stays accurate on an instance with hundreds of jobs.
What is shown
| Builds | Status, duration, trigger, per job |
| Stages | Where the time went, and which stage failed |
| Artifacts | What the build produced |
| Changes | Commits in the build |
| Parameters | What it was run with |
| Agents | Which are online, and what they are running |
| Queue | What is waiting, and for how long |
The queue is the useful one
A build queue that is growing means agents are saturated. That shows up as "CI is slow" long before anybody connects it to a capacity problem — and the queue depth is the number that says so.
Control operations
With the right role, from AccelerUp:
| Action | |
|---|---|
| Rebuild | Re-run a build with the same parameters |
| Enable / disable | A job |
| Set description | Annotate a build |
All audited.
Real-time status
Add /api/v1/jenkins/notify as a Jenkins notification endpoint. Builds then
appear as they happen rather than on the next poll.
Job roles
A job can be tagged with its role in the delivery flow:
| Role | Meaning |
|---|---|
deploy | Ships a version |
rollback | Reverts one |
verify | Checks a deployment |
This is what lets AccelerUp record a Jenkins build as a deployment with the right semantics, rather than as an undifferentiated build.
Approval inbox
Builds that need an approval appear in Delivery → Approval inbox, so an approver does not need a Jenkins account.
Jenkinsfiles
Corrected examples are in docs/jenkins/ in the repository — including the
gotchas hit while setting up the Infisical secret pull.
Where this behaviour lives: backend/internal/integration/jenkins.go, backend/internal/worker/jenkins_poll.go. If the code and this page disagree, the code is right — please fix the page.
Part of Delivery — Deployments, pipelines, releases and everything that ships code.