Pipeline Inbox for GitLab™ CI
A free pipeline list for GitLab, on GitLab.com and GitLab Self-Managed, in IntelliJ IDEA, PyCharm, WebStorm, Rider and the other JetBrains IDEs: monitor the pipelines of every GitLab project you have open and view their jobs and logs, with a notification when yours finish. No AI features, no telemetry.
Get it on JetBrains Marketplace · reading is free, Pro has a 30-day trial
GitLab merge requests in the same IDE: our GitLab merge request plugin.
Comparing GitLab pipeline plugins for IntelliJ IDEA, PyCharm or Rider? See the options side by side.
This plugin is not affiliated, endorsed, sponsored, or approved with or by GitLab Inc. GITLAB is a trademark of GitLab Inc. in the United States and other countries and regions.
Pipelines
- Every GitLab project in the IDE project together (multi-repository projects too), or the most recently active projects of their groups, or of everything you are a member of
- Filters: started by me, my current branch (with the pipelines of its open merge requests), failed
- Each row: status, commit title, branch or merge request, who started it, how it started (schedule, web, merge request), how long it took and when
- A notification when a pipeline you started finishes (without a token: the pipelines of your current branch), for the projects cloned in the IDE, with a link to the log of the job that failed; the current branch's latest pipeline in the status bar
Jobs and logs
- Jobs by stage with their status and duration, allowed failures marked, YAML errors as GitLab reports them
- Downstream and child pipelines: open them from the trigger job, and go back
- Job logs in a console viewer at the bottom, with the log's own colours, searchable, following a running job as it writes
Acting
- Retry a pipeline's failed or canceled jobs, or one job (the log follows the new run); cancel a pipeline or a job
- Run a manual job, with variables for that run
- Run a new pipeline on a branch or tag with variables: the ones
.gitlab-ci.ymloffers are filled in, and yours can be remembered per project; when GitLab refuses, the dialog stays open with its reason
Free and paid
Free: the pipeline list, jobs by stage, job logs, notifications and the status bar. Paid, with a 30-day free trial: retry, cancel, run manual jobs and run new pipelines. 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 retry, cancel or run pipelines need a license.
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 GitLab CI. Then open a project whose Git remote is on gitlab.com or on your GitLab Self-Managed server (add the server in the plugin settings) and find GitLab Pipelines in the right tool window bar.
Works with
- GitLab.com: HTTPS and SSH remotes, including SSH over port 443
- GitLab Self-Managed (Free tier and up, Community or Enterprise Edition): add any number of servers in Settings | Tools | Pipeline Inbox for GitLab, each with its own token; a relative URL root works too. A server whose host name has a part beginning with gitlab is recognised from the remote and read without a token
- Projects nobody has cloned (a deployment repository, for example): add them in the same settings by path or address
- The IDE's proxy settings (including proxy authentication) and trusted certificates, for self-signed or company certificates
- Tested against GitLab CE 18.11 and 19.5 with a runner on October 22, 2026: running a pipeline with variables, cancelling and retrying jobs and pipelines, running a manual job with variables, and job logs
- IntelliJ IDEA, PyCharm, WebStorm, Rider and the other JetBrains IDEs 2024.1 or later with Git, and Android Studio Koala (2024.1.1) or later
Access token
Public projects can be read without a token (unless a project shows its pipelines to members only), except job logs: GitLab's API has given them only with a token on every server we tried. For logs, private projects and "started by me", create a personal access token with the scope api to retry, cancel and run as well (choose it from the start if you want to try Pro), or read_api to read only (how to create one; the plugin settings have a link that opens the form with the name and scope filled in, on GitLab 16.7 or later; on an older GitLab, open Access Tokens in your profile settings). Project and group access tokens work too. Enter it in Settings | Tools | Pipeline Inbox for GitLab: one token for GitLab.com and one for each Self-Managed server, each kept in the IDE's password safe and sent only to its own server. If GitLab answers "insufficient_scope" (The request requires higher privileges than provided by the access token), see which scope to add; if it answers 401 "invalid_token" (Token is expired, Token was revoked), see what happened to the token; if it answers 404 "Project Not Found", see address or access; if listing a group's projects answers 404 "Group Not Found", see why GitLab did not find the group; if it will not run a pipeline or a job ("Reference not found", "The resulting pipeline would have been empty", "Job is not retryable"), see why GitLab refused it; if Run is disabled with "You are not authorized to run this manual job", see protected environments and outdated deployments; if a pipeline failed with no jobs, with "The pipeline failed due to the user not being verified." or another reason, see what each failure reason means; if a job stays at "This job is waiting for resource", see which job uses the resource; if it does not give a job's log (403 for debug logging, 404, or an empty log), see why the log was refused; if GitLab says "This job does not have a trace." after an upgrade to 18.0, see how to turn incremental logging on again; if a job failed as stuck or over its timeout, see jobs dropped by GitLab; if it answers "Insufficient permissions to set pipeline variables", see who may use pipeline variables.
No AI features, no cloud of ours
The plugin talks only to GitLab: gitlab.com, the Self-Managed servers you set and, without a token, a server your Git remote (or a project address you enter) points at whose host name has a part beginning with gitlab. Your code and logs are not sent to any AI service or to any server of ours, and there is no telemetry.
日本語
IDE の言語が日本語のとき、画面の文言は日本語で表示されます（GitLab から届くメッセージやジョブ名はそのまま）。お問い合わせは日本語でも受け付けます。日本語の説明