Pipeline Inbox for Jenkins®
A free build inbox for Jenkins in IntelliJ IDEA, PyCharm, WebStorm, Rider and the other JetBrains IDEs: the builds you care about from every Jenkins you use, in one list in an IDE tool window — started by you, building your commits, or on the branch you have checked out — with their Pipeline stages, failed tests and console logs. A Jenkins integration for your builds, without leaving the IDE. No AI features, no telemetry.
Get it on JetBrains Marketplace · reading is free, Pro has a 30-day trial
Comparing Jenkins plugins for IntelliJ IDEA, PyCharm or Rider? See the options side by side.
This plugin is not affiliated with or endorsed by the Jenkins project.
Builds
- Jobs, folders and multibranch projects (branches and pull requests), on any number of Jenkins servers, chosen per IDE project: from a tree of your server's jobs, or by pasting a job's address from the browser
- Filters: mine (started by you, or building your commits), my current branch, failed or unstable
- Each row: status, job and branch, the commit or pull request, what started it, the failed test count, how long it took or how long it has left, and when
- Only the active jobs of a large multibranch project are read, with the fields the list needs: no timeouts on servers with thousands of builds
- A CI build monitor: a notification when a build of yours or of your current branch finishes, with a link to its console; the current branch's latest build in the status bar
Details and logs
- Who or what started a build, the commits it built, its parameters and the upstream build
- Pipeline stages with their status and duration (from the Pipeline: Stage View or the Pipeline Graph View plugin); double-click a stage to open the console where it starts
- Failed tests with Jenkins' reason, each opening its page
- Console output in a console viewer at the bottom, with AnsiColor colours, searchable, following a running build as it writes
Acting
- Trigger a build (Build Now) with parameters: a field for each parameter (text, choice, checkbox, password), defaults filled in, and the values remembered per job if you like (passwords never are). If Jenkins keeps the build in its queue, the note says why ("Waiting for next available executor" and the other reasons)
- Rebuild with the same parameters, edited first if needed
- Stop a running build (when a Pipeline build will not abort)
- Proceed or abort a Pipeline input step (who may answer, and the input's address for curl)
Free and paid
Free: the build list, Pipeline stages, failed tests, console logs, notifications and the status bar. Paid, with a 30-day free trial: build with parameters, rebuild, stop builds and answer input steps. Licenses are sold through JetBrains Marketplace: US$1.50 a month or US$15 a year for individuals, US$3 a month or US$30 a year per user for organizations (Marketplace shows the price in your currency). Reading is free for everyone, so in a team only the people who build, stop or approve from the IDE need a license. When the trial or a license ends, reading keeps working; only those actions lock.
Buying for a team: an organization license is managed in JetBrains Account, where an administrator assigns it to developers; the on-premises JetBrains License Server can serve it too. Pay by card or PayPal; for a purchase order or a bank transfer, ask for a quote with Get Quote on the plugin's Marketplace pricing page.
Install
Install it from JetBrains Marketplace, or in your IDE open Settings | Plugins | Marketplace and search for Pipeline Inbox for Jenkins. Add your Jenkins server in Settings | Tools | Pipeline Inbox for Jenkins, then open Jenkins Builds in the right tool window bar and click Add Jobs.
Works with
- Any number of Jenkins servers, each with its own user name and API token; a context path (
https://example.com/jenkins) works, and so does a Jenkins whose own address setting is wrong - Freestyle and Pipeline jobs, folders, and multibranch projects with their branches and pull requests
- Stages from the Pipeline: Stage View or the Pipeline Graph View plugin (moving off Blue Ocean), test results from JUnit, colours from AnsiColor, where the server has them
- The IDE's proxy settings (including proxy authentication) and trusted certificates, for self-signed or company certificates
- Every JetBrains IDE with Git support: IntelliJ IDEA, Rider, PyCharm, WebStorm, GoLand, PhpStorm, CLion, RubyMine and others
For the pull requests your multibranch projects build, Lesstep also makes review inboxes, each a separate plugin: Bitbucket, GitHub, GitLab, Azure DevOps and Forgejo and Gitea.
API token
A Jenkins that lets anyone read works without a token. Otherwise, and to build, stop or approve, create an API token on your Jenkins:
open your user page (your name at the top right), then Security, API Token, Add new Token.
Enter your user ID and the token in Settings | Tools | Pipeline Inbox for Jenkins, for each server: each token is kept in the IDE's password safe and sent only to its own server.
With an API token, Jenkins asks for no CSRF crumb ("403 No valid crumb was included in the request").
If Jenkins says "anonymous is missing the Overall/Read permission", the token did not reach it (why, and how to send it); if it answers 401, it got them and did not accept the pair (how to check which part is wrong).
A script that POSTs to /build of a job with parameters gets HTTP 400 "Nothing is submitted"; such a job starts from /buildWithParameters (the commands).
If jenkins-cli.jar stops with "CLI handshake failed with status code 403", see the Jenkins URL check behind it, and the two fixes.
No AI features, no cloud of ours
The plugin talks only to the Jenkins servers you add, in Settings or by pasting a job's address. Your code and logs are not sent to any AI service or to any server of ours, and there is no telemetry.
日本語
IDE の言語が日本語のとき、画面の文言は日本語で表示されます（Jenkins から届くメッセージやジョブ名はそのまま）。お問い合わせは日本語でも受け付けます。日本語の説明
Help
Jenkins® is a registered trademark of LF Charities Inc. Bitbucket, GitHub, GitLab, Azure DevOps, Forgejo and Gitea are trademarks of their owners.