Pin your Jenkins jobs.
Build any branch in one click.
JenKit is a Chrome extension for the daily build grind. Keep only the jobs you care about, trigger a build on any git branch, tweak any parameter, and watch live console logs in a side panel - no more bouncing between Jenkins pages.
Now on the Chrome Web Store · Reuses your existing Jenkins login
Jenkins is powerful. Daily builds are still a chore.
Jenkins gives you everything. That's also the problem - for the handful of jobs you build every day, you navigate folders, fill in parameters, submit, then chase the console across tabs. Multiply by twenty builds and the day leaks away in clicks.
One panel. Your jobs. Done.
Pin. Build. Watch.
The daily build loop, condensed to three moves - all from one side panel, without bouncing between Jenkins pages.
Pin
Pin only the jobs you build every day, across as many Jenkins environments as you run - dev, test, prod. One follow list per environment, switched by a single tab; everything else stays out of the way.
Build
Hit Build, pick a branch from the list Jenkins itself shows, and tweak any parameter inline - booleans, choices, even Active Choices cascading dropdowns that recompute live. One click, fully formed.
Watch
Follow the build from queue to result with the console streaming live in a terminal-styled panel. Stop a runaway build, replay any past log, jump back any time - all without leaving the panel.
Built on Jenkins' own APIs.
JenKit talks to your Jenkins directly from the browser - no proxy, no backend, no middleman. Three things worth knowing.
- 1
Your browser session
Every request rides the Jenkins login you already have in your browser. When the session expires the panel tells you and offers a one-click jump to log back in - no tokens, ever.
- 2
Jenkins' own APIs
Branches come from the Git Parameter plugin, parameters from the job's own definitions, and Active Choices cascading dropdowns from the same stapler proxy the Jenkins UI uses.
- 3
Live & local
Console output streams incrementally via progressiveText, accumulating in the background even if you navigate away. Configs and biometric credentials stay in chrome.storage.local on your machine.
Live logs that feel like a terminal.
Triggered builds are tracked from queue to result, with output streaming incrementally in a console-styled view you can return to at any time.
Started by user you · via JenKit
Running as SYSTEM
Building on the built-in node
[Pipeline] stage
[Pipeline] { (Checkout)
> git rev-parse origin/feature/ship-faster^{commit} # done
[Pipeline] { (Build)
[INFO] Compiling 142 source files...
[INFO] Tests run: 318, Failures: 0, Errors: 0, Skipped: 4
[INFO] BUILD SUCCESS in 47s
▌Your builds, your machine, your call.
JenKit starts with access to nothing and keeps your data on your device. Lock sensitive environments, back up your setup, move it between machines - all without handing credentials to anyone.
No credentials, ever
JenKit rides on your browser's existing Jenkins session. It never stores or transmits a username, password, or API token - and only ever talks to hosts you explicitly authorize.
Optional per-environment lock
Protect any environment with a passkey (stored only as a SHA-256 hash). The side panel hides its jobs and blocks builds until you verify - by fingerprint when supported, or the passkey as a fallback.
Back up & transfer
Export every environment to a JSON file, or import one to replicate or migrate a setup. Importing dedupes by Jenkins URL - matching environments are updated, new ones are added.
Now available on the Chrome Web Store.
JenKit is live. Add it to Chrome, log into Jenkins, and start pinning the jobs you build every day - no token, no setup wizard.
Minimal by design.
JenKit starts with access to nothing. Host access is requested only when you add an environment, and only for that host. Remove the environment and the access goes with it. Biometric unlock uses the platform WebAuthn API - no extra permission, and the credential never leaves your device.
| Permission | What it's for |
|---|---|
| storage | Store environment configs, followed-job lists, and local biometric credentials on this machine only. |
| sidePanel | Display the main interface in the browser side panel. |
| Optional host permissions | Requested on demand - only when you add a Jenkins environment, and only for that host. |
Questions, answered.
Does JenKit need my Jenkins API token or password?
No. It reuses the login session already in your browser via cookies. It never sees, stores, or sends credentials of any kind.
Can I edit build parameters other than the branch?
Yes. JenKit renders every declared parameter as a form with defaults pre-filled - booleans, strings, text, passwords, choices, multi-select, and Active Choices cascading dropdowns. Change what you need and leave the rest.
What is passkey protection?
It's an optional, per-environment lock. Once set, the side panel hides that environment's jobs and blocks builds until you verify. Unlock with Touch ID or Windows Hello when supported, or the passkey as a fallback. The passkey is stored only as a SHA-256 hash, never in plain text.
Can I back up or move my configuration?
Yes. Export all environments to a JSON file, or import one to replicate or migrate a setup. Importing dedupes by Jenkins URL - matching environments are updated, new ones are added. Biometric credentials stay on the original device and are never exported.
Does it work without the Git Parameter plugin?
Branch selection requires the Git Parameter plugin. Jobs without a git branch parameter still let you trigger a build through the full parameter form, or a direct build if the job has no parameters at all.
Why only 5 branches?
JenKit surfaces the top 5 candidates returned by the Git Parameter plugin for fast picking. Whether those are the newest 5 depends on the job's Git Parameter sort settings - sorting by commit date descending is recommended.
What happens to a build if I close the side panel?
Builds triggered by JenKit keep accumulating logs in the background. Reopen the panel and the job's log picks up where you left off. Viewing a historical build's log is a temporary session that stops when you leave.
Where can I get it?
JenKit is on the Chrome Web Store - add it to Chrome, then log into Jenkins and pin your jobs. No API token or setup wizard required.
Stop bouncing between Jenkins pages.
Pin the jobs you build every day, fire them off on any branch, tweak any parameter, and watch the logs stream - all from one side panel.