r/gitlab • • 11h ago

How We Slashed Our Windows CI/CD Pipeline from 14 Minutes to Under 3 🚀

Post image
0 Upvotes

Hello

https://gitlab.com/jakubrojicek11/sentinel-ir-mcp/-/blob/09b61d9dc1b90f3ebc7a37be0493d951249453cf/.github/workflows/windows.yml

Waiting 14 minutes for a Windows CI job kills developer flow. For our Model Context Protocol server (Sentinel-IR-MCP), we refused to tolerate that bottleneck anymore. Here is exactly how we optimized our Windows test suite across Node 20, 22, and 24, dropping the total job runtime to 2 minutes and 44 seconds without sacrificing a single check.

Source (GitLab, Apache-2.0): https://gitlab.com/jakubrojicek11/sentinel-ir-mcp Package (npm): https://www.npmjs.com/package/sentinel-ir-mcp The analyzer behind it: https://www.npmjs.com/package/sentinel-ir

The Bottleneck (GitLab Shared Windows Runners)

A standard run on GitLab SaaS Windows took 13.6 minutes, even though our 118 unit tests executed in just 1.6 minutes. The rest was pure infrastructure drag: • VM Provisioning: 3.5 minutes (unfixable) • Real-time Antivirus: Windows Defender choked on npm ci and execution scripts, dragging out our compat-smoke test to 2.9 minutes.

The Fix: Strategic Split & Target Optimization

Instead of fighting the slow runner environment, we re-architected where and how the jobs run:

  1. Shifted Dev Push Matrices to GitHub Actions: GitHub's windows-latest images spin up in seconds (1–2 s) instead of minutes.

  2. Built-in Security Clearance: Real-time scanning (RealTimeProtectionEnabled) is off by default on GitHub's native dev images. This instantly cut our compat-smoke step down to seconds.

  3. Smart Caching & Selective Runs: We enabled direct Node/npm caching and added strict rules to completely skip the Windows matrix if a commit only modifies the README.md.

  4. Kept GitLab strictly for Releases: The heavy GitLab Windows job was moved to run only on release tags as a final gate before publishing to npm.

The Result

Step (Node 24) Old GitLab Pipeline New GitHub Actions Pipeline VM Boot / Wait ~3.5 min 1–2 s npm ci 84 s 4–9 s Test Execution 95 s 22–28 s Total Job Time 13.6 min 2.7 min

![Image description](https://dev-to-uploads.s3.us-east-2.amazonaws.com/uploads/articles/rdyfp4vs3soo307hpa2k.jpg) The code quality remains identical. All 118 tests run flawlessly across all Node versions, but now the feedback loop takes less than 3 minutes. If your Windows pipelines are killing your productivity, look closely at VM spin-up times and real-time antivirus hooks. The performance lift is hiding right there.

*** Independent Engineering Projects

Built as independent engineering experiments across AI, software analysis, security, and autonomous systems.

Evaluated by reproducible evidence, not by the number of layers.

Explore the projects:

Sentinel Ecosystem: AutoDoc-Sentinel, Sentinel-IR, Sentinel-IR-MCP and related tools. Agentix Lite: Independent security and system-observation project. Find the projects: GitLab repositories | NPM packages

Support the work: ⭐ Star the repositories on GitLab.

Connect: Follow me here on DEV Community or explore the Playground.

Each project is distributed under its own license. Check the corresponding repository or NPM package for licensing terms.

Copyright © 2026 jackymenCZ. All rights reserved. Written for the community.


r/gitlab • • 19h ago

project Generating GitLab Duo merge request review instructions from a repo guideline

0 Upvotes

I maintain ai-rulez v5. It's a CLI and MCP for managing the instructions, skills, and settings that coding agents use in a repository.

For GitLab Duo, I tested a merge request review example using v5.13.2. In a scratch Git repo, run ai-rulez init duo-demo --yes --skip-content and set presets = ["gitlab-duo"] in .ai-rulez/config.toml. Add one review guideline and generate the native file:

ai-rulez add check interface-changes --description 'Review public interface changes' --content 'Check that public interface changes have a matching changelog entry.'
ai-rulez generate
ai-rulez generate --check

The generated instruction was in .gitlab/duo/mr-review-instructions.yaml. That puts the source guideline and Duo’s rendered file in the same merge request for review. The review checks guide describes how the YAML is merged when you already have your own entries.

I'm happy to hear any comments. If you find the tool useful, star it. It really does help. And of course, I'd love to see people use it and get involved with the project.


r/gitlab • • 1d ago

grp: A multi-platform CLI multiplexer for GitHub, GitLab, Gitea, Forgejo, and Codeberg (written in Rust)

Thumbnail
reddit.com
2 Upvotes

r/gitlab • • 3d ago

Git + DVC: Version and Restore ML Data and Models with Google Cloud Storage

Thumbnail
youtu.be
1 Upvotes

r/gitlab • • 3d ago

Announcing the October 2026 community hackathon results!

0 Upvotes

October 2026 Hackathon Wrap-Up 🎉

That's a wrap on another incredible hackathon! It was our biggest yet, with 636 MRs merged by 158 participants. A huge congratulations to everyone who contributed. Every MR helps strengthen this community, and we're grateful for the energy, creativity, and persistence you bring. Keep building with us!

🏆 Winners

First place 🥇 jmrp won with 12,838 points for 99 merged MRs.

Second place 🥈 duewel1982 earned second place with 10,414 points for 75 merged MRs.

Third place 🥉 anishisbusy earned third place with 9,921 points for 81 merged MRs.

❗ Note: The top scores were examined and manually adjusted where needed, to remove points received from bulk label automation.

For full results, please see the hackathon page.

Rewards have been sent 🎁!

What's next

Our next community hackathon runs from January 21 to January 27. More details coming soon.

Thank you to everyone who participated!


r/gitlab • • 3d ago

Migrating from Sonatype Nexus (Package Registry + Dependency Proxy) to GitLab Self-Managed — experiences & gotchas?

13 Upvotes

Hi everyone,

We are currently running GitLab Self-Managed alongside Sonatype Nexus (used both as our internal package registry and as a dependency proxy/cache), and we're evaluating consolidating everything into GitLab's built-in Package Registry, Container Registry, and Dependency Proxy to simplify our stack and reduce maintenance overhead.

Before committing to the move, I’d love to hear from anyone who has gone through a similar migration:

Any lessons learned, storage tips, or things you wish you knew beforehand would be greatly appreciated. Thanks!


r/gitlab • • 4d ago

Massive ‘wfx-loot’ Campaign Probes Over 60,000 GitHub Repositories to Steal CI and Cloud Secrets

Thumbnail
kylesinvestigation.com
0 Upvotes

r/gitlab • • 4d ago

project I built a Mac app that shows what a CI change does to other branches' pipelines - before you merge

0 Upvotes

A merge request's pipeline only tests the merge request. When the change is to `.gitlab-ci.yml` itself, what matters is what happens on main, release branches and tags after the merge - and you only find out once it's merged.

An example: an MR adds `changes: [api/**/*]` to `build-api` to save CI time. The MR's pipeline is green. But on release branches `deploy-production` still has `needs: [build-api]`, so after the merge GitLab refuses to create release pipelines, and you find out on release day.

Pipeline Lens fetches your config with its includes (local, project and wildcard) and simulates the pipeline for any branch, tag or MR: which jobs run and the rule that decided each one, why a job was left out along with the variable values it read, and the errors GitLab would reject the pipeline with. For the case above, "Config from" simulates your release branch with the MR branch's config. Large configs work too - gitlab-org/gitlab's own CI config simulates.

30-second demo: https://monk-studio.com/pipeline-lens

It only reads from GitLab: a `read_api` + `read_repository` token, kept in the Keychain and sent only to your GitLab. It works with gitlab.com, self-managed and Dedicated. The simulation engine is open source (MIT): https://gitlab.com/wddwycc/gitlab-ci-parser

Free on the Mac App Store, macOS 14+: https://apps.apple.com/app/apple-store/id6827171674?pt=119022345&ct=reddit-gitlab&mt=8

If it simulates something differently from your GitLab, I'd love to see the config.


r/gitlab • • 4d ago

meta TIL there are no independent open GitLab instances

17 Upvotes

As a user of OctoDroid for GitHub, I vibe-coded forks of it for GitLab and for Forgejo, on which the "add account" allows inputting a custom instance, but also choosing within a predefined list.

For Forgejo, there's a list of instances at codeberg.org/forgejo-contrib/delightful-forgejo, but for GitLab, there isn't.

So I browsed a crawler's list of 1.1k GitLab instances, filtered it down to the <70 ones that have open non-SSO registration, out of which 40% rejected my email (ProtonMail), 40% required admin approval, 10% had open registration but forbid repo creation, and just 1 instance was opened and allowed creating repos, but I wonder whether they just forgot to close registrations.

It's like people say here, self-hosted GitLab is mostly companies, or open source but only for one project, the owner's.

Thoughts ?


r/gitlab • • 4d ago

Your GitLab CI include: is probably not as pinned as it looks

0 Upvotes

I maintain glsec, an open source linter for .gitlab-ci.yml. I want to share one thing that is easy to get wrong, even if you never use the tool, plus a short note on what I added since my last post here.

Two GitLab constructs look pinned but are not:

  • include: project: without a ref: uses the HEAD of that project's default branch. So it changes whenever that branch changes.

  • Catalog components and includes with @1 or @~latest always take the newest matching version.

In both cases someone changes the upstream, your next pipeline runs the new version, and there is no change in your own repository to review. This is a supply-chain risk, and it is easy to miss, because the line looks like it already contains a version. You should pin to a full tag, or better to a commit SHA.

The same problem exists on a different level. The LiteLLM compromise in March started with a single apt-get install trivy without a version. The repository served a modified Trivy build, and it read the CI credentials of the job. Any install without a fixed version can be affected, and these lines are easy to find.

I also added checks for the more clearly malicious patterns: an interpreter that runs a file with a non-script extension (a payload hidden behind an asset name), an SSH private key that is read and then encoded or copied away instead of written into place, and data sent out over DNS. Before I ship a new rule, I test it against 20,000 real public pipelines, because too many false positives make a linter useless.

Repository and the full rule list: https://github.com/glsec/glsec and https://glsec.github.io/rules/

Disclosure: I maintain it. What did you run into in GitLab CI that was not clear from the docs?


r/gitlab • • 5d ago

Two pipelines for every push? How to read what the pipeline list is telling you

0 Upvotes

A common GitLab CI surprise: you push to a branch with an open merge request, and two pipelines appear. Before changing config, the pipeline list itself usually tells you what’s happening.

What you see → what it likely means

  • Two pipelines, same commit, one labeled for the branch and one for the merge request. Your jobs run in both pipeline types, because their rules: don’t distinguish between them. Both are triggered by the same push.

  • Only a branch pipeline appears, and the MR shows no pipeline. Your jobs probably only match branch pushes. If you expected MR pipelines, check that your rules include $CI_PIPELINE_SOURCE == "merge_request_event".

  • Only an MR pipeline appears, and nothing runs on the branch. The reverse: rules match only MR events. Pushes to a branch with no open MR then produce no pipeline at all, which can surprise people.

  • Jobs that can’t find variables like the MR title or target branch. Some predefined variables only exist in MR pipelines, so a job running in a branch pipeline may not have them. Check the predefined variables docs for the ones you use.

One common way to avoid duplicates:
GitLab’s documentation shows a workflow:rules pattern along these lines (check the current docs for your version, since I’m giving the shape from memory):

workflow:
  rules:
    - if: $CI_PIPELINE_SOURCE == "merge_request_event"
    - if: $CI_COMMIT_BRANCH && $CI_OPEN_MERGE_REQUESTS
      when: never
    - if: $CI_COMMIT_BRANCH

The idea: use an MR pipeline when there’s an open MR, skip the branch pipeline in that case, and fall back to a branch pipeline when there’s no MR.

Caveats:

  • Whether you want MR pipelines at all depends on your workflow. Some teams prefer branch pipelines only.

  • MR pipelines and merged results pipelines have different behavior, and some features (like merged results) have requirements on your plan and settings. Check what applies to your setup.

  • Changing workflow:rules affects the whole pipeline, so try it on a test branch or project first.

  • Predefined variable availability differs between pipeline types, so test any job that depends on them.

How does your team handle this: MR pipelines, branch pipelines, or a mix? And what’s the odd behavior that took you longest to understand?


r/gitlab • • 5d ago

general question Is this a sane plan for moving 300 GitLab projects from Veracode to Checkmarx?

3 Upvotes

We signed Checkmarx One to replace Veracode and the rollout landed on me. Around 300 projects on self-managed GitLab, mostly Java and TypeScript plus a handful of Go services. We’re on Premium, not Ultimate which means the GitLab security dashboard and the MR security widget are off the table. Findings live in Checkmarx and show up in GitLab as MR comments.

Here’s the plan, poke holes in it

  1. Set up the repo integration at group level instead of adding a CI include to 300 pipelines, thats one less thing teams can comment out during an incident.

  2. Turn on MR scans for 20 projects first and tune the preset there for two or three weeks.

  3. Keep the MR comments to new findings only, the old backlog goes to team leads separately.

  4. Roll out to the rest one group at a time.

  5. Export the Veracode mitigations to CSV for the auditors and start clean, only re-triage what shows up again.

Sales says a few weeks to get everything scanning but my director wants a date and I’d rather not hand him the sales one.

If you’ve done a switch like this on GitLab, what would you change?


r/gitlab • • 6d ago

Argo CD in a bank with CAB approval: gate the merge, not the sync, and the 5 defaults

Thumbnail
reddit.com
2 Upvotes

r/gitlab • • 6d ago

Upcoming coordinated security patch

36 Upvotes

We run Gitlab on prem. Today I came in to an email from Gitlab advising of an upcoming security patch scheduled for Nov 10 as part of a coordinated disclosure.

No further details provided and there’s nothing I can see on the Gitlab docs.

Anybody else?


r/gitlab • • 6d ago

Which certificate should I choose?

3 Upvotes

I'm a full-stack developer at the company where I currently work. My boss has told me that I can get a certification and the company will cover the cost.

On a friend’s recommendation, I’ve decided to get a GitLab certification, but I’m not sure which one to choose.

The ones that interest me the most are CI/CD and DevOps, but I think right now the one that will be in highest demand (and one's my boss will like more) is the Duo Agent Platform certification. Which one do you guys recommend?


r/gitlab • • 7d ago

GitLab Support granted me an identity verification exemption instead of requiring a credit card Spoiler

Post image
6 Upvotes

I wanted to share my experience in case it helps other students and developers, especially those who don't have access to a credit or debit card.

I'm a student developer from India, and I recently migrated my projects from GitHub to GitLab. I started using GitLab Pages for hosting my personal project, Daily Spark.

However, when I tried to use GitLab CI/CD, I encountered a credit card verification requirement to verify my account.

Unfortunately, I don't own a credit or debit card, so I couldn't complete that verification process.

Instead of giving up, I contacted GitLab Support and explained my situation:

  • I'm a student developer from India.

  • I use GitLab for academic and personal software projects.

  • I don't have a credit or debit card.

  • I wanted to use GitLab CI/CD without having to provide a credit card.

The good news: GitLab Support reviewed my request and granted me an identity verification exemption!

The response from GitLab Support:

"We have finished review of your request and applied an identity verification exemption. As the bypass has been applied, I will mark this ticket as Solved."

I'm genuinely thankful to the GitLab Support team, particularly Kosuke Kamiya, for reviewing my request and providing an alternative.

Sharing this for anyone facing the same issue: If you're a student or developer who cannot complete credit card verification, consider contacting GitLab Support and politely explaining your situation. An alternative verification process may be available.

I hope this helps someone else facing the same problem!

Have other students here encountered this GitLab verification requirement? I'd be interested to hear about your experiences.


r/gitlab • • 8d ago

Open-source tray app that shows each child pipeline of a push and whether the deploy job ran

0 Upvotes

Disclosure: I run Distronode, the company behind this. It's free and Apache-2.0.

Our main branch runs a parent pipeline that starts a set of child pipelines with trigger:include and strategy: depend. Which children run depends on what the push touched, and one of them has a manual deploy job, because rolling it out drains live calls and we want a person to start it.

While that manual job waits, the parent stays at "running". That's GitLab doing what we told it to, but it means the parent's status doesn't say much. In October one of our parents read "running" for about 13 hours after the website child had already failed, half an hour into the pipeline. Watching only the website child has the opposite problem: it can be green while a sibling, like the one that applies our Sentry config, fails next to it.

bridgewatch sits in the macOS menu bar or the Linux tray and shows one row per push with each child pipeline under it. The verdict comes from a deploy job you name, not from the parent's status, so a push like that one shows as failed as soon as the website child has a blocking failure, and a manual job waiting for a person doesn't count as running. Scheduled pipelines are kept apart from pushes, so a red schedule doesn't look like your commit broke something.

2.0 came out on the weekend. On gitlab.com you sign in with a code in your browser instead of creating a token. It asks for read_api, the token stays in your keychain, and the app is read-only unless you turn on retry and play. Setup lists your ten most recently active projects and ticks the top three. A failure notification names the job and GitLab's failure reason, and clicking it opens the job. Self-managed GitLab works with a token, glab's login or your own OAuth app.

macOS:

brew install --cask distronode-corporation/tap/bridgewatch

Linux, x86_64 and arm64, glibc 2.35 or newer (Ubuntu 22.04, Debian 12, Fedora 36 and later): .deb, .rpm and AppImage at https://github.com/distronode-corporation/bridgewatch/releases/latest. On GNOME the icon needs the AppIndicator extension.

There's a CLI on npm too (npm install -g bridgewatch). bridgewatch wait blocks until a commit's pipeline has a verdict and exits with it, which is handy after a git push in a script.

The source is on GitHub, with a read-only mirror on gitlab.com: https://gitlab.com/distronode-corporation/bridgewatch. If it reads your pipelines wrong, I'd like an issue about it.


r/gitlab • • 8d ago

Recent CS graduate contributing to GitLab — is there a realistic path to joining GitLab as an engineer?

13 Upvotes

Hi everyone!

I'm a recent Computer Science graduate from India, and joining GitLab as a Software Engineer is something I'd genuinely love to pursue.

Over the past few weeks, I've been actively contributing to GitLab's open-source projects. I've had multiple erge requests merged across GitLab Runner, Gitaly, Platform Insights, GitLab LSP and the Trivy analyzer wrapper.

I've really enjoyed working with GitLab's codebases, resolving issues and collaborating with maintainers through code reviews.

Now, I'd love to explore the possibility of transitioning from a community contributor to a full-time engineer at GitLab.

I'd particularly appreciate hearing from GitLab employees or maintainers:

  • Does GitLab consider recent graduates with substantial open-source contributions?

  • What's the best route to get considered for early-career engineering opportunities in India?

  • Would my contribution experience be considered relevant when evaluating my application?

I'm not looking for shortcuts, just some honest guidance from people familiar with GitLab's hiring process.

Edit: Just to clarify, I'm open to opportunities globally, not exclusively in India. I'd be interested in understanding early-career engineering opportunities across GitLab's locations and how international applicants with substantial open-source contributions can approach the hiring process.


r/gitlab • • 8d ago

support Adding Email - Custom Domain

1 Upvotes

I'm trying to add an email to my account. The email address is a personal domain that I own. The registration/confirmation email never reaches the new address, though I can send registration emails to other addresses I own (gmail, etc). I've confirmed that my personal domain email has been set up correctly with the email host. Has anyone had this issue before?


r/gitlab • • 9d ago

How to enable SSH clone on self-hosted GitLab running in a private subnet behind an AWS ALB?

0 Upvotes

We have self-hosted GitLab CE on an AWS EC2 instance.

Current setup:

The instance is in a private subnet with no public IP.

Users reach GitLab through an Application Load Balancer on HTTPS, with access restricted to our office IPs.

HTTPS clone with personal access tokens works fine.

The problem:

We're moving our repos from gitlab.com to this server. On gitlab.com, all our Jenkins jobs and developers clone over SSH (git@...). On our server SSH clone doesn't work, because the ALB only supports HTTP/HTTPS, so port 22 has no way in.

Our Jenkins agent runs in the same AWS VPC. Developers connect from the office network or VPN.

What's the best way to enable SSH clone here, keeping it secure and limited to our office and Jenkins? Any suggestions or experience with a similar setup would help.


r/gitlab • • 10d ago

So if i dont login i get blocked for an hour?

24 Upvotes

I usually login, but i recently was navigating gitlab in my own repos and I got blocked....

I cant even login to increase the limit...

Why is the login page itself behind the limit?

(People who pay can also get blocked by bad luck)

So now with the situation in github there was oppurtunity to take some share of the market

I understand that AI bots are a problem but it can't be this bad


r/gitlab • • 13d ago

general question How do you check that your self-managed GitLab backups actually restore?

13 Upvotes

I run a self-managed GitLab and I'm trying to understand how other people verify their backups, not selling anything.

  1. How do you test a restore today (never, manually now and then, scripted)?

  2. When did a restore last fail or surprise you (missing gitlab-secrets.json, version mismatch, DB errors)?

  3. What did that cost you in hours or downtime?

  4. Have you paid for a tool or written your own script for this? What and how much?

  5. How many repos or users is your instance?


r/gitlab • • 13d ago

GitLab pipeline for Windows 11 images: Packer or Azure Image Builder?

2 Upvotes

Has anyone created a GitLab CI/CD pipeline for building customized Windows 11 images in Azure?

I am considering:

  1. GitLab + HashiCorp Packer

  2. GitLab + Azure Image Builder

The important requirement is that the build must use an existing resource group and existing VNet/subnet. The pipeline should not create a new resource group or network.

The final image should be published to Azure Compute Gallery and temporary build resources should be removed after the build.