Integrations

Jenkins

Connect a Jenkins controller to browse jobs, build, watch the console and abort from the panel, plus an audit report and chat access.

Jenkins runs your builds and deployments. Connect a controller and you can do the everyday Jenkins work from the panel: browse jobs, folders and branches, Build Now or Build with Parameters, watch the Console Output live, Abort a build, and cancel a queued one. You also get a standards audit, and the assistant can answer questions about builds.

Jenkins is hidden from the sidebar until you turn it on: click the gear next to Navigation and click the eye beside Jenkins.

Before you start

You need:

  • the URL of your Jenkins controller, e.g. https://jenkins.example.com — it must be reachable from the internet, not only from your office network (a self-hosted panel can also reach controllers on its own network);
  • a username;
  • an API token for that user.

Getting an API token

  1. Sign into Jenkins.
  2. Click your name (top right) → Configure.
  3. Under API Token, choose Add new Token, name it devops-agent, and Generate.
  4. Copy it now — Jenkins shows it once.

Use a token, never the account password. Tokens can be revoked individually without changing anyone's login.

Best practice: create a dedicated Jenkins user for the panel. Give it Overall/Read and Job/Read to browse, plus Job/Build and Job/Cancel if your team should build and abort from here. Jenkins records builds started from the panel as started by this user.

Adding it

Jenkins → Add Jenkins:

FieldValue
NameA label: Prod Jenkins
Jenkins URLhttps://jenkins.example.com
UsernameThe Jenkins user
API tokenThe token from above

The panel checks the URL and the token when you save. You can register more than one controller per project.

What you get

The screens are laid out like Jenkins, so you find things where you expect them: breadcrumbs across the top, tasks down the left, content on the right.

Dashboard — the view tabs and the job list with S (status), W (weather), Last Success, Last Failure and Last Duration. The ▶ at the end of a row schedules a build; jobs with parameters show a clock and open the parameters form. On the left: Build Queue (with ✕ to cancel a waiting build) and Build Executor Status (what is running, with a progress bar and ✕ to abort).

Folders and multibranch pipelines — open a folder like a job; multibranch projects have the Branches, Pull Requests and Tags tabs, and Scan Multibranch Pipeline Now.

A job — Build Now or Build with Parameters on the left, with Build History under it (running builds show progress and ✕). On the right: the Stage View for pipelines and the permalinks (last build, last successful, last failed…).

A build — result, who started it, revision, parameters, changes, stages, test result and artifacts. On the left: Console Output, Rebuild (the parameters form filled in with that build's values), Previous Build / Next Build, and Explain this failure, which opens the chat with the end of the log so the assistant can tell you why it failed.

Console Output — follows a running build live, like Jenkins. Long logs open at the last 512 KB; Full Log opens the whole log in Jenkins.

Configure, credentials, plugins and nodes stay in Jenkins: Configure and Open in Jenkins link there.

Audit — on the dashboard's left. It scores the controller against a seeded set of standards (security settings, plugin hygiene, build configuration, access control) and produces a PDF report. Use it when you inherit a Jenkins nobody has looked after, before a security review, or to justify the time it takes to fix things.

Chat access — ask "did last night's deploy pass?", "why did the build fail?", "list the jobs that have not run in 90 days". In Execute mode it can trigger builds, and it will ask first. The script console, restarts and plugin changes always ask, even with auto-approve on.

Troubleshooting

ProblemCause
Connection refused / timeoutJenkins is not reachable from the internet
"That address is private or internal"The URL points at a private, loopback or cloud-metadata address. The hosted panel only calls public addresses
"Jenkins redirected to …"Save the address it redirects to, usually the https:// one. The panel does not follow redirects
"Not as Jenkins"The URL is not the Jenkins root (no X-Jenkins header came back)
Jenkins rejected the username or API tokenWrong username or token, or the user lacks Overall/Read
"Doesn't have permission" on Build or AbortThe Jenkins user lacks Job/Build or Job/Cancel
Works in browser, fails hereA corporate VPN or an IP allow-list is in the way
No Stage ViewThe Pipeline Stage View plugin isn't installed; everything else works
File parameter is emptyFile parameters can only be uploaded in Jenkins' own form

Permissions

Adding and removing controllers: Owner or Admin. Building, aborting, cancelling queued builds and running an audit: Operator and above. Viewers see jobs, builds and console output. See Roles.