GitLab Environment Variables Manager
A JetBrains IDE plugin that lets you manage GitLab CI/CD environment variables directly from your editor. No more clicking through the GitLab UI every time you need to add or update a variable.
The Problem
At Pyango, we run everything on self-hosted GitLab with a monorepo architecture. That means a lot of CI/CD pipelines, a lot of environment variables, and a lot of time spent in the GitLab web UI clicking through settings pages.
GitLab doesn't let you group or namespace variables within a single project. When you have a monorepo with multiple services, the variable list gets overwhelming fast. You end up with names like FRONTEND_PROD_API_URL and BACKEND_STAGING_DB_HOST just to keep things organized, and you're constantly switching between your IDE and the browser to check or update values.
I built this plugin because I got tired of the context switching. If I'm already in PyCharm working on a deployment config, I should be able to see and edit the variables right there.
What It Does
View Variables
Browse all project-level and group-level CI/CD variables in a searchable panel inside your IDE. See the key, value, environment scope, and protection status at a glance.
Edit In-Place
Update variable values, toggle protection, change scope, or mark as masked. All without leaving your editor. Changes push directly to GitLab via the API.
Create & Delete
Add new variables or remove old ones from the same panel. Supports all GitLab variable types including file variables.
Works Everywhere
Compatible with every JetBrains IDE: PyCharm, IntelliJ IDEA, WebStorm, GoLand, RustRover, Rider, and the rest. If JetBrains makes it, this plugin runs in it.
By the Numbers
Why I Built It
I have a pattern of building tools when existing workflows annoy me enough. At Pyango, we ran into the variable management problem early when we moved to a monorepo setup. The GitLab UI is fine for a few variables, but it doesn't scale well for a project with dozens of services.
The plugin started as an internal tool. I published it on the JetBrains Marketplace because the problem isn't unique to us. Anyone running GitLab CI/CD with more than a handful of variables deals with the same friction. Over 500 developers have installed it so far, which tells me the pain point is real.
I also ran internal CI/CD workshops at Pyango where the plugin became part of the standard tooling. When your whole deployment workflow lives in GitLab, having fast access to variables from your editor saves a surprising amount of time over a week.
Tech Stack
Try the plugin. It's free on the JetBrains Marketplace.