Checked October 19, 2026

GitLab™ pipelines, jobs and job logs in IntelliJ IDEA, PyCharm and other JetBrains IDEs

JetBrains IDEs have GitLab support built in: IntelliJ IDEA, PyCharm, WebStorm, PhpStorm, GoLand, CLion and Rider have had it since 2023.2, and it already reaches CI/CD in two ways. Per JetBrains' issue tracker, the details of a merge request show its checks with links to the jobs on GitLab, and .gitlab-ci.yml has editing support. If status in the merge request is what you need, the built-in support may be enough, though manual jobs may still show as failed checks (IJPL-84153, open) and we did not try it in an installed IDE. What the tracker lists as open is a CI view in the IDE, a list of a project's builds with their status and restart and cancel (IJPL-82612, in the Backlog, filed in 2015), and Marketplace has plugins for that. These are the general options for seeing GitLab pipelines, jobs and job logs in the IDE that we found.

Disclosure: Lesstep makes one of them (Pipeline Inbox for GitLab CI). The others are described from JetBrains' help and issue tracker and from their JetBrains Marketplace pages (descriptions, change notes, version lists and US prices) and, where linked, their own README. Where those do not say something, this page says "not stated in its description" instead of guessing. GITLAB is a trademark of GitLab Inc. in the United States and other countries and regions. Pipeline Inbox for GitLab CI is not affiliated, endorsed, sponsored, or approved with or by GitLab Inc. Corrections are welcome at support@lesstep.com. 日本語

Which one fits

• You want the pipeline status of a merge request, or help writing .gitlab-ci.yml: start with the built-in support. Per JetBrains' issue tracker the details of a merge request show its checks, and JetBrains' help lists highlighting, inspections and completion for .gitlab-ci.yml. The help names GitLab 14.0 and later for the integration.
• You want a list of a project's pipelines with their jobs, apart from merge requests: a CI view with a list of builds is an open request for the built-in support. GitLab CICD, GitLab Pipeline Monitor, Crocodile for GitLab and Sciak Flow list pipelines, jobs and job logs; MerryLab's change notes list pipeline logs; Pipeline Inbox (ours) lists pipelines and their jobs; Cockpit for GitLab shows pipelines through merge requests.
• You work in several GitLab projects and want their pipelines in one list: GitLab Pipeline Monitor lists the projects found in the workspace and has a dashboard of their latest pipelines; Pipeline Inbox (ours) lists the pipelines of all GitLab projects open in the IDE together, or of the recently active projects of their groups. Sciak Flow does not support projects with several repositories. GitLab Pipeline Viewer (free, version 1.0.0, see the note) also lists the pipelines of several projects.
• You want to retry, cancel or run from the IDE: Crocodile for GitLab and Cockpit for GitLab (both free) list retry and stop or cancel, and Sciak Flow (free) cancel and restart of a job. GitLab CICD (paid) and GitLab Pipeline Monitor (its change notes put creating, cancelling and retrying pipelines in its paid tier, which it calls Premium) list them too; GitLab Pipeline Viewer (free, see the note) also creates, cancels and retries.
• You want a free plugin: Crocodile for GitLab, Cockpit for GitLab and Sciak Flow are free; GitLab Pipeline Monitor is free for viewing; Pipeline Inbox (ours) is free for reading. GitLab CICD and MerryLab are paid. GitLab Pipeline Viewer (in the note) is free too.
• You are on IDE 2024.3 to 2025.2: the built-in support is there. Marketplace offers a version of GitLab CICD, GitLab Pipeline Monitor, Crocodile for GitLab and MerryLab for all three; Sciak Flow has older version lines for 2025.1 and 2025.2 (not 2024.3, and without its MCP tools); Cockpit for GitLab starts at 2025.2, and Pipeline Inbox (ours) at 2024.1.
• Your Self-Managed GitLab is older than 17: the built-in support names 14.0 and later, GitLab CICD 15.x or later; Cockpit for GitLab needs 17 or later. GitLab Pipeline Monitor names 16.5 and later for reading the inputs of .gitlab-ci.yml when you create a pipeline, not for the plugin as a whole, and Pipeline Inbox (ours) names 16.7 and later for the settings link that opens the token form, not for the plugin. Crocodile for GitLab, Sciak Flow, MerryLab and Pipeline Inbox (ours) state no minimum version; we tested ours against GitLab CE 18.11 and 19.5 (October 22, 2026), not against anything older.
• You want AI agent hooks: Sciak Flow's change notes list MCP tools that return a pipeline's jobs and job logs (from version 16.4.0, IDE 2025.3 and later). JetLab, which shows pipeline statuses in its merge request list, lists an MCP server, an "AI Review" action and text improvement with your own API key; MCP Server AI Companion returns a merge request's pipeline to AI agents. The builds differ; see the cards and the note below them.
• You want a pipeline list whose own description says it has no AI features and no telemetry: Pipeline Inbox for GitLab CI (Lesstep's). Crocodile for GitLab, free, lists no AI features and says that tokens and data are never sent to third parties; it also has retry and stop. Most other entries list no AI features and say nothing about telemetry.

The main options

Smaller or narrower entries also exist. Pipeline Viewer (free; Marketplace lists the AGPL-3.0 license; offered for 2024.3 to 2026.2) has a one-sentence description about tracking GitLab pipelines, and its change notes list notifications, watched branches and tags; jobs and logs are not stated. GitLab Pipeline Viewer (free; not published by GitLab, Inc.; version 1.0.0, September 16, 2026) lists the pipelines of several projects, creates, cancels and retries pipelines and jobs, runs manual jobs and shows job logs with search; it names IntelliJ IDEA 2023.1 and later and a token with the api scope. GitPipeline (free) lists pipelines and job logs and names self-hosted GitLab 16.x as optional; its description names IDE 2026.1.x, up to 5 projects and 10 pipelines, and Marketplace offers nothing for 2026.2. GitLab Pipeline Watcher (free; not published by GitLab, Inc.; IDE 2025.2 and later) lists the recent pipelines of the current project, follows the pipeline of a pushed tag and reuses the sign-in of the JetBrains GitLab plugin; its change notes (in Spanish) add retrying a job and downloading job artifacts. Pipeline Notifier (free; IDE 2026.2 and later) alerts when a GitLab pipeline or a GitHub Actions run fails. GitLab CI Companion (free; not published by GitLab, Inc.) checks .gitlab-ci.yml offline; a live window of pipelines and jobs is opt-in with a token. AOne GitLab Connect (free; not published by GitLab, Inc.) is a beta (1.0.0-beta.1, July 25, 2026) for IDE 2026.2 and later; its description says GitLab 13.x to 19.x and lists pipeline status monitoring next to merge request details. JetLab (paid; published by Majera Software, not by GitLab, Inc.; builds for 2025.3 and later) is a merge request plugin whose change notes list pipeline statuses in the merge request list and support for external pipelines; a pipelines view with jobs and logs is not stated. Its change notes list AI features by build: an MCP server for AI agents (its 2026.1 and 2026.2 builds, not the 2025.3 build), an "AI Review" action for merge requests (version 2026.3.3, September 2026; not the 2025.3 build) and text improvement that needs your own API key (all builds). CIclone (paid, $40 a year for individuals, $80 for organizations, 30-day trial) notifies when a CI build finishes and jumps to failed tests; its opening sentence names GitLab CI/CD, but the list of supported CI services in its description does not, and its change notes mention a GitLab tool window in versions up to 2024.2. MCP Server AI Companion (free; IDE 2025.3 and later) is a general MCP server for AI agents; through the IDE's GitLab account its get_merge_request tool returns a merge request's pipeline, and it lists no tool for pipelines or job logs. Merge Request Integration CE (not published by GitLab, Inc.; last updated March 7, 2021) lists checking pipeline status and is not offered by Marketplace for 2024.3 to 2026.2. GitLab's own GitLab Duo (published by GitLab, Inc.) is an AI assistant for code suggestions, agents and chat; its description does not mention pipelines. Plugins for editing or checking .gitlab-ci.yml (CI Aid for GitLab, CI Lint for GitLab, CI Pipeline Lint, GitLab CI Break Lint), tools that generate CI files or trigger builds, and plugins where GitLab pipelines are one module of a toolbox are left out; this page keeps to general tools for seeing GitLab pipelines, jobs and job logs in the IDE.

Prices are the US year-one prices Marketplace listed on October 19, 2026 (ours on October 23, 2026); other countries and later years can differ. Dates are from the same pages (in UTC).

What the built-in support reads from a pipeline, in its source

The issue tracker entries in the card above describe the built-in support from the outside. In the source of IntelliJ IDEA's GitLab support (checked October 30, 2026), its CI is one line in the details of a merge request:

• It reads the merge request's head pipeline, and from it, for each job, only the name, the status, whether the job is allowed to fail, and the address of the job's page on GitLab: up to 1,000 jobs, a name shown once even when several jobs have it (mergeRequest.graphql, pipeline.graphql, ciJob.graphql, GitLabPipelineDTO.kt).
• The line reads "All required checks have passed", "Checks in progress…", "Checks in progress, and some already failed…" or "Checks failed"; a required job that is manual or skipped makes it read "Checks failed". Which jobs count as required, and why, is on GitLab: why the merge was refused.
• Details… next to the line opens a list titled "Open in Browser" with each job's name and status icon; choosing a job opens its page on GitLab in the browser (GitLabMergeRequestStatusViewModel.kt, CodeReviewDetailsStatusComponentFactory.kt, CollaborationToolsBundle.properties).
• We found no request in it for a project's pipelines, a job's log, or retrying, cancelling or running a job or a pipeline: its REST requests and its GraphQL queries and mutations have none (api/request, mergerequest/api/request, resources/graphql). Its other CI part is the .gitlab-ci.yml support in the card.

So the built-in support tells you whether the required jobs of a merge request passed, and sends you to GitLab for the rest: the log of a failed job, a retry, a manual job to run, or the pipelines of a branch without a merge request. The plugins in the cards above bring some or all of that into the IDE; each card says which.

Other comparisons

• Azure DevOps pull requests in JetBrains IDEs
• Bitbucket pull requests in JetBrains IDEs
• GitLab merge requests in JetBrains IDEs
• Forgejo and Gitea pull requests in JetBrains IDEs
• Jenkins builds in JetBrains IDEs
• GitHub Actions runs in JetBrains IDEs

Sources

• JetBrains help (IntelliJ IDEA): GitLab CI/CD (April 22, 2026), set up a GitLab account (August 25, 2026) and review incoming merge requests (June 19, 2026); the same topics are in the help of the other IDEs named above
• JetBrains What's New: GitLab integration in IntelliJ IDEA 2023.2 and the 2023.2 pages of PyCharm, WebStorm, PhpStorm, GoLand, CLion and Rider; the CI checks column in IntelliJ IDEA 2024.1
• JetBrains issue tracker, states on October 19, 2026: the issues linked above
• Plugins: their JetBrains Marketplace pages, linked above (descriptions, change notes, version and compatibility lists, prices and trial lengths as of October 19, 2026), the README of Cockpit for GitLab (linked from its Marketplace page), and for Pipeline Inbox for GitLab its own page
• How the list was made: Marketplace searches on October 19, 2026 for 110 terms, among them "gitlab pipeline", "gitlab pipelines", "gitlab ci", "gitlab ci/cd", "gitlab jobs", "gitlab job log", "pipeline", "ci status", "gitlab runner" and "gitlab", with and without an IDE version filter (2024.3, 2025.2 and 2026.2); every result's description was read for GitLab and for pipelines, jobs or CI. Other plugins may exist that these searches do not return.