Automated Jenkins Job Registry Sync
Every morning, WebRun opens Jenkins, checks every job's latest build status, reconciles that against a Notion registry of jobs your team is supposed to be running, flags any job that was renamed or removed since the last check, and logs the day's total pass and fail counts to Google Sheets so build health trends over time.
How do I keep my Jenkins job registry accurate?
WebRun checks every Jenkins job every morning for its latest build status, reconciling that against a Notion job registry so renamed or removed jobs get flagged instead of silently dropped. It logs the day's total pass and fail counts to Google Sheets, so build health trends over time instead of only being visible one job at a time.
- The job registry never drifts out of sync with what actually exists in Jenkins
- Renamed or removed jobs get flagged instead of silently dropped
- Build health is tracked as a daily trend, not a one time snapshot
Built for DevOps teams · platform engineers · release engineers · engineering managers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
www.jenkins.ioin a real browser with your saved login - no setup, no API keys. -
1
Jenkins - check every job's latest build status
jenkins.io
WebRun opens Jenkins to check every job's latest build status. - Open Jenkins and list every job with its latest build status
- Capture the last build time and result for each
- Note any job that appears renamed or missing since the last check
Done when Every job is listed with its latest build status and result.
-
2
Notion - reconcile against the job registry
notion.so
WebRun opens Notion to reconcile against the job registry. - Reconcile the live job list against the Notion job registry
- Add any job found in Jenkins but missing from the registry
- Flag any registry entry whose job no longer exists
Done when The Notion registry matches the jobs that actually exist in Jenkins.
-
3
Google Sheets - log the day's pass and fail counts
google.com
WebRun opens Google Sheets to log the day's pass and fail counts. - Log today's total pass and fail counts as a new row
- Note which jobs failed today specifically
- Keep prior days in place so the trend is visible
Done when Today's pass and fail totals are logged as a new row in the sheet.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it delete or rename a job?
No. WebRun only reports and reconciles records. Renaming or removing a job is always a decision your team makes in Jenkins.
What if a job was renamed instead of removed?
It shows up as a possible mismatch in the registry so someone can confirm and update the record, rather than being silently dropped.
Can I see the overall build health trend?
Yes. Every day's pass and fail totals are added as a new row in the sheet, so the trend builds up automatically.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.