Live Jenkins Build Status in Confluence: Documentation That Doesn't Go Stale

Every team has that Confluence page: "Release 4.2 – status: green ✅". Written on a Tuesday, still green three weeks later, while the nightly build has been red since Thursday.

Documentation goes stale when someone has to copy information into it by hand. Build status is the worst offender, because it changes many times a day. Jenkins for Confluence fixes this by putting live Jenkins data straight onto the page.

Two macros, two levels of detail

Jenkins Job Badge

The Jenkins Job Badge macro shows the latest status of a Jenkins job as a small inline badge: success, failing or unstable. Because it's inline, you can drop it into a sentence, a table cell or a status list.

Click the badge and a dialog opens with the build details and links to view the job in Jira or in Jenkins. Readers get a quick look without leaving the page, and a quick path to more if they need it.

Use it when you want at-a-glance status across many jobs, like a table of services with one badge per row.

Jenkins Job Status

The Jenkins Job Status macro shows the latest details of a job in an expanded panel: timing, test results, the issues that triggered it, and more.

Use it when the build is the subject of the page: a release page, a deployment guide, or a hand-over document.

No extra Jenkins configuration

Jenkins for Confluence builds on your existing Jenkins for Jira setup:

Jenkins for Jira is installed and connected to at least one Jenkins site.
You install Jenkins for Confluence on your Confluence site.
The Confluence app registers itself with the Jira app automatically.

That's it. No separate Jenkins credentials, no second plugin, no extra firewall rules. Your Jenkins admins don't have to do anything.

Inserting a macro works like any other: type / in the editor, search for Jenkins, pick the macro and select the job.

Five pages that benefit immediately

1. Release pages. Put a Job Status macro for the release pipeline at the top. Stakeholders see whether the release build is green right now, with test results, not whatever someone typed last week.

2. Service overview tables. One row per service, with owner, repository, on-call and a Job Badge for its main pipeline. It's a lightweight status board built in Confluence, no dashboard tool needed.

3. Deployment runbooks. Runbooks tell people how to deploy. Adding the deploy job's status tells them whether it's safe to start. If the last run failed, they know before step one.

4. Onboarding guides. New engineers learn which jobs matter by seeing them, live, in the guide, with a click-through to Jenkins and Jira.

5. Incident and post-incident pages. During an incident, a badge for the fix pipeline shows progress to everyone following the page. Afterwards, the page links straight to the builds involved.

Tips for pages people trust

Badge for lists, Status for focus. More than three or four Job Status panels on one page gets noisy; switch to badges.
Put status next to its context. A badge next to "Deploy to production" in a runbook step is more useful than a separate status section at the bottom.
Remove hand-written status lines. If a macro shows the status, delete the "Status: green" text. Two sources of truth is how pages go stale.
Use templates. Add the macros to your release-page template so every new release page starts with live status.

Part of one connected setup

Jenkins for Confluence completes the picture with the rest of our apps:

Jenkins for Jira links builds and deployments to the issues they belong to.
Jenkins for Compass shows build health per software component.
Jenkins for Confluence puts that same data on the pages where your team plans, documents and shares.

One Jenkins connection, and the data shows up wherever your team works.

Read the Confluence macro documentation or see Jenkins for Confluence.