Just like a first date, you won't want the agent moving too fast without a little vetting first. ✅
Make it show its work before it ships.
GitLab
GitLab is a software forge primarily developed by GitLab Inc. It is available as either a free software "Community" edition or a proprietary software "Enterprise" edition. More on Wikipedia
-
🦊 GitLab
@gitlab
-
🦊 GitLab
@gitlab
What happens in Vegas... should definitely include Booth #274. 🎲
We’re two weeks out from #awsreinvent, and we’re stacking the deck with lightning talks. Don't miss these quick, practical sessions from our experts or the chance to get your biggest questions answered.
Also, don’t leave your schedule to chance. Breakout sessions fill up fast, so reserve your seat now. Learn more. 👉 registration.awsevents.com/flow/awsevents/reinvent2026/ev… -
🦊 GitLab reposted
Chainguard ⛓️
@chainguard_dev
@gitlab Enterprise Edition now comes as GitLab-certified hardened images from Chainguard.
You bring the license and we’ll take care of the maintenance, including signed builds, SBOMs, SLSA L3 provenance, and 7-day fixes for critical CVEs. Learn more: www.chainguard.dev/unchained/run-gitlab-certified-hardene… -
🦊 GitLab
@gitlab
As agents take on more of the work, the big question is who decides what. 🤔
If you’re a leader wondering where your people should stay in the loop, here’s where to start exploring. about.gitlab.com/ai-native-playbook/topics/working-with-a… -
🦊 GitLab
@gitlab
More models. More choice. 🎯 Four new models are now available in GitLab Duo Agent Platform:
Gemini 4 Carbon
Gemini 4 Hydrogen
Claude Mythos 5.2*
Kimi K3.1 Pro
Which one are you choosing next? 👇
*Claude Mythos 5.2 is available for Business Logic Security Analyzer only. -
🦊 GitLab
@gitlab
AI agents can reach issues, pipelines and production signals. Controlling what they touch is the hard part.
GitLab VP of Engineering @tpmtim joined @software_daily to discuss agent governance, tracking the human behind an agent’s actions, air-gapped software, and new players entering code hosting. Listen here. softwareengineeringdaily.com/podcasts/gitlab-and-the-evol… -
🦊 GitLab
@gitlab
95 merged MRs across 23 repos in a single release? Talk about momentum! 🔥
José M. Requena Plens is our GitLab 19.6 Notable Contributor, closing fine-grained token gaps across our GraphQL API, one resolver at a time.
Thank you, José. We’re lucky to have you in the community. 🧡 -
🦊 GitLab
@gitlab
-
🦊 GitLab
@gitlab
GitLab’s own infrastructure secrets are protected, but if your developers use Claude Code, secrets typed into approved commands can end up committed to your repositories.
Use push rules, Secret Push Protection, and scan execution policies to stop it, then let GitLab Duo Agent Platform find every affected project and open the cleanup merge requests. about.gitlab.com/blog/prevent-leaks-from-claude-code-dont… -
🦊 GitLab
@gitlab
A practical framework for deciding when agentic AI can safely act in your software lifecycle, using workflow evidence, risk-based thresholds, and governance. Read more: about.gitlab.com/blog/how-to-develop-a-decision-grade-ai-…
-
🦊 GitLab
@gitlab
AI agents are taking on more of the work. Oversight has to keep up.
The AI Governance Dashboard in GitLab 19.5 shows which agents are active, which tools they call, and who started each action. Now in beta. Colleen Lake shows how it works: about.gitlab.com/blog/ai-governance-dashboard/ -
🦊 GitLab
@gitlab
What's worse - learning your agent "took care of it" without receipts, or realizing you never asked for any? 🤔
Good news is that this one's an easy fix. Start logging everything, every time. -
🦊 GitLab
@gitlab
More code + more speed = better outcomes…? 👀
The math isn’t quite that simple. Catch this take from Elisabeth Hendrickson from the Enterprise AI Summit on what actually counts when AI picks up the pace.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Claude Fable 5.2 from @AnthropicAI is now available in GitLab Duo Agent Platform.
Fable 5.2 brings top-tier coding and reasoning to complex, multi-step work, with outputs up to 30% faster than Fable 5.1. Try it today. -
🦊 GitLab
@gitlab
There are better things to do than babysit a small fix all afternoon ⚙️.
The tests, review comments, waiting for CI… it adds up. Give Duo CLI a /goal and see it work through those steps, with an independent reviewer checking the result.
See it in action in the full demo.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
A deployment token slipped into a CI file. It happens, but what you do next matters.
With Secrets Manager and Duo, you can rotate it and get a merge request ready to fix the code - all from GitLab ✨
Watch the full demo here.👇about.gitlab.com/events/transcend/virtual/This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
See AI agent activity in one place with the GitLab AI Governance Dashboard, across Duo Agent Platform and the externally connected agents your developers use. about.gitlab.com/blog/ai-governance-dashboard/
-
🦊 GitLab
@gitlab
Still measuring AI progress by output alone? Dr. Mik Kersten thinks your operating model could use an update ✅ Catch his take from the Enterprise AI Summit.
-
🦊 GitLab
@gitlab
Learn how to call a custom GitLab flow from Salesforce so every error arrives as a GitLab issue with root-cause analysis, ready to fix and deploy. about.gitlab.com/blog/extend-gitlab-duo-agent-platform-in…
-
🦊 GitLab
@gitlab
Here’s where engineering leaders like you are starting to redesign the work around AI. 👇 about.gitlab.com/ai-native-playbook/topics/redesigning-th…
-
🦊 GitLab reposted
RAPIDFORT
@RapidFortInc
Teams put a lot of work into securing the code they ship. But for self-managed GitLab, the container images running the platform itself need the same scrutiny.
RapidFort and @gitlab are partnering to make that easier. Regulated and air-gapped teams can now deploy GitLab on hardened RapidFort Images that are near-zero CVE, continuously patched, and STIG-hardened, with audit-ready compliance evidence. The images keep GitLab’s existing functionality and version tags, so nothing changes about how teams build and ship.
“For self-managed customers, security doesn’t stop at the application layer,” says Martin Brümmer, Senior Product Manager at GitLab.
Read the announcement 👇
🔗www.rapidfort.com/blog/secure-the-platform-that-builds-yo…
#rapidfort #gitlab #softwaresupplychainsecurity #opensource -
🦊 GitLab
@gitlab
Don’t just watch the demo. Do it yourself.
Explore GitLab’s capabilities through interactive demos and hands-on experiences in the GitLab Demo Hub. about.gitlab.com/demo-hub/This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
With GitLab, every change at Compare the Market follows the same path to production, whether a person or an agent wrote it.
That covers up to 400 engineers working alongside agents, with a reliable record of who or what produced each change.
GitLab Chief Product and Marketing Officer Manav Khurana shares how this visibility is what lets Compare the Market run at agentic speed with enterprise control. technologymagazine.com/news/the-tech-behind-compare-the-m… -
🦊 GitLab
@gitlab
You want your team to experiment with AI. You also want to know where the spend’s going. Fair enough 👀
See who’s using what, set credit caps, and give people more room when they need it. Watch the full demo to see how 👉 about.gitlab.com/events/transcend/virtual/This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
This month, we're digging into GitLab's new AI-Native Engineering Playbook, exploring the latest innovations in GitLab 19.5, and hearing how one financial technology company is putting agentic AI to work.
This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
We submitted our comment on the European Commission’s proposed Cloud and AI Development Act (#cada), but regulation is only one lever for digital sovereignty.
Our Field CTO EMEA, Bryan Ross, shares 10 questions to ask any software vendor about data residency, AI model choice, access controls, audits, and portability, so you can see who takes sovereignty as seriously as you do. about.gitlab.com/blog/10-questions-to-ask-any-software-ve… -
🦊 GitLab
@gitlab
Think you've got an eye for bugs? 🐛
We've hidden one in this merge request.
Take a closer look. We dare you. 🎃 -
🦊 GitLab
@gitlab
Exploitation happens at machine speed now. With GitLab Orbit, now generally available, map every project, owner, and pipeline a critical CVE touches so remediation can keep up.
Read more in our blog. about.gitlab.com/blog/find-vulnerability-blast-radius-wit…This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Finding vulnerabilities is one thing. Preventing them from being merged is another. 🔐
This Cybersecurity Awareness Month, find out how GitLab's merge request approval policies help enforce security checks and make secure code the default. -
🦊 GitLab
@gitlab
GitLab Orbit is now generally available. Agents with full SDLC context complete tasks more accurately and in fewer attempts than agents working from fragments: up to 45x fewer retries and 4.5x fewer tokens in our testing.
Learn more. about.gitlab.com/blog/gitlab-orbit-ga/ -
🦊 GitLab
@gitlab
What happens when vulnerabilities are discovered faster than you can fix them?
The next challenge is bringing that speed to remediation and prevention, inside the software factory.
See how we’re connecting discovery, remediation, and prevention, and how you can run your next security sprint on us. about.gitlab.com/blog/security-at-machine-speed/This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
The GitLab platform isn’t affected by PHP2Shell, but if your teams run PHP, you can use container scanning, GitLab Orbit, and code search to find every affected project and group. Then, let GitLab Duo Agent Platform automate the fix. about.gitlab.com/blog/gitlab-helps-remediate-critical-php…
-
🦊 GitLab
@gitlab
“The biggest risks live in the work that never enters the queue.” GitLab CIO Manu Narayan on why AI governance has to travel with the work. www.cio.com/article/4233151/your-ai-governance-model-is-a…
-
🦊 GitLab
@gitlab
GitLab Duo Agent Platform keeps review, tests, security, and approvals moving without a manual task between every handoff. about.gitlab.com/blog/gitlab-agent-orchestration/
-
🦊 GitLab
@gitlab
Not every vulnerability needs your attention. 🔐
This Cybersecurity Awareness Month, find out how GitLab Duo helps cut through false positives, prioritize real security risks, and accelerate fixes. -
🦊 GitLab
@gitlab
Dependency Firewall checks packages against your policies and blocks those that don’t meet them. You can see why right in the build output.
Watch the full GitLab Transcend demo to see it in action and see what it stopped. about.gitlab.com/events/transcend/virtual/This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
For enterprises with many top-level groups, GitLab now aggregates vulnerabilities and a single risk score across your entire organization.
Learn more. about.gitlab.com/blog/security-risk-in-one-dashboard/ -
🦊 GitLab
@gitlab
“There’s no room for a defender’s mindset in AI security.”
GitLab CISO Chaim Mazal on why security teams need to think like attackers and how to start: thenewstack.io/ai-security-attacker-mindset/ -
🦊 GitLab
@gitlab
How do you build spacecraft faster without cutting corners on oversight and security?
Intuitive Machines is using GitLab to build more efficiently and move faster. Brian Butcher, Software Group Lead, and Dami Alugo, Lead DevSecOps Engineer, share how AI is changing spacecraft development and where it could take the industry next.
Listen to the full episode: federalnewsnetwork.com/podcast/the-space-hour-podcast/how… -
🦊 GitLab
@gitlab
Big build energy is contagious. Keeping tabs on what everyone’s building? That needs a plan.
Michael Winslow talks giving people room to experiment, tracking what they build, and why a confident AI still needs a risk check.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Deleted a secret from your code? That doesn't mean it's gone. 🔐
This Cybersecurity Awareness Month, find out how GitLab helps prevent exposed secrets, detect leaks, and keep your credentials secure. about.gitlab.com/blog/secrets-manager-ga/This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Ever had a build fail because a public repository went down? Been there. Never doing that again with Artifact Central caching our packages 🥳
Watch the full demo here to see how pulling the same packages took less than half the time 👉 about.gitlab.com/blog/transcend-artifact-central/This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
A little less pressure to keep up. A little more focus on moving forward together 🚀
@Steve_Yegge shares why AI adoption needs a human pace and how AI can help teams find a shared language.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
AI agents are sending more and more code into review queues built for human-paced work.
A coding assistant can speed up code writing, but it can’t show you whether review, security checks, and release approvals can keep pace with all that extra code.
AI-native engineering is the practice of intentionally designing the engineering process so people and agents each do what they are best suited to. It starts with identifying delivery bottlenecks, then deciding how much autonomy agents should have and how to maintain control as you scale.
Read the blog to learn more: about.gitlab.com/blog/redesign-how-your-team-ships-softwa… -
🦊 GitLab
@gitlab
Get every merge request in front of the right reviewer, faster.
Most organizations do not lack capable reviewers. They lack a consistent way to get each merge request in front of the right one. With Recommend Reviewers Flow, now generally available in GitLab 19.5, GitLab recommends the best individual reviewer when you create a merge request, based on workload, time zone, availability, and expertise defined by approval rules and CODEOWNERS. The flow explains why it chose each reviewer and lets you assign them in one click, so reviews start sooner and review load spreads across every qualified engineer.
Read the blog: about.gitlab.com/blog/recommend-reviewers-flow/ -
🦊 GitLab
@gitlab
GitLab Secrets Manager is now generally available.
Built on OpenBao, it keeps build-time and runtime secrets under the permissions and audit trail that govern your code. Each secret reaches only the jobs that declare it and fall within its scope.
Learn more.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
GitLab has joined the Open Secure AI Alliance, hosted by the @LinuxFoundation, to support open approaches to AI security and responsible AI.
We’re looking forward to sharing the open-source tools and transparent practices we’re building to help teams use AI with greater choice, control, and trust.
Read more from our CISO Chaim Mazal: about.gitlab.com/blog/gitlab-joins-open-secure-ai-alliance/ -
🦊 GitLab
@gitlab
The GitLab MCP server is now generally available.
Any MCP-compatible agent can run core GitLab workflows from the client your team already works in, with dozens of tools across code, merge requests, work items, and pipelines. Each action runs under your existing GitLab permissions.
Read the blog to learn more. about.gitlab.com/blog/mcp-server-ga/This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
A walking red flag in your workflow? An agent that acts first and explains later 🚩
Put it back in the loop. Some decisions still need your sign-off. -
🦊 GitLab
@gitlab
Speed you can trust, all the way to production.
With GitLab 19.5, you connect any MCP-compatible agent to GitLab from the client your team already uses. You keep secrets under your existing permissions and get every merge request to the right reviewer, faster.
Learn more about the 19.5 release: about.gitlab.com/whats-new -
🦊 GitLab
@gitlab
Gemini 4 Argon is now available on GitLab Duo Agent Platform.
As AI models take on longer, multi-step work, teams need results they can trust. In internal evaluations, Argon completed 93.3% of GitLab’s software engineering benchmark tasks. Your engineers can delegate the work with confidence and spend their time reviewing the result.
Read the blog: about.gitlab.com/blog/gitlab-google-gemini-argon/ -
🦊 GitLab
@gitlab
Commercial space companies are utilizing new AI tech to build faster and more efficiently. 🚀
Brian Butcher and Dami Alugo of Intuitive Machines talk about how they are using GitLab to get there, how AI is changing the way spacecraft are developed, and where the technology could go next.
Listen to the full episode: federalnewsnetwork.com/podcast/the-space-hour-podcast/how… -
🦊 GitLab
@gitlab
As AI agents take on more software development, source control needs to keep pace with the scale and concurrency of agentic workloads.
That’s why GitLab has been developing next-generation SCM for thousands of concurrent agents working against large repositories. We announced this work at GitLab Transcend in June, joined on stage by Nick G. from Anthropic’s source control team. Anthropic’s post today shows how quickly these demands are growing.
Read more on our blog: about.gitlab.com/blog/scaling-git-for-the-agentic-softwar… -
🦊 GitLab
@gitlab
Gemini 4 Argon from @GoogleDeepMind is now available on GitLab Duo Agent Platform, across all tiers and deployment models.
Stuart Moncada, VP of Product Management at GitLab, shared why this matters for teams building with AI:
“As software development becomes more agentic, teams need models that can support long-running, multi-step work across all stages of the development lifecycle. Gemini 4 Argon is designed to help organizations bring AI into development, security, and operations while keeping it within established enterprise workflows and controls.”
Google DeepMind
@GoogleDeepMind
Gemini 4 Argon is now globally available.
Built to solve your hardest problems from start to finish, the model brings frontier capabilities across coding, enterprise workflows, and cyber defense.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
We are excited to recognize Dhairya Majmudar, a Level 3 contributor, as this month’s Notable Contributor!
Dhairya contributed to offline transfer and Organizations support for import, so that groups, projects, and their memberships can move between GitLab instances. Learn more here: docs.gitlab.com/releases/19/gitlab-19-5-released/ -
🦊 GitLab
@gitlab
Want to see how GitLab Artifact Central actually works?
Tim Rizzi and Corinne Dent go deep on the architecture, the migration path, and what it means for teams building with AI agents.
Watch the full deep dive, then read more on the blog: about.gitlab.com/blog/transcend-artifact-central/This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
GitLab CEO @bstaples sat down with Darren Wilkes, CTO at COCC, to talk through how his team runs GitLab Duo, where hundreds of agents now carry engineering work from requirement to production with everything traceable back to source.
Watch the conversation:This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
✨ GitLab Transcend limited-edition merch is here!
Transcend is a moment to celebrate, and now we have merch to match.
From iridescent tanuki tees to travel accessories and customizable macropads, you don’t want to miss this drop. Quantities are limited.
Shop the collection.🛍️ transcendpopupshop.com -
🦊 GitLab
@gitlab
Need it fast? Claude Haiku 5.5 is here.
The fastest model in the Claude 5.5 family is now on GitLab Duo Agent Platform, across all tiers and deployment models. Built for high-volume, speed-sensitive workloads.
Try it today. -
🦊 GitLab
@gitlab
Your group chat just entered a hackathon 👀.
AI can write the code. Now show us what happens after.
Build something that makes review, testing, security or deployment faster, safer, or smarter for the Life After Code Hackathon. $45K in prizes are up for grabs.
Entries close October 27. Find your path to production:
gitlab-transcend.devpost.com -
🦊 GitLab
@gitlab
Missed GitLab Transcend? No worries, we've got the highlights. ✨
We made more than a dozen announcements across all four layers of our architecture for agentic software engineering: agent orchestration, data and context, DevOps workflows, and governance and security.
Read the blog to see what shipped and how to turn on the new capabilities: about.gitlab.com/blog/transcend-india-announcements/ -
🦊 GitLab
@gitlab
GitLab Dependency Firewall checks every package against policy before it enters a build. It warns, blocks, or quarantines packages based on rules the organization sets for package age, vulnerability severity, malicious package detection, and license compliance.
One control plane spans source, build, and registry, helping teams trace exposure to affected projects and prioritize remediation in minutes instead of weeks.
Learn more: about.gitlab.com/blog/transcend-dependency-firewall/ -
🦊 GitLab
@gitlab
GitLab Artifact Central lets platform teams assemble the right software the first time. It brings containers and packages into one control plane alongside source code management and CI pipelines.
Teams can set policy once at the organization level, instantly answer what was published, and realize up to 50% lower total cost of ownership compared with alternative tooling. Learn more: about.gitlab.com/blog/transcend-artifact-central/This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
🚨 Starting in 10 minutes: The Developer Show - Transcend Edition. Don't miss it. Join the livestream. x.com/i/broadcasts/1MJgNbqkLaMGL
-
🦊 GitLab
@gitlab
The Developer Show -Transcend Edition x.com/i/broadcasts/1jGXgBQbZBvKZ
-
🦊 GitLab
@gitlab
Every enterprise already runs a software factory, but most organizations have built theirs from separate tools for coding, planning, source code control, CI/CD, security, artifact management, and deployment.
As AI agents accelerate software development, that fragmentation creates more handoffs, breaks context, and makes it harder to trace changes, govern what reaches production, or measure the impact of AI investments.
GitLab is announcing the foundation for a governed software factory to help organizations optimize software development so they can move from intent to production with greater speed, governance, and visibility.
See what’s new 🧵Post not available here, view on X
🦊 GitLab
@gitlab
Secure what enters the build.
🦊 GitLab
@gitlab
Shorten the path from detection to verified remediation.
🦊 GitLab
@gitlab
Make AI context, cost, and impact visible.
🦊 GitLab
@gitlab
See what’s new: about.gitlab.com/whats-new/
-
🦊 GitLab
@gitlab
-
🦊 GitLab
@gitlab
Today is the day! Join GitLab Transcend for a keynote with @bstaples, alongside GitLab leaders and customer speakers from Barclays and Anthropic. Then stay tuned for an Industry Roundtable hosted by Gene Kim, Founder of IT Revolution, live from the Enterprise AI Summit.
Watch the livestream: about.gitlab.com/events/transcend/virtual/ -
🦊 GitLab
@gitlab
-
🦊 GitLab
@gitlab
Your agent writes code faster than your team can review, test, secure, and ship it. Congrats, you now have a notification problem 🔔
Tomorrow at GitLab Transcend, we're showing how to get the rest of the lifecycle moving at agent speed, so today's Slack doesn't become every day's Slack.
Register for the livestream here. about.gitlab.com/events/transcend/virtual -
🦊 GitLab
@gitlab
October’s Monday Merge is here, and this month we’re talking trust, control, and the next phase of agentic AI.
We’ve spent a lot of time asking what AI agents can do. Write code. Review it. Fix vulnerabilities. Trigger pipelines. Open merge requests. Work toward increasingly complex goals. But as agents gain more autonomy, there’s another question becoming just as important: What should they be allowed to do?
Dive into this and more with Fatima Sarah Khalid in the latest edition of Monday Merge.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
The real battle with writing code with AI is everything that happens after.
Think you can automate the post-code lifecycle? We’re throwing down $45K in prizes 💰
Claim your spot today 👉🏻 gitlab-transcend.devpost.com -
🦊 GitLab reposted
Hookdeck
@Hookdeck
📹 Webhooks by Example, Episode 2
@gitlab webhooks driving a virtual pet for repo health. Colleen Lake walks through event triggers, signing tokens, and emoji events, then has GitLab Duo ship the emoji handler.
Episode 2 ↓
youtu.be/hJJb8LdS0iE -
🦊 GitLab
@gitlab
Plot twist: the maze has an exit. 🌀
See a clearer path forward in the era of agentic AI at GitLab Transcend.
Register for the October 6 livestream here 👇
about.gitlab.com/events/transcend/virtual/ -
🦊 GitLab
@gitlab
"Just give the agent full access, it's faster." 😬
That is, until an agent acts on partial context with no governance and no trail back.
GitLab pairs speed with the control, ensuring every action is traceable and every decision grounded in context. about.gitlab.com/ai-accountability/speed-with-control/ -
🦊 GitLab
@gitlab
AI code agents that guess from similar-looking code can miss whats actually broken.
GitLab Orbit builds one context graph across your code, pipelines, deployments and production so your agent follows real relationships instead. Plus, it works over MCP with any agent you're using.
Watch the demo to learn more, then try it for yourself. about.gitlab.com/demo-hub/This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Learn how Flow Registry, a component-based framework that compiles YAML configurations into fully functional LangGraph flows, helped improve scalability and more. about.gitlab.com/blog/how-gitlab-reduced-code-per-agentic…
-
🦊 GitLab
@gitlab
One week until GitLab Transcend. Live demos on keeping reviews, pipelines, and security checks moving at the pace of agentic AI.
Register for the October 6 livestream here 👇
about.gitlab.com/events/transcend/virtual/ -
🦊 GitLab
@gitlab
.@AnthropicAI Claude Sonnet 5.5 is now live on GitLab Duo Agent Platform, across all tiers and deployment models.
It beats Sonnet 5 on every axis. Try it today. -
🦊 GitLab
@gitlab
Every agent has a job. GitLab keeps every agent's work checked against your standards before it ships.
GitLab gives them the context, guardrails, and platform to work efficiently at every stage, not just the one you're currently watching. Learn more. about.gitlab.com/ai-accountability/speed-with-control/ -
🦊 GitLab
@gitlab
How do you secure an agentic SDLC?
GitLab CISO Chaim Mazal joined the Zero Signal Podcast to discuss identity security, why corporate security is now a big industry challenge, and which fundamentals matter most.
Listen to the full episode. zerosignalpodcast.com/p/chaim-mazal-48 -
🦊 GitLab
@gitlab
Coding agents are speeding up development. Your reviews, security, and release cycles still have to keep pace.
Join us at GitLab Transcend on October 6th to see what it takes to carry the speed of agentic AI across the full software lifecycle.
Register now. -
🦊 GitLab
@gitlab
Software quality conversations can feel abstract. Not at @CSL.
GitLab CEO @bstaples talked with Sri Ramachandran, who leads SDLC platforms at CSL, a biotech company building therapies for rare and serious diseases. For his team, software reliability isn't optional, it's tied to whether a therapy reaches a patient.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Carrefour cut time to market in half with GitLab.
That's not all. Release cadence went from monthly to daily, incidents dropped 25%, and developer onboarding went from two to four days down to half a day. See how they built a software factory for scale. x.com/i/article/2103127028287295488 -
🦊 GitLab
@gitlab
AI agents can clone your entire repo before writing a single line of code, and nothing looks broken. It just doesn't scale.
We're fixing that by addressing how agents access code, how they get context, and how you track what they did.
Try it for yourself.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
-
🦊 GitLab
@gitlab
.@AnthropicAI Claude Opus 5.5 is now live on GitLab Duo Agent Platform, across all tiers and deployment models.
Try it now. -
🦊 GitLab
@gitlab
Thank you to those who contribute to GitLab and help make meaningful improvements to the platform.
✨ Check out the release notes to see contributor highlights in 19.4: docs.gitlab.com/releases/19/gitlab-19-4-released/ 🚀 -
🦊 GitLab
@gitlab
"It's not what happens, it's how you deal with it."
GitLab CISO Chaim Mazal joined the Lead the Team podcast to share his thoughts on how great leaders stay composed under pressure, build resilient teams, and respond when things don’t go according to plan. Listen to the full episode. youtu.be/crWdvsiMUFk -
🦊 GitLab
@gitlab
GitLab Transcend is just 2 weeks out, streaming live from Bangalore Oct 6.
Join us to see how review, pipelines, artifacts, security checks, and deployments keep pace with agentic coding.
Register today. about.gitlab.com/events/transcend/virtual/This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
A long-running refactor needs a large context window and deep reasoning. Routine, high-volume work needs speed and cost efficiency. One model rarely delivers both, so most teams standardize on one and give up ground on the other task type.
Three hosted open weight models now join the frontier models already available in GitLab Duo Agent Platform, so your team can match cost efficiency and performance to each task.
Learn more in the blog. about.gitlab.com/blog/optimize-with-open-weight-models/This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
A subscription cap keeps total spend within budget, it can’t tell you how much AI was used by individual teams.
GitLab Credits usage visibility, now generally available, gives you per-user caps, per-team showback, and exports down to the billable event, so every credit traces back to who spent it and on what.
Learn more in the blog. about.gitlab.com/blog/new-usage-caps-2026/ -
🦊 GitLab
@gitlab
Advanced AI models are giving engineering teams the ability to build software that can test, inspect, and improve itself, with verified remediation at machine speed.
GitLab CISO Chaim Mazal explains why building the right operating standard can turn that advantage into more trustworthy software: about.gitlab.com/blog/securing-the-software-factory-at-ma… -
🦊 GitLab
@gitlab
The more an agent can do, the more a platform team has to think about what it should be allowed to do. That's a governance problem that usually gets solved by restricting access. GitLab 19.4 introduces a solution.
New MCP server tools let any agent run pipelines, open MRs, and triage vulnerabilities in GitLab, governed by the same rules for every agent, internal or third-party. Now in beta.
Read the blog to learn more. about.gitlab.com/blog/new-mcp-tools-for-automation/This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Turn-by-turn chat makes you the continue button, reading, redirecting, and repeating until a task is done.
GitLab Duo CLI's new /goal command takes the whole objective instead. Describe the outcome, walk away, and come back to a result and a record of what was verified.
Learn more. about.gitlab.com/blog/gitlab-duo-cli-drives-automation/ -
🦊 GitLab
@gitlab
GitLab 19.4 is here, bringing new agentic automation built for cost efficiency at scale.. From the terminal to any MCP client, platform owners get the controls to extend it with confidence.
Here are the key changes in this release 🧵:
🦊 GitLab
@gitlab
Handing an agent an open-ended objective has meant trusting it to know when it's done. The new /goal command in GitLab Duo CLI (public beta) verifies its own work.
It automates the objective until it's done or reports what it couldn't resolve. A separate model verifies the work at each step, judging when the goal is met or the iteration limit is hit, all under your project's existing guardrails.
🦊 GitLab
@gitlab
No single model fits every task. GitLab Duo Agent Platform now offers three hosted open weight models (Kimi K3, MiniMax M3, GLM 5.3) alongside frontier models, getting up to 4x more calls per GitLab Credit than many comparable frontier models and giving teams more model options to match cost to task complexity.
Post not available here, view on X
🦊 GitLab
@gitlab
Learn more about the 19.4 release: about.gitlab.com/whats-new/
🦊 GitLab
@gitlab
Ready to dive deeper? The blogs are linked below:
about.gitlab.com/blog/gitlab-duo-cli-drives-automation/
about.gitlab.com/blog/new-mcp-tools-for-automation/
about.gitlab.com/blog/new-usage-caps-2026/
about.gitlab.com/blog/optimize-with-open-weight-models/ -
🦊 GitLab
@gitlab
Small team. Big shipping energy. 👀
For @Boundeal, GitLab doesn’t just help its lean team ship like a much bigger one. It’s also the backbone of a broader control environment built to support enterprise customers and certifications like SOC 2 and ISO.
See how Boundeal built that foundation from day one in the GitLab Startup Program.
👉 about.gitlab.com/customers/boundeal/ -
🦊 GitLab
@gitlab
Your AI agent writes code. Just never the way your project actually does it.
GitLab's Duo Agent Platform fixes this with Skills, one file your agent reads every time so it just knows your rules. No repeating yourself every prompt. about.gitlab.com/demo-hub/
🎥 @ania_kubow -
🦊 GitLab
@gitlab
Agents can write code, review changes, and troubleshoot pipelines, but the handoffs between each step still take manual coordination.
Join us at GitLab Transcend, virtual, to see what we're building to reduce the bottleneck between writing code and shipping it.
Register free. Bonus: unlock the Enterprise AI Summit livestream, October 7-8, a $1,600 value. about.gitlab.com/events/transcend/virtual/ -
🦊 GitLab
@gitlab
AI adoption isn't the goal, fluency is. Our CIO Manu Narayan on why enterprises need a hub and spoke model, with AI engineers embedded inside teams, to actually close the gap. Read more. thenewstack.io/ai-fluency-operating-model/
-
🦊 GitLab
@gitlab
Git's storage layer hasn't changed since 2005. The number of agents hammering Git repos today has.
GitLab's Patrick Steinhardt is talking about rebuilding it at Git Merge 2026 in Lisbon on the upstream effort to rebuild Git's storage layer and make it pluggable, unlocking new headroom for scale and agentic workloads.
Learn more. git-merge.comThis media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Your coding agent just made a decision based on last week's version of your codebase. It looked confident. It was wrong.
With GitLab Orbit, agents work from a context graph across the full SDLC. Fewer hallucinations, faster answers, and decisions grounded in what's true.
So which is the bigger risk for your team, an agent moving fast on bad context, or a team moving slow because nobody trusts the context it has? about.gitlab.com/gitlab-orbit/ -
🦊 GitLab
@gitlab
This month's Monday Merge: a supply chain wake up call, GitLab 19.3's Flow Creator Agent, and why your AI needs a trust boundary too.
This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Your coding agents just got faster. Did your reviews, security, and release cycles keep up?
Join GitLab Transcend on October 6 for live demos on scaling agentic AI across the full software lifecycle, from commit to production. about.gitlab.com/events/transcend/virtual/ -
🦊 GitLab
@gitlab
Under the Cyber Resilience Act, manufacturers have 24 hours to report an actively exploited vulnerability in their product. See how GitLab helps you answer fast.
about.gitlab.com/blog/cyber-resilience-act-reporting-dead… -
🦊 GitLab
@gitlab
Compliance doesn't need to live in spreadsheets, screenshots, and audit-week dread.
GitLab's custom compliance frameworks let you define controls once and continuously verify them, no manual chasing required.
See how to stand up SOC2 in minutes, plus what's next for AI compliance templates. about.gitlab.com/blog/quick-compliance-with-compliance-fr…This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Coding agents are stuck choosing between RAG or knowledge graphs. Both come with tradeoffs.
GitLab connected the whole pipeline instead, one live graph, updated on every push.
Try it with MCP in Claude Code, Codex, or GitLab directly. about.gitlab.com/demo-hub/This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
GPT-6 Astra from @OpenAI is now live on GitLab Duo Agent Platform, across all tiers and deployment models.
Astra completed every task in GitLab’s benchmark evaluation, finishing runs about 40% faster while using 40% fewer tokens. These efficiency gains can save time and AI budget. about.gitlab.com/blog/gpt6-astra-on-gitlab/ -
🦊 GitLab
@gitlab
Two answers in this puzzle say everything about how we think about AI: speed and control. AI made code generation abundant, but delivery didn't get easier. See how GitLab does both at once. about.gitlab.com/why-gitlab/
Can you solve the rest? -
🦊 GitLab
@gitlab
Turns out you don't need the most expensive AI model running on every case.
GitLab's security ops team built a tiered funnel that filters out obvious abuse before it ever reaches an LLM, saving serious budget while keeping accuracy intact. According to GitLab's Matt Coons, sometimes the smartest move is deciding what shouldn't reach the model at all.
Learn more.thenewstack.io/minimize-ai-security-spend/ -
🦊 GitLab
@gitlab
The cosmos has a commit for you. ✨
Today's forecast for GitLab Duo's Planner Agent: your roadmap is full of ambitious possibilities, but not every task needs doing today.
The stars advise you to plan with intent and act with purpose. Let Planner help you prioritize, break down initiatives, and draft status updates so you're working on what actually matters.
Read your full horoscope and learn what Planner can do → docs.gitlab.com/user/duo_agent_platform/agents/foundation… -
🦊 GitLab
@gitlab
The GitLab UI has been getting quieter all year. Here's why. about.gitlab.com/blog/making-room-for-whats-next-in-the-g…
Reduced color, neutral controls, updated theming, and a new bloom effect that draws your eye to GitLab Duo when it needs you. -
🦊 GitLab
@gitlab
Gemini 3.8 Flash from Google DeepMind is now live on GitLab Duo Agent Platform, across all tiers and deployment models.
-
🦊 GitLab
@gitlab
AI tool access ≠ AI fluency.
Our CIO and Chief People Officer share how they partner so GitLab builds AI-fluent engineering teams and internal AI use drives the right business outcomes. about.gitlab.com/blog/how-gitlab-fosters-ai-fluent-teams/ -
🦊 GitLab
@gitlab
Your AI agent writes code in seconds, then you spend the night fixing a bug you didn't write. It's not the AI's fault, it's the tools: built for one human and one repo, not for how agents actually move.
GitLab brings the context, guardrails, and visibility agents need to ship safely at their own speed. See how: about.gitlab.com/demo-hub/duo-agent-platform/ -
🦊 GitLab
@gitlab
We reported our Q2 fiscal year 2027 results on September 1, 2026. You can learn more in our full earnings report below:
ir.gitlab.com/news/news-details/2026/GitLab-Reports-Secon… -
🦊 GitLab
@gitlab
Claude Fable 5.1 from @AnthropicAI is now live on GitLab Duo Agent Platform, across all tiers and deployment models.
-
🦊 GitLab
@gitlab
Automate AWS infrastructure and app delivery end to end: OpenTofu provisions EKS, GitLab CI/CD builds and packages, Argo CD deploys via GitOps.
about.gitlab.com/blog/gitlab-as-your-aws-control-plane/ -
🦊 GitLab
@gitlab
Hackathons aren’t just about coding fast. They’re about building better developers.
Put yourself to the test, take on the challenge, and see how far you can push your ideas, your skills, and the way you build.
You’ll walk away with more than just a finished project ⚡️ -
🦊 GitLab
@gitlab
Preventing Rogue Agents: Building Agents You Can Trust x.com/i/broadcasts/1jxXgBDbWAyJZ
-
🦊 GitLab
@gitlab
Your AI agent has never seen your codebase fail before, but your senior engineers have. GitLab Orbit closes that gap with a live graph connecting your code, tickets, pipelines, deployments, and production alerts, scanning every past incident to surface the exact pattern the moment an agent hits a failure.
Demo Orbit on the GitLab Demo Hub today. ➡️ about.gitlab.com/demo-hub/duo-agent-platform/This media couldn't be displayed. See it on the original post.
🦊 GitLab
@gitlab
📽️: @pvergadia #ad
-
🦊 GitLab
@gitlab
Stop over-provisioning for CI spikes and under-provisioning to save on infrastructure costs. Hosted Runners for GitLab Dedicated gives you isolated, autoscaling runner capacity in the same region as your GitLab Dedicated instance, fully managed by GitLab. about.gitlab.com/blog/hosted-runners-for-gitlab-dedicated/
This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
"Being a first-level contributor... is key to our success." GitLab CISO Chaim Mazal on why security teams need to code, iterate, and build guardrails alongside engineering, not after it.
www.itpro.com/software/development/ai-assisted-software-d… -
🦊 GitLab reposted
Bill Staples
@bstaples
Anthropic published The AI-Native SDLC Playbook last week saying, “code is no longer the bottleneck.” I agree.
All year long, I’ve been asking myself the questions that naturally follow:
What becomes the bottleneck next?
If models can generate code faster and faster, what actually determines whether a change is good enough to ship?
If teams are going to use multiple models and agents, what has to remain durable underneath them?
And as agents become more autonomous, how do people understand and steer what hundreds of them are doing at once?
My view: faster code generation is already exposing the next constraints. Solving them is where the next wave of value in agentic engineering will come from.
Verification, context, execution infrastructure and governance start to matter more than model choice.
Put differently: when implementation becomes abundant, trust becomes scarce.
I wrote down my view of what comes next: When Code Is Abundant
about.gitlab.com/blog/when-code-is-abundant/ -
🦊 GitLab
@gitlab
As AI accelerates both development and exploitation, GitLab 19.3 brings automation that scales to meet it.
Teams can now deliver secrets wherever they're used, inside CI or out, turn process knowledge into automation without learning a schema, clear their vulnerability backlog in one action, share agents and flows across their organization without making them public, and inject scoped secrets directly into the CI jobs that need them.
✨ What's new in 19.3:
- GitLab Secrets Manager, now in limited availability
- Flow Creator Agent, now in general availability
- Bulk SAST False Positive Detection and Agentic SAST Vulnerability Resolution, now in beta
- Restricted visibility for custom agents and flows, now in general availability
…and more improvements!
Read the full 19.3 release notes: docs.gitlab.com/releases/19/gitlab-19-3-released/ 🚀 -
🦊 GitLab
@gitlab
Your security backlog is growing faster than your team can triage it. GitLab 19.3 extends bulk False Positive Detection and Agentic Vulnerability Resolution to your production vulnerability backlog.
Select multiple vulnerabilities and clear them in one bulk action instead of one at a time.
Remediate your backlog with GitLab today. about.gitlab.com/blog/gitlab-scales-remediation/This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Stop waiting on someone else to write your automation.
Flow Creator turns a plain language description into a complete, runnable flow, with no Flow Registry schema experience required. Missing a detail like target project or approval steps? It asks before it builds.
Try Flow Creator in GitLab Duo Agent Platform today. about.gitlab.com/blog/flow-creator-agent/This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Your AI Gateway just moved into the same trust boundary as your code. GitLab Dedicated customers can now run the Duo Agent Platform AI Gateway in-region, inside their own single-tenant environment. Bring your own models. Keep your compliance posture intact.
-
🦊 GitLab
@gitlab
Regulated and data-sensitive enterprises can now run agentic AI in their own single tenant environment, with GitLab Dedicated AI Gateway. Alongside it, GitLab 19.3 ships with automation and remediation built to scale for everyone else.
Here's what's new this month🧵:Post not available here, view on X
🦊 GitLab
@gitlab
Secrets scattered across a separate permission model create risk teams have to manage on top of the CI job itself.
GitLab Secrets Manager, now in limited availability, injects each secret into the CI job that needs it, scoped to that job's environment and branch, with no separate permission model to maintain.
🦊 GitLab
@gitlab
The people who understand a workflow best aren't always the people who know a YAML schema. That gap has kept automation out of reach for a lot of process knowledge.
Flow Creator Agent lets anyone describe an automation in plain English and get back a complete, runnable flow definition, ready to register from the AI Catalog.Post not available here, view on X
🦊 GitLab
@gitlab
Restricted visibility for custom agents and flows, now generally available, lets teams roll agents and flows out across an entire top-level group without exposing them publicly. Internal logic stays inside your organization instead of getting rebuilt project by project.
🦊 GitLab
@gitlab
Learn more about everything that shipped this month: about.gitlab.com/whats-new/
-
🦊 GitLab
@gitlab
Lessons from iterating on AI directives, building a memory system, and discovering what AI still can't replace in software development.
about.gitlab.com/blog/building-an-ai-dev-workflow/ -
🦊 GitLab
@gitlab
GitLab Duo CLI brings agentic AI directly into your terminal.
From troubleshooting pipelines and planning changes to custom workflows, headless automation and governance controls.
Here are 7 things you can do with Duo CLI.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Everyone's got a to-do list. But does your AI agent have a do-not-do list like ours does? 🫣
Responsible AI isn't always about doing more. Sometimes, not doing it is the job. -
🦊 GitLab
@gitlab
Learn how GitLab's improved Scope+Offset fingerprinting keeps vulnerability tracking stable across comments, blank lines, and reformatting. about.gitlab.com/blog/improved-scope-offset-fingerprinting/
-
🦊 GitLab
@gitlab
Mercury is in retrograde but your milestone data is not thanks to the data analyst agent.
This is your sign to ask for the table, the trend, and the truth. Link to the full guide is in the comments. -
🦊 GitLab
@gitlab
Gemini 3.7 Flash is now available directly through GitLab Duo Agent Platform. Try it out today!
-
🦊 GitLab
@gitlab
Stuck in an evaluation with no way out, an AI agent escaped in an hour through the one service on its allowlist. Here's the gap that opened. about.gitlab.com/blog/ai-agent-sandbox/
-
🦊 GitLab
@gitlab
We just launched the GitLab Platform Walkthrough Demo Hub, three tracks, one goal, showing you GitLab in action.
Which one would you explore first? 👇
🔵 Agent Orchestration (Duo Agent Platform)
🔵 Security & Governance
🔵 Workflow Execution (DevSecOps)
Vote below, then try it yourself. about.gitlab.com/demo-hub/ -
🦊 GitLab
@gitlab
Federal software used to be bespoke, one application at a time, and it showed. Slow. Unpredictable.
The fix is the software factory, built around federal security guidelines from day one so teams ship safer software faster. On this episode of the Federal Tech Podcast, GitLab's Jorge Lopez breaks down why most DevSecOps gaps come down to people, not technology, and why monitoring is the difference between catching a problem and finding out after the damage is done.
Listen to the full conversation
www.youtube.com/watch?v=asJhiEZ9wSU -
🦊 GitLab
@gitlab
Why wait for us to build it when you can build it yourself? 🎉
GitLab Custom Flows give you the flexibility to create workflows that fit the way your team actually works. Set the trigger, build the flow, and let GitLab take it from there.
See it in action in the full demo 👉 -
🦊 GitLab
@gitlab
The first commercial Moon landing made history, and now @Int_Machines is building the software behind every mission that follows.
With GitLab, they have reached four times faster deployments, three times more CI pipeline usage, and two times AI adoption, because when the stakes are this high, every deployment matters.
Read the story. about.gitlab.com/customers/intuitive-machines/ -
🦊 GitLab
@gitlab
✈️ AI Agent Pre-Flight Checklist
A practical checklist for shipping AI with speed and control.
Before your AI agent is cleared for takeoff, run through this thread. Save it for your next rollout. 🧵Post not available here, view on X
🦊 GitLab
@gitlab
Can it only access what it needs?
☑️ Repository scope
☑️ Branch restrictions
☑️ Secrets management
☑️ Environment access
Just because it can see something doesn't mean it should.
🦊 GitLab
@gitlab
Guardrails. Who approves changes?
☑️ Merge request approvals
☑️ Protected branches
☑️ Required reviewers
☑️ Policy enforcement
AI can write code. Humans should still decide what ships.Post not available here, view on X
🦊 GitLab
@gitlab
Governance. Have you planned for failure?
☑️ Rollback process
☑️ Ownership
☑️ Monitoring
☑️ Incident response
The best AI rollout includes a plan for when things go wrong.
🦊 GitLab
@gitlab
Build AI agents that follow your workflows, ask before making changes, and keep every action auditable.
That's the standard for AI with control, not just speed.
Ready to put your agent through this checklist? Learn more about GitLab Duo Agent Platform about.gitlab.com/gitlab-duo-agent-platform/ -
🦊 GitLab
@gitlab
Turn governance on. That’s it. Go do it.
Okay, now you should also get the visibility and control to govern what your AI agents generate, review, secure, and deploy.
Flip the switch and ship with authority: about.gitlab.com/ai-accountability/speed-with-control/ -
🦊 GitLab
@gitlab
An agent just committed code to your repo. Quick question: Who approved it before it shipped?
With Claude + GitLab, Claude can catch any vulnerabilities in the session and GitLab can ensure the agent can't approve its own merge.
With that in mind, what's the bigger risk for your team right now, an agent approving its own work, or no audit trail once the session ends? -
🦊 GitLab
@gitlab
AI agents can write, push, and deploy without human review at each step. Learn a practical framework for controlling access, permissions, and audit trails.
about.gitlab.com/blog/govern-agentic-ai-mcps-code-assista… -
🦊 GitLab
@gitlab
🔮 The stars favor agents who know their scope.
With the GitLab Duo Agent Platform, the Security Analyst Agent works inside defined permissions and clear approval paths, so it's ready for whatever threats are looming in the atmosphere without ever overstepping its role.✨ -
🦊 GitLab
@gitlab
Ever scroll past a feature you didn't know existed? That's what the Feature Library fixes.
It's a searchable catalog of everything available in your project, with descriptions, tier info, and one click to pin anything to your sidebar. Rolling out to gitlab.com now, starting with a small percentage of customers and expanding over the coming weeks. Look for "More features" in your left sidebar, or press \ anywhere to open it. -
🦊 GitLab
@gitlab
Claude Security catches vulnerabilities inside a coding session. GitLab picks up from there, scanning, enforcing policy, and producing audit evidence for the software lifecycle. about.gitlab.com/blog/claude-security-and-gitlab/
-
🦊 GitLab
@gitlab
This month's Monday Merge: 400% ROI, GitLab 19.2, and why governance is quietly becoming the real AI differentiator.
This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
What if assignment just happened, the moment work came in, with no one needing to click a thing?
GitLab Duo Agent Platform's "Work item created" trigger fires the second a new issue lands, one agent checking workload across the team through GitLab Orbit, and a second agent handing the item straight to the person with the most capacity.
See the full flow build and fire step by step in the video.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
💾Are any of these your GitLab runner's greatest hits?
"no space left on device"
"reference is not a tree"
"forbidden"
Because it WILL happen again. Here’s how to fix it 👇🏻Post not available here, view on X
🦊 GitLab
@gitlab
Somewhere in your pipeline right now, a job has started, hasn't finished, and isn't planning to.
Find the dead zone in your logs, restart Docker, then gitlab-runner restart.
🦊 GitLab
@gitlab
Congrats, you just solved 80% of your runner problems!!🎉🎉🎉
Tags, connectivity, executor - that's really all it ever comes down to. www.youtube.com/watch?v=QEq357drrCo -
🦊 GitLab
@gitlab
-
🦊 GitLab
@gitlab
POV: Your AI agent is about to ship code with zero adult supervision.
What’s in the speech bubble? Wrong answers only 👇 -
🦊 GitLab
@gitlab
Open weight models let teams control cost, deployment, and data residency, even in air-gapped environments. We think that choice deserves smart, targeted safeguards, not blanket restrictions.
Why we signed: about.gitlab.com/blog/open-weight-model-letter/ -
🦊 GitLab
@gitlab
Your flow just got reflexes 💪🏻 No more manual triggers. No more missed conflicts.
Duo Flows fire automatically on real GitLab events - starting with merge conflicts, with 3 more triggers rolling out too. -
🦊 GitLab reposted
Bill Staples
@bstaples
@gitlab also signed the Open Weights and American AI Leadership letter.
For most companies, software is core IP. How you manage it, and how you protect your business and customers against security, privacy, and competitive threats, is one of the most strategic decisions a company makes. That decision shouldn't be locked to one cloud or one model vendor.
GitLab is the only platform that's genuinely cloud neutral and model neutral. You decide where your code lives. You decide which model does the work.
That choice only holds up if the model market stays open. I think the future is a mix of models matched to the task, each tuned for the best price and performance for the customer. Open models keep that market honest. They drive real competition on performance and price, and they keep control in the customer's hands.
Jensen Huang
@JensenHuang
For my first post, I’m sharing a letter @NVIDIA signed on why open models matter.
AI will transform every industry, power every company, and be built by every country.
Open models strengthen safety and cybersecurity, accelerate innovation and diffusion, and enable sovereignty.
The world needs both frontier closed models and frontier open models.
images.nvidia.com/pdf/Open-Weights-and-American-AI-Leader… -
🦊 GitLab
@gitlab
Claude Opus 5 is live on GitLab Duo Agent Platform. A 93.3% resolve rate in our internal benchmark tests translates to fewer re-prompts and more trusted agent outputs. This model is built for efficiency while handling harder, complex work.
Read more about it here: -
🦊 GitLab
@gitlab
Gemini 3.6 Flash is now available directly through GitLab Duo Agent Platform. 3.6 Flash builds on 3.5 Flash for coding, knowledge work, and multimodal tasks. Try it out today!
-
🦊 GitLab
@gitlab
This tutorial starts with a focused tests fix, introduces quality gates, and implements code changes with development lifecycle context, tests, and review evidence. about.gitlab.com/blog/modernize-java-with-cursor-and-gitlab/
-
🦊 GitLab
@gitlab
AI is only as good as the context it's given.
Bastian Stahmer from Mercedes-Benz shared why unlocking siloed data is key to building smarter, more effective agents.
Watch the full session to see how Mercedes-Benz masters agentic engineering: about.gitlab.com/events/transcend/virtual/ -
🦊 GitLab
@gitlab
Autonomous agents shipping code you haven't seen, to environments you can't trace, with decisions you can't explain.
That's not autonomy. That's exposure.
Govern your agents with GitLab: about.gitlab.com/ai-accountability/speed-with-control/ -
🦊 GitLab
@gitlab
In Vegas, the house always has the edge. We're coming to Black Hat to make sure attackers don't have one over you.
Stop by booth #5009 to see how GitLab brings features like security scanning, SBOM visibility, and AI powered remediation directly into the developer workflow, so vulnerabilities get caught and fixed before they ever ship.
Our team will be on the show floor for live demos, technical conversations, and a few surprises we're saving for booth visitors. See you there. -
🦊 GitLab
@gitlab
2x faster is an assist. 20x faster is autonomous. 🏎️
At GitLab Transcend, our CEO Bill Staples shared exactly how we are learning from these bleeding-edge teams and building the solutions they need to stay in control of that speed.
See what autonomous engineering looks like right now. Watch the restream here: about.gitlab.com/events/transcend/virtual/ -
🦊 GitLab
@gitlab
"The AI did it" is not an audit entry.
Amanda Rueda, Staff Product Manager for AI Execution at GitLab, breaks down why the MCP skeptics have a point for solo projects and completely miss it for enterprise scale. Allowlists feel like governance. Structural least privilege actually is.
Read her take on why "it cannot exceed its scope" beats "it follows the rules," every time. thenewstack.io/mcp-enterprise-agent-governance/ -
🦊 GitLab
@gitlab
As AI generates more code, dependencies, and change than developers can keep up with, GitLab 19.2 brings agentic automation to clear that load.
Teams can now use GitLab to fix vulnerable dependencies automatically, catch the application logic flaws that scanners miss, and run agents from the terminal or across automated workflows, so delivery finally moves at the same speed as generation.
✨ What's new in 19.2:
Dependency Scanning Auto-Remediation (public beta)
Security Review Flow (public beta)
GitLab Duo CLI (GA)
Custom Flows (GA)
…and more improvements!
🦊 GitLab
@gitlab
Read the full 19.2 release notes: docs.gitlab.com/releases/19/gitlab-19-2-released/ 🚀
-
🦊 GitLab
@gitlab
Scanners catch code that looks wrong. They miss code that looks right but does the wrong thing for your business, like broken auth checks or race conditions. GitLab Duo Security Review reasons about intent to catch those flaws at MR time, before they ship. Now in public beta.
This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Custom Flows are now GA. Trigger your own automated sequences of GitLab events like a mention or a reviewer being added, no manual steps. about.gitlab.com/blog/multi-step-software-delivery-with-a…
This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
GitLab Duo CLI is now GA. It puts GitLab Duo Agent Platform's agents and agentic flows directly where you work in your terminal. Ask about a failed pipeline from the same terminal it broke in, get a diagnosis and a fix. about.gitlab.com/blog/gitlab-duo-cli-generally-available/
This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
AI is writing more code and pulling in more dependencies, most of which your team never directly chose. GitLab's new Dependency Scanning Auto-Remediation finds the vulnerable package, opens the MR, and if the fix breaks your build, GitLab Duo Agent Platform fixes that too. Nothing merges without review. Now in beta. about.gitlab.com/blog/dependency-scanning-auto-remediation/
This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
The pace of AI generated code isn't slowing down. GitLab 19.2 keeps up with agentic automation that keeps your team ahead of the change instead of buried under it.
Here are the key changes in this release🧵:Post not available here, view on X
🦊 GitLab
@gitlab
AI Audit Event Report, now in beta, records AI-assisted actions as dedicated audit events. Group-level custom instructions for GitLab Duo Code Review let administrators set review behavior across projects at once, and new MCP access controls govern which agents can run and what they can reach.
🦊 GitLab
@gitlab
Learn more about the 19.2 release: about.gitlab.com/whats-new/
🦊 GitLab
@gitlab
Agentic flows: about.gitlab.com/blog/multi-step-software-delivery-with-a…
GitLab Duo Security Review: about.gitlab.com/blog/gitlab-duo-security-review-flow/
GitLab Duo CLI: about.gitlab.com/blog/gitlab-duo-cli-generally-available/
Dependency Scanning Auto-Remediation: about.gitlab.com/blog/dependency-scanning-auto-remediation/ -
🦊 GitLab
@gitlab
Real customers are sharing real results from using GitLab Duo Agent Platform.
The Forrester Consulting Total Economic Impact™ study breaks down the methodology, costs, and measurable impact behind the results.
Get the full study 👉 about.gitlab.com/blog/gitlab-duo-agent-platform-delivers-… -
🦊 GitLab
@gitlab
Bug in production? Ship it 🫵🏻
Broken dependency? Ship it anyway 🫵🏻
Unfinished feature? You guess it... ship it 🫵🏻
Letting unsupervised AI agents run wild on your codebase is a bold strategy. Reclaim control with GitLab.
Learn how. about.gitlab.com/ai-accountability/speed-with-control/ -
🦊 GitLab
@gitlab
Learn how our three-person pod used GitLab Duo Agent platform, along with other AI tools, to successfully migrate the rate limiting system, and what we learned. about.gitlab.com/blog/ai-agents-for-migrating-rate-limiti…
-
🦊 GitLab
@gitlab
Claude Sonnet 5 is the strongest model we have tested yet, resolving more issues while improving quality and efficiency. It's available on GitLab Duo Agent Platform, across all tiers and deployment models. Try it out today!
Read the blog here: www.anthropic.com/news/claude-sonnet-5 -
🦊 GitLab
@gitlab
"Trust me, the agent handled it" probably won't satisfy your auditor.
GitLab AI Governance gives teams visibility into agent actions, tool usage, approvals, and audit trails, so you can move fast without losing control.
Watch the live demo to see it in action. -
🦊 GitLab
@gitlab
Draft to Ready shouldn't require a human to notice.
New in GitLab 19.1: event triggers let you launch AI flows the moment an MR is ready for review. Daniel Helfand shows how to build a code review assigner that finds your best reviewer automatically.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
GPT-5.6 (Sol, Terra, & Luna) is now live in GitLab Duo Agent Platform, giving you another option for your agentic workflows. Try it today.
-
🦊 GitLab
@gitlab
Don’t let AI agents call the shots without you.
With Gitlab, AI works within your rules so you can move fast and stay in control. about.gitlab.com/ai-accountability/speed-with-control/ -
🦊 GitLab
@gitlab
Secure pipelines shouldn't mean slower pipelines 👀
In the latest Dev Snacks, Staff Developer Advocate Itzik Gan-Baruch introduces the new GitLab Secrets Manager and explains why standard CI/CD variables aren't built for sensitive credentials. He shows how native secrets management keeps your workflows seamless while tightening access at the runtime level. -
🦊 GitLab
@gitlab
Looking for the one? We're talking about your workflow, of course 👀
A thread on the GitLab AI agents built to help your team plan, code, and secure with a whole lot more flow 🧵
🦊 GitLab
@gitlab
First up, the agents helping you plan.
🦊 GitLab
@gitlab
Next, an agent to help you feel secure.
🦊 GitLab
@gitlab
Then there's the coding side. Agents that pick up context fast and help your team move through implementation without losing momentum.
🦊 GitLab
@gitlab
Put them together and you get a workflow that finally feels like it's on your side.
Get to know them in the GitLab Duo platform 👉 about.gitlab.com/gitlab-duo-agent-platform/ -
🦊 GitLab
@gitlab
"Speed without control is chaos." GitLab's Jamie Dicken talks to SC Media about the coming wave of AI-driven vulnerabilities, and why knowledge graphs like Orbit are key to giving AI agents the context they need to act safely.
Read more. www.scworld.com/resource/the-context-gap-building-trusted… -
🦊 GitLab
@gitlab
42x faster. That's what next-generation Source Code Management looks like ⚡
Announced at GitLab Transcend in London, our new architecture is built to keep pace with AI-accelerated coding, cutting the waiting so your team can spend more time shipping.
Learn more. -
🦊 GitLab
@gitlab
Learn how GitLab's restricted access feature prevents seat overages, integrates with your identity provider, and keeps license costs predictable. about.gitlab.com/blog/gitlab-restricted-access-improvements/
-
🦊 GitLab
@gitlab
78% of orgs say AI is speeding up code delivery. Only 20% built the governance to match.
The July Monday Merge breaks down our new AI Accountability Report and why GitLab 19.1's One Vulnerability View exists to close that gap. www.linkedin.com/pulse/weve-solved-speed-now-we-need-acco…This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
The best part of agentic AI? You set the agenda. What are you delegating this weekend?
1) Backlog tasks I've been meaning to tackle
2) Test coverage for the code that needs it most
3) MR reviews so Monday starts clean
4) A pipeline cleanup that's been on the list since Q1
Answer in the replies! -
🦊 GitLab
@gitlab
Fable 5 has been redeployed by Anthropic and is again available for customers on gitlab.com. Learn more here: about.gitlab.com/blog/mythos-class-claude-fable-5-on-gitlab/
🦊 GitLab
@gitlab
. @AnthropicAI's first Mythos-class model is live on GitLab Duo Agent Platform on all tiers and deployment models.
Claude Fable 5 brings long-horizon autonomy, first-shot accuracy, and deeper bug-finding to your agent workflows. Full details on the blog: about.gitlab.com/blog/mythos-class-claude-fable-5-on-gitlab/ -
🦊 GitLab
@gitlab
AI coding agents are only as good as the context they work with. GitLab Orbit gives them the full picture, connecting code, pipeline history, vulnerabilities, deployments, and production signals into a continuously updated lifecycle context graph.
The result: faster, smarter, more cost-effective AI across your entire development workflow. Watch the launch overview.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Claude Sonnet 5 is now live on GitLab Duo Agent Platform, across all tiers and deployment models.
This is the first model in our evaluation suite to handle the full range of our benchmark tasks, up 93.8% from its predecessor Sonnet 4.6, resulting in 8.8% more issues resolved.
Learn more. about.gitlab.com/blog/claude-sonnet-5-on-gitlab/ -
🦊 GitLab
@gitlab
GitLab Transcend is a wrap! 🚀 Leaders from @GoogleCloud, @AWSCloud, and @MercedesBenz joined our CEO @BStaples on stage, and the consensus was clear: we are fully in the AI agent era.
Here are the key takeaways you need to know 👇Post not available here, view on X
🦊 GitLab
@gitlab
📈 The ROI is hitting the metrics. A Forrester study on our Duo Agent Platform found a 400% ROI.
It showed an 80% faster onboarding time for new devs and a 40% jump in fixing vulnerabilities. That’s actual time given back to your teams.
🦊 GitLab
@gitlab
At the end of the day, building in the AI era is unchartered territory for all of us. Our goal isn't just to build faster tools, but to build a more reliable way for engineering teams to scale 💛
Which of these updates are you most excited to try out in your own workflows? -
🦊 GitLab
@gitlab
Security scans shouldn't create more work than they solve.
GitLab Duo automatically detects false positives in secret scanning, delivering AI reasoning and confidence scores directly in your vulnerability report.
Watch the demo.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Let's talk about the reality of using the GitLab Duo Agent Platform (DAP) for DevSecOps.
We put it to the test on 3 highly mechanical, time-consuming tasks in this video: www.youtube.com/watch?v=sFMUes13-Qg
Here is exactly what happened👇Post not available here, view on X
🦊 GitLab
@gitlab
To use GitLab DAP effectively, remember this:
1️⃣ Delegate the mechanical: and over the boring, repetitive tasks.
2️⃣ Hyper-focus your prompts: Define exactly what you want.
3️⃣ Iterate, don't expect perfection: Treat the first output as a draft.
🦊 GitLab
@gitlab
Stop letting the boring work steal your time. Watch our full breakdown of these 3 use cases on YouTube ▶️ www.youtube.com/watch?v=sFMUes13-Qg
Have you tried using AI for your workflows? Share your projects or ask us any questions! 💜 -
🦊 GitLab
@gitlab
GitLab Orbit is now in the @Google Antigravity MCP Store.
Ultimate and Premium users can give agents structured, governed access to GitLab instances directly from their coding platform.
Orbit tests show up to 11x faster responses, 4.5x fewer tokens, and 45x fewer hallucinations. about.gitlab.com/blog/gitlab-orbit-and-google-antigravity/ -
🦊 GitLab
@gitlab
Speed without control isn't progress.
GitLab's Manav Khurana shares his perspective on our newly released AI Accountability Report and what it means for the future of software development. thenewstack.io/gitlab-ai-code-governance/ -
🦊 GitLab
@gitlab
What if the question isn't "how do we introduce AI" but "how do we rebuild work around it?"
GitLab CIO Manu Narayan shares how teams are using agentic AI to focus on what matters most, and why tokenmaxxing is the wrong metric.
Read more: www.computerweekly.com/news/366644996/GitLab-CIO-rejects-…" -
🦊 GitLab
@gitlab
Back at Nasdaq! 🔔 Ian Steward, GitLab's CRO, rings the opening bell on the Nasdaq floor.
From our historic, livestreamed IPO in 2021 to today, one platform for the entire software development lifecycle has never been more essential. -
🦊 GitLab
@gitlab
Are we generating AI code faster than we can control it? 🚨 Get the answer in our AI Accountability Report.
More in the full report: about.gitlab.com/resources/ai-accountability-survey-2026/ -
🦊 GitLab
@gitlab
Automation that still needs a human to start it isn't automation. GitLab 19.1 ships event-driven triggers for Duo Flows so your AI workflows run the moment conditions are met. Watch the demo to learn more. about.gitlab.com/blog/ai-catalog-updates-for-governance-a…
This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
We surveyed 1,528 developers and tech buyers across six countries with The Harris Poll and found AI is reshaping software development. But how do organizations make it scale?
The full AI Accountability Report drops tomorrow. You don't want to miss this 👀 -
🦊 GitLab
@gitlab
New in GitLab 19.1: third-party SARIF scanner support, secret false positive detection (GA), tool approval guardrails for Duo agents, Code Owners auto-assigned as reviewers, stacked MR visibility in the UI, and inline blame as a toggle.
Read the notes: docs.gitlab.com/releases/19/gitlab-19-1-released/ -
🦊 GitLab
@gitlab
With GitLab 19.1, approving a merge request is the trigger, not the finish line.
The new MR Approved trigger fires your Duo Flow automations the moment an MR is approved, automatically kicking off post-approval steps like deployment readiness checks, compliance logging, and handoff notifications. No manual follow-up, no missed steps, just event-driven automation that runs exactly when it should. For a full list of all the new triggers, plus a summary of what else is available in AI governance and operations in 19.1, check out the release blog.
about.gitlab.com/blog/ai-catalog-updates-for-governance-a…
Watch the demo. -
🦊 GitLab
@gitlab
With GitLab 19.1, your team spends time reducing risk, not chasing false positives. about.gitlab.com/blog/one-vulnerability-view/
Secret detection loses its value when findings are buried in noise. GitLab 19.1 scans every commit on a new branch so nothing slips through early in the history, and Secret False Positive Detection (GA) adds a confidence score and an easy to understand explanation to each finding so your team knows exactly what to prioritize. Watch the demo. -
🦊 GitLab
@gitlab
With GitLab 19.1, third-party scanner coverage is a policy, not a manual task. about.gitlab.com/blog/one-vulnerability-view/
Third-party scanners are defined once at the group level and enforced on every pipeline automatically. Any SARIF-compatible scanner feeds into one unified vulnerability view, so your security team always knows what's covered and can prove it. Watch the demo to see it in action. -
🦊 GitLab
@gitlab
GitLab 19.1 is here. Integrate third-party scanners and get full scanner coverage of your projects. AI workflows now run without a human trigger, and governance controls give enterprises the authority to decide what runs in their environment and prove what it did.
Here are the key changes in this release 🧵:
🦊 GitLab
@gitlab
Scanner blind spots happen when teams are chasing the next project to secure. GitLab 19.1 changes that. You can now enforce third party scanners into GitLab merge requests.
Any SARIF-compatible scanner feeds natively into GitLab, and all findings land in one governed view your security team can prove rather than hope for.
🦊 GitLab
@gitlab
With event-driven triggers, Duo Flows now run automatically on real GitLab events, no manual handoff required. Secret Detection now scans every commit on a new branch, not just the latest. Secret False Positive Detection, now generally available, adds a confidence score to each finding so your team focuses on real exposures, not noise.And AI audit event streaming and agent tool approval guardrails, both now in beta, record every agent action and let admins control what agents can do before they act.
🦊 GitLab
@gitlab
Learn more about the 19.1 release: about.gitlab.com/whats-new/
Ready to dive deeper into 19.1? Learn more here:
AI Governance and Third Party Integrations: about.gitlab.com/blog/one-vulnerability-view/
AI Catalog Updates for Governance and Operations: about.gitlab.com/blog/ai-catalog-updates-for-governance-a… -
🦊 GitLab
@gitlab
GitLab has been named a Leader in the 2026 @Gartner_inc Magic Quadrant™ for DevSecOps Platforms for the fourth consecutive year! 🎉
Read the report: about.gitlab.com/blog/gitlab-leader-2026-gartner-mq-devse… -
🦊 GitLab
@gitlab
Join us for a big day in the Big Apple at #awssummit New York.
Find us at booth #700 to learn more about our latest innovations designed to make agentic AI for software engineering faster, smarter, and more cost effective at scale. -
🦊 GitLab
@gitlab
GitLab and @Capgemini have signed a global alliance partnership agreement.
The collaboration brings together GitLab's intelligent orchestration platform for DevSecOps and Capgemini's expertise in digital and business transformation, helping organizations modernize their software delivery, secure their supply chain, and bring AI into their development workflows.
🦊 GitLab
@gitlab
Read more about the partnership here: about.gitlab.com/blog/gitlab-and-capgemini-global-allianc…
-
🦊 GitLab
@gitlab
Is your GitLab pipeline stuck on pending? Runner issues account for 15% of all GitLab support tickets, but you can fix 80% of them by checking just three things.
Check out our latest episode of "GitLab for Everyone" series, where we break down GitLab for developers at every level. youtu.be/QEq357drrCo -
🦊 GitLab
@gitlab
If you missed GitLab Transcend last week, the on-demand is live.
50x faster agent execution. 11x faster responses. 45x fewer hallucinations. Full audit and policy controls for every agent action. We packed a lot into one event, catch everything at your own pace.
Check it out here: about.gitlab.com/events/transcend/virtual/ -
🦊 GitLab
@gitlab
4 announcements from GitLab Transcend, and the numbers do the talking:
50x faster agent execution with next-gen SCM. 11x faster responses and 4.5x fewer tokens with GitLab Orbit. Full audit and policy controls with Governance for Agents. One annual commitment that actually flexes with GitLab Flex.
Blogs in the replies 👇
🦊 GitLab
@gitlab
Engineering teams are scaling agent activity faster than the infrastructure governance, and commercial models built for human-speed delivery can handle. GitLab Transcend marks our next step in giving enterprises the infrastructure, context, and controls to run agent-driven software delivery at scale.🧵
-
🦊 GitLab
@gitlab
Git was built for a distributed workforce. That model breaks when each team member runs hundreds of agents.
That's why we built Next Generation SCM, now in private beta. Same Git compatibility and auditability, with a backend designed for agentic access from the start. Early internal results are promising: up to 2x fewer tokens, up to 50x faster wall clock time, and up to 1,000x less network traffic.
Learn more. about.gitlab.com/blog/gitlab-transcend-announcements/ -
🦊 GitLab
@gitlab
The Monday Merge is back, with a special edition straight from GitLab Transcend London!
Watch to see what we covered.
Read more in our Monday Merge Newsletter: www.linkedin.com/pulse/speed-easy-control-hard-gitlab-com…This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
The shift to agentic software engineering is not only a product shift. It is a budgeting and planning shift.
GitLab Flex gives organizations one agreement for platform and AI spend, plus a clearer operating model for managing both and a structure built to keep pace as needs change.
Learn more. about.gitlab.com/blog/introducing-gitlab-flex/ -
🦊 GitLab
@gitlab
GitLab Orbit, now in public beta, is the context graph for the entire software lifecycle. about.gitlab.com/blog/introducing-gitlab-orbit/
It continuously maps code, work items, pipelines, deployments, and production signals into a single live graph, so agents reason from first-party context instead of fragmented signals.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Most enterprise software contracts lock-in spend before teams know how they will use it.
GitLab Flex is one annual commitment that covers platform seats, GitLab Credits, and new eligible capabilities as they become available.. No contract amendments required.
GitLab Flex is now accepting requests for orders. Learn more here. about.gitlab.com/blog/introducing-gitlab-flex/ -
🦊 GitLab
@gitlab
Agents operating without lifecycle context don't just fail. They create cleanup work.
GitLab Orbit, now in public beta, maps code, work items, pipelines, deployments, and production signals into a context graph for the entire software lifecycle that agents and engineers query from the same source of truth. Based on internal testing, agents using GitLab Orbit responded up to 11x faster response, used up to 4.5x fewer tokens, and produced up to 45x fewer hallucinations.
Learn more. about.gitlab.com/blog/introducing-gitlab-orbit/ -
🦊 GitLab
@gitlab
Join us for The Developer Show LIVE in London at GitLab Transcend! x.com/i/broadcasts/1jGXggbwBgNKZ
🦊 GitLab
@gitlab
Submit your GitLab Orbit Questions here: docs.google.com/forms/d/e/1FAIpQLSemM-RzbdFFxktL4oim-Q6Gx…
-
🦊 GitLab
@gitlab
Engineering teams are scaling agent activity faster than the infrastructure governance, and commercial models built for human-speed delivery can handle. GitLab Transcend marks our next step in giving enterprises the infrastructure, context, and controls to run agent-driven software delivery at scale.🧵
Post not available here, view on X
🦊 GitLab
@gitlab
GitLab Flex is one annual commitment that covers platform seats, GitLab Credits, and new eligible capabilities as they become available, with monthly reservations that can be reshaped without a contract amendment.
🦊 GitLab
@gitlab
Learn more about what was announced at GitLab Transcend: about.gitlab.com/blog/gitlab-transcend-announcements/
-
🦊 GitLab
@gitlab
Enterprises with data sovereignty and other regulatory requirements can now run a fully managed GitLab offering on @GoogleCloud, delivered by certified managed service providers, with full control over where their code, pipelines, and security data reside.
We're also deepening our AI roadmap collaboration with @GoogleCloud. The latest Gemini models, including Gemini 3.5, are now available for use in GitLab Duo Agent Platform, and Gemma 4 is now available for GitLab Duo Self-Hosted customers.
Read the full announcement here: about.gitlab.com/blog/gitlab-expands-google-model-support/ -
🦊 GitLab
@gitlab
GitLab CEO, @bstaples, takes the stage at GitLab Transcend! 🎉
This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Join us for GitLab Transcend LIVE in London! Tune in below! x.com/i/broadcasts/1OxwbbLPlvVJB
-
🦊 GitLab
@gitlab
Today is the day. GitLab Transcend is live from London.
Bill Staples, CEO, GitLab, is sharing the latest innovations making agentic AI for software engineering faster, smarter, and more cost effective at scale. Plus, hear from Anthropic, Mercedes Benz, Google Cloud, AWS, Cube, and Compare the Market on where software innovation is headed next.
Register for the livestream. about.gitlab.com/events/transcend/virtual/ -
🦊 GitLab
@gitlab
. @AnthropicAI's first Mythos-class model is live on GitLab Duo Agent Platform on all tiers and deployment models.
Claude Fable 5 brings long-horizon autonomy, first-shot accuracy, and deeper bug-finding to your agent workflows. Full details on the blog: about.gitlab.com/blog/mythos-class-claude-fable-5-on-gitlab/ -
🦊 GitLab
@gitlab
Last month, we welcomed Chaim Mazal as GitLab's Chief Information Security Officer!
Chaim brings 15 years of security leadership experience, with deep expertise spanning adversarial security, enterprise security program design, and AI, to lead GitLab's global security organization.
A longtime GitLab customer and former member of our advisory board, Chaim understands the platform the way builders do. His work will help ensure GitLab delivers the security rigor that AI agents require as we define what world-class AI security looks like for the next generation of software development.
Welcome to the team, Chaim! -
🦊 GitLab
@gitlab
Happening tomorrow. GitLab Transcend streams live from London. RSVP 👉 about.gitlab.com/events/transcend/virtual/
Don't miss the keynote featuring GitLab CEO Bill Staples and CPMO Manav Khurana, followed by a customer panel with @AnthropicAI, @googlecloud, @AWScloud, @MercedesBenz, Compare the Market, and Cube.
Stanford SWEPR scientists will share their latest findings on software engineering productivity in the AI era, and a live workshop will give you hands-on time with GitLab Duo Agent Platform. -
🦊 GitLab
@gitlab
From basic code assistance to AI agents running in production, this is how you scale a DevSecOps platform to a 400% ROI.
European technology partner Cube has placed GitLab Ultimate and the GitLab Duo Agent Platform at the center of their entire software development lifecycle. By using GitLab as their single source of truth, they are running custom AI agents in production and connecting external tools like Anthropic's Claude via Model Context Protocol. Operating within strict ISO 27001 guardrails, they have automated repetitive workflows without sacrificing security.
See how Cube achieved 50% faster project setups and multiple daily production deploys. Read the full customer story here: about.gitlab.com/customers/cube/ -
🦊 GitLab
@gitlab
Here's what's waiting for you at Transcend on June 10.
Hands-on demos, actionable engineering insights, discussions about AI and software delivery from industry leader, and a special edition of The Developer Show.
Live from London, accessible from anywhere. Register for the livestream: about.gitlab.com/events/transcend/virtual/ -
🦊 GitLab
@gitlab
What does the next era of agentic AI actually mean for the day-to-day lives of software engineers?
You are invited to a special edition of the Developer Show: Live from London, hosted by GitLab’s Colleen Lake. Fresh off the ground at GitLab Transcend, we are bringing you a first-hand recap of the biggest announcements and breaking down exactly what they mean from a developer angle. We will dive deep into the latest innovations designed to make agentic AI for software engineering faster, smarter, and significantly more cost-effective at scale.
Get the insider perspective and see how these updates will transform your development workflows. Register now to save your spot: about.gitlab.com/events/transcend/virtual/ -
🦊 GitLab
@gitlab
In one week, GitLab Transcend goes live from London on June 10 and streams globally.
Get hands-on with agentic AI, hear from technology leaders at @AnthropicAI, @MercedesBenz, @googlecloud, @awscloud, Cube, and Compare the Market on the future of software development, and dive into new research from @Stanford's SWEPR scientists on engineering productivity in the AI era.
Save your spot. about.gitlab.com/events/transcend/virtual/ -
🦊 GitLab
@gitlab
We reported our Q1 fiscal year 2027 results on June 2, 2026. You can learn more in our full earnings report below:
www.businesswire.com/news/home/20260602438182/en/GitLab-R… -
🦊 GitLab
@gitlab
The difference between an agent that sees only your repository vs. one with full platform context?
Repository-only: compiles code
Platform-aware: ships changes aligned to requirements, security policies, and approval rules
Context determines whether agents accelerate delivery or create rework about.gitlab.com/blog/agentic-coding-only-as-good-as-cont… -
🦊 GitLab
@gitlab
Nice! Your AI shipped faster. But did the business notice? 👀
If you cannot explain how AI moved a business metric, you have a measurement problem. Most teams measure what is easy, not what matters.
Here is a simple 3-step framework to fix it 👇Post not available here, view on X
🦊 GitLab
@gitlab
Goal ➡️ Drivers ➡️ Indicators
Once you build that chain, you'll know exactly what to watch, what to adjust, and how to prove real business value.
How is your team measuring impact right now? Let’s talk below! 💬
🦊 GitLab
@gitlab
Read more here: about.gitlab.com/the-source/ai/connect-ai-tools-to-busine…
-
🦊 GitLab
@gitlab
Come join GitLab Developer Advocate, Colleen Lake, on the Developer Show London livestream on June 10, 1:30PM BST ✨
Expect technology trends, AI, DevSecOps, and probably fewer musical numbers than this video. Probably.
RSVP here: www.linkedin.com/events/thedevelopershow-livefromlondon74… -
🦊 GitLab
@gitlab
Claude Opus 4.8 is now available in GitLab Duo Agent Platform. Built for complex multi-step agent work with less mid-run disruption.
More precise execution, stronger reasoning and planning, better performance on professional work beyond coding.
Read more: -
🦊 GitLab
@gitlab
A Critical vulnerability in an internal batch job is not the same risk as a Medium one in a public auth service. CVSS treats them identically.
GitLab severity override policies fix that. Match on CVE, CWE, file path, or directory. Here are five ways to put it to work.Post not available here, view on X
🦊 GitLab
@gitlab
Apply org-wide risk models at the group level.
Use policy_scope to target a compliance framework like PCI-DSS. Security team defines the risk model once. It applies across every project in scope.
🦊 GitLab
@gitlab
Learn more. about.gitlab.com/blog/severity-override-vulnerability-man…
-
🦊 GitLab
@gitlab
Barclays transformed its DevSecOps toolchain with GitLab, and GitLab Duo adoption exploded from 6,000 to 23,000 users in 12 months. Now the bank is projecting to save 1 million developer hours per year.
Read the full story: about.gitlab.com/customers/barclays-plc/ -
🦊 GitLab
@gitlab
In 2 weeks, intelligent orchestration gets a new layer. Context.
Join us for GitLab Transcend, live from London on June 10 and streaming globally. Get hands-on with agentic AI and hear from technology leaders at @MercedesBenz, @googlecloud, @awscloud, Cube, and @Comparethemkt on where software development is headed. Then dive into industry research with scientists from @Stanford's SWEPR on engineering productivity in the AI era.
Save your spot. about.gitlab.com/events/transcend/virtual/ -
🦊 GitLab
@gitlab
Manual scanner config across every pipeline file doesn't scale.
Security configuration profiles in GitLab 19.0 let security teams enable SAST, dependency scanning, and secret detection across every project from one UI.
Thousands of projects covered in minutes with no gaps.
Learn how: about.gitlab.com/blog/security-configuration-profiles/ -
🦊 GitLab
@gitlab
The future of software engineering isn't just faster code generation, it's agents that understand your entire software system.
Transcend returns June 10. Live from London. Streaming globally.
✅ Live keynote + product demos
✅ Stanford SWEPR research premiere
✅ Hands-on developer workshops
✅ Executive program with peer dinners
Register here: about.gitlab.com/events/transcend/virtual/ -
🦊 GitLab
@gitlab
Agentic Memory and GitLab 19.0 x.com/i/broadcasts/1nxnRRBgbAMxO
-
🦊 GitLab
@gitlab
Nearly half of AI-generated code contains vulnerabilities, and third-party code dominates most codebases.
SBOM-based dependency scanning in GitLab 19.0 inventories every direct and transitive dependency, traces how each one got in, and surfaces what your application actually uses.This media couldn't be displayed. See it on the original post.
🦊 GitLab
@gitlab
Learn more. about.gitlab.com/blog/sbom-based-dependency-scanning/
-
🦊 GitLab
@gitlab
Copilot's BYOK offers flexibility, but true enterprise governance requires more. GitLab Duo CLI provides auditable, controlled CI/CD automation for AI agents.
🦊 GitLab
@gitlab
Here’s our take on what enterprise-grade AI automation requires. about.gitlab.com/blog/gitlab-duo-cli-governance/
-
🦊 GitLab
@gitlab
AI is generating more code than ever, but the work surrounding that code hasn't kept up. GitLab 19.0 is here to close that gap. ⚡️
Agentic AI extends across Secrets Management, Merge Request Automation, CI Pipeline Visibility, New Open Source Models and SBOM-based dependency scanning.
✨ What's new in 19.0:
➡️ Secrets manager: GitLab Secrets Manager (Public Beta) keeps credentials in the same platform that runs your code, scoped per job and governed by the access controls you already use.
➡️ Developer Flow Across the MR: Now extends across the full MR lifecycle, paired with autonomous merge conflict resolution (Beta) and one-click rebase-and-merge (Beta).
➡️ CI Catalog Governance: Components Analytics gives visibility into which CI/CD Catalog components and versions are running.
➡️ Expanded Model Support: Duo Agent Platform Self-Hosted adds four new open source models for air-gapped and regulated environments.
…and more improvements! Read the full 19.0 release notes: docs.gitlab.com/releases/19/gitlab-19-0-released/ 🚀 -
🦊 GitLab
@gitlab
GitLab Secrets Manager is now in public beta.
Store credentials in the same platform that runs your code, scoped per job and governed by the access controls you already use.
about.gitlab.com/blog/secrets-manager-in-public-beta/This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Stop manually untangling merge conflicts. GitLab 19.0's Developer Flow reads both branches, picks a resolution strategy, commits, and explains what it did.
See it in action below. Learn more: about.gitlab.com/blog/transform-mrs-to-automated-workflow/ -
🦊 GitLab
@gitlab
Pipeline standards drift the moment they ship. GitLab 19.0 helps you get them back on track. about.gitlab.com/blog/track-ci-component-usage/
Components Analytics for the CI/CD Catalog lets you see how widely your components are being used across all tiers, and on Ultimate, drill in to see exactly which projects are running which versions.
Watch the demo to learn more.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Air-gapped environments have been the last to realize AI productivity gains. The most capable models land in cloud-first deployments first.
GitLab 19.0 adds four new open source models, Mistral Devstral 2 123B, GLM-5.1, Kimi-K2.6, and MiniMax-M2.7, for GitLab Duo Agent Platform self-hosted, delivering capable agentic workflows, with no data leaving your environment.
Learn more. about.gitlab.com/blog/more-ai-models-for-duo-agent-platfo… -
🦊 GitLab
@gitlab
AI sped up writing code, but the work between opening an MR and merging it stayed manual, slowing teams down.
Developer Flow in GitLab 19.0 now spans the full MR lifecycle, including reviewer feedback, conflict resolution, codebase research, and more.
Watch the demo.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
AI is generating more code than ever, and the work surrounding that code hasn't kept up.
GitLab 19.0 expands our Intelligent Orchestration to close the gap between writing code and shipping it.
Here are the key changes in this release🧵:Post not available here, view on X
🦊 GitLab
@gitlab
Learn more about the 19.0 release: about.gitlab.com/whats-new/
🦊 GitLab
@gitlab
Ready to dive deeper into 19.0? Learn more here:
about.gitlab.com/blog/secrets-manager-in-public-beta/
about.gitlab.com/blog/transform-mrs-to-automated-workflow/
about.gitlab.com/blog/track-ci-component-usage/
about.gitlab.com/blog/more-ai-models-for-duo-agent-platfo… -
🦊 GitLab
@gitlab
Codex + Gitlab. Better together.
In this new tutorial, you'll learn how to use Codex and GitLab Duo Agent Platform to:
🟠 Fix a Rust WebSocket bug locally to get started with Codex
🟠 Enrich the context with GitLab MCP to fix the Rust bug aligned to issue requirements
🟠 Use Codex within GitLab Duo Agent Platform as an external agent to help address review feedback in the merge request
Read the full tutorial: about.gitlab.com/blog/fix-bugs-with-codex-and-gitlab/ -
🦊 GitLab
@gitlab
We're expanding our partnership with @Carahsoft to bring GitLab's intelligent orchestration platform to commercial markets across North America.
Commercial resellers and services partners in the U.S. and Canada can now offer GitLab, including GitLab Duo Agent Platform, to their customers with no separate vendor agreement required.
Carahsoft
@Carahsoft
.@GitLab’s DevSecOps platform is now easier to access across industries via our reseller and services partners, enabling faster, secure software delivery and simplified procurement. Read more: carah.io/GitLabPR #devsecops #secureapps #innovation
-
🦊 GitLab
@gitlab
Level up your skills at the GitLab Transcend Hackathon!
Post not available here, view on X
🦊 GitLab
@gitlab
Choose your track, start hacking, and earn swag credits for exclusive GitLab merchandise.
🦊 GitLab
@gitlab
👉 Register today at the Transcend Experience hub: contributors.gitlab.com/transcend-hackathon
-
🦊 GitLab
@gitlab
Intelligent orchestration, now with context. Register for the livestream: about.gitlab.com/events/transcend/virtual/[…]g_global_chnl_webcast_ai_en_20260610_gitlabtranscend_virtual
On June 10, join hundreds of developers and leaders at GitLab Transcend in London to hear how early adopters are:
🚀 putting AI into practice
🚀 building with intelligent orchestration
🚀 shipping faster and more safely at scale -
🦊 GitLab
@gitlab
Hilti expanded its software capabilities and adopted GitLab to bring code in-house with SCM, CI/CD, and security scanning. @HiltiNAmerica
The results speak for themselves. Learn more: about.gitlab.com/customers/hilti/ -
🦊 GitLab
@gitlab
Every org has AI-written code in their repo, and most can't tell you which agent wrote it.
GitLab logs every agent action, runs every MR through your approval rules, and scans every diff before merge.
See how teams are keeping agent code in check at about.gitlab.com. -
🦊 GitLab
@gitlab
AI agents are shipping code faster than security can see it. The pipeline is where humans, agents, and third-party code converge, and most companies have no control plane that can actually see, enforce, and fix every change. Here's how to harden your pipeline perimeter:
-
🦊 GitLab
@gitlab
GitLab Dedicated for Government is now GovRAMP-authorized.
State and local agencies get single-tenant SaaS with enterprise DevSecOps, U.S.-based data residency, native security scanning, and GitLab Duo, all within an authorized boundary.
A faster path to secure modernization. Learn more here: about.gitlab.com/blog/govramp-gitlab-dedicated-for-govern… -
🦊 GitLab
@gitlab
For a platform serving 645 million job seeker profiles across 60+ countries, Indeed’s operational scale is an engineering requirement.
Jeff Davis, VP of Core Infrastructure at @Indeed, shares how GitLab's dedicated single-tenant SaaS model reduced the maintenance burden on its platform teams, freeing capacity for more innovation.
Now, Indeed is going even deeper with GitLab Duo Agent Platform, building a connected agent ecosystem across tools like Salesforce and Claude Code.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Sick of fixing pipeline typos and triaging security vulnerabilities?
In this snippet from our "GitLab for Everyone" series, Developer Advocate Colleen Lake explains how the GitLab Duo Agent Platform (DAP) takes the "excruciating" out of development by handling mechanical coordination and repetitive tasks.
In her words, "Let the robots handle the boring stuff so you can focus on major architectural decisions and writing great code!" -
🦊 GitLab
@gitlab
Learn how University of Washington lecturer Stephen G. Dame uses GitLab for Education to manage student assignments, distribute course materials, and provide inline code feedback at scale.
about.gitlab.com/blog/teaching-software-development-the-e… -
🦊 GitLab
@gitlab
AI needs guardrails, especially at scale.
GitLab Duo Agent Platform gives you policy-driven control over which agents and flows run, full traceability into every flow session, and the option to self-host LLMs as part of GitLab Self-Managed.
With GitLab Duo Agent Platform, governance and transparency are built in from the start.
🦊 GitLab
@gitlab
Learn more. about.gitlab.com/gitlab-duo-agent-platform/
-
🦊 GitLab
@gitlab
The future of software engineering is being written in real time. Join us June 10 for GitLab Transcend - live from London, streaming globally.
See threaded posts for the agenda from the event!
🦊 GitLab
@gitlab
💡Morning Keynote - GitLab CEO Bill Staples and CPMO Manav Khurana reveal how intelligent orchestration with context makes AI agents across the SDLC faster, smarter, and more cost-effective. Featuring real-world results from Mercedes-Benz and Google Cloud.
Post not available here, view on X
🦊 GitLab
@gitlab
🤝Hands-On Workshop - Top 5 use cases for automating code review, fixing failed pipelines, and remediating vulnerabilities with agentic AI. Live sessions for EMEA, AMER, and APAC time zones.
🦊 GitLab
@gitlab
👉 RSVP here for the global livestream about.gitlab.com/events/transcend/virtual/
-
🦊 GitLab
@gitlab
Your AI agent wrote perfect code.
Then it failed security scanning. Got blocked by your pipeline policy. Broke three integration tests. And sat in review for two days.
Agentic AI without platform integration is just faster code that still shouldn’t ship.
GitLab Duo Agent Platform operates inside the system that actually controls deployment. That's the difference. -
🦊 GitLab
@gitlab
A flowfession we can definitely get behind: a perfectly timed espresso ☕️
What’s your pre-meeting ritual? -
🦊 GitLab
@gitlab
Sound off in the replies. 📢
-
🦊 GitLab
@gitlab
Personal access tokens often carry far more permission than the job needs. If one leaks, the exposure spans every project that user can reach.
Fine-grained PATs, now in beta, let you scope a token to a specific project and a specific set of permissions. One token per job, nothing more.
Read more: about.gitlab.com/blog/fine-grained-pats/ -
🦊 GitLab
@gitlab
Your AI agents, your way.
GitLab Duo Agent Platform gives you the flexibility to work with agents built for how your team actually operates. No matter your workflow, there's an agent for it.
docs.gitlab.com/user/duo_agent_platform/agents/ -
🦊 GitLab
@gitlab
AI coding tools are great at writing code, but shipping it securely is a different problem.
This tutorial shows how Claude Code + GitLab Duo Agent Platform closes the gap, from bug fixes to production, with CI/CD, security scanning, and code review built in.
1️⃣ Fix a bug with Claude Code and let GitLab CI/CD, security scanning, and GitLab Duo Code Review do the rest.
2️⃣ Add GitLab MCP context so Claude works from the context saved within the GitLab issue, and not just local files.
3️⃣ Use a Claude-powered external agent in GitLab Duo Agent Platform to address review feedback directly in the MR.
See how they work together in our blog: about.gitlab.com/blog/claude-code-and-gitlab/
🦊 GitLab
@gitlab
Watch this tutorial from Developer Advocate, Michael Friedrich, to see it in action: youtu.be/JH4Sae3eDpw
-
🦊 GitLab
@gitlab
The attack surface for agentic AI is fundamentally different from anything traditional security models were built to catch.
Rob Smith, GitLab's Public Sector Area VP, breaks down the threat model for agentic AI and what IT leaders need to do about it. federalnewsnetwork.com/commentary/2026/04/when-ai-agents-… -
🦊 GitLab
@gitlab
Your terminal just got a lot smarter.
GitLab Duo CLI now lets you plan the architecture and execute code in a single flow. “Plan Mode” handles the strategy while “Build Mode” handles the implementation. A single Tab press moves you between them without losing any context along the way.
Watch GitLab’s Colleen Lake break down exactly how it works. -
🦊 GitLab
@gitlab
When AI agents lack direct access to your projects, they guess.
glab gives them a reliable interface to GitLab, so you spend less time relaying context and more time on actual work.
Learn how to set it up. ➡️ about.gitlab.com/blog/give-your-ai-agent-direct-structure… -
🦊 GitLab
@gitlab
Security tools fail because the operational foundation wasn't ready for them.
GitLab's Jamie Dicken breaks down why security excellence should start with operational maturity, and what a realistic path forward actually looks like for enterprise teams.
Read the full piece in The New Stack: thenewstack.io/security-operational-maturity-scaling/ -
🦊 GitLab
@gitlab
Your team deserves an agent built for your workflow, not a generic one.
GitLab custom agents: give it a name, write a system prompt, pick its tools, and ship it. Works in GitLab Duo Chat, VS Code, and JetBrains.
Build yours in the AI Catalog. gitlab.com/explore/ai-catalog -
🦊 GitLab
@gitlab
The dark side is tempting.
But good workflows always win. -
🦊 GitLab
@gitlab
AI is generating more code than ever. So why do so many teams feel slower? Our May Monday Merge breaks down the hidden tax of AI-generated code and what GitLab 18.11 is doing to address it.
Plus: new agentic capabilities, the Omdia Universe Leader recognition, and a conversation with Rivian on software quality at scale.
Watch for a preview, then read the full edition: www.linkedin.com/pulse/more-ai-code-problems-gitlab-com-f…This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Because “just rerun it” isn’t a strategy.
Happy May 4th!
#maythe4thbewithyou -
🦊 GitLab
@gitlab
If you could only use an AI agent for ONE task today, what would save you the most time?
-
🦊 GitLab
@gitlab
Part analyst, part detective. 🔍 Melissa’s on the hunt for insights with jungle beats in the background and green tea on standby 🍵
Her flow formula? Focused sprints, quick resets, and knowing exactly what works for her brain.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Your AWS environment already has the policies. Your GitLab instance already has the context.
GitLab Duo Agent Platform + Amazon Bedrock connects them, so AI works where your code lives, not in a separate tool without governance.
about.gitlab.com/blog/gitlab-amazon-platform-orchestratio… -
🦊 GitLab
@gitlab
What they don’t tell you when you start with CI/CD:
it’s not hard…
it just feels like it’s judging you.
Pipelines fail. YAML breaks. Nothing explains why.
So yeah, most of us avoid it. 👀👇Post not available here, view on X
🦊 GitLab
@gitlab
Best way to learn CI/CD?
Break it on purpose once.
Watch it fail early.
Fix it.
Suddenly… it clicks.
🦊 GitLab
@gitlab
Takes ~10 minutes to set up your first pipeline.
After that it’s just:
push → pipeline runs → done ✅
Colleen walks you through it step-by-step here: youtu.be/IV5MQUEUx44 -
🦊 GitLab
@gitlab
GitLab is now available in @stripe Projects.
Developers and AI coding agents can add GitLab to a new project in seconds, with credentials and environment variables handled automatically.
Run "stripe projects add gitlab/project" to get started.
Learn more:This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
As AI reshapes the speed of software development, product security must keep pace. Cycode's Product Security Leaders to Watch list recognizes the practitioners setting new standards for how teams do exactly that.
Congratulations to our very own Jamie Dicken, Senior Director of Security Platforms and Architecture, on being named to this year's list. Well deserved.
Read Jamie’s full interview: cycode.com/2026-product-security-allstars/ -
🦊 GitLab
@gitlab
🏆 Celebrating our GitLab AI Hackathon winners! 🚀
What an incredible display of innovation, collaboration, and AI-powered creativity from teams across the GitLab AI Hackathon. -
🦊 GitLab
@gitlab
"Our single source of truth for collaboration within the software development lifecycle."
Mans Booijink from Cube sat down with GitLab CEO, Bill Staples and chatted through Cube's 8 years with GitLab, from source code management to running 4 dev teams in parallel. -
🦊 GitLab
@gitlab
GitLab is deepening its integration with @AnthropicAI's Claude models, now built into GitLab Duo Agent Platform with full audit and policy enforcement, no separate governance layer needed.
Claude models, including Claude Opus 4.7, are available via Google Cloud, Amazon Bedrock, and the Claude Marketplace, routing AI workloads through existing hyperscaler and Anthropic spending commitments.
🦊 GitLab
@gitlab
Read more here: about.gitlab.com/blog/gitlab-and-anthropic-governed-ai-fo…
-
🦊 GitLab
@gitlab
GitLab Duo Agent Platform can be used for many use cases. Here’s how @sajjaad_khader built an agent to help him keep track of his gym routine. 💪
This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Before joining the GitLab team, Shubham Kumar was a contributor.
He didn't start his GitLab career with a job posting, he started with a merge request. The path into a career at GitLab looks different for everyone.
Curious what yours could look like? Explore open roles: -
🦊 GitLab
@gitlab
AI is speeding up code output. But insight into what's actually shipping and where things are breaking is still buried in dashboards and manual queries.
GitLab 18.11 helps address that gap. The Data Analyst Agent (now GA) lets you query MR cycle time, pipeline health, and project metrics in plain language inside Agentic Chat. No GLQL, no third-party tools, always-current data.
Watch the demo to learn more. about.gitlab.com/blog/ci-expert-and-data-analyst-ai-agent…This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
AI has gotten really good at accelerating the 15% of a developer's day spent writing code.
The other 85%, which includes planning, review, testing, debugging, coordination, and compliance, is manual, fragmented, and slows them down. The fix is AI across the entire software lifecycle.
📖 about.gitlab.com/the-source/ai/why-enterprises-can-t-affo… -
🦊 GitLab
@gitlab
The Developer Show: Specialized Agents & Skills x.com/i/broadcasts/1DxLdvNEPpvxm
-
🦊 GitLab
@gitlab
In Vegas for #googlecloudnext? Join us today for a breakout session alongside @temporalio and Vellum AI.
We'll be sharing our solutions for delivering reliable, next-gen multi-agent systems at production scale.
Register to join. g.co/cloudnext -
🦊 GitLab
@gitlab
See GitLab Duo Agent Platform in action at #googlecloudnext. Live demos, lightning talks, real workflows.
Booth 2423. Come find us. -
🦊 GitLab
@gitlab
GitLab wins the 2026 @GoogleCloud Technology Partner of the Year for DevSecOps for the 6th consecutive year.
Stop by booth #2423 at #googlecloudnext to learn how we’re helping joint customers apply AI across the full software lifecycle with the visibility and governance they need.
www.businesswire.com/news/home/20260422151197/en/GitLab-W… -
🦊 GitLab
@gitlab
Anthropic's Mythos model found a 27-year-old OpenBSD bug in testing, and attackers will get comparable tools within a year. A ready GitLab pipeline answers "are we exposed" in minutes when the next CVE drops.
Learn more. about.gitlab.com/blog/prepare-your-pipeline-for-ai-discov… -
🦊 GitLab
@gitlab
Run our AI agents inside AWS.
@gitlab and @AWSCloud have made it possible to use GitLab Duo Agent Platform with Amazon Bedrock, using the models, IAM policies, and spend commitments AWS customers already have in place.
No new vendors. No new infrastructure. Just agentic DevSecOps in the stack you already trust.
Learn more. about.gitlab.com/blog/gitlab-amazon-platform-orchestratio… -
🦊 GitLab
@gitlab
Meet Nick Skoretz, Site Reliability Engineer at GitLab.
His flow mode secret? A vinyl record. One side = ~20 minutes.
When the music stops, he gets up, stretches, flips it, and goes again. -
🦊 GitLab
@gitlab
Specialized agents. Duo CLI in beta. Open source x AI.
This week’s episode of The Developer Show drops April 23 at 10:00 UTC and we’re going to break it all down for you.
Set your calendars now to tune in! -
🦊 GitLab
@gitlab
Most CI/CD tools can build your code and deploy it.
Where they can fall apart is when your monorepo has a dozen services, microservices are spread across repos, you’re deploying to dozens of environments, and your platform team is trying to enforce standards at scale.
Here are 5 pipeline patterns where GitLab's model stands out.🧵Post not available here, view on X
🦊 GitLab
@gitlab
Governed pipelines: platform teams shouldn't have to patch every repo manually.
The problem: every team has its own .gitlab-ci.yml with subtle variations. Security scanning gets skipped. Deployment standards drift. Audits are painful. CI/CD Components let platform teams publish versioned, reusable pipeline building blocks to the CI/CD Catalog. App teams consume them with a single include: line and optional inputs. Push a security fix to a new version, and teams opt in on their schedule, or the platform team pins everyone to a minimum version.
Why it matters: one change propagates everywhere instead of needing to be applied repo by repo. Platform engineering teams enforce compliance without becoming a bottleneck
🦊 GitLab
@gitlab
These primitives compose, and that's the real unlock.
A monorepo uses parent-child pipelines, and each child uses DAG execution. A microservices platform uses multi-project pipelines, and each project uses MR pipelines with merged results. A governed platform uses CI/CD Components to standardize all of the above across every team.
Most teams find one of these when they hit a specific pain point. The ones who invest in understanding the full model end up with a delivery system that reflects how their engineering org actually works. about.gitlab.com/blog/5-ways-gitlab-pipeline-logic-solves… -
🦊 GitLab
@gitlab
Software running Rivian and VW Group vehicles carries families.
Here’s Eric Hulser, Sr. Dir. of Connected Services at VW & Rivian Group Technologies, on why reliable, validated software is non-negotiable, and why GitLab is the infrastructure they trust to deliver it. -
🦊 GitLab
@gitlab
AI adoption can stall when costs aren't predictable.
GitLab 18.11 introduces spending caps and per-user budget controls for GitLab Credits, so you can scale GitLab Duo Agent Platform.
Set a ceiling. Roll out to more teams. Ship with confidence. Learn more. -
🦊 GitLab
@gitlab
AI made writing code faster. Setting up the pipeline to run it and understanding how delivery is actually going? Still on you... until now.
CI Expert (Beta) generates a working pipeline config from your repo in minutes, and Data Analyst (GA) answers natural-language questions from live GitLab data in Agentic Chat. Both run inside the same platform as your code, pipelines, and issues.
about.gitlab.com/blog/ci-expert-and-data-analyst-ai-agent…This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Faster code generation hasn't meant faster delivery. GitLab 18.11 is here to address that gap. ⚡️
Agentic AI now covers pipelines, security, and delivery analytics so your entire delivery chain moves as fast as your IDE.
✨ What's new in 18.11:
➡️ Automate Remediation: Agentic SAST Vulnerability Resolution is now GA, generating ready-to-merge code fixes before vulnerabilities reach production.
➡️ Two New Agents: The CI Expert Agent (beta) can spin up a working pipeline in minutes, and the Data Analyst Agent (GA) answers live delivery questions in natural language.
➡️ Spend Controls: New subscription-level and per-user caps for GitLab Credits give organizations control over on-demand AI spend at scale.
...and more improvements!
🦊 GitLab
@gitlab
Read the full 18.11 release notes:docs.gitlab.com/releases/18/gitlab-18-11-released/ 🚀
-
🦊 GitLab
@gitlab
Faster code generation hasn't meant faster delivery.
GitLab 18.11 helps address that gap with agentic AI across pipelines, security, and delivery analytics.
Here are the key changes in this release🧵:Post not available here, view on X
🦊 GitLab
@gitlab
Learn more about the 18.11 release: Learn more about what's available in 18.11 here:
about.gitlab.com/releases/whats-new/
🦊 GitLab
@gitlab
Ready to dive deeper into 18.11? Learn more here:
Learn more about what's available in 18.11 here:
about.gitlab.com/blog/automate-remediation-with-ready-to-…
about.gitlab.com/blog/ci-expert-and-data-analyst-ai-agent…
about.gitlab.com/blog/gitlab-18-11-budget-guardrails-for-… -
🦊 GitLab
@gitlab
Claude Opus 4.7 from @AnthropicAI is now available in GitLab Duo Agent Platform.
Teams get stronger reasoning and more precise agents across every workflow. about.gitlab.com/blog/claude-opus-4-7-is-now-available-in… -
🦊 GitLab reposted
Bill Staples
@bstaples
GitLab Duo Agent Platform agents can now call foundation models through Vertex AI, including Gemini. Every agent action is governed by the same controls as your human developers, and you can choose to have usage count toward your existing Google Cloud commitments.
🦊 GitLab
@gitlab
GitLab Duo Agent Platform agents can now call foundation models through Vertex AI, including Gemini.
AI agents that build software need more than a capable model. They need context from the issue that started the work, the repository it touches, the pipeline that validates the result, and the security policies that govern what ships. -
🦊 GitLab
@gitlab
Building an AI agent is the easy part. Securing it and deploying it is where many teams stall.
Our own Regnard Raquedan will be at @googlecloud Next, showing how GitLab + Agent Engine takes agentic development all the way from build to ship.
Join us April 22-24, booth #2324. -
🦊 GitLab
@gitlab
We answered community questions during the last episode of The Developer Show. Here’s our take on how and when to use multi-agents. 👇
This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
The attack surface grows every time an AI agent commits code.
Most security tools scan after the fact.
GitLab Duo Agent Platform’s Security Analyst Agent works inside the workflow, triaging vulnerabilities, filtering false positives, and generating fixes before anything ships.
🦊 GitLab
@gitlab
Learn more: docs.gitlab.com/user/duo_agent_platform/agents/foundation…
-
🦊 GitLab reposted
CXOTALK
@cxotalk
#softwaredevelopment coding with AI tools + platforms, including AI agents, can accelerate coding, but lead to bottlenecks downstream in s/w delivery. These bottlenecks result from fragmented context.
-- Bill Staples, CEO @GitLab
www.cxotalk.com/episode/intelligent-orchestration-softwar…
#cxotalk
#ai #aiagents -
🦊 GitLab
@gitlab
GitLab Duo CLI is now in beta.
Bring GitLab Duo Agent Platform to your terminal for local development workflows. Pull context from issues and Agentic Chat sessions, iterate in plan mode, then let Duo implement, commit, and open MRs.
🦊 GitLab
@gitlab
Learn more here: about.gitlab.com/blog/gitlab-duo-cli/
-
🦊 GitLab
@gitlab
GitLab Duo Agent Platform agents can now call foundation models through Vertex AI, including Gemini.
AI agents that build software need more than a capable model. They need context from the issue that started the work, the repository it touches, the pipeline that validates the result, and the security policies that govern what ships.
🦊 GitLab
@gitlab
Read more: about.gitlab.com/blog/gitlab-and-vertex-ai-on-google-cloud/
-
🦊 GitLab
@gitlab
AI test insights are only as powerful as the data feeding them.
Pipe real-time GitLab data into @SmartBear QMetry and unlock AI that catches flaky tests, predicts failures, and tells you where to optimize before things break.
🦊 GitLab
@gitlab
Continuous data. Accurate insights. Faster releases. about.gitlab.com/blog/streamline-test-management-with-the…
-
🦊 GitLab
@gitlab
Rivian and Volkswagen Group Technologies run one of the world's largest Gitaly deployments, processing thousands of jobs/sec as they build software-defined vehicles.
Every line of code that goes into a car flows through GitLab Dedicated for validation and testing before it ships.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
🚨Contributor Developer Missing 🚨
Last seen: entering flow mode
Wearing: GitLab merch
Last known location: contributors.gitlab.com/hackathon -
🦊 GitLab
@gitlab
The more code AI writes, the bigger your attack surface gets.
GitLab Duo's Security Analyst Agent triages findings, cuts the noise, and proposes fixes inside the repo before the MR merges.
Security that moves as fast as the AI generating the code.
about.gitlab.com/blog/automating-detection-gap-analysis-w… -
🦊 GitLab
@gitlab
"Just ship the fix" sounds simple until you remember you need to:
Branch from the right commit
Write the actual code
Run tests locally
Fix what broke
Open the MR
Tag reviewers
Address feedback
Merge
Monitor deploy
What if an AI agent could own that entire loop? That's what we built GitLab Duo Agent Platform for.
Curious, what workflows would you automate first? -
🦊 GitLab
@gitlab
GitLab is named a Leader in the 2026 Omdia Universe for AI-assisted Software Development, IDE-based Tools
Best-in-class scores:
🏆100% Solution Breadth
🏆88% Strategy and Innovation
🏆82% Core Features
What separated Leaders from Challengers this year: full SDLC coverage, not just code gen
🦊 GitLab
@gitlab
Read more here: about.gitlab.com/blog/gitlab-named-a-2026-omdia-universe-…
-
🦊 GitLab
@gitlab
GitLab Duo can now create issues, write code, open MRs, and respond to comments. It's not just assisting your workflow, it's operating inside your workflow.
-
🦊 GitLab
@gitlab
Your refresher on how automation worked its way into AppSec.
-
🦊 GitLab
@gitlab
Security scanners are essential.
But not every finding needs your attention.
Here are 5 vulnerability types you should stop reviewing manually. 🧵Post not available here, view on X
🦊 GitLab
@gitlab
One policy definition. Applied automatically. Across your entire organization.
🦊 GitLab
@gitlab
Full tutorial with copy-ready YAML configs: about.gitlab.com/blog/auto-dismiss-vulnerability-manageme…
-
🦊 GitLab reposted
CXOTALK
@cxotalk
#ai #softwaredevelopment Advice (2:2)
4. Do pilots b/c they also point to dev processes + lifecycle that may need to change
5. Define upfront criteria team members must “hold fast to” vs rules that can be bent
-- Bill Staples, CEO @GitLab
www.cxotalk.com/episode/intelligent-orchestration-softwar…
#cxotalk #sdlc #aiagents -
🦊 GitLab
@gitlab
The SDLC is becoming a conversation between humans and agents. Make sure you're building on a platform where both can speak the same language.
-
🦊 GitLab
@gitlab
Finding vulnerabilities isn’t the hard part. Knowing which ones matter, and whether they’re reachable in production, requires context. GitLab’s intelligent orchestration platform provides that context.
-
🦊 GitLab
@gitlab
Your deployment process is yours. Custom AI agents can learn it, automate it, and handle the tedious parts for you.
We’re showing this live at Google Cloud Next, April 22-24. More soon. -
🦊 GitLab
@gitlab
Which task would you trust an AI agent to handle fully autonomously today?
A) Creating and opening a merge request
B) Running security scans and creating fix issues
C) Updating documentation after code changes
D) All of the above (we're ready)
Comment below ⤵️ -
🦊 GitLab
@gitlab
The hard truth: Automated checks can handle more work, but human judgment doesn't scale the same way.
🦊 GitLab
@gitlab
@briancwald breaks down how to add structure to your review workflow on @thenewstack: thenewstack.io/hidden-tax-ai-code/
-
🦊 GitLab
@gitlab
When your security scanner or AI model gateway becomes an attack vector, you need a new defense layer.
GitLab Pipeline Execution Policies enforce mandatory checks across every pipeline. We open-sourced 3 policies that catch the exact patterns from the March 2026 supply chain attacks.
🦊 GitLab
@gitlab
Read how centralized policy enforcement can stop supply chain attacks: about.gitlab.com/blog/pipeline-security-lessons-from-marc…
-
🦊 GitLab
@gitlab
The shift from "AI suggests code" to "AI ships code" is happening faster than most teams are ready for. Agentic AI can now handle entire workflows, from planning to deployment. Your SDLC is about to change fundamentally.
-
🦊 GitLab
@gitlab
Your CI/CD pipeline fails. You click "Fix Pipeline with Duo." GitLab Duo debugs the logs, identifies the issue, and opens an MR with the fix.
This is what AI agents actually solving dev problems looks like.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
GitLab gives you AI teammates that understand your repo structure, your CI/CD pipelines, and your security policies. Context is everything with agentic AI.
-
🦊 GitLab
@gitlab
When it comes to scaling agentic AI across your org, what's the biggest blocker?
🦊 GitLab
@gitlab
Full breakdown of the build vs. buy tradeoffs for agentic AI in regulated industries.
🔗 about.gitlab.com/the-source/ai/the-real-cost-of-build-vs-… -
🦊 GitLab
@gitlab
Who reviews your detections after an incident? And how consistently does that actually happen?
GitLab's Signals Engineering team solved this with an AI agent that automatically analyzes incidents and surfaces detection gaps.
🦊 GitLab
@gitlab
Here’s how they did it. about.gitlab.com/blog/automating-detection-gap-analysis-w…
-
🦊 GitLab
@gitlab
Turn early AI wins into lasting competitive advantage with three enterprise strategies to build on your AI momentum.
about.gitlab.com/the-source/ai/beyond-the-quick-win-how-e… -
🦊 GitLab
@gitlab
Why does more AI-generated code sometimes mean slower delivery? Because coding is only 15% of shipping software.
Review, testing, security, and deployment are still manual. But GitLab Duo Agent Platform helps close the gap. -
🦊 GitLab
@gitlab
Here are five hard-won lessons from building an autonomous AppSec agent.
This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
After a year in development, it’s finally time.
What if you could feel the thrill of software development like a real developer?Post not available here, view on X
🦊 GitLab
@gitlab
The Friday Deploy was engineered for precision timing and high-stakes decision making.
It is technically safe. We simply advise guests to plan their visit accordingly.
🦊 GitLab
@gitlab
Pending merge approval.
-
🦊 GitLab
@gitlab
@CarrefourGroup cut time to market in half and saved 450+ engineering hours monthly by standardizing on GitLab.
The results: 2x faster e-commerce delivery, 30x increase in deployment frequency, 50% reduction in platform costs, and 99.91% uptime across critical retail systems.
From 17,000 repositories to AI-assisted code reviews, GitLab now powers digital operations for one of the world's largest retailers across e-commerce, logistics, warehouses, and point-of-sale systems.
🦊 GitLab
@gitlab
Read how Carrefour built a unified software factory: about.gitlab.com/customers/carrefour/
-
🦊 GitLab
@gitlab
We’ve got you covered on using the AI Catalog in GitLab Duo Agent Platform. 🤓
-
🦊 GitLab
@gitlab
Epics and issues used to live on separate list pages. Not anymore. GitLab 18.10 brings them together in a unified work items list, with saved views so you never have to rebuild your filters again. Planning just got faster.
Read more here: about.gitlab.com/blog/agile-planning-gets-a-boost-from-ne… -
🦊 GitLab
@gitlab
Here’s a snippet of how to use GitLab Duo Agent Platform, an agentic chat tutorial. 😎
This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
The Developer Show: Multi-Agent Episode, No Filter x.com/i/broadcasts/1nxeLyDRANqJX
-
🦊 GitLab
@gitlab
Two days left to enter the GitLab, @googlecloud , and @AnthropicAI Hackathon.
📅Deadline: Wednesday, March 25th
🔗Register: gitlab.devpost.com -
🦊 GitLab
@gitlab
Your environment dictates your output. How have you optimized your workspace this year?
Answer the poll and show off your workspace in the replies! -
🦊 GitLab
@gitlab
GitLab 18.10 includes the GA of SAST false positive detection for GitLab Ultimate customers using GitLab Duo Agent Platform, to help security and development teams prioritize vulnerabilities that pose a real risk and accelerate remediation.
Dive into the details:This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
AI is helping developers write code faster than ever. The queue for code reviews hasn't kept up.
GitLab Agentic Code Review is now available at a flat cost of $0.25 per review, automatically reviewing merge requests across all groups and projects with full repository, pipeline, and security policy context. Every organization can enable it on every change.
Learn more: about.gitlab.com/blog/code-review-without-the-bottlenecks… -
🦊 GitLab
@gitlab
Organizations on the gitlab.com free tier can now start using GitLab Duo Agent Platform by purchasing a monthly commitment of GitLab Credits, giving every team access to agentic AI across the full software lifecycle.
Read the blog to learn more:This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
As AI-assisted coding has made writing code faster, the bottleneck has shifted to the tasks that follow.⚡️ GitLab 18.10 is here to help bridge that gap.
We’re introducing agentic automation and AI-driven security to keep your workflows moving as fast as your IDE.
✨ What’s new in 18.10:
➡️ AI Access: gitlab.com free tier customers can now purchase credits to use GitLab Duo Agent Platform
➡️ Affordable Agentic Code Reviews: Now at a flat cost of $0.25 per review, making it simple to scale automated reviews across all groups and projects.
➡️ Accelerate Remediation: SAST false positive detection flow is now GA, using AI to help identify false positives and accelerate remediation on GitLab Duo Agent Platform with flat-rate pricing at one flow per GitLab Credit.
...and 60+ more improvements!
Read the full 18.10 release notes: about.gitlab.com/releases/2026/03/19/gitlab-18-10-released/ -
🦊 GitLab
@gitlab
They said there’d be gold at the end of the rainbow. 🌈
We found a green merge instead. ✅
Happy St. Patrick’s Day 🍀 -
🦊 GitLab
@gitlab
The Matrix runs on ones, zeros… and irrational numbers.
International Pi Day detected. Infinity confirmed. -
🦊 GitLab
@gitlab
How have you up-leveled your workflow this year? 👇
-
🦊 GitLab
@gitlab
Developers should be able to work where they want to work. We're making that easier by bringing GitLab into more of the tools and environments your teams already use.
Check out GitLab in the @cursor_ai Marketplace: cursor.com/blog/new-plugins -
🦊 GitLab
@gitlab
Two weeks to go! 🕵️ The GitLab team is heading to San Francisco for RSAC.
@OneRSAC
Join us Wednesday, March 25 for two sessions you don’t want to miss:
✅Five Lessons from Building an Autonomous Security Agent
✅Build vs. Buy, We Did Both, and This Is What We Learned (GRC tools)
Hope to see you in the North hall, booth #6453. -
🦊 GitLab
@gitlab
Learn how GitLab's Signals Engineering team uses our AI platform to automatically surface detection gaps from security incidents — no manual review required.
about.gitlab.com/blog/automating-detection-gap-analysis-w… -
🦊 GitLab
@gitlab
Our latest Flow Tour is here, and this time we’re featuring Frontend Engineer, Javi Garcia. His setup is a masterclass in "cozy.”
✅ Warm lighting for long stretches
✅ 65% Qwertykeys keyboard for the efficient key strokes
✅ Pro-audio for the cleanest calls
✅ Sit-to-stand desk for the midday reset
Watch the tour and see how Javi balances high-end hardware with a low-stress aesthetic. -
🦊 GitLab reposted
CXOTALK
@cxotalk
AI agents make #softwaredevelopment lifecycles more complex:
* Context is the 1st thing #aiagents look at
* Too many #ai tools explodes cost
* Trusting AI tool vendors + their LMM token providers w your org’s data
-- Bill Staples, CEO @GitLab
www.cxotalk.com/episode/intelligent-orchestration-softwar…
#cxotalk
#sdlc #devops -
🦊 GitLab
@gitlab
If you’re juggling Docker Hub, Harbor, and Quay, you’re battling a web of credentials and high egress fees. It’s time to centralize with the new Container Virtual Registry, now in Beta.
By pointing your pipelines to one GitLab endpoint, you get:
✅ Unified Auth: No more token juggling
✅ Pull-Through Caching: Faster "warm" pulls and lower bandwidth costs
✅ Resilience: If an upstream registry is flaky, your cached images keep things moving
🛠️ Ready to speed up your builds? The beta is API-ready in 18.9. Read the full breakdown on the blog: about.gitlab.com/blog/new-gitlab-metrics-and-registry-fea… -
🦊 GitLab
@gitlab
GitLab Duo Agent Platform is now available in the @Claudeai Marketplace.
Organizations can now use their existing Anthropic commitment to purchase GitLab and orchestrate agentic AI across the entire software lifecycle, while maintaining enterprise-grade security, quality, and governance. -
🦊 GitLab
@gitlab
Step 1: Get invited to speak at Embedded World last minute.🗓️
Step 2: Panic. 😱
Step 3: Just kidding! Build a portable device cloud using Raspberry Pis and GitLab CI. 🛠️
Colleen Lake, Developer Advocate, GitLab, is taking "live dangerously" to a new level. Check out her journey from the electronics store to a fully functioning Embedded DevOps lab, just in time for her presentation next week at Embedded World.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Everyone's asking if AI will replace AppSec tools.
That's the wrong question.
🧵Post not available here, view on X
🦊 GitLab
@gitlab
The harder questions enterprises are asking:
Is what we're about to ship safe?
Has our risk posture changed as environments, dependencies, and infrastructure shift?
How do we govern a codebase increasingly assembled by AI — that we're still accountable for?
🦊 GitLab
@gitlab
Detection surfaces risk.
Governance determines what happens next.
Those are not the same thing, and no developer-side tool is built to do both.Post not available here, view on X
🦊 GitLab
@gitlab
In an agentic world, governance becomes the foundation that makes AI-assisted development trustworthy at scale.
🦊 GitLab
@gitlab
AI will accelerate development dramatically.
The orgs that win won't just have the smartest assistants. They'll have the strongest governance.
Here's how GitLab is built for that: about.gitlab.com/blog/ai-can-detect-vulnerabilities-but-w… -
🦊 GitLab
@gitlab
Flow Tours is officially live. 🎬💻🔥
Think of your favorite house tour show, but built for WFH setups.
Our first stop is Colleen Lake’s desk. As a Developer Advocate at GitLab, her workspace is designed for context switching, live demos, and deep work. The lighting, layout, and overall coding mood all play a role in how she gets into flow.
Watch the premiere and get inspired to upgrade your own setup.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
We reported our Q4 and full fiscal year 2026 results on March 3, 2026. You can learn more in our full earnings report below:
www.businesswire.com/news/home/20260303140705/en/GitLab-R… -
🦊 GitLab
@gitlab
New Monday Merge video is live!
This month, Fatima covers the AI Paradox, what's new in GitLab 18.9, and why intelligent orchestration is the real unlock for enterprise software delivery.
Watch it here 👇This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Toolchain sprawl is slowing down your entire software delivery pipeline.
GitLab CEO Bill Staples joined Michael Krigsman on CXO Talks to talk about why measuring end-to-end flow in software delivery is the missing piece for many AI development strategies.
🎧Hear more: -
🦊 GitLab
@gitlab
Demand is growing for AI-powered development capabilities that accelerate innovation velocity while meeting local data sovereignty requirements. MSPs are uniquely positioned to meet that demand.
GitLab's expanded MSP Partner Program gives qualified partners the tools, support, and revenue opportunities to deliver GitLab's intelligent orchestration platform for DevSecOps as a fully managed service across the entire software development lifecycle.
Enhanced margins. Priority support. Flexible deployment. And a growing base of enterprises ready to modernize.
Read the full announcement: about.gitlab.com/blog/introducing-the-gitlab-managed-serv… -
🦊 GitLab
@gitlab
Great news for GitLab Ultimate customers 🎉
We're announcing our 99.9% availability commitment with service credits for about.gitlab.com and GitLab Dedicated to support your mission-critical DevSecOps workflows.
about.gitlab.com/blog/gitlab-backs-99-9-availability-with… -
🦊 GitLab
@gitlab
We're excited to announce our new partnership with Tata Consultancy Services (TCS) to bring GitLab Duo Agent Platform to enterprises around the world.
By combining GitLab's intelligent orchestration platform with TCS' AI-led enterprise transformation capabilities, we’re helping organizations worldwide deliver secure software faster.
Learn more: about.gitlab.com/blog/agentic-sdlc-gitlab-and-tcs-deliver… -
🦊 GitLab
@gitlab
If your issue backlog feels personal…
it’s probably because you’re the one triaging it.
GitLab Duo Agent Platform can:
• Read every issue (not just the title)
• Flag missing details
• Loop in the right teammate
• Triage your entire backlog at once.
Hundreds of issues.
Over a day saved.
Let’s flow with Duo! -
🦊 GitLab
@gitlab
There's an irony at the heart of agentic AI that Özer Dondurmacıoğlu, our VP of Product Marketing, keeps coming back to.
The more you hand off to agents, the more intentional you have to be upfront.
AI is forcing software teams to architect first and execute second. And in doing so, it's quietly making DevSecOps best practices easier to adopt than ever.
Hear more on RedMonk’s podcast: redmonk.com/videos/gitlab-platform/ -
🦊 GitLab
@gitlab
The GitLab Hackathon is open and we want to see what you build with GitLab Duo Agent Platform.
If you’ve got ideas for how AI agents can transform the way you build, test, and ship software, this is your moment.
Link to sign up: gitlab.devpost.com -
🦊 GitLab
@gitlab
GitLab 18.9 delivers two new capabilities for enterprise engineering teams: Self-hosted AI models in GitLab Duo Agent Platform and Bring Your Own Model (BYOM).
Full infrastructure control. Granular cost transparency. The flexibility to use models you've already invested in. All-in-one governed control plane.
about.gitlab.com/blog/agentic-ai-enterprise-control-self-… -
🦊 GitLab
@gitlab
Introducing GitLab's updated Security Dashboard 🎉
One view. All your vulnerability data. Across every project, group, and business unit.
Risk scoring, trend charts, and smart filters so your team always knows where to focus next. 📊
about.gitlab.com/blog/track-vulnerability-remediation-wit…This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
GitLab 18.9 shipped with 530+ community contributions and some serious upgrades:
✅Self-hosted AI model support for GitLab Duo Agent Platform
✅ Vulnerability resolution with GitLab Duo Agent Platform (beta)
✅ Collapsible file tree to navigate repos
✅ Zero Downtime Upgrades supported for Helm chart deployments
✅ Web-based commit signing on gitlab.com
Full release post → about.gitlab.com/releases/2026/02/19/gitlab-18-9-released/ -
🦊 GitLab
@gitlab
Curiosity is Darva Satcher’s secret to staying in flow.
Diving into topics that excite her, hearing from others, and then partnering with AI to turn those ideas into something real.
What new tools have been getting you into flow lately? -
🦊 GitLab
@gitlab
Anthropic's most intelligent model is now available in GitLab Duo Agent Platform for all agents, including Agentic Chat.
Read more here: about.gitlab.com/blog/claude-opus-4-6-now-available-in-gi… -
🦊 GitLab
@gitlab
Southwest Airlines supports 4,000 flights a day with 3,000 technical resources. Keeping it running at scale 24/7 requires reliability and resilience. ✈️
Grant Morris at Southwest talked to GitLab’s Sherrod Patching about using agentic AI to automate routine work across the SDLC, expecting Duo agents to handle 90% of component version updates so teams can focus on work that moves the business forward.
Watch the full conversation at GitLab Transcend on demand: about.gitlab.com/events/transcend/virtual/ -
🦊 GitLab
@gitlab
AI is making coding faster, but teams aren't seeing faster innovation. We call this the AI Paradox.
GitLab CEO Bill Staples joined @mkrigsman on @cxotalk to discuss why AI-accelerated coding creates new bottlenecks in downstream software development and how intelligent orchestration can solve it.
Check out the full conversation → www.cxotalk.com/episode/intelligent-orchestration-softwar… -
🦊 GitLab
@gitlab
Missed #gitlabtranscend? No problem. 😅
Get instant access to all of the content when you watch on-demand: about.gitlab.com/events/transcend/virtual/ -
🦊 GitLab
@gitlab
Together. In every language. 💜
From YAML to HTML, some things just belong together.
What code pair did we miss? 👇
Happy Valentine’s Day from GitLab! -
🦊 GitLab
@gitlab
Love, but make it infinite. 💜
Happy Valentine’s Day from Tanuki (and GitLab).
How would you write love in code? 👇 -
🦊 GitLab
@gitlab
At GitLab Transcend, our team tackled challenges, fixed a broken pipeline, and resolved a security vulnerability in minutes.
Watch GitLab Transcend on-demand to see how John, Fatima, and Cesar showed intelligent orchestration in action. about.gitlab.com/events/transcend/virtual/ -
🦊 GitLab
@gitlab
Spotted this Tanuki-themed driving machine in Munich for GitLab Transcend outside the famed Doppelkegel (Double Cone) at BMW World.
Think this would turn heads in your neighborhood? -
🦊 GitLab
@gitlab
AI doesn’t need opinions. It needs orchestration.
Check out GitLab Duo Agent Platform.about.gitlab.com/gitlab-duo-agent-platform/ -
🦊 GitLab
@gitlab
Team members across the globe joined us for GitLab Transcend, both virtually and in-person.
If you missed hearing about the true potential of agentic AI for software delivery live, check out the replay here. about.gitlab.com/events/transcend/virtual/This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
You heard the vision. Now try GitLab Duo Agent Platform yourself.
Premium and Ultimate customers now get monthly GitLab Credits at no extra cost. Not a customer yet? Start a trial and put it to work. about.gitlab.com/blog/introducing-gitlab-credits/ -
🦊 GitLab
@gitlab
Stop managing servers and start shipping code.
Data Intensity's DevSecOps as a Service brings GitLab self-managed to @OracleCloud Infrastructure for peak performance and security.
Get the details here: about.gitlab.com/blog/devsecops-as-a-service-on-oracle-cl… -
🦊 GitLab
@gitlab
From early-morning setup and rehearsals to last-minute run-throughs, a village brought GitLab Transcend to twelve cities and a global remote audience.
Here are some behind-the-scenes moments. -
🦊 GitLab
@gitlab
Real demos. Real customer stories. Real momentum.
From customer perspectives to live technical demos, we are showing how intelligent orchestration helps teams move faster across the software development lifecycle.
Missed us? Stay tuned for on-demand content coming soon. -
🦊 GitLab
@gitlab
Here’s a BTS look at Transcend.
Follow along for more updates. about.gitlab.com/events/transcend/virtual/[…]&utm_campaign=eg_global_corp_webcast_ai_en_transcend_virtual -
🦊 GitLab
@gitlab
GitLab Transcend is officially underway. 🌏🚀
Across the globe, teams are exploring what’s possible with agentic AI and what it takes to scale software delivery without slowing teams down.
Huge thanks to everyone joining us in person and online today. -
🦊 GitLab
@gitlab
🚨GitLab Transcend is starting! 🚀Register now to tune in.
about.gitlab.com/events/transcend/virtual/ -
🦊 GitLab
@gitlab
Explore the full potential of agentic AI in software delivery at GitLab Transcend. about.gitlab.com/events/transcend/virtual/
Join us from anywhere in the world to explore the future of intelligent orchestration, take part in live Q&A, and get a first look at what’s ahead on GitLab’s product roadmap.
Choose the time that works best for you and watch in your preferred language, with local subtitles available in 16 languages:
AMER: 9AM PT
EMEA: 10AM GMT
APJ: 12PM SGT -
🦊 GitLab
@gitlab
Stop documenting, start delegating. ✍️
Imagine agents that establish your standards and auto-update docs as your code evolves, all while using a Knowledge Graph to keep your architecture synced. No context switching, just your IDE and total clarity.
Want to see what else GitLab Duo Agent Platform can take off your plate?
Tune in on February 10. ⬇️
🦊 GitLab
@gitlab
Register here: about.gitlab.com/events/transcend/virtual/
-
🦊 GitLab
@gitlab
🎙️ GitLab VP of Americas and Public Sector Bob Stevens recently joined John Gilroy on @FederalTechPod to share his thoughts on how AI is impacting software development in the government, including:
⚡AI-driven federal modernization at scale
🔍Shifting from reactive to proactive security
👥 AI will help increase the government's development capacity, as SMEs directly translate their knowledge into functional software solutions
🦊 GitLab
@gitlab
Full episode here: www.theoakmontgroupllc.com/ep-293-predictions-for-2026-fr…
-
🦊 GitLab reposted
VMblog
@vmblog
Centralized security can't keep pace with modern business complexity. As attack surfaces grow, federated #governance is becoming essential. #cisos set policy, business units execute with context. The result? Faster decisions, smarter tech adoption, and #security that scales. Read why Josh Lemos, CISO at @gitlab says #federation will reshape enterprise security in 2026 → vmblog.com/archive/2026/02/05/why-enterprise-security-tea…
-
🦊 GitLab
@gitlab
The secret to focus? Sherrod Patching, VP, Customer Success, lets us in on her secret in this "Flow-fession".🧠
Watch to see how she gets in flow mode. It’s all about those alpha waves. 🌊 -
🦊 GitLab
@gitlab
Flow breaks. Progress stalls.
Learn to move again at GitLab Transcend.
Tune in on February 10. 👇 -
🦊 GitLab
@gitlab
Did you miss the latest episode of The Developer Show?
Kelsey Hightower joined GitLab to explore AI's impact on development and discuss GitLab Duo Agent Platform going GA.
Here’s one of many thought-provoking insights.
Watch now:This media couldn't be displayed. See it on the original post.
🦊 GitLab
@gitlab
Train Your Brain: Kelsey Hightower on AI & Duo Agent Platform Goes GA x.com/i/broadcasts/1mrGmByWPaZJy
-
🦊 GitLab
@gitlab
You heard it here first. We’ve got the scoop on new features, top reads, and a global event you won’t want to miss!
📺Watch the latest edition of the Monday Merge to catch up on everything that’s happening at GitLab.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Curious about static reachability, but not sure where to start?
@awkwardferny has you covered in under a minute; he shares snackable content for busy devs. #devsnacks 😉
www.youtube.com/shorts/ukLXgczTk3c -
🦊 GitLab
@gitlab
Train Your Brain: Kelsey Hightower on AI & Duo Agent Platform Goes GA x.com/i/broadcasts/1mrGmByWPaZJy
-
🦊 GitLab
@gitlab
Learn how to automate user provisioning and sync permissions with Google groups with this step-by-step guide. about.gitlab.com/blog/how-to-set-up-gitlab-saml-sso-with-…
-
🦊 GitLab
@gitlab
POV: You just offloaded test writing to GitLab Duo Agent Platform. ☕️Now you have time to check out GitLab Transcend.
Join us for hands-on demos, from fixing pipelines to securing software, with insights from the experts who built it. Learn more. about.gitlab.com/events/transcend/virtual/ -
🦊 GitLab
@gitlab
Join GitLab Transcend on February 10th to learn how to turn faster coding into faster delivery. Learn more. about.gitlab.com/events/transcend/virtual/
Tune in to watch technical demos that showcase how your teams can use agentic AI to automate real-world use cases and solve production pain points across your software lifecycle. -
🦊 GitLab
@gitlab
The next evolution in AI for software development: the "meta-agent" that functions as an "agent of agents."
Emilio Salvador predicts that meta-agents will act as project managers and chief architects, orchestrating specialized subordinate agents handling design, coding, QA, and deployment. This will increase the velocity with which software is developed.
What's top of mind for Emilio: This new paradigm will fundamentally shift the role of human developers. Instead of focusing on line-by-line coding, their responsibilities will transition to high-level strategy. -
🦊 GitLab
@gitlab
Did you hear that?
…We thought so 😉 -
🦊 GitLab
@gitlab
Experience the platform that orchestrates everything. Catch GitLab Transcend live this Feb 10.
Save the date. about.gitlab.com/events/transcend/virtual/ -
🦊 GitLab
@gitlab
Beyond Tools. Into Orchestration.
See how GitLab is redefining the software lifecycle.
Stay tuned 👀. -
🦊 GitLab
@gitlab
What if you never had to debug a broken pipeline again? 🤖
Our Developer Advocate is letting Agentic AI handle the troubleshooting. His AI sidekick catches issues and fixes them in real-time while he focuses on building.
Are agents part of your workflow yet? -
🦊 GitLab
@gitlab
Join us live with Kelsey Hightower on The Developer Show.
Kelsey and Fatima separate AI reality from hype and break down what training your own model actually takes.
Save your spot. www.linkedin.com/events/7420582919632723969?viewAsMember=… -
🦊 GitLab
@gitlab
Register for GitLab Transcend on February 10th.
Our virtual event offers:
✅ The latest lessons from fellow technology leaders like Southwest Airlines® and Oracle Cloud Infrastructure
✅ Strategies to optimize your modernization journeys
✅ A deep dive into agentic AI use cases
🔗X: about.gitlab.com/events/transcend/virtual/ -
🦊 GitLab
@gitlab
Real companies. Real results 👇
✈️ Southwest Airlines: 4,000 daily flights, zero margin for error
☁️Oracle Cloud: Enterprise flexibility at global scale
Join Sherrod Patching, VP of Customer Experience at GitLab, as she shares how Southwest Airlines and Oracle Cloud Infrastructure are shipping faster and more securely at enterprise scale.
📅 Transcend on Feb 10th
🔗 Register at the link in the comments
🦊 GitLab
@gitlab
Register here: about.gitlab.com/events/transcend/virtual/
-
🦊 GitLab
@gitlab
91% of executives plan to increase AI investments, but only 52% have implemented AI governance policies.
Julie Davila predicts this gap creates a strategic security advantage for early movers. Organizations that establish AI governance now gain critical experience, while those that delay it will struggle as the AI threat landscape shifts.
What's top of mind for Julie: Evolve security and governance to mitigate AI risk. -
🦊 GitLab
@gitlab
We're curious: what productivity hacks keep you moving through your to-do list? Drop your secrets below 👇
Our Developer Advocate Colleen has a simple system. She keeps a stash of really good candy at her desk and only allows herself a piece when she crosses a task off her to-do list.
It's a small reward, but it works. The dopamine hit from completing work + the dopamine hit from candy = motivation to keep going. -
🦊 GitLab
@gitlab
🚀 GitLab Hackathon kicks off in two days!
Join developers worldwide for a week of collaboration, innovation, and open source contribution from January 22-29.
Whether you're into coding, documentation, translation, or UX design, there's a way for you to contribute and make an impact.
What you'll gain:
→ Hands-on experience with real GitLab projects
→ Prizes, achievements, and level-ups on your GitLab profile
→ Connection with our global developer community
Ready to build with us? Register at the link in the comments.This media couldn't be displayed. See it on the original post.
🦊 GitLab
@gitlab
Register now: contributors.gitlab.com/hackathon
-
🦊 GitLab
@gitlab
Proud of what we achieved together through GiveLab. One community coming together to make an impact and build stronger connections. 💛
This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Want to learn how to build and manage custom agents in GitLab Duo Agent Platform?
Developer Advocate, John Coghlan, breaks it down for you!This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
GitLab Duo Agent Platform is now GA 🎉
In the last few months, three model releases have crossed a capability threshold that transforms how engineers code with AI. Gemini 3, Opus 4.5, and GPT-5.2 are increasingly capable of writing production-ready code, and in some cases, developers are reporting 10x productivity gains.
That's the good news. But coding is only ~20% of the delivery cycle, so making coding faster yields only an incremental increase in innovation velocity. Sometimes it even creates new bottlenecks. To achieve exponential innovation velocity, we need to apply agentic AI across all stages of the software development lifecycle.
In this video, GitLab CEO Bill Staples and VP of Customer Experience Sherrod Patching unpack why faster code alone doesn’t translate to faster delivery, where teams are hitting the AI ceiling, and how GitLab Duo Agent Platform addresses that gap by orchestrating AI across planning, security, and delivery. They also break down how GitLab Credits make it practical for organizations to adopt agentic AI at team scale.
See what's next at GitLab Transcend on Feb. 10 👉 about.gitlab.com/events/transcend/virtual/This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
GitLab Duo Agent Platform is now generally available in GitLab 18.8, and that’s not all that shipped in the release! 🚀
✨ What’s new:
➡️Auto-dismiss irrelevant vulnerabilities with vulnerability management policies
➡️GitLab Runner 18.8
➡️Group access control for GitLab Duo features
➡️Multiple container scanning in Beta
…and more!
With GitLab 18.8, teams can orchestrate agentic AI across planning, building, securing, and shipping software in one unified system.
Full release notes below 👇
about.gitlab.com/releases/2026/01/15/gitlab-18-8-released/ -
🦊 GitLab
@gitlab
POV: One team member's idea literally becomes the core of your entire platform 🤯
Martin's been at GitLab long enough to see it happen. When one engineer added CI to GitLab, it didn't just ship, it became the foundation of our DevSecOps platform.
That's what happens in a #remoteandtogether environment. When team members have agency, it leads to game-changing results ✨ -
🦊 GitLab
@gitlab
We asked our Developer Advocate team to share their confessions: the quirky rituals, habits, and little superstitions that help them get into Flow Mode.
Turns out, focus comes in all forms: lucky hoodies, quiet playlists, perfectly timed coffee refills.
💭 These are the moments, big and small, that keep developers in their zone… powered by GitLab and celebrated by the community! -
🦊 GitLab
@gitlab
Vulnerability triaging doesn't have to be an overwhelming manual process.
By combining GitLab's integrated security scanners with GitLab Duo Security Analyst Agent, development teams can quickly identify and prioritize the vulnerabilities that truly matter.
Learn more here ⬇️ -
🦊 GitLab
@gitlab
AI is only as intelligent as the context it can access. Business data across disconnected systems creates the primary barrier to unlocking AI's full potential.
Michelle Gill predicts companies will discover their biggest AI barrier is data architecture. Organizations prioritizing unified data and context frameworks will see AI investments compound in value.
What's top of mind for Michelle: Solve for context architecture first, or face diminishing returns with ad hoc approaches. -
🦊 GitLab
@gitlab
Life doesn’t come with focus mode, but every developer has that thing that gets them in the zone.
What puts you in flow mode? 👇 -
🦊 GitLab
@gitlab
What goes through your mind when you're deep in the zone? 🧠✨ Drop your favorite one-liners: those mental snapshots from your flow mode, and you could see your words featured when we share more Flow Thoughts! 😉
You know the ones: when the world disappears, time stops, and it's just you and the code. 💻🔥
This month, we’ll share community-sourced content that captures raw, unfiltered thoughts that bubble up when you're in pure focus mode. -
🦊 GitLab
@gitlab
What’s a Cognitive Architect?
GitLab’s Emilio Salvador sits down with @thenewstack's Frederic Lardinois to discuss the rise of the cognitive architect, how AI is reshaping developer roles, why GitLab is building an agent orchestration platform, and what the "meta agent" of the future might look like.
Full article here. thenewstack.io/the-rise-of-the-cognitive-architect/ -
🦊 GitLab
@gitlab
AI-generated code is 34% of development work. Discover how to balance productivity gains with quality, reliability, and security at GitLab Transcend. about.gitlab.com/blog/ai-is-reshaping-devsecops-attend-gi…
-
🦊 GitLab
@gitlab
We are honored that @BuiltIn selected GitLab as one of the Best Fully Remote Places to Work!
This recognition reflects our commitment to remote work done right. Regardless of where you work, we’re proud that team members are empowered to collaborate, contribute, and thrive across the globe.
We have an incredible team around the world. This award is because of you!
Interested in being part of our team? We're hiring, explore open roles here: about.gitlab.com/jobs/ -
🦊 GitLab
@gitlab
Explore new supply chain and error handling risks, ranking shifts, and remediation strategies for all 10 categories. about.gitlab.com/blog/2025-owasp-top-10-whats-changed-and…
-
🦊 GitLab
@gitlab
Real talk: agentic AI is changing how we ship software. But how do you actually implement it without breaking everything? 🤔
GitLab Transcend is happening on February 10th and will be your crash course to:
🤝Real customer stories
💻Live product demos
🔮Sneak peek at what's next
💬Direct Q&A with our product leaders
🌍Available in 16 languages
Reserve your seat here: about.gitlab.com/events/transcend/virtual/ -
🦊 GitLab
@gitlab
Learn how this GitLab Duo Agent Platform capability uses AI to prioritize vulnerabilities, reduce alert fatigue, and help teams focus on critical security risks. about.gitlab.com/blog/vulnerability-triage-made-simple-wi…
-
🦊 GitLab
@gitlab
💡 Federal agencies will reduce legacy system updates from multi-year projects to months-long sprints using AI-powered refactoring tools.
Bob Stevens, our VP of Americas and Public Sector, predicts agencies adopting AI-driven modernization will complete system updates 10x faster. -
🦊 GitLab
@gitlab
New year, new features ⚡
GitLab 18.7 brings Custom Flows, AI-powered SAST false-positive detection, and policy warn mode. Plus, get ready for GitLab Duo Agent Platform GA coming in 18.8.
This week's Monday Merge also features how Ericsson 10x'd their testing scenarios while cutting deployment time in half.
Want to jump in? GitLab Hackathon runs Jan 22-29. Everyone's invited 🙌
Read more in the newsletter: www.linkedin.com/pulse/new-year-smarter-platform-whats-ne…This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Congratulations to Bob Stevens on receiving a FORUM IT 100 Award! This recognition honors the most influential leaders shaping the future of public sector technology.
Bob's leadership continues to drive innovation that impacts how government agencies deliver critical services. Congrats once again.🎉
Learn more about the IT 100 honorees: www.govforum.io/event/forum-it-100-2025 -
🦊 GitLab
@gitlab
Discover how trust in AI agents is developed from small, positive micro-inflection points, not big breakthroughs.
about.gitlab.com/blog/building-trust-in-agentic-tools-wha… -
🦊 GitLab
@gitlab
Commit Countdown, Complete! 🪩
2026 is in production. 🚀 Happy New Year!
Developers, tell us, what's getting resolved in your pipelines this year? -
🦊 GitLab
@gitlab
Commit Countdown, Day 1! 🪩
Resolve the disconnects. GitLab brings agents, code, pipelines, and security into one platform.
Get ready to celebrate the new year with one unified platform. -
🦊 GitLab
@gitlab
Commit Countdown, Day 2! 🪩 GitLab Knowledge Graph gives you two essentials:
1️⃣ Context to understand your codebase.
2️⃣ Intelligence to power your AI agents. -
🦊 GitLab
@gitlab
Commit Countdown, Day 3! 🪩
Here are 3 ways to simplify compliance and reduce risk with built-in controls using compliance management.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Commit Countdown, Day 4! 🪩
With Duo Agent Platform, multiple agents can handle your routine tasks simultaneously.
Whether you deploy four or 40 agents, they can provide project status updates, fix bugs, and conduct code reviews, freeing up your time to focus on strategic technical work that requires creativity and expertise. -
🦊 GitLab
@gitlab
Commit Countdown, Day 5! 🪩
53% of DevSecOps teams use more than 5️⃣ security tools. That's 5 dashboards, 5 logins, and 5 places to check before you can ship.
GitLab consolidates everything in one view.
As your company heads into the new year, replace fragmented toolchains with a single platform that encompasses planning, coding, security, and compliance, reducing the time your team loses to inefficient processes. -
🦊 GitLab
@gitlab
Commit Countdown, Day 7! 🪩
Strengthen your security posture with scans that run automatically.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Commit Countdown, Day 8! 🪩
Security scans, CI results, approvals, and code review, all in your merge request. No plugins, no extra tabs.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
No matter how tangled the year’s branches become, a good merge always brings everything together.
-
🦊 GitLab
@gitlab
Commit Countdown, Day 9! 🪩
According to GitLab's Global C-Suite Insights Survey 2025, 9 out of 10 executives agree that in the AI era, software development isn't just an expense, it's an economic growth engine for companies.
As 2025 wraps up, we’d love to see your thoughts in the comments! What will unlock the most growth for you in 2026?
A) Using AI agents to free up my time
B) Getting AI tools for my team to automate more
C) Modernizing our legacy systems
D) Strengthening our security and compliance
E) Something else (tell us!) -
🦊 GitLab
@gitlab
Commit Countdown, Day 10! 🪩
The best present makes your pipeline fly.
With GitLab Duo Agent Platform, multiple AI agents work with you in parallel to speed up planning, coding, testing, securing, and shipping.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Some celebrate with carols, we celebrate with commits!
Join us for the Commit Countdown, your daily drop of insights, interactive experiences, and product discoveries to power your 2026.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Live Coding Session: Digging Into Contributors' Garden x.com/i/broadcasts/1ynKOMRNOOvJR
-
🦊 GitLab
@gitlab
What’s new in GitLab 18.7? Watch as GitLab CEO Bill Staples and Distinguished Engineer Shekhar Patnaik break down the newest updates.
This release takes another important step in evolving GitLab Duo Agent Platform, bringing automation, control, and clarity to engineering teams at scale.
Watch the full video to see it in action.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Gitlab 18.7 is live!🚀
Here are the new capabilities that will help teams automate confidently while maintaining control:
🤖 SAST False Positive Detection Flow that cuts security review noise
📊 Data Analyst Agent for exploring GitLab data using natural language
🔧 Dynamic Input Selection for intuitive pipeline triggers without editing YAML
⚙️ Custom Agent and Flow Versioning to control exactly which variants run in your projects
⚠️ Warn Mode for MR Approval Policies that surfaces violations without blocking merges
Full release notes: about.gitlab.com/releases/2025/12/18/gitlab-18-7-released/ -
🦊 GitLab
@gitlab
Adversarial agents are lowering the barriers to executing complex cyberattacks. Hackers now use AI to navigate infrastructure and find security weaknesses with unprecedented speed and sophistication.
Julie Davila, our VP of Product Security, predicts that the exploitability of every vulnerability has just increased. Foundational security hygiene (e.g., SBOMs and efficient patch management) will be essential to reduce risk.
What's top of mind for Julie: Attackers have the AI advantage. Defenders need to catch up, fast. -
🦊 GitLab
@gitlab
Mercedes-Benz knows that security and compliance are more critical now than ever.
That’s why it trusted GitLab as its unified platform of choice, ensuring security for developers through every step of the process.
Hear more from @MercedesBenz's IAA Mobility 2025 talk here: -
🦊 GitLab
@gitlab
Learn about our AI-assisted localization infrastructure – with docs-as-code principles – that expands access to critical product documentation. about.gitlab.com/blog/how-we-built-and-automated-our-new-…
-
🦊 GitLab
@gitlab
Two new premium developer roles will dominate 2026: Cognitive Architects who design "blueprints of thought" for AI agents, and AI Guardians who validate non-deterministic outputs and audit security vulnerabilities.
Emilio Salvador, our VP of Strategy & Developer Relations, predicts that companies will pay premium salaries for developers who bridge human creativity with AI capability and ensure security from prompt to production.
What's top of mind for Emilio: 99% of executives believe human contributions remain valuable, and these emerging premium developer roles represent the future. -
🦊 GitLab
@gitlab
Our engineers at GitLab collaborate beyond our virtual walls. We're proving that being #remoteandtogether has no limitations.
Our open core codebase invites co-creation from anyone, including customers, students, passionate developers, and weekend contributors. This is what happens when thousands of minds collaborate across borders to build the platform they use and love. 🧡 -
🦊 GitLab
@gitlab
Our VP of Americas and Public Sector Bob Stevens shares how AI will transform government operations in 2026.
We’ll cue you in:
1️⃣AI-powered Federal IT modernization
2️⃣ Reactive to proactive cybersecurity
3️⃣Democratizing development
Read more in @cyberdefensemag starting on page 269. Read more here: www.cyberdefensemagazine.com/newsletters/december-2025/fi… -
🦊 GitLab
@gitlab
We’ve got tips, tricks, and teachable moments during each monthly episode of The Developer Show. 🍎
Should you use Codex or Haiku, or Sonnet?🤔 We’ve got some opinions!
Check out this clip and make sure to join us for our next episode of The Developer Show going live on December 19th at 5 p.m. UTC! -
🦊 GitLab
@gitlab
We loved connecting with you at #awsreinvent 2025!
Thank you to everyone who visited us at the GitLab booth last week. We solved hard problems, made connections, and shared ideas that help co-create the software that powers the world.
Missed us? Get a behind-the-scenes look at the booth, and we'll see you at the next one!
@awscloud @AWSEvents -
🦊 GitLab
@gitlab
Organizations are facing a "shadow AI" problem as teams spin up autonomous agents without centralized oversight. Traditional access control systems weren't designed for autonomous agents directing other agents.
Michelle Gill, our Sr. Director of Engineering, predicts that the most successful organizations will implement governance platforms that track which agents are running, the resources they consume, the business value they deliver, and agent-to-agent interactions.
What's top of mind for Michelle: Visibility alone isn't enough; we need strategic governance for the agent era. -
🦊 GitLab
@gitlab
Automate embedded systems compliance with GitLab and CodeSonar. about.gitlab.com/blog/automate-embedded-systems-complianc…
-
🦊 GitLab
@gitlab
Learn how to carry out the full migration from Azure DevOps to GitLab using GitLab Professional Services migration tools — from planning and execution to post-migration follow-up tasks. about.gitlab.com/blog/migration-from-azure-devops-to-gitlab/
-
🦊 GitLab
@gitlab
Take a deep technical dive into GitLabs deployment pipeline, including progressive rollouts, Canary strategies, database migrations, and multiversion compatibility.
about.gitlab.com/blog/continuously-deploying-the-largest-… -
🦊 GitLab
@gitlab
That's a wrap on #awsreinvent 2025.
Thanks to everyone who grabbed a GitLab-sponsored Hydrate and Help water bottle. Every refill supported @charitywater's work building clean water systems. -
🦊 GitLab
@gitlab
What really determines AI success in software development teams? 👀
Some may say it’s developer advocacy for AI; others may say it’s top-down pressure.
Our very own Emilio Salvador and Jessie Young chat with Nathen Harvey, Google Cloud's DORA team lead, on the success of AI implementation.
🦊 GitLab
@gitlab
Tune in here: about.gitlab.com/the-source/ai/webcast-nov18-dora-gitlab-…
-
🦊 GitLab
@gitlab
We reported our Q3 fiscal year 2026 results on December 2, 2025 and announced the appointment of Jessica Ross as chief financial officer, effective January 15, 2026. You can learn more in our full earnings report below:
ir.gitlab.com/news/news-details/2025/CORRECTING-and-REPLA…This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Viva Las re:Invent 🎰
Swing by booth 521 at #awsreinvent where our experts will discuss:
✅ AI-powered DevSecOps workflows
✅ Platform capabilities tailored to your needs
✅ Solutions for your biggest dev challenges
Learn more: about.gitlab.com/events/aws-reinvent/ -
🦊 GitLab
@gitlab
CSPs expect speed and reliability at once, and Ericsson OSS/BSS found a way to deliver both. Working with GitLab, @EricssonSoftw consolidated its DevSecOps toolchain into a single platform, transforming how telecoms software reaches global markets.
This resulted in 50% faster deployments, 130,000 hours saved over 6 months, and a 10x increase in testing scenarios, delivering faster and more reliable deployments that keep billions of subscribers connected worldwide.
Learn more about our collaboration: about.gitlab.com/customers/ericsson/
#oss #bss #telecommunications -
🦊 GitLab
@gitlab
🎬 Watch Fatima as she unpacks the powerful new features in GitLab 18.6, including GPT-OSS-120B support, enhanced Duo agents, and Web IDE for air-gapped environments.
Plus: New research reveals the "AI Paradox" costing dev teams nearly a full workday per week.
Catch up on our latest edition of the Monday Merge 👇
www.linkedin.com/feed/update/urn:li:activity:740131460931…This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
#awsreinvent 2025 kicks off next week.
As you put the final touches on your prep, what is one thing you can’t come to re:Invent without? Let us know in the comments. -
🦊 GitLab
@gitlab
At GitLab Epic Conference London, we heard directly from Chris Hutchison from Barclays about how their engineering teams are transforming with GitLab. There's nothing quite like hearing real customer stories from the people living it every day, serving 48M+ customers worldwide while modernizing their platform.
As Chris put it, "The proof is in the pudding." Engineers across Barclays are actively sharing how things have changed, and that authentic feedback is what drives us forward. -
🦊 GitLab
@gitlab
The AI talent paradox: Companies that replace expertise with tools will lose to those that amplify expertise with tools.
The winners? Organizations that double down on collaborative learning while embracing AI as an amplifier, not a replacement.
GitLab’s Lee Faus digs in deeper in his article on The Source.
about.gitlab.com/the-source/ai/the-next-wave-of-devsecops… -
🦊 GitLab
@gitlab
Didn’t get a chance to see our latest episode of The Developer Show?
We’re talking all things agentic chat and breaking down the functions of various GitLab agents👇
📺 Watch the full episode here:This media couldn't be displayed. See it on the original post.
🦊 GitLab
@gitlab
Live Coding with GitLab 18.6 Release Features x.com/i/broadcasts/1MnGnPmgdDexO
-
🦊 GitLab
@gitlab
GitLab’s Vulnerability Research team uncovered a widespread npm supply chain attack involving a destructive malware variant with a built-in “dead man’s switch.”
The malware spreads through compromised npm packages, steals credentials, and contains a data-wiping payload if its channels are disrupted.
We’re sharing early details to help developers and security teams assess exposure and stay protected.
👉 Read the full analysis: about.gitlab.com/blog/gitlab-discovers-widespread-npm-sup… -
🦊 GitLab
@gitlab
Our customers put the EPIC in GitLab Epic Conference London!
From live demos that brought GitLab to life on stage to powerful customer stories that reminded us why this work matters, this event captured what happens when innovation meets real-world impact. -
🦊 GitLab
@gitlab
The Controversial Ranking "Most stressful phrases in tech (ranked):
5. The build is failing
4. Can you hop on a quick call?
3. It was working yesterday
2. I'll just push directly to main
1. Don't worry, I didn't touch your code -
🦊 GitLab
@gitlab
Experience AI that works the way you do.
GitLab 18.6 delivers more than features. It's about GitLab Duo Agent Platform becoming an embedded part of everyday workflows, supporting everyone from experienced developers to newcomers launching their first project.
Watch this demo to see it in action. Learn more here: about.gitlab.com/blog/gitlab-18-6-from-configuration-to-c…This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Live Coding with GitLab 18.6 Release Features x.com/i/broadcasts/1MnGnPmgdDexO
-
🦊 GitLab
@gitlab
GitLab 18.6 is here: From configuration to control. Learn more: about.gitlab.com/blog/gitlab-18-6-from-configuration-to-c…
GitLab 18.6 advances AI integration across the software development lifecycle with enhancements that give teams greater choice, control, and compliance in planning, building, and securing software.
Here’s what’s new:
🔄 Greater flexibility to select the right models for your workflows
➕ Extend AI into secure and self-managed environments
💪 Strengthen visibility and governance across the SDLC -
🦊 GitLab
@gitlab
Developers spend only 21% of their time actually building apps. The rest? Manual processes and context-switching.
Join GitLab's Lee Faus, @SouthwestAir's Grant Morris, and @AWS's Kyle Seaman at #awsreinvent to learn how #amazonq combined with the GitLab DevSecOps platform can help change that by offering agentic AI workflow automation across the entire software development lifecycle.
In this breakout session (AIM102-S) you’ll learn how to:
✨ Boost productivity
✨ Maintain security & compliance
✨ Implement agentic AI workflows
Don't miss "Developers Soar at Southwest Airlines®: A Journey to AI-Powered DevSecOps (sponsored by GitLab) (AIM102-S)."
Learn more.🔗 about.gitlab.com/events/aws-reinvent/
@AWSEvents -
🦊 GitLab
@gitlab
#awsreinvent is happening in two weeks, and the forecast calls for cloudy with a chance of lightning talks. ☁️⚡
Join us at booth #521 for exciting lightning talks and one-on-one demos with GitLab experts.
@AWSEvents
Learn more. -
🦊 GitLab
@gitlab
Learn about release contributions, including the new git-last-modified(1) command, improvements to history-rewriting tools, and a new maintenance strategy. about.gitlab.com/blog/whats-new-in-git-2-52-0/
-
🦊 GitLab
@gitlab
97% of organizations are using or are planning to use AI in software development, but DevSecOps teams trust #ai to handle only 37% of daily tasks without human review.
The challenge extends beyond trust. GitLab surveyed 3,266 DevSecOps professionals and found that teams are losing nearly 7 hours per week to tool sprawl.
60% use more than 5 development tools, and 49% juggle more than 5 AI tools, creating bottlenecks that prevent organizations from capitalizing on AI's speed advantages.
The solution? Platform engineering approaches that can address the interconnected requirements of AI orchestration, governance, and compliance.
Read the full report to learn how leading organizations are balancing AI acceleration with human expertise. ➡️ about.gitlab.com/developer-survey/ -
🦊 GitLab
@gitlab
This guide explains how to deploy an ADK-based AI agent to Google Kubernetes Engine using GitLab's AI-powered DevSecOps platform, with ease and security. about.gitlab.com/blog/secure-ai-agent-deployment-to-gke/
-
🦊 GitLab
@gitlab
Finish this sentence: I knew I was a real developer when I spent _____ hours debugging only to find _____.
-
🦊 GitLab
@gitlab
Here’s what to look forward to from GitLab at #awsreinvent 2025.
Mark you calendars for Dec. 1-5 booth #521!
about.gitlab.com/events/aws-reinvent/ -
🦊 GitLab
@gitlab
Purpose > tools. Kelsey Hightower joined GitLab on The Developer Show and discussed the importance of purpose-driven tools.
📺 Watch the full replay here:This media couldn't be displayed. See it on the original post.
🦊 GitLab
@gitlab
Interview with Kelsey Hightower and the GitLab 18.5 Release Q&A x.com/i/broadcasts/1djGXWEmLOdKZ
-
🦊 GitLab
@gitlab
🤩 GitLab is on-site at KubeCon NA 2025, booth #120.
At our booth you can win swag by 👇
🧩 Solving a Rubik’s Cube the fastest each day
🌏 Sharing the location of your first commit on our commit sticker wall
⚙️Helping us fix our failing CI/CD pipeline
👟 Competing for a lapel pin-pack with a variety of challenges -
🦊 GitLab
@gitlab
Bill Staples, CEO, takes the stage at GitLab Epic Conference London to talk about the rise of the Agents! A journey of AI and DevSecOps with a focus on who GitLab is today and where we are going.
This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
This guide explains how to deploy an ADK-based AI agent to Google Kubernetes Engine using GitLab's AI-powered DevSecOps platform, with ease and security. about.gitlab.com/blog/secure-ai-agent-deployment-to-gke/
-
🦊 GitLab
@gitlab
Plot twist! AI won't replace engineers; it will actually create more jobs.
GitLab surveyed 3,266 professionals and found that AI is reshaping software development roles, creating a workforce evolution:
🟠 76% believe AI will create more engineering jobs, not fewer
🟠 87% view AI adoption as essential for career longevity
🟠 87% want more organizational investment in AI upskilling
Read the full report to discover how top companies are addressing both. ➡️ about.gitlab.com/developer-survey/ -
🦊 GitLab
@gitlab
Follow this guide to learn about stronger controls around pipeline customization, including how to implement explicit declarations, type safety, and validation.
about.gitlab.com/blog/migrate-from-pipeline-variables-to-… -
🦊 GitLab
@gitlab
Problem? Solved.
If you could build your dream AI agent, what would it do, and more importantly, what problem would it solve? -
🦊 GitLab
@gitlab
One-size-fits-all deployment strategies? Not on our watch.
While others limit your options, GitLab maintains complete deployment flexibility, including self-managed, cloud, or hybrid, all within a single AI-powered DevSecOps platform.
Learn more here: about.gitlab.com/blog/atlassian-ending-data-center-as-git… -
🦊 GitLab
@gitlab
Pipeline failed? Deploy an agent to fix it while you grab coffee ☕
Multiple agents. Working in parallel. Zero context-switching.
This is the future of dev work. -
🦊 GitLab
@gitlab
Our async culture helps foster faster collaboration across time zones and deliver results to our customers.
Courtney shares why working #remoteandtogether at GitLab helped her team succeed! 🧡 -
🦊 GitLab
@gitlab
🎪 Viva Las DevSecOps! We’re ready for AWS re:Invent.
Join us at AWS re:Invent (booth 521) to learn how GitLab is delivering powerful AI capabilities built directly into the platform. Check out one-on-one demos with our experts as we explore the latest capabilities with Amazon Q and GitLab Duo.
Learn more in the link: about.gitlab.com/events/aws-reinvent/ -
🦊 GitLab
@gitlab
We’re one week out from KubeCon NA. If you’re heading to the conference, stop by booth 120.
We’ve got demos and swag to share with you 😉
Register for our AI workshop here: events.gitlab.com/e/build-with-gitlab-duo-hands-on-ai-wor… -
🦊 GitLab
@gitlab
"AI is amazing, but so is real intelligence, and how do we protect the dignity of people that do this kind of work?" 💡
Kelsey Hightower doesn't shy away from the hard questions in tech. In our latest Developer Show episode, he reflects on 30+ years of industry shifts, from system administration to DevOps to platform engineering, and what makes this AI moment different.
This is the kind of honest, human-centered tech dialogue we need more of.
👉To catch the full recap, you can watch here:
🦊 GitLab
@gitlab
Interview with Kelsey Hightower and the GitLab 18.5 Release Q&A x.com/i/broadcasts/1djGXWEmLOdKZ
-
🦊 GitLab
@gitlab
🎬 The November Monday Merge is live, and Fatima's got the scoop on everything happening this month!
Make sure to check out the Monday Merge newsletter for all the details, links, and everything you need to stay in the loop! 💜
www.linkedin.com/pulse/new-agents-smarter-security-hands-…This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
This Halloween, beware what lurks in your workflow… because the scariest creatures aren’t in costumes, they’re in your code.
-
🦊 GitLab
@gitlab
If your stack's under siege and it don't look good...
Who you gonna call? GitBusters -
🦊 GitLab
@gitlab
Time for a dev check-in. 🧑💻
Describe your workflow in emojis only. -
🦊 GitLab
@gitlab
Stop context-switching. Start shipping code.
GitLab 18.5 brings AI agents into your daily workflow. From the UI to your IDE.
Watch one developer use AI agents to:
➡️Get onboarded on a new codebase in minutes
➡️Transform vague tickets into detailed technical specs
➡️Build features with intelligent code suggestions
➡️Get automated code reviews before human review
➡️Triage and prioritize security vulnerabilities with detailed remediation plans automaticallyThis media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Have you registered yet? 👀
We’re meeting up with devs in Atlanta on November 10th for an AI workshop.
Here’s what you can expect:
✔️Ship a complete cloud-native app in hours, not days
✔️Experience AI-powered development flows that deliver real value
✔️Learn GitOps and the Kubernetes Agent hands-on
✔️Connect with fellow developers over actual builds
Learn more. ➡️ events.gitlab.com/e/build-with-gitlab-duo-hands-on-ai-wor… -
🦊 GitLab
@gitlab
Interview with Kelsey Hightower and the GitLab 18.5 Release Q&A x.com/i/broadcasts/1djGXWEmLOdKZ
-
🦊 GitLab
@gitlab
Still manually upgrading legacy Java apps? There's a better way.
Transform Java 8 ➡️ Java 17 with AI-powered automation. One command. Full traceability. Zero functionality loss.
See GitLab Duo with Amazon Q modernize an entire codebase, from source files to pom.xml, in this quick demo.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Here’s what we know: SAST adoption hinges on both accuracy and speed.
Last year, we introduced Advanced SAST, and now we’re building on that foundation with a set of performance enhancements to boost the dev experience.
Learn more in the blog listed in the comments below ⬇️
🦊 GitLab
@gitlab
Full blog: about.gitlab.com/blog/delivering-faster-and-smarter-scans…
-
🦊 GitLab
@gitlab
For Cybersecurity Awareness Month, check out this guide on how to transform federal software development with AI agents that accelerate delivery, reduce costs, and modernize legacy systems for mission success.
Step 1️⃣: Build foundational AI proficiency
Step 2️⃣: Establish governance frameworks and compatibility standards
Step 3️⃣: Deploy and expand AI agent capabilities strategically
Step 4️⃣: Enhance performance through monitoring and training
Learn more here: about.gitlab.com/the-source/ai/ai-agents-for-government-a… -
🦊 GitLab
@gitlab
GitLab 18.5 introduces the Security Analyst Agent. Ask "Which vulnerabilities are most critical?" in natural language and get intelligent triage with exploit analysis, reachability data, and automated issue creation.
Watch the Security Analyst Agent help prioritize critical vulnerabilities for remediation in minutes, saving hours of manual investigation time. GitLab 18.5 helps turn security noise into intelligent prioritization.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
At GitLab, we put the “Sec” in DevSecOps.
In this episode of Fed Tech Podcast Bob Stevens touches on why this is one of the most important parts of the software development lifecycle.
Full episode here: www.theoakmontgroupllc.com/ep-274-ai-driven-devsecops-acc… -
🦊 GitLab
@gitlab
Security shouldn’t be a bandage fix, but instead a core practice implemented from the start. 🩹
Don’t worry, Fern’s got you covered! He dives into how GitLab is empowering developers to build applications that are secure from the start.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
GitLab 18.5 is live! 🚀
57 improvements across the platform, powered by 278 community contributions.
From AI agents to security enhancements, this release has something for every team.
New in GitLab 18.5:
🤖 AI agents that understand your workflow
🔒 Security tools that prioritize real risk
📦 Visual registry management
🏠 Personalized homepage
Full release notes here: about.gitlab.com/releases/2025/10/16/gitlab-18-5-released/ -
🦊 GitLab
@gitlab
GitLab 18.5 brings AI agents into your everyday workflow, security insights that cut through the noise, and a reimagined interface that keeps your AI teammate always in view.
Plus: Valuable new platform security and DevOps features.
This is the future of software development. Watch the full video to see it in action.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Claude Haiku 4.5 now in GitLab Duo: lightning-fast AI assistance with 73.3% on SWE-bench Verified, built for developers who need speed without compromise.
Read more here: about.gitlab.com/blog/claude-haiku-4-5-now-available-in-g… -
🦊 GitLab
@gitlab
GitLab CISO Josh Lemos breaks down how we approach AI governance, emphasizing the importance of working with vendors to ensure security requirements are baked into AI tools from the start.
GitLab’s AI Transparency Center also helps customers understand exactly which model powers each feature so they can make informed decisions about how Duo accesses data.
Key takeaway: AI governance starts with understanding how AI will shape risk and your attack surface. Then, work in partnership with vendors to build the right security assurances for your organization and customers. -
🦊 GitLab
@gitlab
🚄 How Germany's national railway company built a world-class digital platform.
Deutsche Bahn's DB Navigator app handles 1.5 billion travel requests annually, serving as the digital gateway for millions of travelers. But building software at this scale requires infrastructure that matches the precision of German engineering.
Here's how they did it:
✅ 400 people across 35 teams collaborated on GitLab to build DB Navigator from the ground up
✅ 11,500 active users managing 75,000 repositories
✅ 91% success rate in continuous deployments
✅ 15% reduction in infrastructure costs
✅ Replaced complex Jenkins setup with unified DevSecOps platform
The result? Faster development, automated compliance, and significantly happier developers.
Read the full customer story here about.gitlab.com/customers/deutsche-bahn-ag/ -
🦊 GitLab
@gitlab
Real talk: How is AI actually changing your day-to-day coding?
We are curious about what's working (and what's just hype). Are you using AI coding assistants? Code review tools? Documentation generators?
Drop your thoughts below 👇 -
🦊 GitLab
@gitlab
Explore how federal agencies can balance AI innovation with cybersecurity as traditional security measures fail to keep pace with rapid AI development cycles. about.gitlab.com/the-source/ai/securing-federal-ai-from-l…
-
🦊 GitLab
@gitlab
Learn how to simplify complex CI/CD pipelines with these best practices for sharing data in more modular pipeline setups. about.gitlab.com/blog/variable-and-artifact-sharing-in-gi…
-
🦊 GitLab
@gitlab
Devs are using AI to generate code faster than security teams can secure it. 75% of exploits target memory safety vulnerabilities. Supply chain attacks are escalating.
The question isn't whether your systems will be targeted—it's whether they'll be resilient.
We recently hosted a fireside chat for Cybersecurity Awareness Month exploring why secure-by-design isn't just best practice, but mission-critical. Our panel of experts discusses the security challenges keeping government CISOs awake at night.
🦊 GitLab
@gitlab
📹 Watch the replay: Secure by Design in an Uncertain World www.youtube.com/watch?v=vWpRxBCZmdM
-
🦊 GitLab
@gitlab
Executives say software development has an agentic future, but some organizations are behind in their AI governance practices.
In Josh Lemos’ byline for Cyber Defense Magazine, he shares how CISOs can minimize this AI governance gap.
📖 more here:
www.cyberdefensemagazine.com/newsletters/october-2025/mob… -
🦊 GitLab
@gitlab
Learn how @Avalara, Inc., a global leader in automated tax solutions, moved beyond legacy systems and achieved dramatic growth and efficiency by adopting GitLab's end-to-end #devsecops platform.
The solution? Adopting GitLab Premium as their single platform. This strategic move enabled modernization, fostering global team collaboration, automating critical processes, and implementing consistent security gates.
The impact, recorded through Uplevel has been profound:
✔️ 1,100% increase in deployment frequency
✔️ 90% reduction in deployment problems
✔️ Merge request times cut from 4 weeks to hours -
🦊 GitLab
@gitlab
⚡ "Security should be an enabler of software innovation, not a blocker."
Julie Davila, VP of Product Security at GitLab, shares critical advice for Cybersecurity Awareness Month: Organizations adopting AI must prioritize governance from the start.
Her recommendation? Implement SLSA-aligned controls, create "paved roads" for AI adoption with pre-approved models, and apply security controls to AI-generated code the same way you would human-written code, just earlier in the workflow.
🦊 GitLab
@gitlab
Read her insights here: vmblog.com/archive/2025/10/02/the-cybersecurity-reality-c…
-
🦊 GitLab
@gitlab
Merge conflicts? Try merging in and out of the fast lane 🏁
Our VP Ben Caller just navigated 10,000 corners at race speed to finish the Tour de Corse Historique: 80/420🏆
8 days in Corsica. Zero merge conflicts. Mission complete. ✅ -
🦊 GitLab
@gitlab
What do we want?!
Built-in compliance!
When do we want it?!
NOW.
We heard you loud and clear. Here is how GitLab is ensuring built-in compliance at every level.This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Do you know if your tools are using your prompts to train their models? Bob Stevens has some food for thought on why it might be best to switch over to a self-hosted model.
Listen in 👇 -
🦊 GitLab
@gitlab
The GitLab Duo Agent Platform Gemini CLI Extension brings powerful GitLab context for issues, merge requests, and more directly into your Gemini CLI to help you build software faster.
-
🦊 GitLab
@gitlab
Code reviews slowing you down? Same. 😅
Watch as GitLab Duo catches bugs, style issues, and that missing semicolon you ALWAYS forget, then suggest fixes with one click. -
🦊 GitLab
@gitlab
Federal software supply chain resilience in 2025: 48,000+ new Common Vulnerabilities and Exposures (CVEs) expected, with 28% exploited within 24 hours.
The exploitation window between vulnerability disclosure and exploitation is shrinking, but so are modernization timelines. Liz Burrows and Rob Smith, of GitLab’s public sector team, sat down to discuss how AI is transforming legacy system modernization in months, rather than years.
The bottom line? Stop adding tools. The agencies leading in 2026 are consolidating into single platforms with AI built in, turning technical debt into mission advantage.
Watch the full conversation to hear what's driving secure, AI-accelerated software development in the public sector. 👇This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Whether you’re attending KubeCon NA 2025 or just in the Atlanta area, join us for a hands-on AI workshop on Nov. 10 to learn how to ship code with GitLab Duo.
We’ll be building projects, troubleshooting, and diving into AI-assisted workflows together!
Register now:
🦊 GitLab
@gitlab
Register for the Build with GitLab Do: Hands-On AI Workshop here: events.gitlab.com/e/build-with-gitlab-duo-hands-on-ai-wor…
-
🦊 GitLab
@gitlab
The best CTOs aren't defined by a single leadership style—they adapt to what their company needs right now.
GitLab's CTO Sabrina Farmer breaks down three operational models:
1. Builder (create products customers want)
2. Strategist (align tech vision with market realities)
3. Guardian (protect customer experience through operational excellence).
The key insight? Exceptional technical leadership never loses sight of the customer. Your technical architecture doesn't matter if your product doesn't solve their problems better than alternatives.
www.fastcompany.com/91409560/how-technical-leaders-drive-… -
🦊 GitLab
@gitlab
🎥 October's Monday Merge is here with Fatima! ✨
This month we're covering:
🚀 GitLab 18.4's AI-powered features
📊 FinServ leaders seeing 53% revenue growth from AI
🚄 Deutsche Bahn's transformation story
🌍 Our October events across the globe
💻 GitLab Hackathon (ends Oct 8!)
Read all about it in our newsletter: www.linkedin.com/pulse/ai-native-development-750b-finserv…This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
How many vibe-coders does it take to write a light bulb application?
None, it’s all done by AI. -
🦊 GitLab
@gitlab
What does DAST (Dynamic Application Security Testing) really stand for?
Developers
Advancing
Security
Talk
Good thing GitLab DAST advances security in your live application - right from your CI/CD pipeline, scheduled, or even on-demand!
🦊 GitLab
@gitlab
Read more to learn about Dynamic application security testing
about.gitlab.com/blog/comprehensive-guide-to-gitlab-dast/ -
🦊 GitLab
@gitlab
Want to know what’s new with GitLab 18.4?
We've got you covered with a complete roundup of every new feature, integration, and improvement. From AI-powered workflows to enhanced collaboration tools.
Discover how this release can transform your development process.
Catch up here: about.gitlab.com/releases/whats-new/ -
🦊 GitLab
@gitlab
Whether you’re in New Zealand or the USA, our team members co-create the software that powers our world.
That’s why Chris loves working at GitLab. 🧡 #remoteandtogether -
🦊 GitLab
@gitlab
It’s Hackathon time again from October 1 to October 7!
We can’t wait to see the GitLab community come together to contribute, learn, and even win exciting prizes.
See how you can get started: contributors.gitlab.com/hackathonThis media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Our Cybersecurity Awareness Month content is coming in hot! 🔥
Which topic are you most excited to learn about in October? -
🦊 GitLab
@gitlab
Have questions about the Knowledge Graph? Well Ben has the answers. 👇
🦊 GitLab
@gitlab
The full show is available to watch here:
🦊 GitLab
@gitlab
Q&A + Code: Exploring GitLab 18.4 and Growing the Contributor’s Garden x.com/i/broadcasts/1BdGYZLneVBJX
-
🦊 GitLab
@gitlab
Claude Sonnet 4.5 is available in GitLab Duo Pro, Duo Enterprise, and Duo Agent Platform, giving teams access to Anthropic’s most advanced model for coding and agents.
Learn more in our blog: about.gitlab.com/blog/greater-ai-choice-in-gitlab-duo-cla… -
🦊 GitLab
@gitlab
Didn’t get a chance to watch the show live?
Catch up now and hear all the great new features that came out in GitLab 18.4. Also, watch as we start to build out The Developer Show’s Contributor’s Garden project.
🦊 GitLab
@gitlab
Q&A + Code: Exploring GitLab 18.4 and Growing the Contributor’s Garden x.com/i/broadcasts/1BdGYZLneVBJX
-
🦊 GitLab
@gitlab
Pick your kryptonite 👇
-
🦊 GitLab
@gitlab
GitLab's MCP support enhances AI-powered dev workflows, connecting Duo Agent Platform as an MCP client and serving as an MCP server for external AI assistants. about.gitlab.com/blog/duo-agent-platform-with-mcp/
-
🦊 GitLab
@gitlab
GitLab was named a Leader in @Gartner_inc's 2025 Magic Quadrant™ for DevOps Platforms for the third year! 🎉 Read the report: about.gitlab.com/blog/gitlab-named-a-leader-in-the-2025-g…
-
🦊 GitLab
@gitlab
POV: You're a developer and spot ONE tiny font issue... 🔍
👀 What happens next? Bug reports, AI agents, failed pipelines, and lots of coffee ☕
Watch how modern devs turn a simple font fix into a full-stack adventure!This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Is your company taking advantage of the $750 Billion Opportunity?
New research of C-level FinServ executives reveals some interesting stats:
➡️ 99% of executives say human contributions are valuable for software development.
➡️ 95% say software innovation is now a core business priority.
➡️ They estimate a 53% increase in revenue and a 55% increase in developer productivity due to the use of AI.
The companies pulling ahead are the ones blending AI with human expertise, leveraging agentic AI with intention, aligning software strategy with business value, and building guardrails to innovate responsibly.
Explore the full FinServ C-Suite Insights Report here: about.gitlab.com/software-innovation-report/finserv/ -
🦊 GitLab
@gitlab
🎉 Announcing GitLab 18.4 with new features including GitLab Duo Model Selection (GA) and the introduction of the GitLab Duo AI Catalog!
Key highlights:
🤖 GitLab Duo Model Selection is now GA! Organizations get greater control over AI models powering development workflows
📖 Introducing GitLab Duo AI Catalog - a central library where teams can create, save, and share custom-built agents across their organization.
🧠 GitLab Knowledge Graph provides rich code intelligence across codebases for better context and planning
⚙️ End user model selection lets developers choose preferred models for Agentic Chat
🔐 CI/CD job tokens can now authenticate Git push requests
🛡️ GitLab Duo Agent Platform context exclusion protects sensitive information
☁️ Expanded AWS region support for GitLab Dedicated
Plus: Pipeline simulation against different branches, enhanced job artifact controls, OpenTofu modules support, and Duo Code Review GA on Self-Hosted!
Thank you to our community for 136 contributions! 🧡 about.gitlab.com/releases/2025/09/18/gitlab-18-4-released/ -
🦊 GitLab
@gitlab
Q&A + Code: Exploring GitLab 18.4 and Growing the Contributor’s Garden x.com/i/broadcasts/1BdGYZLneVBJX
-
🦊 GitLab
@gitlab
GitLab CEO Bill Staples joins AI engineer Angelo Rivera and Senior Director of Product Management Sarah Waldner to showcase how GitLab 18.4 advances our AI-native DevSecOps platform with groundbreaking innovations.
Watch them showcase:
📊 Knowledge Graph: Live codebase mapping in <100ms
⚙️ Agentic Chat: Intelligent workflow prioritization
🔧 Pipeline Automation: Automated failure analysis & fixes
🤖 AI Catalog: Custom agent creation & sharing
🔒 Enterprise Controls: Governance & security at scale
The Knowledge Graph transforms how agents understand your code—moving from guesswork to structural clarity across entire repositories.
This is AI-native development where agents become true collaborators, not just tools.
Ready to see the future of software engineering? Learn more here: about.gitlab.com/blog/gitlab-18-4-ai-native-development-w…This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
PSA: Make sure you save room in your calendar for 23 September at 10 a.m. PT/5 p.m. GMT.
Join us LIVE on X as we explore GitLab 18.4 with the people who know it best - our product team! This isn't just another product demo - it's your chance to get real answers from real experts in real time.
Plus, we're coding LIVE on the project YOU voted for! Tune in to watch us build the Contributor's Garden community project.
This will be an episode you don’t want to miss! 💥 -
🦊 GitLab
@gitlab
Learn how we reduced API calls on GitLab's CI job status updates from 45 million to 3.4 million calls per day. about.gitlab.com/blog/how-we-supercharged-gitlab-ci-statu…
-
🦊 GitLab
@gitlab
DevSecOps teams can learn how to implement and configure dynamic application security testing, perform passive/active scans, and set security policies. about.gitlab.com/blog/comprehensive-guide-to-gitlab-dast/
-
🦊 GitLab
@gitlab
The vote is in! 👀
The Contributors Garden will be the community project we build on the next episode of The Developer Show. 🌱
Tune in on Tuesday, 23 September to see how we build it! -
🦊 GitLab
@gitlab
GitLab has been recognized as a Leader in @Gartner_inc's 2025 Magic Quadrant™ for AI Code Assistants for the second time! 🎉
Read the report: about.gitlab.com/gartner-mq-ai-code-assistants/ -
🦊 GitLab
@gitlab
AI is rewriting the rules of software innovation, and now every company is a software company.
Executives recognize that AI-enhanced software innovation is driving a significant economic shift, serving as a key driver of business growth and expansion.
91% report that software innovation is now a core business priority, and 58% report that their organization has experienced business growth tied to software innovation efforts over the last 12 months.
How is your company taking advantage of AI-powered software innovation? Let us know in the comments. -
🦊 GitLab
@gitlab
Did you catch our very own Bob Stevens join the Keeping IT Brief Podcast? 🎙️
He discussed the government's AI adoption journey and highlighted top concerns for organizations rapidly adopting AI, including cybersecurity threats, data privacy, and governance. -
🦊 GitLab
@gitlab
🎉 GitLab is proud to be named a Fortune Best Workplace in Technology™!
When 96% of your team feels welcome from day one, you're building something special. 💜
Shoutout to our amazing GitLab team! -
🦊 GitLab
@gitlab
GitLab and @accenture are pleased to announce a global reseller agreement with a global reach. As an authorized GitLab Reseller and Professional Services Provider, Accenture can now offer GitLab directly to customers and through the AWS Marketplace.
Post not available here, view on X
🦊 GitLab
@gitlab
This collaboration combines GitLab's industry-leading DevSecOps platform with Accenture's world-class implementation and consulting services to enable organizations to build and deliver secure software at scale.
Joint customer benefits:
✔️ Direct access to GitLab's comprehensive DevSecOps platform via Accenture.
✔️ AWS Marketplace fulfillment capabilities include consolidated billing, flexible payment options, simplified procurement, and reduced contract complexity.
✔️ Expert implementation and adoption services via Accenture Consulting and Advisory, and Cloud First teams globally.
🦊 GitLab
@gitlab
We're excited to help our joint customers accelerate innovation, streamline development processes, and strengthen their security posture to achieve their business objectives more effectively!
about.gitlab.com/blog/gitlab-and-accenture-announce-globa… -
🦊 GitLab
@gitlab
Optimize git clone operations in any environment — up to 93% reduction in clone times and 98% reduction in disk space usage — with the Git Much Faster script.
Read more here: about.gitlab.com/blog/supercharge-your-git-workflows/ -
🦊 GitLab
@gitlab
At GitLab, Julie Davila, VP of Product Security, leads efforts to secure the GitLab platform, its environments, and the software supply chains customers rely on.
She recently sat down withTechnology Magazine to discuss
1️⃣ How to deploy AI securely
2️⃣ Upskilling the workforce to combat AI-driven social engineering attacks
3️⃣ Balancing innovation and risk in the age of AI
More here: technologymagazine.com/news/how-gitlab-powers-the-worlds-…. -
🦊 GitLab
@gitlab
Okay, let’s hear it… we want to share some creative answers on our next Developer Show 😉
-
🦊 GitLab
@gitlab
⚡ New GitLab Duo Agent Platform Flow: Issue ➡️ MR in minutes
No more hunting through codebases for simple UI tweaks.
1️⃣ Create issue with clear requirements
2️⃣ Click "Generate MR with Duo"
3️⃣ Review proposed changes
4️⃣ Merge
A way for you to spend less time on setup and more time building! 🙌This media couldn't be displayed. See it on the original post.
🦊 GitLab
@gitlab
Learn more here: about.gitlab.com/blog/vibe-coding-with-gitlab-duo-agent-p…
-
🦊 GitLab
@gitlab
🧑💻Talent gaps are real and the future still needs human innovators.
99% of executives say human contributions are valuable for software innovation, with creativity and strategic vision ranking as the most valued qualities.
So what’s the right balance for the human-AI partnership?
73% believe that human input for the human-AI partnership should be at least 50/50, with only 27% believing that AI should do the majority of the work.
The companies pulling ahead are the ones blending AI with human expertise, leveraging agentic AI with intention, aligning software strategy with business value, and building guardrails to innovate responsibly.
Download the full report learn more: about.gitlab.com/software-innovation-report/ -
🦊 GitLab
@gitlab
AI is changing the software development landscape, but it’s not eliminating the need for skilled engineers.
To set software teams up for success in the AI era, companies must let humans focus on tasks that AI cannot perform well.
According to our latest research, executives aspire to build human-AI partnerships that split software development work 50-50, though the majority report that AI is currently only handling about 25% of the work.
Hear more from GitLab’s CTO, Sabrina Farmer, about how companies that frame upskilling as an investment in the human-AI partnership can deliver competitive advantages. -
🦊 GitLab
@gitlab
GitLab has earned ISO/IEC 42001 certification, the first international standard for establishing, implementing, maintaining, and improving an Artificial Intelligence Management System (AIMS).
This certification covers our comprehensive AI offering, GitLab Duo, including our new Agent Platform (now in public beta). As AI transforms every industry, organizations need trusted partners who prioritize responsible AI development.
Key benefits for our customers:
✅ Enhanced trust through globally recognized AI governance standards
✅ Strategic risk management across operational, technical, and security domains
✅ Continuous improvement through regular audits and assessments
✅ Alignment with emerging AI regulations like the EU AI Act
Leading the way in responsible AI-powered DevSecOps. 💡
🦊 GitLab
@gitlab
Learn more here: about.gitlab.com/blog/gitlab-achieves-iso-iec-42001-certi…
-
🦊 GitLab
@gitlab
Last week on The Developer Show we had a special guest, Ebru Engwall, join us and she shared a demo on building an AI agent. Then we voted on what our collective community project should be. Listen to the options.
Did you vote?! 👀 There’s still time to vote in the comments 👇 -
🦊 GitLab
@gitlab
We reported our Q2 fiscal year 2026 results on September 3, 2025. You can learn more in our full earnings report below:
ir.gitlab.com/news/news-details/2025/GitLab-Reports-Secon…This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Learn how to update your application in minutes with our newest agent Flow that takes developers from idea to code. about.gitlab.com/blog/vibe-coding-with-gitlab-duo-agent-p…
-
🦊 GitLab
@gitlab
Let us drop some knowledge on you: Scaling is never "done.” It requires continuous reassessment and adaptation.
And we learned that from our CTO, Sabrina Farmer.
📖If you’d like to learn more, you can read her insights on sustainable scaling at @thenewstack. -
🦊 GitLab
@gitlab
GitLab now allows the use of fine-grained permissions for CI/CD job tokens, enhancing the security of your software supply chain. about.gitlab.com/blog/fine-grained-job-tokens-ga/
-
🦊 GitLab
@gitlab
Discover how CTOs can unlock $750 billion in AI value through strategic leadership, platform thinking, and team restructuring for competitive advantage. about.gitlab.com/the-source/ai/how-ctos-can-capture-the-7…
-
🦊 GitLab
@gitlab
"The questions tech leaders are asking today are leading to make-or-break decisions."
GitLab CLO Robin Schulman breaks down why platform control and AI transparency matter more than ever.
Read the full insights on our blog ➡️ about.gitlab.com/blog/why-enterprise-independence-matters…This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Learn about this new ISO certification, our associated GitLab Duo features, and our commitment to responsible AI development. about.gitlab.com/blog/gitlab-achieves-iso-iec-42001-certi…
-
🦊 GitLab
@gitlab
Learn how GitLab supports Rust development through its CI/CD capabilities, security scanning, dedicated Rust integrations, AI features, and more. about.gitlab.com/blog/secure-rust-development-with-gitlab/
-
🦊 GitLab
@gitlab
Did you catch this month’s edition of the Monday Merge?
Check out our LinkedIn Newsletter to catch all the latest and greatest:
www.linkedin.com/posts/gitlab-com_september-monday-merge-…This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
It’s not just “software”, it’s not just “code”. It’s powering the industries that fuel our world.
GitLab’s Solutions Architect, EMEA Mam Joof shares why working #remoteandtogether makes her proud. 🧡 -
🦊 GitLab
@gitlab
What if we told you there's a way to get 127x faster lead times AND reduce costs by 30-40%?
Most organizations avoid CI/CD modernization because of the million dollar consulting fees and months long timelines.
Game changer: Agentic AI reduces migration time by 81% and makes consolidation finally achievable.
The numbers don't lie:
📈 5x increase in translation efficiency
📉 25% fewer incidents, 50% faster resolution
🚀 182x more deployments per year
Download our comprehensive white paper to see the implementation framework, real customer examples, and ROI calculations. about.gitlab.com/the-source/ai/cicd-modernization-break-d…This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
*Clears throat* Can we have your attention, please? 🎤
Fast Co. published a piece by GitLab CTO Sabrina Farmer, and it’s giving a $750 BILLION AI opportunity. 💅
www.fastcompany.com/91384330/how-ctos-can-capture-the-750… -
🦊 GitLab
@gitlab
Exploring GitLab Release 18.3 - GitLab Duo Agent Platform and Code Review x.com/i/broadcasts/1RDxlAVgMYNKL
-
🦊 GitLab
@gitlab
Tune in tomorrow for The Developer Show, Episode 3. In this episode, we will cover:
1️⃣ GitLab 18.3 Release
2️⃣ GitLab Duo Agent Platform
3️⃣ Code Review
You won’t want to miss this: www.linkedin.com/events/exploringgitlabrelease18-3-gitl73… -
🦊 GitLab
@gitlab
✨Introducing Ebru ✨
August co-host of The Developer Show. She’s got all the info on the show. -
🦊 GitLab
@gitlab
Claude Code now runs in GitLab CI/CD pipelines 🚀
Tag @ Claude in issues or merge requests to run automated coding tasks in secure containers, with all changes following your branch protection and review workflows.
✅ Available via the @AnthropicAI API, Amazon Bedrock, and Google Vertex AI
✅ Customize Claude Code for your codebase by adding a claude.md file to your repository root
✅ Delegate code reviews, bug fixes, and implementation plans to complete routine tasks asynchronously
Get started with Claude Code in GitLab: docs.gitlab.com/user/duo_agent_platform/agent_assistant/ -
🦊 GitLab
@gitlab
🎉 Announcing GitLab 18.3 with 38 improvements including Duo Agent Platform in Visual Studio (Beta) and Embedded views!
Key highlights:
🤖 Duo Agent Platform now in Visual Studio (Beta)
📊 Embedded views powered by GLQL (GA) 🔄 Migration by direct transfer (GA)
🔐 Fine-grained permissions for CI/CD job tokens
🛠️ Code Review on GitLab Duo Self-Hosted (Beta)
⚙️ GitLab Duo CLI Agents (Experiment)
Plus: AWS Secrets Manager support, custom admin roles, enhanced wiki functionality, and much more!
Thank you to our community for 314 contributions! 🧡
about.gitlab.com/releases/2025/08/21/gitlab-18-3-released/ -
🦊 GitLab
@gitlab
GitLab CEO, Bill Staples, and Senior Director of Product Management for AI, Sarah Waldner, share how we're transforming our comprehensive DevSecOps platform into an AI-native software engineering platform for human and AI collaboration.
Our unique advantage? GitLab’s 3-layer architecture that no competitor has: 📊 System of Record → Your unified data platform ⚙️ Software Control Plane → Orchestrating critical processes 👥 User Experience → 50M+ users, zero context switching.
GitLab Duo Agent Platform extends every layer: 🧠 Knowledge Graph for superior AI context 🔄 Orchestration layer with multi-agent flows 🤖 True human-AI collaboration everywhere.
This means parallel human-AI software engineering work can be done with full lifecycle context that transforms agents from tools into teammates.
Ready to experience the future of software engineering? Learn more in our GitLab 18.3 blog: about.gitlab.com/blog/gitlab-13-expanding-ai-orchestratio…This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
At GitLab, your wins are our wins. ✨
In 2019, Intuitive Machines had less than five years to build a complete lunar mission software suite from scratch. Using GitLab’s complete DevSecOps platform, Intuitive Machines could handle all of its software challenges in one place and contribute immediately, regardless of what they were working on.
The company was able to make history with its lunar landing and experienced a 10x increase in release cadence, a 99% reduction in downtime and a 20x decrease in pipeline execution time.
📖More insights here:
thenewstack.io/how-intuitive-machines-used-devsecops-to-r… -
🦊 GitLab
@gitlab
The big question: “How will developers and AI agents work together?”
GitLab’s VP of Strategy and Developer Relations, Emilio Salvador, touches on this in his TechVoices podcast episode.
🎧Listen here:
techvoices.com/video-podcasts/gitlabs-emilio-salvador-on-… -
🦊 GitLab
@gitlab
If you want to discover how AI can understand your codebase, follow your conventions, and generate production-ready code with minimal review cycles, we’ve got the tutorial for you! 🤓
🦊 GitLab
@gitlab
Full article and demo here 👇
about.gitlab.com/blog/custom-rules-duo-agentic-chat-deep-… -
🦊 GitLab
@gitlab
Security teams! Some food for thought: whether you’ve sanctioned AI use or not, developers are going to use AI daily to boost their productivity.
You shouldn’t be asking whether you should adopt AI tooling, but rather how to enable the secure use of these tools. 🤔
At least that’s what Josh Lemos says in his interview with @SCMagazine.
In the podcast episode, Josh talks about AI governance and GitLab’s findings from our latest C-Suite report on AI.
🦊 GitLab
@gitlab
🎧If you’re interested in learning more, tune in:
www.scworld.com/podcast-segment/14186-softwares-agentic-f… -
🦊 GitLab
@gitlab
Cybersecurity, privacy, and governance concerns are the real barriers executives face when deploying AI across their organizations.
The good news: Leaders are finding ways to build trust into AI from the ground up.
See their strategies in our new C-Suite Report ⬇️
🦊 GitLab
@gitlab
Full report here:
about.gitlab.com/software-innovation-report/ -
🦊 GitLab
@gitlab
Guess who’s back, back again.
The Developer Show, powered by GitLab, is back - tell a friend! 🎶
📺 Tune into Episode 3
📅 August 27, 2025
⏱️ 10 a.m. PT
We’ll be covering GitLab 18.3 Release with Fatima Sarah Khalid, Fernando Diaz, and Ebru Engwall.
See you live in the episode comments! -
🦊 GitLab
@gitlab
Discover how GitLab Dedicated can help financial services organizations achieve compliant DevSecOps without compromising performance.
Read more here: about.gitlab.com/blog/why-financial-services-choose-singl… -
🦊 GitLab
@gitlab
Not sure how to streamline security with chat agents? 👀
Our CISO Josh Lemos covers this during his interview with Shelly Kramer.
🎧Full podcast episode here: www.youtube.com/watch?v=wZytaN-1URM -
🦊 GitLab
@gitlab
The Life of a Developer! 🧡
-
🦊 GitLab
@gitlab
News flash 🚨
AI adoption in government is no longer optional. And successful implementation requires more than just buying AI tools.
💡In fact, the federal agencies that ARE getting ahead aren't rushing into AI—they're being strategic about it. They're setting up governance frameworks, security protocols, and quality standards from day one.
👉If you need a push to get ahead, check out these 4 steps GitLab recommends to improve your development processes and move toward a human-AI collaborative environment.
federalnewsnetwork.com/commentary/2025/08/agentic-ai-is-r… -
🦊 GitLab
@gitlab
Py py py - Crypto Theft Busted by GitLab
Not a boy band reunion, just another reason to double-check your dependencies.
Our research team just uncovered a coordinated PyPI attack targeting Bittensor wallets via typosquatted packages.
What we found:
→ 5 lookalike packages published within 25 minutes
→ Malicious code injected into stake_extrinsic() to silently drain entire wallets
→ Funds laundered through a chain of wallets to a final cash-out point
→ All hidden inside what looked like routine staking functionality
This is exactly why proactive supply chain monitoring matters.
🧠 Full technical breakdown, attacker TTPs, and IOCs in the blog: about.gitlab.com/blog/gitlab-uncovers-bittensor-theft-cam… -
🦊 GitLab
@gitlab
What happens in Vegas…always makes it onto our social feed.
It was great seeing so many familiar faces at Black Hat this week. Thanks for stopping by the GitLab booth! -
🦊 GitLab
@gitlab
Discover how to leverage AI while maintaining control over your data, infrastructure, and security posture. about.gitlab.com/blog/gitlab-duo-self-hosted-models-on-aw…
-
🦊 GitLab
@gitlab
Sabrina Farmer, GitLab CTO, shares her thoughts on the reliability and efficiency of GPT-5:
“GPT-5 delivers exceptional performance for complex software engineering tasks. The model consistently requires fewer tool calls to solve problems while producing more robust, maintainable code. GPT-5's reliability and efficiency give us confidence in deploying it."
OpenAI
@OpenAI
GPT-5 is here.
Rolling out to everyone starting today.
openai.com/gpt-5/This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
Learn how to transform raw usage data into actionable business insights and ROI calculations with this in-depth tutorial. about.gitlab.com/blog/measuring-ai-roi-at-scale-a-practic…
-
🦊 GitLab
@gitlab
Story time 🥸
We want to hear from you: What's the most embarrassing thing you've looked up on a search engine as a developer? (We won't judge... much) -
🦊 GitLab
@gitlab
If you’re on the Black Hat show floor today, come talk to our security professionals about our complete DevSecOps platform.
👉 Booth 5745
Trust us, these devs put the secure in security. 😉 -
🦊 GitLab
@gitlab
Today, we announced a strategic collaboration with @awscloud (AWS) to expand access to GitLab Dedicated.
GitLab Dedicated eliminates the compliance vs. cloud efficiency trade-off for organizations in regulated industries.
✅ Single-tenant environment
✅ Data residency and isolation controls, private networking
✅ Unified DevSecOps platform
✅ AWS region flexibility
Innovation without compromise 🔐
about.gitlab.com/press/releases/2025-08-06-gitlab-aws-str… -
🦊 GitLab
@gitlab
💡 The future of software development isn't AI vs. humans—it's collaboration.
New research from GitLab shows companies are saving an average of $28K per developer annually from AI investments.
Dig deep: When applied to the world’s 27 million developers, this translates to more than $750 billion in potential global value!
Digging deeper: Developers who master 'cognitive architecture'—thinking systematically about human-AI workflows—will lead this transformation.
@Thenewstack has more insights from Emilio Salvador and the latest on GitLab’s C-Suite data here: thenewstack.io/50-50-the-future-of-human-ai-collaboration… -
🦊 GitLab
@gitlab
Our AI in Action Hackathon became a vibrant stage for developer innovation. Meet the winners here: about.gitlab.com/blog/ai-in-action-hackathon-celebrating-…
-
🦊 GitLab
@gitlab
As we reflect on Black Hat USA 2025, you might find yourself asking some of these critical questions:
1️⃣ How is my company leveraging AI defensively?
2️⃣ What's the biggest cybersecurity blind spot I should look out for?
3️⃣ What should be at the top of my security priority list as we move through 2025?
Don’t fret! Our CISO Josh Lemos already answered the questions for you in this interview from VMblog 👇
vmblog.com/archive/2025/07/25/gitlab-ciso-josh-lemos-on-a… -
🦊 GitLab
@gitlab
🚨 The reskill reckoning is here!
Human creativity and strategic vision remain essential in development.
Yet skill gaps and talent shortages could slow progress. The upskilling imperative is urgent.
The truth:
➡️ 99% of execs say human contributions are valuable for software development
➡️ 92% express that businesses should prioritize training employees to work alongside agentic AI to address skill gaps.
➡️ 73% believe that human input for human-AI partnership should be at least 50/50, with only 27% believing that AI should do the majority of the work.
The future belongs to those who can build bridges between human creativity and AI capability.
Learn more in GitLab’s 2025 C-Suite survey. about.gitlab.com/software-innovation-report/ -
🦊 GitLab
@gitlab
POV: Your favorite AI-native DevSecOps platform just dropped the latest updates in the August Monday Merge. And it's 🔥🔥🔥 if we do say so ourselves 😉
This media couldn't be displayed. See it on the original post.
🦊 GitLab
@gitlab
Full newsletter here: www.linkedin.com/pulse/ai-agents-new-releases-750-billion…
-
🦊 GitLab
@gitlab
⚡ Platform Engineering is reshaping how we think about developer experience.
The days of developers juggling 20+ disconnected tools are numbered. In 2025, everything beyond application development will be abstracted to the portfolio level through centralized platforms.
🔥Hot take: The most successful teams in 2025 won't be the ones with the most tools—they'll be the ones with the most integrated workflows.
What's your take? Are you seeing this platform consolidation trend in your organization? -
🦊 GitLab
@gitlab
Sounds like: 🐈⬛
Looks like: 🔐🥳
Do you need us to spell it out?
Okay… We’ll be at Black Hat next week!
🌎 Las Vegas, NV
📅 August 6-7
🎯Booth 5745 -
🦊 GitLab
@gitlab
Inside GitLab's Healthy Backlog Initiative
We are refining issue management to help our Product and Engineering teams prioritize strategic work that aligns with our current product direction.
How this initiative benefits you:
✅ Sharper focus = faster delivery
✅ Clearer expectations on roadmap priorities
✅ Accelerated feedback loops for new requests and issue triage
We're excited to collaborate on developing the features and improvements that matter most to our community.
about.gitlab.com/blog/inside-gitlabs-healthy-backlog-init… -
🦊 GitLab
@gitlab
📊 Managing security across hundreds of repositories?
GitLab 18.2's Security Inventory gives AppSec teams:
1️⃣ Centralized view of scan coverage gaps
2️⃣ Portfolio-wide risk assessment
3️⃣ Direct remediation actions from one interface
🦊 GitLab
@gitlab
Move from reactive triage to strategic security governance → about.gitlab.com/blog/bridging-the-visibility-gap-in-soft…
-
🦊 GitLab
@gitlab
Business leaders estimate that developers have saved 943 hours over the past year by investing in AI software innovation.
That’s the equivalent of 117 working days.
Imagine what your business could do with that kind of time back.
GitLab’s 2025 C-Suite insights report lands on July 29.
Don’t miss the insights shaping the next era of software innovation. -
🦊 GitLab
@gitlab
AI for Everyone: Security, Education, and Building AI-native apps x.com/i/broadcasts/1dRJZYElYRbGB
Post not available here, view on X
🦊 GitLab
@gitlab
Fork this demo: gitlab.com/gitlab-da/the-developer-show/housing-affordabi…
🦊 GitLab
@gitlab
-
🦊 GitLab
@gitlab
Episode 2 of The Developer Show, powered by GitLab, is here! 🥳
We’ve got a great lineup of speakers and topics for you to listen to.
📺 Fatima Sarah Khalid, Fernando Diaz, Greg Hogg, and Jessie Young
5️⃣ Topics you won’t want to miss!
1. AI/ML
2. Agentic Platform Live
3. Chain of Thought reasoning (prompting technique)
4. Dev confessions
5. Most embarrassing stories about debugging from the community
🖇️ youtube.com/live/C3CcwG90B6o -
🦊 GitLab
@gitlab
🚀 Last week we announced that GitLab Duo Agent Platform is now in public beta!
More exciting features coming soon, including our Knowledge Graph 📊
Leveraging GitLab as the system of record for source code, we're building a comprehensive Knowledge Graph that:
✅ Maps files and dependencies across your codebase
✅ Accelerates AI query times
✅ Increases accuracy through relationship understanding
This enables GitLab Duo agents to quickly understand connections across your entire development environment—from code dependencies to deployment patterns.
To see what other features are coming soon, check out the blog about.gitlab.com/blog/gitlab-duo-agent-platform-public-beta/ -
🦊 GitLab
@gitlab
73% of executives surveyed believe that human input for human-AI partnership should be at least 50/50.
Because creativity, strategic vision, and collaboration still matter.
This isn’t just a stat.
It’s a call to action.
GitLab’s upcoming C-Suite report lands July 29. -
🦊 GitLab
@gitlab
A genie granted you one wish, but you had to share it with your first @. What would it be, and why is it, security and AI integrated into the entire SDLC?
…who said that?! 🤭 -
🦊 GitLab
@gitlab
We did it once and we’ll do it again 😉
RSVP to attend our second episode of The Developer Show here: www.linkedin.com/events/aiforeveryone-security-educatio73… -
🦊 GitLab
@gitlab
Discover how self-hosted models enable federal agencies to leverage artificial intelligence while maintaining strict security and compliance standards. about.gitlab.com/the-source/ai/self-hosted-ai-balance-inn…
-
🦊 GitLab
@gitlab
The future of software liability is about embracing shared responsibility and Bob Stevens outlines how to create this Unified Standard of Care.
More on @TheNewStack 👉 thenewstack.io/software-security-imperative-forging-a-uni… -
🦊 GitLab
@gitlab
The $750 Billion Code Rush is real.
And the leaders shaping it aren’t just investing in technology, they’re redefining their business priorities around it.
Discover what C-level executives across eight global markets are prioritizing in our upcoming C-Suite report, launching July 29. -
🦊 GitLab
@gitlab
GitLab 18.2 includes support for comprehensive scanner coverage and transitive dependency visualization. about.gitlab.com/blog/bridging-the-visibility-gap-in-soft…
-
🦊 GitLab
@gitlab
How does GitLab grow open source communities?
Easy, we invest time into our improvements and make sure our updates are repeatable for other open source projects.
If you’d like to dig deeper, here's how we used GitLab's own tools to solve the newcomer dilemma and grow our open source community. 👇
about.gitlab.com/blog/how-we-use-gitlab-to-grow-open-sour… -
🦊 GitLab
@gitlab
💡 Real results from real customers.
“True collaborators" is how NatWest describes the GitLab Duo AI agents.
From coding to tests to CI/CD pipeline scans, the GitLab Duo agents understand context, break down problems, and let developers focus on what they do best - innovate. -
🦊 GitLab
@gitlab
"The future of software development isn't about replacing developers—it's about orchestrating human-AI collaboration at scale."
Watch our CEO Bill Staples, introduce the public beta of the GitLab Duo Agent Platform, where AI agents become your specialized team members handling testing, security scanning, and code reviews while developers focus on innovation.
Watch the full video on our blog: about.gitlab.com/blog/gitlab-duo-agent-platform-public-beta/This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
🎉 Announcing GitLab 18.2 with 30+ improvements, including GitLab Duo Agent Platform public beta and custom workflow statuses for issues and tasks. Let's dive into some of the exciting new features:
Post not available here, view on X
🦊 GitLab
@gitlab
More great features in 18.2:
- Group and project controls for GitLab Duo Core
- Instance workspace agents for improved scalability
- PDF export of security reports
- Epic assignments and milestone support
- Enhanced DAST with TOTP MFA support
- Security Inventory for comprehensive asset visibility (beta)
🦊 GitLab
@gitlab
Thank you to our incredible community for 152 contributions to GitLab 18.2! Your commitment to open source continues to push us forward. 🧡
Learn more about all the new features: about.gitlab.com/releases/2025/07/17/gitlab-18-2-released/ -
🦊 GitLab
@gitlab
🤖 AI is transforming how we code, but are we coding securely?
Here are 3 essential practices for building secure software in the LLM era:
✅ Zero-trust AI code - Treat AI output like input from a junior developer
✅ Master prompt engineering - Security-aware prompts = secure code
✅ Automate security scanning - More code = wider attack surface
Read more here: about.gitlab.com/blog/3-best-practices-for-building-softw… -
🦊 GitLab
@gitlab
Learn how to use the DevSecOps platform to solve onboarding problems for new contributors.
Read here: about.gitlab.com/blog/how-we-use-gitlab-to-grow-open-sour… -
🦊 GitLab
@gitlab
Organizations achieve successful AI operationalization by implementing AI with clear business objectives and targeted strategies.
Lucky for you, our CTO, Sabrina Farmer, shares her latest insights on how to further operationalize AI for engineering teams.
📖about.gitlab.com/the-source/ai/three-ways-to-operationali… -
🦊 GitLab
@gitlab
🦊: We’ll take “songs about cities” for $300.
Taylor Swift, Jay Z, Frank Sinatra all pay homage to this beloved concrete jungle.
🦊: What is New York City? -
🦊 GitLab
@gitlab
GitLab is enhancing its deletion flow for groups and projects with features like pending deletion, self-service recovery, and an extended 30-day recovery window.
Here's what you need to know: about.gitlab.com/blog/improving-gitlab-deletion-flow-what… -
🦊 GitLab
@gitlab
Wherever you are in the world, we love seeing you come out and rep GitLab.
📸 Here’s a snapshot of our time at We Are Devs last week.
#remoteandtogether -
🦊 GitLab
@gitlab
That time you spent 6 hours debugging only to find you had a typo in a variable name. The variable was literally called 'temprary' instead of 'temporary'.
What's your most embarrassing debugging story? 👇 -
🦊 GitLab
@gitlab
🚀 Mark your calendars! The GitLab Hackathon runs July 17-24, 2025.
A full week of virtual collaboration, innovation, and contribution to open source projects that matter.
Code, design, document, translate - there's a place for everyone!
Learn more here: -
🦊 GitLab
@gitlab
AI isn’t just a nice-to-have, it’s business critical.
Here’s how you can unlock DevSecOps success with GitLab DORA metrics and AI in action!
📺 learn.gitlab.com/ai-dora-m/e5675b6b79 -
🦊 GitLab
@gitlab
Missed out on watching The Developer Show live? Check out the link below to catch up on all the things we discussed around GitLab 18, MCP, live coding, and more!
🦊 GitLab
@gitlab
The Developer Show - GitLab 18 Event Recap x.com/i/broadcasts/1yNGaLQDODQKj
-
🦊 GitLab
@gitlab
What makes GitLab a special place to work:
✔️Collaboration
✔️Results for customers
✔️Efficiency
✔️Diversity, inclusion, and belonging
✔️Iteration
✔️Transparency
🦊 GitLab
@gitlab
Help us shape the future of DevSecOps. Your ideas and energy could be the driving force behind our success.
about.gitlab.com/jobs/ -
🦊 GitLab
@gitlab
Follow this step-by-step guide, complete with a demo application, to learn how to use agentic AI, along with GitLab's native integrations and CI/CD components. about.gitlab.com/blog/fast-and-secure-ai-agent-deployment…
-
🦊 GitLab
@gitlab
Learn how agentic AI helped generate comprehensive gRPC documentation in minutes, not hours. about.gitlab.com/blog/accelerate-learning-with-gitlab-duo…
-
🦊 GitLab
@gitlab
Redesign your platform onboarding to boost adoption, reduce friction, and create seamless experiences for development teams.
about.gitlab.com/the-source/platform/transform-your-platf… -
🦊 GitLab
@gitlab
Learn how CI/CD inputs provide type-safe parameter passing with validation, replacing error-prone variables for more reliable pipelines. about.gitlab.com/blog/ci-cd-inputs-secure-and-preferred-m…
-
🦊 GitLab
@gitlab
📺The July Monday Merge is here: Recap the GitLab 18 Launch event and check out what features are shipping. Watch to learn more.
This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
New AI models drop daily, but enterprise teams need control. GitLab Duo Model Selection provides LLM control for each GitLab Duo feature, enabling organizations to adopt AI while meeting strict governance and compliance standards.
Learn more here: about.gitlab.com/blog/speed-meets-governance-model-select… -
🦊 GitLab
@gitlab
Learn how GitLab Duo with Amazon Q improves the QA process by automatically generating comprehensive unit tests. about.gitlab.com/blog/enhance-application-quality-with-ai…
-
🦊 GitLab
@gitlab
Learn how embedded development teams address long feedback cycles, manual compliance, and isolated development with DevSecOps. about.gitlab.com/blog/why-now-is-the-time-for-embedded-de…
-
🦊 GitLab
@gitlab
Mid-week pulse check: How’re you doing?
❤️ Never better
👍 Taking it day by day
🪩 Ready for the weekend
😴 Could use a nap -
🦊 GitLab
@gitlab
We asked, you answered 👇
These are some of your never-seen commit messages 🤫This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
GitLab 🤝 IBM
That’s a partnership worth mentioning! GitLab’s Mike Flouton has the latest on our partnership with IBM and why Devs need to know about it. -
🦊 GitLab
@gitlab
We had a blast at the GitLab 18 launch event last week. Here’s a behind-the-scenes look at our E-Group and devs in action. 🎥
Didn’t catch the event live? Check out the recording here: about.gitlab.com/eighteen/ -
🦊 GitLab
@gitlab
🚨 Supply Chain Attack Caught in the Wild
Our Vulnerability Research team recently flagged a live typosquatting attack in the Go ecosystem—qiniiu/qmgo, a near-identical clone of the popular MongoDB driver.
What stood out:
→ Malicious code hidden in NewClient to trigger during normal app use
→ Multi-layered payload delivery ending in a full remote access trojan
→ Attackers re-uploaded a second variant just days later—we caught that too
💡 These threats are subtle but serious. Our automated system—powered by heuristics, AI, and human review—detected and stopped it fast.
🔗 Full breakdown, IOCs, and defense tips in the blog: about.gitlab.com/blog/gitlab-catches-mongodb-go-module-su… -
🦊 GitLab
@gitlab
Missed the GitLab 18 Launch Event? No worries! Watch the full event on demand and discover all the exciting new features and updates.
Catch up at your convenience 👉 about.gitlab.com/eighteen/ -
🦊 GitLab
@gitlab
ICYMI 👀 we went LIVE with our first-ever episode of The Developer Show.
We recapped all things GitLab 18 and even had a live coding session!
Check out the show here:
🦊 GitLab
@gitlab
The Developer Show - GitLab 18 Event Recap x.com/i/broadcasts/1yNGaLQDODQKj
-
🦊 GitLab
@gitlab
To break organizational misalignment, platform teams must prioritize what is truly needed, like developer satisfaction, according to Bryan Ross via TheNewStack.
So Devs this question is for you: How do you measure your workplace satisfaction?
🦊 GitLab
@gitlab
Read more on accelerating developer velocity with effective platform teams → thenewstack.io/accelerating-developer-velocity-with-effec…
-
🦊 GitLab
@gitlab
Duo Model Selection provides LLM control for each GitLab Duo feature, enabling organizations to adopt AI while meeting strict governance and compliance standards. about.gitlab.com/blog/speed-meets-governance-model-select…
-
🦊 GitLab
@gitlab
🤖 What if you could delegate routine dev tasks to AI agents while focusing on the work that inspires you?
GitLab Duo Agent Platform makes this possible with specialized agents that understand your full SDLC context—not just code.
Learn more about GitLab Duo Agent Platform here: about.gitlab.com/blog/gitlab-duo-agent-platform-what-is-n… -
🦊 GitLab
@gitlab
Discover how this new GitLab feature can find exact matches, use regex patterns, and see contextual results across terabytes of codebases.
about.gitlab.com/blog/exact-code-search-find-code-faster-… -
🦊 GitLab
@gitlab
Discover what the bundle URI Git feature is, how it is integrated into Gitaly, configuration best practices, and how GitLab users can benefit from it.
about.gitlab.com/blog/reduce-the-load-on-gitlab-gitaly-wi… -
🦊 GitLab
@gitlab
🎶 Oh, I wanna co-create with somebody
I wanna ship it with somebody
Yeah, I wanna iterate with somebody
With somebody creating on GitLab 🎶
At GitLab, we're proud to build the future of software development with a mission to enable everyone to contribute to and co-create the software that powers our world. Our platform doesn't just bring people together—it unites teams and organizations, breaking down barriers and redefining what's possible.
Interested? Dance on over to our careers page 👇This media couldn't be displayed. See it on the original post. -
🦊 GitLab
@gitlab
We’re BAAAAAAAACK! And better than ever with this first iteration of The Developer Show, powered by GitLab. 🦊
Tune in NOW to learn about all things AI and open source.
This is something you’ll want to catch LIVE! 📺
www.linkedin.com/events/7340777668130312193/ -
🦊 GitLab
@gitlab
The Developer Show - GitLab 18 Event Recap x.com/i/broadcasts/1yNGaLQDODQKj
-
🦊 GitLab
@gitlab
3...2...1... ACTION! 🎬
Our GitLab 18 Launch Event is happening NOW!
Watch here 👀
about.gitlab.com/eighteen/ -
🦊 GitLab
@gitlab
🚀 GitLab 18 is here! Built WITH developers, not just for you.
✨ Quick test generation
🤖 Auto code reviews with Duo
⚡ Duo Agent handles the tedious work so you can focus on what matters
Ready to see it in action?
📅 GitLab 18 Launch Event - June 24th Register now! -
🦊 GitLab
@gitlab
🧵 Big News: GitLab + @IBM announce GitLab Ultimate for IBM Z! 🎉
We're bringing modern DevSecOps directly to mainframe environments with native z/OS Runner support. No more workarounds, no more security risks.Post not available here, view on X
🦊 GitLab
@gitlab
This isn't just about updating tools—it's about creating unified development experiences that help organizations accelerate innovation while maintaining enterprise security and reliability. 🔒⚡
🦊 GitLab
@gitlab
Ready to modernize your mainframe development without business disruption? GitLab Ultimate for IBM Z is available now.
Learn more → about.gitlab.com/blog/gitlab-ultimate-for-ibm-z-modern-de… -
🦊 GitLab
@gitlab
This week, GitLab's Chief Technology Officer, Sabrina Farmer, spoke at the United Nations Open Source Week panel on the Open Source Programme Offices (OSPOs) for Good Day.
The panel focused how open-source principles can foster transparency, accountability, and collaboration in AI, thereby mitigating risks while maximizing its potential for positive impact. -
🦊 GitLab
@gitlab
Tell
All your
Never
Uncovered
K(commit) messages
In the chat 🤫
We’re curious! Did you have a commit message that never saw the light of day? 👀 -
🦊 GitLab
@gitlab
While software keeps on moving forward⚡
Security needs to keep pace 🛡️
GitLab 18 elevates native security workflows for the age of agentic AI, from compliance to secrets protection.
GitLab 18 launch event → June 24th → about.gitlab.com/eighteen/ -
🦊 GitLab
@gitlab
🎉 Announcing GitLab 18.1 with 110+ improvements, including Maven virtual registry (beta) and Duo Code Review GA. Let's dive into some of the exciting new features:
Post not available here, view on X
🦊 GitLab
@gitlab
More great features in 18.1:
- Enhanced CODEOWNERS validation with permission checks
- VS Code downstream pipeline job logs
- PHP support for Advanced SAST
- Epic support for GitLab Query Language views
- Enhanced merge request review panel
🦊 GitLab
@gitlab
Thank you to our incredible community for 311 contributions to GitLab 18.1! Your commitment to open source continues to push us forward. 🧡
📝 Learn more about all the new features: about.gitlab.com/releases/2025/06/19/gitlab-18-1-released/ -
🦊 GitLab
@gitlab
Well, we’ve had another awesome week connecting with customers and partners on the ground. This time at AWS re:Inforce. Here’s some of our favorite moments. 🧡
To find out where we’re going to be next check out our latest Monday Merge. -
🦊 GitLab
@gitlab
Secure and safe login and commits with GitLab + @Yubico! 🔐
Want to strengthen your software development security? We've partnered with Yubico to bring you robust authentication measures that protect against today's cyber threats. Check out our latest article to see how YubiKeys can secure your GitLab experience and keep your code safe.
Read the full story here: about.gitlab.com/blog/2025/04/02/secure-and-safe-login-an… -
🦊 GitLab
@gitlab
🚀 One small step for GitLab, one giant leap for @Int_Machines. They built spacecraft software in record time using GitLab, even patching code 250,000 miles away. 🌕
-
🦊 GitLab
@gitlab
What is your go-to version control system? ⚙️
-
🦊 GitLab
@gitlab
What is your preferred operating system for development?
-
🦊 GitLab
@gitlab
🚨 Our 15.10 release includes the ability to automatically resolve SAST findings when rules are disabled, a new view to see all branch-related settings together, and so much more. docs.gitlab.com/releases/
-
🦊 GitLab
@gitlab
The pandemic forced orgs to embrace flexibility, and two years later, our #asyncwork report in partnership with @Qatalog confirms flexibility is top of mind for employees. How important is a flexible work schedule for you?
Read the full report here. sprawl.work -
🦊 GitLab
@gitlab
Our next Hackathon is just around the corner! Get together with the GitLab community to contribute, learn and win prizes. about.gitlab.com/community/hackathon/
-
🦊 GitLab
@gitlab
Whether a job is remote or hybrid, employees are pushing for more flexibility. In our Work-from-Home Field Guide created, with workspace experts @HermanMiller, learn how to help employees work healthier from home. about.gitlab.com/work-from-home-field-guide/
-
🦊 GitLab
@gitlab
When designing your workspace, @HermanMiller's Ryan Anderson says customization is the key. In our co-created Work-from-Home Field Guide, we point out ways leadership can help champion diverse workspaces for their employees. about.gitlab.com/work-from-home-field-guide/
-
🦊 GitLab
@gitlab
The DevOps Platform has arrived.
$GTLB is officially listed on @Nasdaq!
#everyonecancontribute -
🦊 GitLab
@gitlab
How do you know what you need to create the right office for you? Check out @HermanMiller's WFH tool for the best recommendations: wfh.hermanmiller.com #remotebygitlab
-
🦊 GitLab
@gitlab
Before you start designing a workplace, home or co-located office, @HermanMiller's Ryan Anderson says there are a few questions you'll need to answer first. #remotebygitlab
-
🦊 GitLab
@gitlab
The top remote leaders in the world will detail how remote work is transforming lives, companies, and communities at #remotebygitlab. Join us to learn how to create and sustain scalable remote practices.
-
🦊 GitLab
@gitlab
Join @simonsteinbeiss to help get closer to @xfce 4.18.
Here's how you can get involved: docs.xfce.org/contribute/dev/start -
🦊 GitLab
@gitlab
🥳👏
@videolan migrated their issue tracker to GitLab! #movingtogitlab
Nuritzi Sanchez (She/Her)
@1nuritzi
Awesome to hear that @videolan has migrated their issue tracker to @gitlab 🥳
The new bug tracker for VLC can be found here: code.videolan.org/videolan/vlc/-/issues/
#movingtogitlab #vlc #foss #devops -
🦊 GitLab
@gitlab
Exciting @gitchat news...
Gitter is joining @element_hq and entering the @matrixdotorg community! 🎉
about.gitlab.com/blog/gitter-moves-to-element/ -
Post not available here, view on X
🦊 GitLab
@gitlab
"We’ve always had a bit of a crush on Gitter" - @element_hq 💜
The Matrix.org Foundation
@matrixdotorg
BIG NEWS: Huge welcome to @gitchat, who are entering Matrix!! Gitter is moving from @gitlab to @element_hq & building the ultimate Matrix bridge, showcasing how a large chat app can natively talk Matrix, while bringing Gitter goodness to Element! 🚀🌉🎉 matrix.org/blog/2020/09/30/welcoming-gitter-to-matrix
-
🦊 GitLab
@gitlab
🎉 15 Years of Git!
Way back in 2005, @Linus__Torvalds changed our entire world with the development of Git! #git15 -
🦊 GitLab
@gitlab
Join us for #gitlabconnect on Nov 19th for a day of #devops! page.gitlab.com/gitlabconnect_toronto2019.html
📍 Toronto, Canada
🕒 3:30-7:30pm -
🦊 GitLab
@gitlab
We're #hiring an Associate Production Designer!
This is a #remote, junior-level role 🙌 Apply or help us spread the word among early-career designers!
about.gitlab.com/jobs/apply/associate-production-designer… -
Post not available here, view on X
🦊 GitLab
@gitlab
It's always easier to hold yourself accountable with a buddy! Tweet us your commitments using #justcommit, and we'll do our best to help. Plus, we have 100 cozy PJ pants to giveaway! Tweeting with the hashtag will enter you to win 😻
-
🦊 GitLab
@gitlab
See how GitLab + @FastlaneTools can build, sign, and publish apps for Android to the Google Play Store 💥
about.gitlab.com/blog/android-publishing-with-gitlab-and-… -
🦊 GitLab
@gitlab
We're #hiring a Gitter Engineer! Read all the details & apply:
about.gitlab.com/jobs/?gh_jid=4114968002 -
🦊 GitLab
@gitlab
We’re honored to win the Google Cloud Partner Award for innovative developer solution at #googlenext18!
-
🦊 GitLab
@gitlab
Read GitLab CEO @sytses on how open source became the default business model for software: www.forbes.com/sites/forbestechcouncil/2018/07/16/how-ope…
-
🦊 GitLab
@gitlab
ICYMI: Open source content management system @NetlifyCMS has launched support for GitLab! 🎉
about.gitlab.com/blog/netlify-launches-gitlab-support/ -
🦊 GitLab
@gitlab
Automate your localization with GitLab + @crowdin! about.gitlab.com/2018/02/06/crowdin-localization-for-agil…
-
🦊 GitLab
@gitlab
So, what happened yesterday? Here's what went wrong and what we're doing to fix it: about.gitlab.com/2017/02/01/gitlab-dot-com-database-incid…
-
🦊 GitLab
@gitlab
WHY are you reading about #git over the holidays? (jk, we are too) Here are some tricks from @_axil #opensource about.gitlab.com/2016/12/08/git-tips-and-tricks/
-
🦊 GitLab
@gitlab
GitLab dev advocate @AmbassadorAwsum chats with @JasmineAnteunis from @RecastAI about community building about.gitlab.com/2016/11/23/how-to-build-a-strong-dev-com… #startups
-
GitLab.com Status
@gitlabstatus
This incident is now resolved, as we didn’t see the issue return during our monitoring period and CI/CD pipelines are running normally. We’re continuing to investigate the root cause internally with details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/23401. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We’re seeing recovery, and CI/CD pipelines should be running normally again. We’re continuing to monitor to confirm the issue doesn’t return while we investigate the root cause. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We’re continuing to investigate this issue and don’t have any new information to share at this time. Our team is working to identify the cause, and we’ll provide another update within an hour. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're investigating reports of customers being unable to run pipelines on gitlab.com without encountering Gitaly-related errors. Details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/23401. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
After continuous monitoring, the latency has returned to baseline. We're marking this incident resolved.
Find more information about the incident here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23392 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We continue to monitor the incident to ensure the issue doesn't recur.
Find more information about the incident here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23392 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We've applied a mitigation for the intermittent slowness affecting CI/CD on gitlab.com, and performance has returned to normal. We're monitoring to make sure the issue doesn't recur. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've identified a contributing factor to intermittent slowness affecting CI/CD on gitlab.com, including slower job requests, job updates and artifact uploads. We're still investigating the root cause and working to mitigate the issue. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Some users may have seen intermittent slowness with CI/CD jobs, including slower job updates and artifact uploads. Latency is recovering and we're continuing to investigate. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're investigating elevated latency affecting CI/CD on gitlab.com. No user impact has been observed at this time. We'll update as we learn more. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The database maintenance for the Customers Portal (customers.gitlab.com) is complete. The Customers Portal and its APIs are available again and working normally. Thank you for your patience. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The database maintenance for the Customers Portal (customers.gitlab.com) is taking longer than planned. Our team needs more time to complete it. The Customers Portal and its APIs remain unavailable. We apologize for the inconvenie... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The scheduled database maintenance for the Customers Portal (customers.gitlab.com) has started. The Customers Portal and its APIs are temporarily unavailable. We expect the maintenance to end by 12:00 UTC. We’ll post an update when it’s complete. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have resolved the issue that caused slowness on gitlab.com. gitlab.com is operating normally, and we are continuing to monitor the platform. The impact may have included partial degradation to the web UI and Git operations. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We identified and resolved an issue that caused slowness on gitlab.com. gitlab.com is operating normally, and we are monitoring the platform to ensure the issue remains resolved.
More details here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23320 status.gitlab.com -
GitLab.com Status
@gitlabstatus
The monitoring period has concluded, and the incident has been confirmed resolved. See the issue for more details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23297 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The Customers Portal is loading normally again, and we are no longer observing the intermittent 404 errors affecting sign-in and page loading. A redeployment has completed successfully, and we are monitoring the service for any recurrence before resolvi... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We’re continuing our investigation of 404s on the customers panel. We’ll update you as we learn more. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've investigating 404s on the customers panel. We'll update as we learn more status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have not seen any more HTTP 500 errors for GitLab Secrets Manager since the mitigation was applied. This incident is now resolved. Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23288 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
This issue affects projects and groups using GitLab Secrets Manager. Users saw HTTP 500 errors, not 503 as previously stated. A mitigation has been applied and we're monitoring. Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23288 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're investigating intermittent HTTP 503 errors when opening project pages. At this time, this issue only occurs in specific projects. More details at: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23288 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The issue is fully resolved and operations on gitlab.com and GitLab Duo are operating normally. More details at: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have taken steps to resolve the slowness and 503s on gitlab.com and are monitoring the situation. More details at: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Most services on gitlab.com have recovered but we are seeing slowness with Duo requests and services and are looking to resolve it. More details at: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have identified the cause of 503s on gitlab.com and are working to remediate the issue. We are still seeing intermittent 503s and site slowness as we work to resolve the issue. More details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are still investigating the cause of 503 on gitlab.com. We are seeing some services return but errors still intermittent. More details at: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating the cause of 503s on gitlab.com and the site moving slowly. We will update once we have additional details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The issue causing CI/CD failures and UI slowness for a limited number of gitlab.com customers has been resolved. Thank you for your patience. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've applied a temporary mitigation to address CI/CD failures and UI slowness affecting a limited number of gitlab.com customers. We're monitoring recovery while working on a longer-term solution. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We’re investigating an issue affecting CI/CD on gitlab.com for a limited number of customers. Pipelines may fail with the following error:
“CI configuration fetch from Gitaly timed out. This may indicate Gitaly service slowness ... status.gitlab.com -
GitLab.com Status
@gitlabstatus
We have taken steps to mitigate the delays on CI/CD jobs on gitlab.com and services have returned to normal. More details at: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23234 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have identified the cause of the issue causing CI/CD delays on gitlab.com and are working to take corrective actions. The issue may persists intermittently as we do so. More details at: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23234 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating an issue affecting gitlab.com CI/CD. Some pipelines may remain in the created state for an extended period or fail to start, causing CI/CD workflows to stall. More Details at gitlab.com/gitlab-com/gl-infra/production/-/work_items/23234 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The issue affecting customers.gitlab.com has been resolved. Customers Portal pages and subscription-related operations have returned to normal. More details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23240 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Mitigations have been applied to customers.gitlab.com, and we are monitoring service availability. Intermittent errors may continue to affect Customers Portal pages and gitlab.com groups that rely on the portal for subscription-re... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material updates to report. We'll share another update when we have more information. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material updates to report. We are still investigating the root cause. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have received reports that some groups on gitlab.com are experiencing HTTP 500 errors because the group is unable to sync with customers.gitlab.com. We are continuing to investigate the issue.
status.gitlab.com -
GitLab.com Status
@gitlabstatus
We're investigating an issue that's stopping pages on customers.gitlab.com from loading. Purchasing, renewing, and managing subscriptions may be affected. gitlab.com itself is not affected. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have been monitoring this issue for a few days with no reported occurrences. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The source of the issue has been identified and we have taken steps to remediate and resolve the issue. gitlab.com is stable now. More details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23192 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We identified the issue affecting gitlab.com and general site errors and slowness related to the initial issue. We are actively working to resolve the issue. More details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23192 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating an issue affecting gitlab.com and general site errors and slowness related to the initial issue. We are actively investigating the issue. More details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23192 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating an issue affecting gitlab.com CI/CD. Merge train, scheduled, and child/downstream pipelines may be delayed, remain in a created or pending state, or fail to start. Mergeability analysis and webhook notificatio... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating an issue affecting gitlab.com merge trains. Some merge train pipelines may remain in the created state for an extended period or fail to start, causing merge trains and related CI/CD workflows to stall. More d... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Monitoring confirms that gitlab.com services have remained stable. We are continuing to monitor for any recurrence of the issues before marking this incident as resolved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The fix was deployed and continued monitoring has shown that the identified tool failure has been addressed. This issue is now resolved. Details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/23158 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Job start times for CI/CD jobs on gitlab.com small Linux x86-64 hosted runners have returned to normal, and the backlog of pending jobs has been processed. The issue with the provider persists, but we are not seeing any impact on ... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Job start times for CI/CD jobs on gitlab.com small Linux x86-64 hosted runners have returned to normal, and the backlog of pending jobs has been processed. The delays were caused by errors and capacity constraints from our cloud p... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have identified an ongoing Google Cloud Compute Engine issue affecting runner-capacity provisioning in us-east1. Some gitlab.com CI/CD jobs using small Linux x86-64 hosted runners may remain pending longer than usual before sta... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating increased queue times for CI/CD jobs using gitlab.com small Linux x86-64 hosted runners. Affected jobs may remain pending longer than usual before starting. We have identified errors and delays when provisioni... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are seeing improvements across all services on gitlab.com. We are resuming our investigation on identifying the root cause. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
General gitlab.com service continues to improve. We're now focused on restoring Duo services. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are seeing an improvement in errors rates in our monitoring, starting from 07:14 UTC. We are still identifying the root cause. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are currently investigating reports of an increase of HTTP 50X errors on gitlab.com status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Monitoring shows failures are still occurring in a tool used by Duo Code Review. The service remains available, but reviews may contain less context than expected. A fix is merged and awaiting deployment; we’ll update once recovery is confirmed. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Errors affecting Code Review tools have decreased, and the tools appear to be operating normally. We’re monitoring error rates and investigating the improvement. A fix is merged but not yet in production, so recovery is still being validated. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've identified the cause of the issue affecting GitLab Duo Workflow operations. Duo Code Review remains available, but reviews may contain less context than expected. Our engineering teams are expediting a fix and will continue monitoring until servic... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We’re investigating an issue affecting some GitLab Duo Workflow operations. Duo Code Review results may be incomplete or lower quality than expected. Our engineering teams are working on mitigation and will provide further updates. More details: https:/... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The issue has been resolved, and systems have returned to normal operation. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have applied a mitigation and are seeing sustained recovery in error rates and performance on merge request and pipeline pages for the affected projects. We are continuing to monitor. Details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/23150 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating reports of errors and slow performance on merge request and pipeline pages for projects in the specific groups. Details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/23150 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
After continued monitoring, services remain stable. The incident has been resolved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are beginning to see signs of recovery and are continuing to monitor the situation closely while we investigate the root cause. If you have been affected, please retry any failed or timed out jobs. Details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23131 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are continuing to investigate the root cause and will provide further updates as they become available. Details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23131 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are continuing to investigate. In addition to delays, users may experience job timeouts or failures during this time. If affected, please retry the job. Details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23133 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our investigation is ongoing and we are actively working to identify the root cause. We will provide further updates as more information becomes available. Details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23133 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Job completion delays are still being observed and we are actively working to address the issue. Details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23133 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are currently investigating delays in job completion: CI jobs remain running after success, delaying pipeline progression. Details gitlab.com/gitlab-com/gl-infra/production/-/work_items/23133 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The incident affecting CI/CD jobs on gitlab.com instance runners has been resolved. Following a period of monitoring, everything has remained stable. Details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23117 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
An incident affecting CI/CD jobs on gitlab.com instance runners has been resolved. Job pickup delays should no longer be occurring and we are continuing to monitor to confirm full recovery. Details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23117 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Jobs on saas-linux-small-amd64 hosted runners have been processing as expected, and this incident is now resolved. Details at: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23077 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material updates, monitoring continues. Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23077 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Job processing is stable; monitoring continues. Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23077 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Jobs are processing as expected at this time, and graphs have returned to normal. We are now monitoring the situation. For details, see gitlab.com/gitlab-com/gl-infra/production/-/work_items/23077. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Some CI/CD jobs using saas-linux-small-amd64 hosted runners are experiencing delays before starting. We are restoring affected runner capacity and monitoring recovery. Delays may continue while the backlog clears. The root cause remains under investigat... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have not seen new failures, so we are marking this as solved. More information is available in gitlab.com/gitlab-com/gl-infra/production/-/work_items/23061. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
There were no new bounced emails since 02:29 UTC. We will continue to monitor the logs and provide updates when new information is available. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our monitoring has not observed any bounced emails since 02:29 UTC. We are seeing early signs of improvement in email delivery, but some messages may continue to be delayed or fail for certain email service providers.
The team continues to monitor de... status.gitlab.com -
GitLab.com Status
@gitlabstatus
We have taken additional measures to reduce elevated email volumes and improve platform stability. The team continues to monitor the impact and will provide another update as more information becomes available. The incident is being tracked in g... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are continuing to escalate with our email delivery provider, and other affected email service providers directly. The team continues to monitor the impact and will provide another update as more information becomes available. The incident is being tr... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are escalating this issue directly with our email delivery provider. The team continues to monitor the impact and will provide another update as more information becomes available. The incident is being tracked in gitlab.com/gitlab-com/gl-infra/production/-/work_items/23061 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We’ve detected email delivery delays affecting a small number of email service providers. The team is actively investigating to identify the full scope and impact. The incident is being tracked in gitlab.com/gitlab-com/gl-infra/production/-/work_items/23061 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We observed that the backlog of jobs have been processed and new reports should be coming in on the normal schedule. With this update the incident is resolved.
More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 status.gitlab.com -
GitLab.com Status
@gitlabstatus
No material updates to report. We are continuing to monitor the report-ingestion backlog and working on mitigation.
More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 status.gitlab.com -
GitLab.com Status
@gitlabstatus
No material updates to report. We are continuing to monitor the report-ingestion backlog and working on mitigation. More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Monitoring continues. A backlog of ingestion events is currently being processed, which we expect will take some time. See: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Monitoring continues. A backlog of ingestion events is currently being processed, which we expect will take some time. We will keep posting updates as we have them. See: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We continue to see improvements across our graphs and reduced backlog, more info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We continue to see improvements across our graphs, see also: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The mitigation we implemented is reducing the backlog of events. We are now monitoring the situation, see also: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've identified the cause and are working on mitigation. More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Security and vulnerability reports are not loading or being ingested for some users. We are investigating now. For more info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Graphs continue to drop and security report functionality should now be normal. We're resolving this incident. If you have further issues with security reports, please contact support. More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The fix has been deployed and we're seeing our graphs return to normal. Users should no longer be seeing missing security reports. We'll continue to monitor for now. More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The team continues to work on mitigating the underlying cause of the issue. More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The fix is still being implemented and progress is being made on resolving the problem. More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The team is still working on the fix.
More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 status.gitlab.com -
GitLab.com Status
@gitlabstatus
The changes we've tried have so far been ineffective. The fix is still in progress. More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
A fix is being implemented and we will update here once it's complete. More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The team is still working on the fix. More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material updates at this time. Mitigation efforts are ongoing. More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Some users are not able to generate security reports in pipelines. We've indetified the cause and are working on mitigation. More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
This incident has been resolved. gitlab.com is operating normally, and we are continuing to monitor the service. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
GitLab services are operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
GitLab services are now operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
GitLab remains stable and error rates have decreased. We are still actively engaging in recovery efforts. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Error rates are decreasing, but some customers may still see errors. We are continuing to address the remaining impact and will update again soon. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Error rate is decreasing after active mitigation efforts. We're still actively working on addressing the root cause. We will update with more details shortly. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've identified the cause of 503 errors on gitlab.com and are working on mitigating the issue. We're aware that the API is also affected. We will update with more details shortly. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've identified the cause of 503 errors on gitlab.com and are working on mitigating the issue. We will update with more details shortly. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are recieving reports of 503 errors on gitlab.com. This is under active investigation. We will update with more details shortly. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're no longer seeing elevated errors, so we are resolving this incident. If you continue to experience any errors on gitlab.com, please open a ticket. More information: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The team is still working on the fix. More information: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The team has identified the potential cause of the spike in 500 errors and is working on the fix. More information: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're continuing our investigation. More information: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material updates at this time. We are continuing our investigation. More information: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The incident team continues to investigate the cause of this incident. In the meantime, we are seeing intermittent improvements in the ability to access projects. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The incident team is continuing to investigate the issue to identify its root cause and implement an appropriate resolution. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have implemented a temporary mitigation and are continuing to investigate the issue. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have received reports that some users are unable to access projects and are encountering 500 error messages. Our team is currently investigating the cause. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
At this time we are resolving this incident. If you continue to experience performance degradation in the Singapore area, please open a support ticket. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're still monitoring this incident. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
At this time the situation is unchanged. We will continue to monitor. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material updates at this time. We will continue to monitor the situation. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Cloudflare confirmed the traffic degradation was resolved, with recovery observed at approximately 13:40 UTC. Our application and backend checks remained healthy during the degradation, supporting that the impact was outside the GitLab application stack... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are still investigating the cause for the performance degradation. There are no material updates at the moment. The problem is tracked under gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're experiencing degraded package, artifact, and registry download speed in APAC/Singapore region due to elevated CDN/Cloudflare latency. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The incident has been resolved following the completion of the rollback deployment across the Gitaly nodes. All nodes have returned to a stable state, repository access has been restored. Incident team is currently investigating the root cause. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Gitaly nodes have stabilized following the completed rollback deployment. The incident has been mitigated and we remain focused on continued monitoring. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
A rollback release has been deployed to all Gitaly nodes. They are stable at present. However, we are continuing to monitor the situation. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are currently rolling back the deployment of Gitaly. We're waiting for the deploy to land, and we are continuing the investigation. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Further mitigation change are currently being applied, and we are continuing to investigate the issue. HTTP 500 errors may continue affecting the GitLab UI and Git operations in certain projects. Further updates will follow. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
A further mitigation change has been applied, and we are assessing its impact. HTTP 500 errors continue affecting the GitLab UI and Git operations in certain projects. Further updates will follow. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Further mitigation is being rolled out while we continue to investigate HTTP 500 errors affecting the GitLab UI and Git operations. We will provide further updates as the mitigation progresses. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The restart of the affected Gitaly node did not improve the issue; HTTP 500 errors continue affecting the GitLab UI and Git operations in certain projects. We are investigating and will provide further updates as the situation changes. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Investigation continues. We will shortly be restarting the affected Gitaly node after reconfiguration. Further updates will be provided accordingly. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Mitigation has not yet fully restored the GitLab UI and Git operations in certain projects. We are still investigating HTTP 500 errors and will provide a further update as more information becomes available. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are continuing mitigation and monitoring recovery. Customers may still encounter HTTP 500 errors in the UI and during Git operations for certain projects. We will provide a further update as mitigation progresses. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We’re continuing mitigation efforts and have observed some recovery. Customers may still encounter HTTP 500 errors in the UI and during Git operations when accessing certain projects. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We’ve identified an abuse vector as the root cause and begun mitigation efforts. Early signs indicate that the service is recovering. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material updates are available at this time. Our team continues to investigate the root cause of the issue. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're investigating reports of customers unable to open projects, receiving error 500 instead. Details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22925. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are no longer observing elevated error rates and have identified the root cause. We are marking this incident as resolved while we implement additional fixes behind the scenes. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are still seeing cases but tat a much less frequent rate. We will continue looking for the root cause and monitor the error rate. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We’ve detected issues affecting artifact uploads. The team is actively investigating, and we’ll provide another update as soon as we have findings to share. Thank you for your patience. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We'll now mark this as resolved while we look at additional changes as preventative measures for the future. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Policy evaluations and MR approvals are executing normally. We're continuing to monitor the situation while working on improvements to prevent this in the future. More: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22904 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We believe we have identified the underlying problem and are working to implement mitigating changes. More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22904 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are still investigating this issue. Users may still experience delays in Security Policy Evaluations, impacting MR approvals. Details in: More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22904 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our product team is still working on finding the cause and potential mitigation steps for this issue. More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22904. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are seeing delays in Security Policy Evaluation which are affecting MR approvals. The cause is under investigation. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22904. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are no longer observing delays in CI job execution and the backlog of pending jobs has been worked through. We'll now be marking this as resolved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
CI job execution delays have improved significantly, and the backlog of pending jobs is shrinking. We're continuing to monitor the situation. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're still observing elevated CI job queues and are working to address the problem. Details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22897 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're observing an increase in CI job queues. Users may see jobs stuck in a pending state for longer than usual. Jobs may not fire their associated webhooks or integrations. Details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22897 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The merge request that introduced the failure was reverted, and custom/catalog agents are working again. More information is available in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22880. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Starting a new chat with an agent from the AI catalog does not work, and the websocket connection is immediately dropped. We are reverting the merge request that introduced the failure. The incident is being tracked in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22880. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The incident affecting gitlab.com CI/CD jobs using instance runners is now resolved. Some jobs were delayed or remained pending while a manually initiated pg_repack database maintenance operation caused contention on the CI databa... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating an incident affecting gitlab.com CI/CD jobs using instance runners. Some jobs may remain pending longer than expected or may not be picked up by a runner, which can delay pipelines and deployments. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Performance remains stable and prevention steps are being implemented. Find more information here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22807 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The issue has been identified and resolved. We are monitoring for changes. More information here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22807 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
There are elevated HTTP 500 errors affecting users accessing their Pipelines. Our engineers are actively investigating the issue and working to restore normal service. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our upstream provider mitigated a genuine distributed HTTP DDoS attack against gitlab.com, but incorrectly blocked a small amount of legitimate traffic. This has now been resolved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have identified a temporary filtering event by an upstream provider that affected some traffic to gitlab.com. The event has ended, and we are working with our service provider to investigate the cause and prevent recurrence. We... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are currently investigating reports of connectivity issues affecting some users accessing gitlab.com. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The fix has been implemented and the issue is now resolved. We have not observed any active user impact. More information: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We continue to monitor and have not observed any active user impact. We are working towards a permanent fix and will provide our next update once it has been implemented. More information here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have not seen active user impact for several hours and we have identified the possible root cause. We are monitoring for changes. More information here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Slowness & 502s have been bursty with not much impact. A revert MR is under way while we are investigating other possible root causes. More information here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are currently investigating reports of slowness and 502 errors. More information here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The deployment failures affecting the GitLab Agent for Kubernetes (KAS) have been resolved. Details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22777 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The rollback has been completed and we are actively monitoring to confirm resolution of the deployment failures affecting KAS. Details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22777 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have identified a recent change believed to be contributing to the deployment failures affecting KAS. We are actively reverting this change and will provide an update once complete. Details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22777 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are currently investigating reports of deployment failures affecting GitLab Agent for Kubernetes (KAS). Our team is actively looking into the root cause and will provide updates as the investigation progresses. Details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22777 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The elevated 403 errors affecting gitlab.com have been resolved and error rates have returned to normal levels. More details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22762 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're monitoring an incident where 403s were seen across gitlab.com. The fix for this is already in place.
More about the incident here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22762 status.gitlab.com -
GitLab.com Status
@gitlabstatus
The error rate remains within normal thresholds and the issue is now resolved. Further details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The error rate has continued to remain within normal thresholds. We're continuing to monitor the error rate.
Further developments can be read here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729 status.gitlab.com -
GitLab.com Status
@gitlabstatus
Our monitoring shows the error rate decreasing towards normal thresholds. We're continuing to monitor the incident.
More information here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729 status.gitlab.com -
GitLab.com Status
@gitlabstatus
Investigation for the root cause of 500 errors while fetching commits on gitlab.com is still ongoing.
More information here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We are still investigating the root cause for 500 errors while fetching commits on gitlab.com.
More information here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We are investigating an issue causing a subset of requests to gitlab.com receiving 500 errors. We will provide updates as we learn more from our investigation.
More information here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729 status.gitlab.com -
GitLab.com Status
@gitlabstatus
All deletion queues have been processed for projects, we expect the same to continue for group deletions.
This incident is moved to resolved.
More information here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We're continuing to monitor the deletion queue being processed via the deletion workers.
Delay of deletions and visibility of scheduled/queued deletions would be experienced until the queue is cleared.
More information here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714 status.gitlab.com -
GitLab.com Status
@gitlabstatus
The fix is now in production and we're now working on processing the deletion queue via the deletion workers.
The last 4 status updates were missing a "4" infrastructure work item link shared; this has been corrected on the status page.
More infor... status.gitlab.com -
GitLab.com Status
@gitlabstatus
We've identified a fix for the issue affecting project and group deletions on gitlab.com.
Due to routine DB maintenance there will be a delay for when the fix will land in production. Given the current state of a known fix and ... status.gitlab.com -
GitLab.com Status
@gitlabstatus
We are still investigating the issue affecting project and group deletions on gitlab.com.
Immediate and scheduled deletion of projects and groups may not complete as expected. Ones that have been scheduled for deletion may rema... status.gitlab.com -
GitLab.com Status
@gitlabstatus
We are still investigating the issue affecting project and group deletions on gitlab.com.
Immediate and scheduled deletion of projects and groups may not complete as expected. Projects and groups that have been scheduled for de... status.gitlab.com -
GitLab.com Status
@gitlabstatus
We are currently investigating an issue affecting project and group deletions on gitlab.com.
Immediate and scheduled deletion of projects and groups may not complete as expected. Projects and groups that have been scheduled for... status.gitlab.com -
GitLab.com Status
@gitlabstatus
The queue of pending jobs on the affected runners has returned to normal and has stayed at that level. This incident is now resolved. Please open a ticket with support if you are still seeing job delays. Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22702 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The queue of pending jobs on the affected runners has returned to normal and we are monitoring recovery. Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22702 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The issue is mitigated and the queue of pending jobs on saas-linux-medium-arm64 is going down. We are monitoring recovery. Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22702 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are seeing a growing queue of pending jobs on the saas-linux-medium-arm64 hosted runner on gitlab.com. We are rolling out a mitigation. Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22702 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're seeing consistent background job and webhook delivery. The issue is now resolved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have identified the cause of the issue and we are taking action to mitigate customer impact. For more info, see: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22661 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating an issue affecting background jobs, including webhook delivery and pipelines. For more info, see: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22661 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've applied mitigations that have stabilized the job queue. The issue is now resolved. Details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22654. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've identified a likely root cause, and the job queue has remained healthy. Details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22654. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've disabled a worker, which should let the job queue begin recovering while we continue investigating the root cause. Details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22654. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're investigating reports of pipelines failing and becoming stuck. Details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22654. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Webhook delivery failures have subsided in logs, and customer reports indicate no further errors. This incident is considered resolved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
A fix has been deployed and checks have confirmed that unexpected IP addresses are no longer being used. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Deployment of the fix is progressing steadily. Another update will be provided once deployed. Details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22637. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've traced the issue to a recent network change and are preparing a fix. Another update will be provided by 23:00 UTC. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our investigation is ongoing. We will provide another update by 21:00 UTC. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Duo Code Review sessions on gitlab.com have returned to normal operation. This issue is now resolved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating reports of webhook deliveries from gitlab.com originating from IP addresses outside our documented ranges. Details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22637. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've identified the cause of the issue and have temporarily reverted the default Agentic Chat model to Sonnet 4.6 while we continue to investigate. Details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22633. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating an issue which may be affecting Duo Code Review Flows. For more info, see: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22633 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
After a period of monitoring we have seen continued Gitaly stability and consider the incident resolved. Details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Restarting the affected Gitaly node relieved pressure on it, and error rates have dropped significantly. We're monitoring for continued stability. Details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The team is still working on actions to mitigate impact from the affected Gitaly node. For more info, see: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Impact is limited to projects on a single Gitaly node. The team is currently focused on relieving pressure from the overloaded Gitaly node to mitigate impact in the affected projects. For more info, see: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The team is investigating an issue related to a Gitaly node. Customers may experience errors or slowness when performing git operations. For more info see: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have continued to observe normal error rates. We will now be marking this incident as resolved. Details surrounding the incident can be seen here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22579 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have confirmed these errors are no longer occurring. We've identified the cause of this incident and are working to prevent this from occurring in the future. We'll now move this incident to monitoring. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We observed a spike in 5xx errors on gitlab.com. These have subsided, but we are investigating the root cause. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Earlier login problems have been resolved and logins are working normally again. This incident is now considered closed. Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22551 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're aware of previous login problems for gitlab.com and are monitoring the situation. For details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22551 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are still monitoring the situation with possible issues logging into gitlab.com and will provide further updates when they are available. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are currently receiving reports and investigating issues with signing into gitlab.com. We will provide more information once it is available. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've identified and mitigated the root cause of this issue. Service has remained stable throughout the monitoring period, and this incident is now resolved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're seeing service recover and error rates return to expected levels. We'll continue to monitor the environment to ensure the recovery is sustained. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're seeing signs of recovery, but our investigation into the root cause remains ongoing. We'll continue to provide updates as more information becomes available. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We continue to investigate the root cause of this issue. There are no material updates at this time, and we'll share additional information as it becomes available. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our team is actively investigating the root cause of this issue. We'll continue to share updates as we learn more. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're investigating an issue affecting GitLab Duo Custom Agents on gitlab.com. Our team is actively working to identify the cause and restore normal service. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Mitigation efforts have been successfully completed, and service has returned to normal. This incident has been resolved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Mitigation efforts remain in progress. We're continuing to monitor the implementation and will provide another update once additional progress has been made. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
There are no significant updates to share at this time. Mitigation efforts are still underway, and we will continue to provide updates as they become available. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have no material updates at this time. Our team remains focused on mitigation efforts and will continue to share updates as we make progress. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've identified the root cause of the issue and are continuing to implement mitigation measures. We'll provide additional updates as progress is made. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Mitigation efforts are ongoing to address the issue affecting package pulls from our registry. Slow or failed Omnibus package downloads may still occur. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material updates to report at this time. We are continuing to investigate the current issue and engineers are working to determine remediation steps. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Recovery efforts remain in progress for the issue impacting package pulls from our registry. Some Omnibus package downloads may continue to be slow or fail until the issue is resolved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Work to resolve the package registry issue is ongoing. During this time, some users may continue to experience slow or unsuccessful Omnibus package downloads. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We continue to work on resolving the issue with package pulls from our registry. Users may still experience slow or failed Omnibus package downloads. We will share another update as soon as we have more information. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating degraded performance affecting package pulls from our registry. Users may experience slow or failed Omnibus package downloads while we investigate. Currently, the engineering team has identified the cause of the degraded performance... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are seeing error rates return to normal. This issue has been resolved. Details at gitlab.com/gitlab-com/gl-infra/production/-/work_items/22519 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are monitoring the situation to ensure that services have returned to normal. Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22519 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Deployment for the revert has reached production. Manual verification is successful with error rates trending down. We are continuing to monitor. Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22519 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The revert remains in progress. Additional updates will be shared in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22519 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're continuing to work on reverting the change causing this issue. Details will be shared in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22519 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have identified the problematic change causing this behavior and are working to revert it. Details will be shared in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22519 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're aware of elevated errors affecting AI Gateway health checks. We've identified a likely cause and are actively working on a fix. Details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22519 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The fix has been completed in production. This incident is now resolve.
More: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22470 status.gitlab.com -
GitLab.com Status
@gitlabstatus
The fix has been merged and we are now monitoring. If you still experience the issues, please open a ticket with support. More: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22470 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The fix will merge as soon as it's pipeline completes. The status will change to monitoring at that time. More: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22470 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No further updates at this time. The merge request is in progress. More: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22470 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No updates at this time. A merge request fix has been created and is currently being worked on. More: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22470 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
A merge request fix has been created and is currently being worked on. We will update as the situation changes. More: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22470 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The fix is still in progress, no updates at this time. More: gitlab.com/gitlab-org/gitlab/-/work_items/605117 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've discovered that attempts to delete newly created MR approval rules may fail in certain cases. The cause has been identified and the fix is in the works. More: gitlab.com/gitlab-org/gitlab/-/work_items/605117 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've discovered that attempts to delete newly created MR approval rules may fail in certain cases. The cause has been identified and the fix is in the works. More: gitlab.com/gitlab-org/gitlab/-/work_items/605117 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Incident has now been mitigated. CI pipelines are now resuming. Engineers will continue to monitor this recovery. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are continuing to investigate and look into CI pipelines being stuck in pending state. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are currently investigating the cause of CI pipelines being stuck in pending state. More details can be found here:
gitlab.com/gitlab-com/gl-infra/production/-/work_items/22433 status.gitlab.com -
GitLab.com Status
@gitlabstatus
Operations have returned to normal and this issue is resolved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The fix is pushed and systems appear to be operating normally. We are monitoring the situation to ensure that services have returned to normal. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have identified the issue and are pushing a fix. While this fix is pushed we still recommend switching to Claude Sonnet 4.5 until the fix is fully pushed. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are continuing to investigate the issue, but it appears to be isolated to specific models and we recommend for the time being switching to Claude Sonnet 4.5 for code completion while we continue to investigate the matter. Details on how to do that ca... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating errors with code suggestion not completing. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
This issue is resolved and performance on gitlab.com has returned to normal. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have identified the issue and taken action to correct the matter and are monitoring gitlab.com. We will provide further updates as information is available or when the issue is confirmed resolved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are continuing to investigate and work to resolve the degraded performance on gitlab.com status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have identified the cause of the increased error rate and are taking corrective action and monitoring the incident. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are continuing to investigate and look into the increased errors on gitlab.com status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating the cause, but the symptoms are: 500 errors, CI jobs can't check out repos, slow merge request page loading, slow page loading status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Incident has now been mitigated and runner backlogs are now back to normal. CI pipelines are now resuming. Engineers will continue to monitor this recovery. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Queues and runner backlog are trending back towards normal, while systems continue to work through the remaining backlog. Engineers are continuing to monitor this. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our engineers are still investigating the issue but jobs are starting to be processed with a delay. More details can be found here:
gitlab.com/gitlab-com/gl-infra/production/-/work_items/22412 status.gitlab.com -
GitLab.com Status
@gitlabstatus
No material updates to report. We are continuing to investigate the current issue and engineers are working to identify the cause. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have identified that the sidekiq workers processing the jobs are getting deferred. The team is working on identifying the remediation steps. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are currently investigating an issue affecting CI pipelines not starting on merge requests. Our team is actively investigating the root cause.
status.gitlab.com -
GitLab.com Status
@gitlabstatus
We have continued to observe successful SSH interactions after implementing our mitigating changes. We will now mark this as resolved. Details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22364 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've addressed the underlying issue and are observing SSH interactions succeed. We will place this incident in a monitoring state as we keep an eye on things. Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22364 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are still working to revert this problematic change as quickly as possible. Once reverted, we will post an update here. Details will be made available in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22364 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have identified the problematic change causing this behavior and are working to revert it. Details will be posted in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22364 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating ongoing errors when attempting to interact with repositories via SSH. HTTPS does not appear to be impacted at this time. We are investigating. Details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22364 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
A recent code change was rolled back and the error rates have subsided since it was merged. Our team has been monitoring and performance has returned to expected levels. This incident is now resolved. gitlab.com/gitlab-com/gl-infra/production/-/work_items/22335 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've identified a recent code change as the likely cause of elevated Sidekiq job execution errors on the low-urgency-cpu-bound shard, which may delay processing of some background jobs. Mitigations are in progress. We'll continue to update as soon as t... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
gitlab.com is currently operating normally. The issue has been resolved. For more info, please see: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22308 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The revert MR to remove the Claude Fable was merged and deployed to production. While the gitlab.com service is back to normal, Fable remains unavailable due to an upstream suspension. Customers need continue to select a different... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Although Claude Fable is not available on gitlab.com, it still appears in the model selection menu. Customers who are currently using it should manually select a different model. Please see the notice from the upstream provider: h... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Claude Fable is not available through gitlab.com. Please see the notice from the upstream provider: status.claude.com/incidents/s9w82lp9dcn9 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
gitlab.com is currently operating normally. We have confirmed the root cause was a Cloud provider incident affecting a disk backing our primary database and the issue should be resolved now. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
gitlab.com is currently operating normally. We have confirmed the root cause was a Cloud provider incident affecting a disk backing our primary database, and we are continuing to monitor closely. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The gitlab.com service is now operational. We are keep investigating why it is occurring intermittently. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We changed the status title to reflect the intermittent nature of this incident. We'll share another update as soon as we have more information. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are currently investigating 5XX errors when accessing gitlab.com. We'll share another update as soon as we have more information. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
GitLab Credits dashboards are operating normally again. The issue has been resolved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Mitigation has been applied and GitLab Credits dashboards appear to be loading again. We’ll leave affected components marked as Partial Service Disruption as we monitor error rates closely to ensure the service remains stable. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The gitlab.com credit dashboard fails to load, displaying the error message: "An error occurred while fetching data". This issue is under investigation. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The job queue is now cleared and we do not expect any further customer impact. This is considered resolved. For more info, see: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Error rates have recovered back to normal levels and we started processing jobs again. We expect that the job queue should be processed over the next 30 minutes. For more info, see: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The change has been reverted and we are seeing that error rates are recovering. For more info, see: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are still working on rolling back the change that we believe is the root cause. This issue impacts GitLab Hosted Runners and Hosted Runners on Linux. For more info, see: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have identified a recent change as a possible root cause and we are working on rolling back the change. For more info, see: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating an issue where CI jobs are not processing. For more info, see: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
This issue has been resolved and error rates have returned to normal. For more info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Error rates have decreased significantly following the fix. We are continuing to monitor the situation. For more info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have merged a fix for the Duo Agent Platform Flow failures and it is awaiting deployment. Deployment is expected to take several hours. We will share our next update once the deployment is complete. For more info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have identified the root cause of the recent Duo Agent Platform Flow failures and are deploying a fix. Customers should begin seeing improvements as the deployment completes. For more info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating an issue where Duo Agent Platform Flows, including Duo Code Review, are not working on some projects. See issue for more info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The fix has been deployed, and Duo Agent Platform Flows are working as expected. We will now mark this incident as resolved. For details, see: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22241 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have identified the issue and we're rolling out a fix to production. Customers should start to see improvement as deployment completes. For more info, see: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22241 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating an issue where Duo Agent Platform Flows fail to start when used with the default Docker image. For more info, see: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22241 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're no longer seeing errors related to this in the logs, so we are resolving this incident. If you're still experiencing errors when using `@GitLabDuo` mentions in merge requests, please contact support. support.gitlab.com status.gitlab.com
-
GitLab.com Status
@gitlabstatus
A fix has now been deployed that should remediate the errors. We will continue to monitor, and as long as error rates remain low, we will resolve the incident. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material updates at this time. Our team is still seeing some failures which prompted additional investigation. While there has been a drop in errors, some users continue to experience issues. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
After monitoring, our team is still seeing some failures which is prompting additional investigation. While there has been a drop in errors, some users continue to experience issues. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are still monitoring the deployed fix. We will share another update once we can confirm it's fully resolved. More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22228 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
A fix has been deployed via a revert MR. We're moving the incident to Monitoring and will share another update once we can confirm it's fully resolved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've identified a likely root cause for the `@GitLabDuo` access errors in merge requests and are preparing a revert MR. We'll share another update once it's deployed. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're investigating an issue where customers using `@GitLabDuo` mentions in merge requests are receiving access errors. Impact has been reported across gitlab.com, Dedicated, and Self-Managed.
Our team is actively investigating. ... status.gitlab.com -
GitLab.com Status
@gitlabstatus
The Git operation errors have been resolved and metrics have returned to normal. Thank you for your patience throughout the incident. Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22217 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've implemented mitigation rules and are seeing a reduced rate of errors. All signals indicate the incident is resolved. We'll continue monitoring for a bit before marking it as fully resolved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Investigation into the Git operation errors is ongoing. The team is reviewing logs and has identified a few potential culprits, though we haven't yet confirmed whether any of them are causing the incident. We'll share another update as soon as we have m... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our Gitaly team is continuing to investigate the reported Git operation errors. We don't have new information to share at this time, but work is ongoing. Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22217 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We receive report regarding git operation error. Our Gitaly team is investigating the problem. See more detail: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22217 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The fix has been deployed, and hared runners saree picking up jobs normally. We will now mark this incident as resolved. More: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22212 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The fix has been deployed. Shared runners should be picking up jobs normally. We will continue to monitor the situation. More: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22212 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Some users may see jobs pending while waiting for runners. The team is currently working on the fix. We will update in 30 minutes. More: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22212 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
All metrics confirm that the issue impacting GitLab Duo Agent Platform (DAP) is fully resolved, and we're marking this incident as closed. We appreciate your patience while we worked through it. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The cache is refreshed for some users, and we've received confirmation from a few customers that DAP is working again for them. We're keeping a close eye on metrics before marking this as fully mitigated. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've identified a feature flag on the Customers Portal as the likely cause of the issue affecting GitLab DAP. The flag has been disabled, and we're monitoring logs and metrics for recovery. Customers may continue to see errors due to cache duration. We... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our team is continuing to investigate the issue affecting GitLab Duo Agent Platform (DAP). We don't have new information to share at this time, but work is ongoing. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're currently investigating an issue affecting GitLab Duo. Some customers using the Duo Agent Platform (DAP) may be unable to access the service and are seeing a "Usage quota exceeded" error. Our team is actively looking into the cause. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've identified that the scope of impact is limited to gitlab-org.
We will continue to investigate this but as we're not seeing impact outside of gitlab-org, we're moving this to an internal incident with the incident issue marked confidential. status.gitlab.com -
GitLab.com Status
@gitlabstatus
We're still investigating for the root cause of elevated error rates for webservice.
Progress and updates can be followed here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22182 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We're investigating for the root cause of elevated error rates for webservice.
You can follow the progress and updates here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22182 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We've continued to monitor the job queues following the additional provisioning of runners to the resource pool and we observe that the queueing is back to normal. This incident is moved to resolved.
More details about the incident here: gitl... status.gitlab.com -
GitLab.com Status
@gitlabstatus
We're seeing improvements in job queueing after additional runner allocations to the runner resource pool. We will continue to monitor until the the jobs are getting picked up at normal rates.
More details about the incident he... status.gitlab.com -
GitLab.com Status
@gitlabstatus
We've identified the root cause of some jobs not getting picked up due to runner pool exhaustion. We're working on getting more runners added to the pool.
More details about the incident here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22145 status.gitlab.com -
GitLab.com Status
@gitlabstatus
The revert has been merged and deployed and we are seeing error rates return to normal and flows running. This issue has been resolved.
More details at gitlab.com/gitlab-com/gl-infra/production/-/work_items/22135 status.gitlab.com -
GitLab.com Status
@gitlabstatus
The revert has been deployed and we are now monitoring the situation. Error rates look to be returning to normal.
More details at gitlab.com/gitlab-com/gl-infra/production/-/work_items/22135 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We have identified the cause and have created an MR to revert. We are waiting for that MR to deploy. We will provide further updates once that has merged and deployed.
More details at gitlab.com/gitlab-com/gl-infra/production/-/work_items/22135 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We’ve identified the issue affecting GitLab Duo Agent Platform workflows across gitlab.com, and GitLab Dedicated. Some code review and custom flows may fail or show “Session failed.”
We are working on a revert to correct the is... status.gitlab.com -
GitLab.com Status
@gitlabstatus
We’re continuing to investigate an issue affecting GitLab Duo Agent Platform workflows on gitlab.com and GitLab Dedicated. We have identified a likely cause and are testing a revert. More details at gitlab.com/gitlab-com/gl-infra/production/-/work_items/22135 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We’re investigating an issue affecting GitLab Duo Agent Platform workflows across gitlab.com, and GitLab Dedicated. Some code review and custom flows may fail or show “Session failed.” More details at gitlab.com/gitlab-com/gl-infra/production/-/work_items/22135 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The backlogs of jobs has dropped and this issue has been resolved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are seeing a high backlog of jobs which may be experienced as slowed pipelines and ci/cd jobs.
We will provide more information when it is available. status.gitlab.com -
GitLab.com Status
@gitlabstatus
This issue has resolved and error rates have returned to normal.
More information can be found in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22107 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We have identified the issue as a frozen Gitaly node and are working to correct the issue. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
This issue has been resolved and the affected Redis sidekiq cluster has recovered.
More information can be found in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22103 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We are seeing an increase in 5xx errors on gitlab.com and are investigating the issue.
User may experience issues on gitlab.com. We will provide updates as we have them. status.gitlab.com -
GitLab.com Status
@gitlabstatus
Error rates have started to lower and return to normal values and we are actively monitoring the issue.
The issue is being tracked in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22103
status.gitlab.com -
GitLab.com Status
@gitlabstatus
We are continuing to investigate the issue.
A major Redis Sidekiq cluster outage caused widespread elevated error rates and authentication failures for git, CI runners, and web services. We've performed targeted restarts and forced resets to restore ... status.gitlab.com -
GitLab.com Status
@gitlabstatus
We have identified the cause of the elevated error rates and are working to correct the issue.
We will continue to post updates as we have them. status.gitlab.com -
GitLab.com Status
@gitlabstatus
We're investigating elevated error rates on gitlab.com. Some users may experience intermittent failures or degraded performance while we work to identify the cause.
Users may experience delayed pipelines or pipelines not runnin... status.gitlab.com -
GitLab.com Status
@gitlabstatus
We are seeing elevated error rates across gitlab.com and gitlab.com services.
We are investigating the issue and will continue to update as we have more information. status.gitlab.com -
GitLab.com Status
@gitlabstatus
We're investigating elevated error rates on gitlab.com. Some users may experience intermittent failures or degraded performance while we work to identify the cause.
We'll share another update as soon as we have more information. status.gitlab.com -
GitLab.com Status
@gitlabstatus
Background job processing has returned to normal and this issue is resolved. More information available at gitlab.com/gitlab-com/gl-infra/production/-/work_items/22017 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The issue has been resolved. The 500 errors when accessing repositories should not seen anymore and affected Git operations should work as expected. More details at gitlab.com/gitlab-com/gl-infra/production/-/work_items/22041 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
To restore the service, we restarted the Gitaly process. We will monitor for any recurrence. More details at gitlab.com/gitlab-com/gl-infra/production/-/work_items/22041 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are currently investigating 500 errors when accessing repositories and Gitaly errors when pushing to a repository. More details at gitlab.com/gitlab-com/gl-infra/production/-/work_items/22041 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The background job backlog has mostly cleared and merge train delays should be significantly reduced. We're keeping this incident in monitoring while we implement performance improvements. More: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22017 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have identified the cause of the background job processing delays. We are working to identify mitigating measures. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating an issue background jobs being processed with delay. The problem is being tracked in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22017. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've applied our fix and confirmed this is no longer occurring. We will now mark this as resolved. Details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22008 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The fix is still in progress. For now, the workaround is to use GitLab - Current instead of GitLab - Next. More: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22008 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
A configuration update may cause some intermittent error messages on GitLab Next (Canary). We have identified the cause and the fix is in progress. More: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22008 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
With the configuration changes, we were able to process the backlog and jobs are being processed normally. More details can be found in the issue: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21936 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our team is working on configuration changes to improve resourcing. We're still seeing a job backlog and are continuing to monitor with these changes. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our team has identified a resource issue that has lead to a delay in pending jobs on Small GitLab Hosted Runners. Users with CI jobs tagged for small runners (saas-linux-small-amd64) might experience some delays. Our team is continuing to work on this. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are currently investigating issues with hosted `saas-linux-small-amd64` GitLab runners. More details about this incident can be found in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21936 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
This incident has been resolved and dependency scanning is now operational. More information can be found in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21905. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've identified cause of the issue and are working on resolving it. More details can be found in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21905. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are currently investigating issues with dependency scanning. More details about this incident can be found in `gitlab.com/gitlab-com/gl-infra/production/-/work_items/21905`. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Latency and service health has stabalized after a period of monitoring. Incident is considered resolved. More details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21867 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have increased max concurrency and are monitoring the impact on latency. We'll further investigate segfaults, which may have contributed to this incident. More details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21867 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The root cause is still under investigation. We are taking steps to address the sustained request saturation in order to mitigate latency issues. More details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21867 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating which model and provider are causing the latency. Apdex for ai-assisted service is not stable yet. More details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21867 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating issues related to our ai-assisted service and ai-gateway. Some users may experience higher latency or errors affecting Duo features. More details here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21867 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The root cause has been identified and addressed, and monitoring shows the incident to be resolved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We detected increased error rates for web services on gitlab.com. This recovered after 5 minutes. We're monitoring the situation to ensure the service remains stable. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Pipeline job metrics have returned to a healthy state and jobs are being picked up and processed normally. We consider this incident resolved. Follow the incident: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21835 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We’ve rolled out an infrastructure change and pending job metrics are improving. We’ll continue to monitor. Follow the incident: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21835 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are seeing infrastructure capacity errors and we’re inclined to treat this as the likely cause; investigation continues. Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21835 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We’ve identified some potential causes but haven’t yet confirmed the root cause of the problem. Investigation continues. Track progress: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21835 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are continuing to investigate the issue; there are no material updates to share at this time. Follow gitlab.com/gitlab-com/gl-infra/production/-/work_items/21835 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating an issue with pipelines where jobs are not being picked up or they are stuck in pending. See issue for more details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21835 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We continued to monitor following the rollback and have confirmed that image pulls are functioning normally for GitLab Runners. This incident is now resolved. Details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21778 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The rollback is finished and our internal testing indicates that GitLab-maintained images are once again pulling as expected. We will monitor the situation before marking this incident as resolved. More details gitlab.com/gitlab-com/gl-infra/production/-/work_items/21778 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have identified an MR that causes this issue. We are working on reverting this change. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating the failure of GitLab runners to pull container images. We will provide updates as more information becomes available. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Duo performance has returned to normal so we are resolving this incident. If you're still experiencing Duo performance problems, please open a ticket with support. More information can be found here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21726 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Performance has returned to normal and users should no longer be experiencing degraded performance. This incident is resolved, but if you still have trouble, please open a support ticket. More details can be found here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21732 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Performance has improved following an earlier database performance issue that caused slower than normal responses on gitlab.com. We are continuing to monitor closely while we investigate the underlying cause. More details: https:/... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are currently investigating an issue affecting the response time of database queries. Our team is actively investigating the root cause. More details can be found here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21732 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
GitLab Duo services, including Agentic Chat and Code Suggestions, have returned to normal operation. We're continuing to monitor to ensure stability. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've identified the cause of the degraded GitLab Duo performance as an upstream provider outage affecting Claude models. Error rates are beginning to decrease as the upstream issue is being resolved. We'll provide further updates as the situation progr... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're continuing to investigate degraded performance with GitLab Duo features, including Agentic Chat and Code Suggestions. This is linked to an ongoing upstream provider incident affecting Claude models. Switching to an alternative model may help as a ... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're currently investigating intermittent issues with GitLab Duo Agentic Chat and Code Suggestions. We'll provide updates as more information becomes available. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
After rollback of the feature flag we've observed a low error rate for this issue, but are continuing to monitor to ensure it remains that way. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
After a period of monitoring we have not seen a recurrence of the issue and consider it resolved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're rolling back the feature flag and exploring alternative options for a long-term fix. We've observed that the scope of impact is limited to a small set of customers. Details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21689. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have begun rolling out a feature flag to address the intermittent Git clone failures and timeouts within pipelines. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21689. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating reports of Git clone failures and CI pipeline timeouts. Affected users may see "GitLab is currently unable to handle this request due to load" or "CI configuration fetch from Gitaly timed out." We are actively investigating and will... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The incident has been mitigated. Users should now be able to log in with email-based 2FA. We continue investigating the root cause and will provide further updates. Details can be found in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21683 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Investigation is ongoing. We are narrowing down potential causes and will provide an update once we have more to share. Details can be found in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21683 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material updates on resolution. We continue investigating logs to identify the root cause. Details can be found in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21683 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The incident remains under investigation. The scope is confirmed as affecting only free-tier users attempting to log in with email-based 2FA. Details can be found in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21683 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Multiple users are unable to log in when using two-factor authentication via email. Several customers and users raised the issue. We are actively investigating logs to identify patterns in sign-in endpoint requests and confirming the issue is limited to... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
After a period of monitoring we have not observed a recurrence of the issue and are considering it resolved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've confirmed the traffic filtering rules are applied, with errors dropping to near zero. Claude models should be available now. A permanent fix has been merged and deployment is in progress. We continue monitoring and working on follow-up improvement... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've applied traffic filtering rules to block the primary source of excess requests to our endpoints. We're seeing a significant drop in rate limit errors and are continuing work on permanent fixes. More details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21672 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
As we continue investigating, we're working on immediate mitigation steps. Additional information can be found in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21672 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We continue investigating the issue, no material updates to report. Additional information can be found in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21672 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are currently investigating an issue with Duo Agent Platform and LLM proxy endpoints hitting rate limits. Users may experience errors using Claude models. We recommend switching to a different model as a workaround. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Operations have returned to normal and the gitlab-org repository is accessible as normal. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are seeing things recover now and users should now be able to access the gitlab-org namespace. We are doing integrity checks to understand if there is any lingering impact on the impacted system. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The gitlab-org group are seeing 500 errors due to a specific Gitaly node. We are working to bring things back online but anyone accessing that repository, such as through pipelines or other tasks, will experience errors accessing it. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The combination of infrastructure and application improvements made has sustained stability during peak hours yesterday. This incident has been moved to resolved following our monitoring.
Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21562 status.gitlab.com -
GitLab.com Status
@gitlabstatus
The team has continued to make improvements to the underlying infrastructure to prevent further impact. We have not seen any recent occurrences of background job delays. We will keep this incident open through peak load times over the next 20 hours to m... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We observed an increased delay in background job processing and CI job queue times, both of which have now recovered. We're closely monitoring the situation as we work on additional improvements. Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21562 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are currently investigating performance degradation and our team is currently actively working on a mitigation. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21562 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The team has continued to make improvements since yesterday's update to further reduce impact during peak load. We are actively monitoring the situation. Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21562 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Background job processing has recovered. Additional changes have been implemented which helped to reduce impact during peak load. We will continue to monitor this as we move through peak load times tomorrow. Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21562 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating delay in background job processing. After a monitoring period that followed yesterday fixes, and expanding infra resources, we are investigating further improvements, more details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21562 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our metrics indicate this is now fixed. We will now be marking this as resolved. Details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21573 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Background job processing has recovered as peak load has passed. Additional changes are under review to address this going forward. This incident will remain in monitoring as we deploy these changes and observe metrics through tomorrow's peak. Details: ... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Improvements to help address this issue are currently under review. We are still observing a delay in background job processing. Users may still see delays in CI job status updates. Details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21562 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating delay in background job processing. We are working on further improvements, more details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21562 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The fix has reached production and users should not experience 500 errors on API calls. We will be monitoring the fix before marking this incident as Resolved. More details gitlab.com/gitlab-com/gl-infra/production/-/work_items/21573 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The fix has now reached Canary environment, users can enable it by clicking "Next" at next.gitlab.com until the fix reaches production. More details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21573 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
After monitoring the CI pipelines, we are marking the incident as resolved. More details gitlab.com/gitlab-com/gl-infra/production/-/work_items/21562 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Monitoring of CI pipelines shows metrics have returned to normal. We will keep monitoring the fix for the next hour. More details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21562 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The revert change has been merged, users will still experience 500 errors until the fix reaches production. We estimate it will be fully deployed at the end of EMEA day. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21573 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have identified a code change that provokes 500 errors for API requests. We are currently reverting the change. Workaround in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21573 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are observing improved system metrics and reduced user impact. Mitigations are pending deployment with the goal of preventing future recurrence. This incident will remain in monitoring status as we observe system behavior. Deta... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The primary fix has been merged and deployment is underway. Full rollout typically takes several hours, so we're pursuing additional mitigations and implementation changes in parallel. Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21562 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've identified a potential fix and are working to deploy it. We'll update you once we have a production deployment timeline. Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21562 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our investigation is ongoing. Users may still observe delays in CI job status updates. Details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21562 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating a delay in background job processing. Users may observe a delay in CI job status updates in the UI. Details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21562 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our team has been monitoring and job processing has returned to normal. This incident is now resolved. Further details available in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21532 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The fix has been deployed and we have not seen any more errors. This incident is now resolved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
For clarification, it was noted earlier in the incident that we saw GitLab-hosted Runners were primarily impacted. However, the background job processing delay has impact on self-hosted runners as well. Our team has seen a recovery and we are still moni... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The backlog has recovered and we are no longer seeing delays. Our investigation points to a Sidekiq backlog which lead to delays in CI job execution. Our team is currently monitoring. Additional details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21532 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our team is seeing some recovery but are still investigating the root cause. We believe that a previous Sidekiq backlog caused CI jobs to accumulate, leading to delays. More detail in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21532 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
This incident is pending a deployment to resolve the issue. We'll provide an update once it is deployed. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our team is still investigating the issue. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material updates at this time, our team is still investigating the issue. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're seeing increased job queuing rates that are primarily affecting small CI runners. Our team is still investigating. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our team is investigating potential delays with background job processing. This could impact CI/CD job processing. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our team is currently reverting some recent changes to resolve the issue. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our team has identified the issue as related to a recent commit. Our team is discussing next steps.
Users may also experience NotImplementedError with Code Review flows.
More information will be available in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21529 status.gitlab.com -
GitLab.com Status
@gitlabstatus
The situation has now stabilized. We are closing this incident. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The job backlog is draining and we see the situation stabilizing. We will continue monitoring the queue. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are currently investigating an issue affecting Duo Workflow and AI Gateway for requests routed through GPT models. Users may experience errors using only gpt models on DAP. Engineering is currently investigating the issue. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are seeing the CI job backlog building up, which causes CI job operations to be delayed. We are investigating the cause for this issue. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our team has mitigated this issue and has been monitoring for stability. This incident is now resolved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our team has been monitoring for stability and have taken additional steps to help reduce database saturation. This incident is now resolved. More details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21498 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The revert has deployed and we are no longer observing 403 Forbidden responses when downloading packages. We are resolving this incident. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The MR in question has been reverted and error rates have decreased. We are currently monitoring this endpoint. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
GitLab is currently operational and the incident has been mitigated. We're currently monitoring and will provide an update at a later time. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our team has taken steps to mitigate the issue and services are back to normal. Our team is monitoring and discussing next steps. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are experiencing 5XX errors. The cause for the errors is under investigation. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Starting from approximately 08:00 on 2026-03-10, multiple users were unable to download NuGet packages due to 403 Forbidden errors. We have identified the cause, and are going through the process of reverting the MR. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Background processing has recovered and CI wait times are back to normal. Our team is continuing to monitor for stability. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're seeing stabilization and recovery but are still monitoring and discussing next steps. More info in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21498 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our team has identified the issue as PgBouncer saturation and are looking at mitigation efforts. Users may see small delays in background processing. More information in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21498 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material updates at this time. Our team is still investigating this issue. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our team is investigating potential delays with background job processing. This could impact CI/CD job processing. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The configuration change has been deployed and we have seen stability with Sidekiq and pipeline processing. This incident is now resolved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are continuing to monitor but the main backlog drivers are mitigated. Users should expect normal operations. Our team is currently deploying a configuration update to further address this. We'll provide an update once it is deployed. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our team has turned off a specific worker to help improve pipeline processing. There has been significant recovery, and our team has identified this as a resource issue. We are monitoring for stability in addition to investigating the root cause and det... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our team is considering increasing resources to address the issue with the Sidekiq backlog impacting CI/CD pipelines. We're working on a deployment fix to address this, though we are seeing some improvement overall with queue durations. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our team is still investigating this issue. Users might encounter some delays with processing CI/CD pipelines. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are seeing delays in CI/CD pipeline processing. The cause for this problem is under investigation. Please follow gitlab.com/gitlab-com/gl-infra/production/-/work_items/21484 for more details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
If a pipeline still appears stuck, please cancel and retry the affected job or pipeline. Protections deployed during this incident will prevent this in new pipelines. See gitlab.com/gitlab-com/gl-infra/production/-/work_items/21462 for complete details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
After consideration, we have decided not to automatically change previously stuck pipelines. Doing so could cause unsafe or stale state changes, for example around deployments and environments. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Pipelines affected by a previous incident on 3/5 continue to be stuck in Running status. We are working on a process to identify and safely correct these stuck pipelines, and will update this notice once that remediation is in place. Follow gitl... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
This incident is now resolved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have now identified the root cause and took actions to mitigate the issue. Git pull operations for GitLab's main repo are now working as expected. We'll continue to monitor the situation. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're noticing errors while pulling GitLab's main repository. This issue is currently under investigation. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
This incident has now been mitigated and services are back to normal. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We identified the cause of errors as excessive access by a specific user and implemented mitigation measures. We will continue to monitor the overall status of our services. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have identified the cause is due to excessive traffic against specific endpoints and have implemented mitigation measures. We're continuing to monitor the situation, and are seeing the error rates decrease. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Users are intermittently seeing HTTP 50X errors when attempting to access to gitlab.com. We will post again when we have material updates. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
As there is no current impact, we are setting this incide to Resolved. We have identified the problematic behavior behind it and are working on a long-term fix. However, we know this defect can reoccur under certain high‑concurrency conditions. See http... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
At this time, we are confident that current pipelines are not being affected by this behavior. We are continuing to monitor new reports closely until the top of the hour to ensure there is no ongoing impact. See gitlab.com/gitlab-com/gl-infra/production/-/work_items/21462 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have identified the cause of this incident as the recurrence of an existing defect in the pipeline job deferral mechanism. In this case, it was triggered by a period of temporary high pipeline concurrency. See gitlab.com/gitlab-com/gl-infra/production/-/work_items/21462 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We’ve identified a potential issue with the job deferral mechanism that may be affecting pipeline transitions between stages. For details, please see gitlab.com/gitlab-com/gl-infra/production/-/work_items/21462. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are currently reviewing logs from our production infrastructure and specifically the status and behavior of the pipeline workers for potential causes. Follow gitlab.com/gitlab-com/gl-infra/production/-/work_items/21462 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We’re still actively investigating and are currently collating data from affected pipelines to better understand the patterns and root cause. Please follow gitlab.com/gitlab-com/gl-infra/production/-/work_items/21462 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material change since the last update. The incident remains under active investigation. Follow gitlab.com/gitlab-com/gl-infra/production/-/work_items/21462 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Some users are experiencing CI/CD pipelines where jobs and pipelines are stuck in a “running” state, even though earlier-stage jobs have completed successfully. Follow gitlab.com/gitlab-com/gl-infra/production/-/work_items/21462 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are wrapping up our monitoring period and this incident is now resolved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
After deploying the patch, we are no longer seeing related errors and the service appears stable. We will continue to monitor for a period before considering this incident resolved. See gitlab.com/gitlab-com/gl-infra/production/-/work_items/21448 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have merged a patch that we believe will help restore GitLab Duo to a usable state, we are waiting for this change to be deployed to observe its impact. See gitlab.com/gitlab-com/gl-infra/production/-/work_items/21448 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
After further testing, the deployment without the suspected merge request has started exhibiting the errors again. We have identified an authentication failure as the cause of this issue and continue to troubleshoot it. Follow gitlab.com/gitlab-... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
GitLab Duo Agentic Chat is showing promising improvement after rolling back to a previous version, with responses returning more consistently. We are continuing to review the identified merge request and its changes to confirm whether it is the root cau... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have identified a recently deployed merge request as a potential cause of this issue and have begun rolling out the previous version to observe if behavior improves. See gitlab.com/gitlab-com/gl-infra/production/-/work_items/21448 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are observing transient authentication issues in our cloud connector service and are investigating this as a potential cause of the incident. Please follow gitlab.com/gitlab-com/gl-infra/production/-/work_items/21448 for updates. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are continuing to investigate this incident. The team is currently reviewing the stability of the cloud connector as a potential contributing factor, but this has not yet been confirmed. See gitlab.com/gitlab-com/gl-infra/production/-/work_items/21448 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material updates to share yet, please follow gitlab.com/gitlab-com/gl-infra/production/-/work_items/21448 for any updates. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Agentic chat on gitlab.com intermittently fails to return responses to user messages; the root cause is under investigation. See gitlab.com/gitlab-com/gl-infra/production/-/work_items/21448 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
This incident has now been mitigated and services are back to normal. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We identified the cause of errors as excessive access by a specific user and implemented mitigation measures. We continue to monitor the overall status of our services. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Users are intermittently seeing HTTP 50X errors when attempting to access to gitlab.com. We will post again when we have material updates. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Per further log inspection on our side, we're no longer seeing the problem occurring. The incident is now resolved. Refer to gitlab.com/gitlab-com/gl-infra/production/-/work_items/21436 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The upstream Cloudlfare incident has been resolved and now we monitor to confirm the login error is no longer present in our logs before proceeding to resolve this incident. See gitlab.com/gitlab-com/gl-infra/production/-/work_items/21436 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Cloudflare has declared a public incident to investigate this issue on their end. Please follow www.cloudflarestatus.com/incidents/t2skq2t69g5s and gitlab.com/gitlab-com/gl-infra/production/-/work_items/21436 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Cloudflare has identified a potential lead on their side and is investigating further. We will update this status page once we have more information to share from their side. Follow gitlab.com/gitlab-com/gl-infra/production/-/work_items/21436 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We continue working with Cloudflare support to figure out the cause of these errors. We will update this incident as any findings come along. See gitlab.com/gitlab-com/gl-infra/production/-/work_items/21436 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are involving Cloudflare to investigate a potential upstream problem and have reached out for their assistance. Please follow gitlab.com/gitlab-com/gl-infra/production/-/work_items/21436 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We started reviewing a recent change to our HTTP router as a contributing factor, but have now ruled it out and continue investigating other potential causes. We’ll provide another update once we have new information to share. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are now investigating whether an upstream component could be contributing to the behavior, though this has not yet been confirmed. See gitlab.com/gitlab-com/gl-infra/production/-/work_items/21436 for updates. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The rollback has completed, but we are not yet seeing a reduction in the frequency of the error messages. Investigation continues, see gitlab.com/gitlab-com/gl-infra/production/-/work_items/21436 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Rollback is still in progress. We’ll update this status page as soon as we have new information to share. See gitlab.com/gitlab-com/gl-infra/production/-/work_items/21436 for details.
status.gitlab.com -
GitLab.com Status
@gitlabstatus
We’ve identified a recent deployment that may be contributing to this issue and are preparing a rollback to see if it improves the situation. Keep tuned for more updates on gitlab.com/gitlab-com/gl-infra/production/-/work_items/21436. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material updates to report at this time. We continue tracing the errors to determine the root cause. Follow gitlab.com/gitlab-com/gl-infra/production/-/work_items/21436 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Users are intermittently seeing 400 Bad Request errors when attempting to log into gitlab.com. This does not seem to be affecting all users at the moment and investigation is ongoing. See gitlab.com/gitlab-com/gl-infra/production/-/work_items/21436 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
This incident is now resolved. More details here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21429 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The revert has been merged, and the flows are now operational. We are now monitoring the situation. More details here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21429 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Still no material updates at this time, the revert is in progress. More details here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21429 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material updates at this time, the revert is still in progress. More details here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21429 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've identified failures for remote flows, including Duo Developer, and other foundational workflows. Users are seeing failures such as "Session failed" when requesting code reviews through GitLab Duo. The root cause has been identified and a revert is... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have not seen any further reports of 403 or 429 errors on Git HTTPS requests, and customers should no longer be experiencing related CI/CD pipeline issues. As the service has remained stable, we will now resolve this incident. Details in: git... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We observed increased 403 and 429 errors on Git HTTPS requests affecting some CI/CD pipelines on gitlab.com. We have adjusted our protection rules to alleviate these errors and are monitoring to ensure stability. Details: https://... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We observed increased 403 errors on Git HTTPS requests affecting some CI/CD pipelines on gitlab.com. The underlying issue has been corrected and we are monitoring to ensure stability. Details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21389 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
After continued monitoring, performance has remained stable and within normal levels. As systems are operating as expected, this incident is now marked as resolved. Details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21361 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Background processing on gitlab.com has stabilized. We will continue monitoring for the next 24 hours. If the issue does not recur, this incident will be resolved. Otherwise, we’ll provide updates and take additional action as nee... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Background processing on gitlab.com continues to improve, but some users may still experience delays in pipeline execution and merge trains while the backlog is processed. Our engineers continue to investigate the root cause. Deta... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Background processing on gitlab.com has largely recovered, and user experience has noticeably improved over the past 15 minutes. We’re continuing to investigate the root cause and will share additional updates if we see any recurr... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We continue to see delays in background job processing on gitlab.com. Our engineers continue to investigate the root cause and work to restore normal performance. More details: gitlab.com/gitlab-com/gl-infra/production/-/issues/21361 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We do not have a material update to share at this time. Our engineering team continues to actively investigate and will provide further updates as soon as more information becomes available. Details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21361 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We’re investigating increased background processing delays on gitlab.com that are affecting pipeline execution and merge trains. Our engineering team is actively working to identify the cause and restore normal performance. Detail... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
After continued monitoring over the weekend, performance has remained stable and within normal levels. As systems are operating as expected, this incident is now marked as resolved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Performance for the Duo Agent Platform in Europe has been restored to normal.
For more information, please see: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21352 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We are experiencing degraded performance with the Duo Agent Platform in Europe. We have identified the root cause and are monitoring the situation.
More information on the incident can be found here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21352 status.gitlab.com -
GitLab.com Status
@gitlabstatus
The Gitaly team has applied mitigations to address performance issues and will monitor over the weekend. We have confirmed that current performance issues only affect internal GitLab operations. Customer activity should not be impacted at this time.
Wi... status.gitlab.com -
GitLab.com Status
@gitlabstatus
The Gitaly team continues to investigate and mitigate the performance issues on affected Gitaly nodes. We have not seen issues within the past 24 hours and continue to monitor closely. We are still working to identify a root cause. A status update will ... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The service has been stable for the past 90 minutes. The issue has been resolved.
gitlab.com/gitlab-com/gl-infra/production/-/work_items/21340 status.gitlab.com -
GitLab.com Status
@gitlabstatus
The Anthropic service in asia-northeast1 experienced partial disruption between 00:15 and 04:50 UTC, impacting the Duo Agentic Platform (DAP). The service has been stable now for the past 20 minutes and we are monitoring the situation for the next hour ... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are experiencing some Anthropic service disruption in the asia-northeast1 region. We are currently investigating to identify the cause. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The Gitaly team continues to investigate and mitigate the performance issues on affected Gitaly nodes. We are still working to identify a root cause and mitigation steps. A status update will be made within the next 8 hours. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The Gitaly team continues to investigate and mitigate the performance issues on affected Gitaly nodes. We are still working to identify a root cause and mitigation steps. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The Gitaly team continues to investigate and mitigate the performance issues on affected Gitaly nodes. We are still working to identify a root cause and will post an update within the next four hours if not sooner. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The Gitaly team continues to investigate and mitigate the performance issues on affected Gitaly nodes and are still working to identify a root cause. We will post an update within the next four hours. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The Gitaly team continues to investigate the performance issues on these Gitaly nodes and are still working to identify a root cause. We will update again in about two hours. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
GitLab is investigating ongoing issues with several Gitaly nodes that are causing intermittent 500 errors. We are working to identify the cause of instability on these nodes. Our investigation is ongoing; we will post again when we have material updates... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Restarting specific nodes improved the situation. We'll mark the incident as resolve while we keep monitoring the situation.
More information: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21303 status.gitlab.com -
GitLab.com Status
@gitlabstatus
Restarting specific nodes improved the situation. We'll keep monitoring the situation for now.
More information: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21303 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We're still exploring the solution for the git problem.
See details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21303 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We've identified the problem related to git activities. We're looking into solution.
See issue: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21303 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We're observing elevated 500 error rate on gitlab.com again and we're investigating the root cause.
See detail issue: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21303 status.gitlab.com -
GitLab.com Status
@gitlabstatus
Gitaly appears to be working normally at this time. We are continuing to monitor the issue and have mitigation steps should the issue reoccur. We do not anticipate further updates unless we start seeing degraded Gitaly performance again.
Further deta... status.gitlab.com -
GitLab.com Status
@gitlabstatus
The nodes have been rebooted and Gitaly appears to be working as expected. We are moving this incident to Monitoring. Our team is working to identify the root cause of these errors while we monitor the node performance.
Further details: gitl... status.gitlab.com -
GitLab.com Status
@gitlabstatus
We have rebooted the VMs that were generating 500 errors. Once the VMs have rebooted we will validate that Gitaly is responding normally and work to identify the root cause of these issues to prevent re-occurrence.
Further det... status.gitlab.com -
GitLab.com Status
@gitlabstatus
We are continuing to investigate the 500 errors on gitlab.com. We are investigating the root cause of the incident. We are preparing to apply mitigations to reduce error rates.
Further details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21310 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We have seen an unexpected increase in 500 errors on gitlab.com pages, often related to Merge Requests. We are investigating the root cause of these issues.
Further details in the incident issue: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21303 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We have recovered and are still monitoring.
gitlab.com/gitlab-com/gl-infra/production/-/work_items/21303 status.gitlab.com -
GitLab.com Status
@gitlabstatus
Partial service disruption due to this issue. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We see a 1.5% degraded state on two of our Gitaly nodes. Some customer may experience delays while contributing to their projects. We have identified the problem and we are working through steps to resolve this.
gitlab.com/gitlab-com/gl-infra/production/-/work_items/21303 status.gitlab.com -
GitLab.com Status
@gitlabstatus
The fix has been deployed, and no further errors are apparent. This is now resolved. For more information, please see: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21266 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The fix has been deployed, and we're monitoring the situation. We will resolve this incident if no further errors are observed. For more information, please see: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21266 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No updates at this time. The fix has been merged, and we're awaiting deployment to production. For more information, please see: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21266 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The fix has been merged. It should deploy to production in about an hour. For more information, please see: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21266 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Developer and Fix CI/CD Pipeline Duo Flows are currently failing due to a bug. The cause has been identified, and the fix is set to merge. For more information, please see: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21266 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
This issue is now resolved. The CI job queue on Hosted Runners and Environments/Review Apps have remained stable during our monitoring period. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have applied a fix and are now monitoring before marking as resolved. More details can be found in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21190. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Background processing remains degraded, affecting Environments and Review Apps, a fix is awaiting deployment. Hosted Runners and CI jobs are healthy. Details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21190. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've disabled the worker responsible for the issues. We've merged another fix for that specific worker and are in the process of deploying it to production before re-enabling it. The next update will be posted once that is completed. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Background processing remains degraded, however the revert MR has been merged a short time ago. We are monitoring performance to see if the MR results in performance returning to optimal levels.
See: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21190 status.gitlab.com -
GitLab.com Status
@gitlabstatus
Background processing remains degraded, affecting Environments & Review Apps. Hosted Runners and CI jobs are healthy. A revert MR is queued for production, with more changes needed to address background processing. See: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21190 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Hosted Runners continue to process without delay and are able to retrieve cached CI/CD variables. However some background processing is currently impacted and users may observe environments/review apps URLs not updating. We continue to wait for the fix ... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have observed that jobs on Hosted Runners are processing without delay and are able to retrieve cached CI/CD variables. We are currently awaiting deployment of a fix to ensure the issue remains mitigated. Details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21190. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have observed some improvement in queue times but are still investigating CI job delays on Hosted Runners and CI variable retrieval. Details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21190. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material update available at this time. Investigation into CI job delays on Hosted Runners and CI variable retrieval is ongoing. Details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21190. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Issues with Hosted Runner CI job queue delays and cache errors related to CI/CD variables are still under investigation. Self-hosted Runners are not currently affected. Details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21190. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Duo is once again fully available from within the GitLab UI and Visual Studio Code. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
In addition to CI job processing delays, users may also see "Failed to retrieve CI/CD variables from cache" when running new pipelines manually via the UI. Details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21190. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are continuing to see delays in CI job processing and are actively investigating mitigation steps. Details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21190. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Duo availability is back to normal. We are currently monitoring. See issue for details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21192 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
CI workloads are recovering as expected and should return to normal within the next hour. Some pipelines may still be delayed during this time. We are currently monitoring.
See issue for details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21190 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We have identified the cause and taken action to mitigate re-occurance. We are seeing recovery on CI workloads and it should return to normal within the next hour. Some delays are still expected during this time.
See issue for details: gitlab.... status.gitlab.com -
GitLab.com Status
@gitlabstatus
The issue has been identified to have been caused by a recent change. The change has been reverted and we expect Duo should be available for VSC and Web UI. See issue for details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21192 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Mitigation action has been taken and new pipelines can be triggered. Pipelines are being processed, but delays are still expected for up to 2 hours. Jobs may still be stuck in pending state during this time. See issue for details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21190 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The resource limits increase did not sufficiently mitigate impact. Investigation into cause and mitigation options is still in progress. See issue for details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21190 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
GitLab Duo is still unavailable for all users in both the VSCode extension and the web interface. We are currently investigating.
See issue for details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21192 status.gitlab.com -
GitLab.com Status
@gitlabstatus
GitLab Duo is unavailable for all users in both the VSCode extension and the web interface. Attempting to use the agentic chat triggers an error: "GitLab Duo is already responding to this chat in another tab or location." See issue for details: https://... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Resource limits have been increased and we are monitoring the impact. Investigation into the root cause is still in progress. See issue for details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21190 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Investigation is still underway. An MR to increase resource limits to mitigate impact is currently awaiting merge. See issue for details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21190 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have received reports of delayed or stuck pipelines, and jobs waiting longer than expected to execute. We are investigating. See issue for more details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21190 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've confirmed that the fix has been deployed and inline comment threads on merge requests can now be expanded and collapsed normally. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The fix has been deployed and we've observed the error rate return to 0%. This is now resolved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are experiencing elevated error rates affecting External Agents on the Duo Agent Platform caused by a recent deployment. We have reverted the offending merge request and are awaiting deployment of the fix. Details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21185. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Deployment of the fix is progressing. We will provide another update once the fix has landed within the next ~4 hours. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The fix has been merged and is currently being deployed to production.
A workaround is available, see issue for details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21184 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We have identified the recent refactor of a Vue component as the cause. We are preparing a fix for the problematic MR.
Workaround is available, see issue for details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21184 status.gitlab.com -
GitLab.com Status
@gitlabstatus
Collapsing and expanding inline comment threads is broken for merge requests. We are investigating. Workaround is available, see issue for details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21184 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have identified and disabled a feature flag that was the cause. Error rates have returned to normal.
Additional information can be found in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21160 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We identified that a recently enabled feature flag may have contributed to the pipeline failures on gitlab.com. The feature flag was just disabled, and we're now seeing a sharp drop in error rates.
Initial checks confirm that p... status.gitlab.com -
GitLab.com Status
@gitlabstatus
We are currently seeing issues with starting pipelines on gitlab.com and are investigating the issue. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The issue has been resolved and systems have returned to normal. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No changes since the last update. Access to gitlab.com remains restored, and monitoring alerts continue to show normal operation. We're continuing to monitor before marking this issue as resolved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The access gitlab.com has been restored, with users now able to log in and access previously affected pages.
Both the sign-in page and repository URLs are working again for users, and monitoring alerts have resolved. The request ... status.gitlab.com -
GitLab.com Status
@gitlabstatus
Some GitLab users and automated monitoring tools may see 404 errors when accessing the infrastructure repository on gitlab.com.
Workaround: Clearing your browser cache and logging in again to start a new session may resolve the i... status.gitlab.com -
GitLab.com Status
@gitlabstatus
A fix has now been deployed, and the issue is resolved. Details in: gitlab.com/gitlab-com/gl-infra/production/-/issues/21138 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
A partial workaround to this error is available: Duo availability for a group can be updated via the API. Please see the following comment in the production issue for important details and limitations: gitlab.com/gitlab-com/gl-infra/production/-/issues/21138 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
A revert MR has been merged and we are working to get this deployed to production. This may take up to 5 hours or more. Details in: gitlab.com/gitlab-com/gl-infra/production/-/issues/21138 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are aware of an error occurring when attempting to update Duo settings for groups on gitlab.com. We have identified the problematic change and are working on a revert. Details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21138 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The issue has been resolved. Foundational flows are now operating correctly as a GA feature. More details are available in gitlab.com/gitlab-org/gitlab/-/work_items/586912 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Foundational flows now run correctly when experimental/beta features are disabled.
Workaround: To enable foundational flows, temporarily turn on experimental/beta features, enable the flows, save, then disable experimental/beta features.
A complet... status.gitlab.com -
GitLab.com Status
@gitlabstatus
Foundational Flows are temporarily restricted to users with Beta/Experimental features enabled despite being a GA feature.
Our team has identified a fix. As a workaround, you can enable Beta and Experimental features to enable Foundational Flows.
... status.gitlab.com -
GitLab.com Status
@gitlabstatus
This incident is now resolved. Our team has confirmed that the rollback fixed the issue and we are no longer seeing 502 Bad Gateway errors. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our team has identified that the 502 Bad Gateway errors were related to a Cloudflare Worker deployment in the HTTP router. A rollback of the deployment is showing a decline in 502 errors for the artifact endpoints. Our team is continuing to monitor. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material updates at this time. Users may still experience intermittent "502 Bad Gateway" errors when running pipelines. More details available at gitlab.com/gitlab-com/gl-infra/production/-/issues/21096 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our team is currently working with Cloudflare to investigate the ongoing 502 errors. Users may still experience intermittent "502 Bad Gateway" errors when running pipelines. More details available at gitlab.com/gitlab-com/gl-infra/production/-/issues/21096 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material updates at this time. Users may still experience intermittent "502 Bad Gateway" errors when running pipelines. More details available at gitlab.com/gitlab-com/gl-infra/production/-/issues/21096 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are continuing to investigate intermittent "502 Bad Gateway" errors when running pipelines. More details available at gitlab.com/gitlab-com/gl-infra/production/-/issues/21096 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are continuing to investigate possible backend performance bottlenecks and other upstream factors that could be causing the intermittent "502 Bad Gateway" errors when running pipelines. More details available at gitlab.com/gitlab-com/gl-infra/production/-/issues/21096 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are still investigating the 502 intermittent errors when running pipelines. More details available at gitlab.com/gitlab-com/gl-infra/production/-/issues/21096 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating the rate limiting and related configuration changes is ongoing. Users might still experience intermittent 502 errors when running pipelines. More details available at gitlab.com/gitlab-com/gl-infra/production/-/issues/21096 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating a possible root cause, users still experience intermittent "502 Bad Gateway" errors when running pipelines. More details available at gitlab.com/gitlab-com/gl-infra/production/-/issues/21096 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating possible saturation. Users will still experience intermittent "502 Bad Gateway" errors when running pipelines. More details available at gitlab.com/gitlab-com/gl-infra/production/-/issues/21096 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are still investigating "502 Bad Gateway" errors when running pipelines. More details available at gitlab.com/gitlab-com/gl-infra/production/-/issues/21096 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are currently investigating pipelines failing with "502 Bad Gateway" errors. More details available at gitlab.com/gitlab-com/gl-infra/production/-/issues/21096 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We observe no more error on Classic Duo chat and confirm successful responses in the UI.
For further details, see gitlab.com/gitlab-com/gl-infra/production/-/work_items/21059 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We have deployed the changes to production. We're monitoring the situation.
For further details, see gitlab.com/gitlab-com/gl-infra/production/-/work_items/21059 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We're deploying the revert change to production.
For further details, see gitlab.com/gitlab-com/gl-infra/production/-/work_items/21059 status.gitlab.com -
GitLab.com Status
@gitlabstatus
The cause of degraded performance has been identified. We are preparing a code change to revert the recent deployment that introduced the issue.
A merge request has been opened to restore functionality: gitlab.com/gitlab-org/modelops/applied... status.gitlab.com -
GitLab.com Status
@gitlabstatus
We are investigating degraded performance with classic Duo chat. Requests may fail intermittently at this time.
For further details, see gitlab.com/gitlab-com/gl-infra/production/-/work_items/21059 status.gitlab.com -
GitLab.com Status
@gitlabstatus
The load has dropped down to normal after the fix. All systems are now operational. More details can be found in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21046. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have applied a fix and are now monitoring for 1 hour before marking as resolved. More details can be found in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21046. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are still working on narrowing down the cause for the low performance. The incident is tracked in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21046. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're investigating gitlab.com slow performance. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've completed our monitoring period and can confirm Duo Chat is back to operating normally. We appreciate your patience during this time. Full details in gitlab.com/gitlab-com/gl-infra/production/-/issues/21032 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are seeing further improvement and are continuing investigations. As a possible workaround, switching to a different model can be used. Full details in gitlab.com/gitlab-com/gl-infra/production/-/issues/21032 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are seeing improvements in the error rate and are continuing investigations. For full details, see gitlab.com/gitlab-com/gl-infra/production/-/issues/21032 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are seeing increased errors for Duo Classic. Users are experiencing Error Code: A1004. For full details, see gitlab.com/gitlab-com/gl-infra/production/-/issues/21032 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The fix has reached production and we're no longer seeing jobs stuck in pending state. This incident is resolved, but if you still see stuck jobs, please open a support ticket. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material updates at this time. We're continuing to monitor the situation. Please see here for more information: gitlab.com/gitlab-com/gl-infra/production/-/issues/20996 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our graphs show no new instances of jobs stuck as pending. We're continuing to monitor the situation. Please see here for more information: gitlab.com/gitlab-com/gl-infra/production/-/issues/20996 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material updates to report at this time. We are continuing to monitor recovery. Please see here for more information: gitlab.com/gitlab-com/gl-infra/production/-/issues/20996 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material updates to report at this time. We are continuing to monitor recovery. Please see here for more information: gitlab.com/gitlab-com/gl-infra/production/-/issues/20996
status.gitlab.com -
GitLab.com Status
@gitlabstatus
We have rolled out the feature flag for the fix, and will continue to monitor impact. For details: gitlab.com/gitlab-com/gl-infra/production/-/issues/20996. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No updates at this time. We are continuing to monitor recovery. Please see here for more information: gitlab.com/gitlab-com/gl-infra/production/-/issues/20996 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No further updates at this time. We are continuing to monitor recovery. Please see here for more information: gitlab.com/gitlab-com/gl-infra/production/-/issues/20996 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've merged a mitigation to address the issue and are continuing to monitor recovery. Please see here for more information: gitlab.com/gitlab-com/gl-infra/production/-/issues/20996 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Duo functionality has returned to normal and this incident is now resolved. For more details, please see: gitlab.com/gitlab-com/gl-infra/production/-/issues/21003 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We’ve identified the issue and merged a revert MR to address it. We’re seeing error rates recover and return to normal. For more details, please see: gitlab.com/gitlab-com/gl-infra/production/-/issues/21003 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have identified a recent change that was causing GitLab Duo to fail to respond for some customers. We are working on a fix. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're still investigating reports of CI/CD jobs stuck in pending status. Our team continues working to identify the root cause. Details: gitlab.com/gitlab-com/gl-infra/production/-/issues/20996 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No updates at this time. The team is still investigating the root cause, and a potential mitigation effort is underway. Please see here for more information: gitlab.com/gitlab-com/gl-infra/production/-/issues/20996 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The team is still investigating the root cause, and a potential mitigation effort is underway. Please see here for more information: gitlab.com/gitlab-com/gl-infra/production/-/issues/20996 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The team is still investigating the root cause. A potential mitigation effort is underway. Please see here for more information: gitlab.com/gitlab-com/gl-infra/production/-/issues/20996 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're receiving reports that some CI/CD jobs are stuck in pending status. The cause is currently under investigation. Please see here for more information: gitlab.com/gitlab-com/gl-infra/production/-/issues/20996 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The deployment for the fix for SSH signature endpoint errors has completed.
Please see gitlab.com/gitlab-com/gl-infra/production/-/issues/20989 for details. status.gitlab.com -
GitLab.com Status
@gitlabstatus
Deployment of the fix is ongoing and we estimate it will be ~4 hours until it is fully available. Details on a workaround for projects with SSH-signed commits in gitlab.com/gitlab-com/gl-infra/production/-/issues/20989. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are in the process of deploying the fix and are expecting this to take 4+ hours to complete. For full details, see gitlab.com/gitlab-com/gl-infra/production/-/issues/20989 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are seeing an increase in 500 errors from the SSH signature endpoints affecting commit-related pages for projects using SSH-signed commits. A possible workaround is to use `git pull` and work locally. Details in gitlab.com/gitlab-com/gl-infra/production/-/issues/20989 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The deployment is finished. We are marking this incident as solved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Development of the fix is complete and has been merged, we are now awaiting deployment to production. We will provide a further update once deployment is complete. Details in gitlab.com/gitlab-com/gl-infra/production/-/issues/20963 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material updates to provide. Development of the fix is progressing. We will provide another update within the next two hours. Details in gitlab.com/gitlab-com/gl-infra/production/-/issues/20963. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Development of the fix is ongoing and the issue remains mitigated in production on gitlab.com. We will provide another update in one hour. Details in gitlab.com/gitlab-com/gl-infra/production/-/issues/20963. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
After a rollback we've observed that the error rate has subsided, mitigating the issue. We're now focused on shipping a permanent fix for the issue. Details in gitlab.com/gitlab-com/gl-infra/production/-/issues/20963. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've identified that a recent deployment introduced the issue and are currently investigating mitigation options. Details in gitlab.com/gitlab-com/gl-infra/production/-/issues/20963. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating an issue in which requests to the Commits API is returning status code 400. Git operations remain operational. Details in gitlab.com/gitlab-com/gl-infra/production/-/issues/20963. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
gitlab.com functionality has returned to normal after Cloudflare applied a fix at 09:12 UTC. For more details, see gitlab.com/gitlab-com/gl-infra/production/-/work_items/20939 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
gitlab.com is becoming available for users. Cloudflare have applied a fix at their side at 09:12 UTC. We will continue to monitor the situation status.gitlab.com
-
GitLab.com Status
@gitlabstatus
gitlab.com is inaccessible at the moment due to a Cloudflare outage. We are currently investigating the cause. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
This issue has been resolved and all systems are back to fully operational. Details can be found in gitlab.com/gitlab-com/gl-infra/production/-/work_items/20914 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have finished the rollback of the MR to restore full operation. For further details, see gitlab.com/gitlab-com/gl-infra/production/-/work_items/20914 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have started the rollback of the MR that is the cause to restore full operation. For further details, see gitlab.com/gitlab-com/gl-infra/production/-/work_items/20914 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are seeing a problem with the Merged tab of merge request homepage not loading. The workaround is to use the Search tab instead. We are working on rolling back the relevant MR. Details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/20914 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The fix has been deployed to production. We are no longer seeing failures for pipelines that use inputs. This is now resolved. More details in: gitlab.com/gitlab-com/gl-infra/production/-/issues/20886 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are currently testing a fix for the pipeline creation issues in our sandbox environment. We estimate that the fix will be deployed to the production environment in approximately three hours.
More info: gitlab.com/gitlab-com/gl-infra/production/-/issues/20886 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We are in the process of deploying a fix for the pipeline creation issues. Our next update will follow deployment completion as we monitor the resolution.
More info: gitlab.com/gitlab-com/gl-infra/production/-/issues/20886 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We've identified the root cause of pipeline creation failures affecting pipelines that use inputs since Nov 24, 11:00 UTC. A fix is in the process of being deployed and we're monitoring for resolution. More info here: gitlab.com/gitlab-org/gitlab/-/merge_requests/213976 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have completed the infrastructure restoration tasks to fix the connectivity issue with the affected Runner. Since 17:51 UTC jobs on this Runner are being processed normally. This is now resolved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have identified the configuration causing network disruption with the affected Runner and we are working on fixing it. See gitlab.com/gitlab-com/gl-infra/production/-/issues/20878 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material updates to share. We appreciate your patience while we continue investigating this issue, please see gitlab.com/gitlab-com/gl-infra/production/-/issues/20878 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have identified a misconfiguration in our Runner infrastructure's routing policies as the potential cause for this issue. Follow gitlab.com/gitlab-com/gl-infra/production/-/issues/20878 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We continue to troubleshoot network connectivity for the affected Runner, no material updates to report. Follow gitlab.com/gitlab-com/gl-infra/production/-/issues/20878 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Latest troubleshooting results point a networking issue preventing connectivity with the affected macOS Runner. Investigation continues at gitlab.com/gitlab-com/gl-infra/production/-/issues/20878. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We continue investigating the root cause. See gitlab.com/gitlab-com/gl-infra/production/-/issues/20878 for more details status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material updates to report. We continue troubleshooting the runner's unavailability. See gitlab.com/gitlab-com/gl-infra/production/-/issues/20878 for more details status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Investigation is ongoing, and we're reviewing relevant runbooks for additional troubleshooting steps. See gitlab.com/gitlab-com/gl-infra/production/-/issues/20878 for more details status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've received reports that jobs that run on a specific macOS GitLab Runner (with the tag `saas-macos-large-m2pro`) have been failing with a “context deadline exceeded” error. We are in the process of investigating. As a workaround, you can switch to ot... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Performance has returned to normal, and we are marking this incident as resolved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The issue has been mitigated and we are monitoring for stability. For more info see gitlab.com/gitlab-com/gl-infra/production/-/issues/20870 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are working on mitigation of this issue. For more info see gitlab.com/gitlab-com/gl-infra/production/-/issues/20870 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've identified the cause of the service degradation to be related to excessive requests. For more info see gitlab.com/gitlab-com/gl-infra/production/-/issues/20870 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We’re seeing degraded performance on gitlab.com, investigation is underway in gitlab.com/gitlab-com/gl-infra/production/-/issues/20870 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The Cloudflare service incident affecting gitlab.com has been fully resolved. gitlab.com services are fully operational. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
GitLab services remain fully operational. We will continue to monitor the incident until Cloudflare finishes recovery. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have received no further reports of MacOS Runners failing to create CI caches so this incident is being marked as resolved. For more info see: gitlab.com/gitlab-com/gl-infra/production/-/issues/20841 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The affected MacOS Runners have been rolled back to a previous version and they have resumed creating CI caches. We will continue to monitor the Runners to ensure the matter is resolved. Further info: gitlab.com/gitlab-com/gl-infra/production/-/issues/20841 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have received reports that some MacOS GitLab Runners have been unable to create CI caches following a version update earlier today. We are in the process of rolling back the update. See gitlab.com/gitlab-com/gl-infra/production/-/issues/20841 for more details status.gitlab.com
-
GitLab.com Status
@gitlabstatus
It was determined that no further corrective action is required from an engineering standpoint. As a result, we're resolving the incident in favor of the two workarounds mentioned in the production issue here: gitlab.com/gitlab-com/gl-infra/production/-/issues/20827. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've identified that the API mismatch is a result of the Docker v29 release, which requires API v1.44+ (Docker v25.0+). For workarounds and details, please see the production issue: gitlab.com/gitlab-com/gl-infra/production/-/issues/20827 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've identified that recent pipeline failures were caused by an update to the latest Docker (DinD) image. For workarounds and details, please see the production issue: gitlab.com/gitlab-com/gl-infra/production/-/issues/20827 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Investigation is ongoing into blocked deployments caused by a mismatch in Docker API versions. More details can be found here: gitlab.com/gitlab-com/gl-infra/production/-/issues/20827 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our team is still investigating deployment issues linked to a mismatch between Docker API versions. Please see the incident issue for more information: gitlab.com/gitlab-com/gl-infra/production/-/issues/20827 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're still investigating blocked deployments due to a mismatch in API versions of Docker. More information about the incident can be found here: gitlab.com/gitlab-com/gl-infra/production/-/issues/20827 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our team is still investigating deployment issues that appear linked to a mismatch between Docker API versions. Please see the incident issue for more information: gitlab.com/gitlab-com/gl-infra/production/-/issues/20827 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Investigation is ongoing into deployment failures related to a Docker API version mismatch. Please see the incident issue for more information: gitlab.com/gitlab-com/gl-infra/production/-/issues/20827 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We’re continuing to investigate the blocked deployments, which appear to be caused by a mismatch in Docker API versions. More details are available here: gitlab.com/gitlab-com/gl-infra/production/-/issues/20827 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're still investigating blocked deployments due to a mismatch in API versions of Docker.
More information about the incident can be found here: gitlab.com/gitlab-com/gl-infra/production/-/issues/20827 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We're continuing to investigate blocked deployments due to a mismatch in API versions of Docker.
More information about the incident can be found here: gitlab.com/gitlab-com/gl-infra/production/-/issues/20827 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We're seeing errors with blocked deployments due to a mismatch in API versions of Docker.
More information about the incident can be found here: gitlab.com/gitlab-com/gl-infra/production/-/issues/20827 status.gitlab.com -
GitLab.com Status
@gitlabstatus
This incident has been resolved, and the secondary email confirmation functionality is now working as expected. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Until the issue is resolved on Monday APAC time, we have identified a workaround. See gitlab.com/gitlab-com/gl-infra/production/-/issues/20820 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We expect the issue with secondary email confirmations causing 404s to be resolved on Monday APAC time. See gitlab.com/gitlab-com/gl-infra/production/-/issues/20820 for more details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are aware of an issue where users are unable to confirm a newly added secondary email address. See gitlab.com/gitlab-com/gl-infra/production/-/issues/20820 for more details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Queues have returned to normal, and users should no longer be seeing delays. More info: gitlab.com/gitlab-com/gl-infra/production/-/issues/20797 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Some users may still be seeing slowness and delays on gitlab.com with background jobs. Queues have returned to normal, and we're monitoring the situation. More info: gitlab.com/gitlab-com/gl-infra/production/-/issues/20797 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Some users may still be seeing slowness and delays on gitlab.com with background jobs. We're seeing a reduction in delays, and are monitoring the situation. More info: gitlab.com/gitlab-com/gl-infra/production/-/issues/20797 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Some users may see slowness and delays on gitlab.com with background jobs. We're investigating the cause now. More info: gitlab.com/gitlab-com/gl-infra/production/-/issues/20797 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
After a period of monitoring we have seen no recurrence of the issue and consider the incident resolved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The errors affecting Duo Agentic chat have ceased and we are no longer seeing reports of this issue. We were unable to identify a definitive root cause, but deployed changes to improve monitoring. We will continue to monitor closely for the next hour be... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material updates available at this time as our investigation is still in progress. Another update will be provided no later than 23:00 UTC. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are continuing to investigate the root cause behind Duo reporting authentication errors and assessing if there is impact to other services. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating reports that some users may be receiving 401 authentication errors when using GitLab Duo Agentic chat. Updates will be provided as we learn more. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
GitLab services are now stable as AWS is recovering from the service disruption. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're currently experiencing degraded performance on services such as package registry, that depend on AWS services. We're currently monitoring the issue. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
This incident has been resolved and exact code search is now operational. For more information see gitlab.com/gitlab-com/gl-infra/production/-/issues/20706. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are in the process of releasing an update that should resolve issues with exact code search. For more information see gitlab.com/gitlab-com/gl-infra/production/-/issues/20706. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
This incident has been mitigated. More information can be found in gitlab.com/gitlab-com/gl-infra/production/-/issues/20706. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
A recent change has been confirmed as the cause of this issue. Our team is working on reverting the change. More details here: gitlab.com/gitlab-com/gl-infra/production/-/issues/20706 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material updates to report. Our team is still investigating this issue. More details here: gitlab.com/gitlab-com/gl-infra/production/-/issues/20706
status.gitlab.com -
GitLab.com Status
@gitlabstatus
Our team is still investigating this issue. More details here: gitlab.com/gitlab-com/gl-infra/production/-/issues/20706 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are currently investigating 500 errors affecting code search functionality on gitlab.com. Users may experience failures when searching code in repositories. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our team has been monitoring and GitLab is now operating normally. This incident is now resolved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The issue is currently mitigated and we're seeing recovery across GitLab. Our team is continuing to monitor. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're currently experiencing 500 errors on gitlab.com. Our team is currently investigating. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
This issue is now resolved. We experienced unavailability accompanied with 500 errors around 17:15 - 17:30 UTC. This has now returned to normal operations. Our team is continuing to investigate the root cause. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material updates at this time. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're seeing that behavior is largely normal at this time. Our team is still investigating the root cause. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our team is still investigating . No material updates at this time. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our team is still investigating this issue but error rate is currently improving. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our team is currently investigating 500 errors on gitlab.com. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our team has not seen any additional issues with git operations within the last hour. We are creating follow up items to further investigate resource exhaustion patterns. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are currently investigating issues with git operations. More details about this incident can be found in gitlab.com/gitlab-com/gl-infra/production/-/issues/20686. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
This incident has been resolved is now operational. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
This incident only impacts the gitlab-org/gitlab project and it's forks. Other projects are not affected by this incident. More details can be found in gitlab.com/gitlab-com/gl-infra/production/-/issues/20681. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No current updates at this time. We will provide more updates as new information becomes available. More details can be found in gitlab.com/gitlab-com/gl-infra/production/-/issues/20681. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've disabled the canary infrastructure as to mitigate the issues. We continue to monitor the situation to verify that this mitigates the incident. More details about this incident can be found in `gitlab.com/gitlab-com/gl-infra/production/-/issues/20681`. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are currently investigating issues with our canary infrastructure returning 5XX errors. More details about this incident can be found in `gitlab.com/gitlab-com/gl-infra/production/-/issues/20681`. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
This incident has been resolved and git operations are operational. More information can be found in `gitlab.com/gitlab-com/gl-infra/production/-/issues/20680`. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Git operations have recovered. We are investigating the root cause. More details can be found in `gitlab.com/gitlab-com/gl-infra/production/-/issues/20680`. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are currently investigating issues with git operations. More details about this incident can be found in `gitlab.com/gitlab-com/gl-infra/production/-/issues/20680. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The fix has been deployed and our monitoring shows that jobs are running as normal now. For full details, please see: gitlab.com/gitlab-com/gl-infra/production/-/issues/20621 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The recently merged changes have resolved the issue. We will continue to monitor system performance to ensure ongoing stability. More details are available here: gitlab.com/gitlab-com/gl-infra/production/-/issues/20664 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have merged changes to address this issue. Our next update will be provided once the changes have been fully deployed. More details are available here: gitlab.com/gitlab-com/gl-infra/production/-/issues/20664 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our teams are continuing to verify and implement mitigation steps. We’ll share additional updates as soon as more information becomes available: gitlab.com/gitlab-com/gl-infra/production/-/issues/20664 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Mitigation work is still underway as we continue to address the issue. Updates will be shared as progress is made: gitlab.com/gitlab-com/gl-infra/production/-/issues/20664 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
There are no new updates to share at this time. Work on mitigation is ongoing, and further information will be provided here: gitlab.com/gitlab-com/gl-infra/production/-/issues/20664 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material updates at this time. Mitigation efforts are still in progress, and additional details will be shared here: gitlab.com/gitlab-com/gl-infra/production/-/issues/20664 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We continue to work on mitigation efforts. Additional details are available in gitlab.com/gitlab-com/gl-infra/production/-/issues/20664 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've traced the artifact upload and download failures to a misconfiguration. We are working on implementing a mitigation. More information is available in gitlab.com/gitlab-com/gl-infra/production/-/issues/20664. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are still working on finding the root cause for this issue. The incident link is gitlab.com/gitlab-com/gl-infra/production/-/issues/20664. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material updates as of now, we're still investigating. More details here: gitlab.com/gitlab-com/gl-infra/production/-/issues/20664 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are investigating a problem which is causing CI jobs to time out when downloading or uploading artifacts. For additional details please see gitlab.com/gitlab-com/gl-infra/production/-/issues/20664. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The incident is now resolved, and we are no longer observing 401 errors. Please see gitlab.com/gitlab-com/gl-infra/production/-/issues/20621 for more details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The rollback has been completed, and we are observing a reduced rate of 401 errors. Please see gitlab.com/gitlab-com/gl-infra/production/-/issues/20621 for more details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have identified the MR that caused GitLab Runner versions older than 18 to see 401s when picking up jobs from gitlab.com.
We are rolling back the MR and will update here when rollback is complete.
See gitlab.com/gitlab-com/gl-infra/product... status.gitlab.com -
GitLab.com Status
@gitlabstatus
We are investigating reports of self-managed runners receiving 401 errors when trying to pick up jobs. See gitlab.com/gitlab-com/gl-infra/production/-/issues/20621 for more details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our monitoring shows that all jobs are running as normal now.
www.dockerstatus.com also shows no active issues. We will mark this as resolved. status.gitlab.com -
GitLab.com Status
@gitlabstatus
Docker has deployed a fix and we can see jobs being picked up.
See www.dockerstatus.com for more details. status.gitlab.com -
GitLab.com Status
@gitlabstatus
An ongoing incident at Docker Hub is causing pipeline jobs to fail.
Please follow www.dockerstatus.com for more details. status.gitlab.com -
GitLab.com Status
@gitlabstatus
The fix has been deployed and we are no longer seeing the related errors. For full details, please see gitlab.com/gitlab-com/gl-infra/production/-/issues/20588 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
An issue with epic board rendering has been identified on gitlab.com.
The cause has been identified and the fix is being deployed.
We will update here when deployment is complete. See more here: gitlab.com/gitlab-com/gl-infra/production/-/issues/20588 status.gitlab.com -
GitLab.com Status
@gitlabstatus
An issue with epic board rendering has been identified on gitlab.com. The cause has been identified and a fix will be deployed once a release hold is removed. We will update when release status changes. Incident tracked in: https:... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our monitoring shows that CI job functionality has fully recovered.
See gitlab.com/gitlab-com/gl-infra/production/-/issues/20592 for more details. status.gitlab.com -
GitLab.com Status
@gitlabstatus
The change has been deployed and CI Jobs have started to recover. The team is continuing to monitor the improvement.
See gitlab.com/gitlab-com/gl-infra/production/-/issues/20592 for more details. status.gitlab.com -
GitLab.com Status
@gitlabstatus
The configuration change to address the problem is in progress, and our team is monitoring the deployment.
See gitlab.com/gitlab-com/gl-infra/production/-/issues/20592 for more details. status.gitlab.com -
GitLab.com Status
@gitlabstatus
We have identified the issue and are working to mitigate it now. There will be an update in the next 30 minutes.
See gitlab.com/gitlab-com/gl-infra/production/-/issues/20592 for more details. status.gitlab.com -
GitLab.com Status
@gitlabstatus
Our team has identified a problem that is preventing CI jobs from being executed. We are working to fix the problem, and will update in the next 30 minutes.
More details here: gitlab.com/gitlab-com/gl-infra/production/-/issues/20592. status.gitlab.com -
GitLab.com Status
@gitlabstatus
The fix has been deployed and gitlab.com has returned to normal operation. If you still see elevated "Too Many Requests" errors on gitlab.com, please open a support ticket. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've deployed a fix and are currently monitoring the situation. If you still see elevated "Too Many Requests" errors on gitlab.com, please open a support ticket.
status.gitlab.com -
GitLab.com Status
@gitlabstatus
We've identified the cause of the elevated "Too Many Requests" error messages on gitlab.com. Mitigation is incoming. More info: gitlab.com/gitlab-com/gl-infra/production/-/issues/20564 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Certain users may see elevated "Too Many Requests" error messages on gitlab.com. We're currently investigating. More info: gitlab.com/gitlab-com/gl-infra/production/-/issues/20564 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Certain users may see elevated rate limiting errors on gitlab.com. We're currently investigating. More info: gitlab.com/gitlab-com/gl-infra/production/-/issues/20564 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
This incident is now resolved. After a monitoring period we have observed no further degraded performance across gitlab.com. More details at gitlab.com/gitlab-com/gl-infra/production/-/issues/20541 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are currently monitoring the situation, we do not expect users to see any impact at this stage. More information gitlab.com/gitlab-com/gl-infra/production/-/issues/20541 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are seen degradation across gitlab.com platform: slow or failing operations might be observed. More details at gitlab.com/gitlab-com/gl-infra/production/-/issues/20541 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
After a brief monitoring period we've confirmed that Gitaly is once again available. Clones and operations involving gitlab-org projects are now operational, so we're considering the incident resolved. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are continuing to investigate the root cause of the issue. Customers whose pipelines interact with artifacts hosted in gitlab-org may see 500 errors. Details in gitlab.com/gitlab-com/gl-infra/production/-/issues/20510. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The gitlab-org group is experiencing 500s. This issue is not widespread. Customers interacting with any gitlab-org repos might be affected.
More information about the incident: gitlab.com/gitlab-com/gl-infra/production/-/issues/20510 status.gitlab.com -
GitLab.com Status
@gitlabstatus
The rollback of production is complete. We are no longer seeing any performance degradation in code suggestion functionality.
More info can be found in the issue: gitlab.com/gitlab-com/gl-infra/production/-/issues/20499 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We're waiting for the fix to be completed in production.
Updates about the incident can be found here: gitlab.com/gitlab-com/gl-infra/production/-/issues/20499 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We're awaiting the completion of the fix on production.
Updates about the incident can be found here: gitlab.com/gitlab-com/gl-infra/production/-/issues/20499 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We're currently waiting for the fix to be completed in production.
Updates about the incident can be found here: gitlab.com/gitlab-com/gl-infra/production/-/issues/20499 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We're seeing elevated errors for the rails_request component, which affects AI-related services like code completion and code generation. We've identified the cause, and a fix is being implemented.
Read more about the incident ... status.gitlab.com -
GitLab.com Status
@gitlabstatus
Scheduled maintenance to upgrade our Gitaly storage nodes has now been successfully completed. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The gitaly storage nodes will now be upgraded. There may be brief, short-lived disruptions during the upgrade; however, no action is required from customers before or after the upgrade. Retrying operations should be sufficient once the service is restored. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
A recent change has been reverted and confirmed as the cause. Duo chat (Classic) is now working. For details, see gitlab.com/gitlab-com/gl-infra/production/-/issues/20483 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
All messages to Duo Chat classic are currently receiving A1004 errors. Duo Chat (Agentic) is working normally. Our team is currently investigating. For more information, see gitlab.com/gitlab-com/gl-infra/production/-/issues/20483 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our team is currently investigating an issue with Duo Chat. Users may experience A1004 errors. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Scheduled maintenance to upgrade our Gitaly storage nodes has completed for today. The maintenance will remain open to continue with additional batches on 2025-08-31. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Database is healthy and handling load as expected. This incident is now considered resolved. You can review all the details in gitlab.com/gitlab-com/gl-infra/production/-/issues/20442. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The database infrastructure expansion has been completed and is now fully operational. We will now monitor this to make sure performance is as expected. See gitlab.com/gitlab-com/gl-infra/production/-/issues/20442 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're now in the process to increase database capacity in our infrastructure. We will update this incident when this action completes. See gitlab.com/gitlab-com/gl-infra/production/-/issues/20442 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have identified saturation in one of our database replicas as the cause of this issue. We are adding additional database capacity to improve reliance while investigation continues. See gitlab.com/gitlab-com/gl-infra/production/-/issues/20442 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
CI activity is back to normal and the issue is no longer occurring. We continue working to identify the root cause of the issue. More details about this incident can be found in gitlab.com/gitlab-com/gl-infra/production/-/issues/20442 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are seeing CI activity returning to normal and jobs are being processed again. We continue working to identify the root cause of the issue. More details about this incident can be found in gitlab.com/gitlab-com/gl-infra/production/-/issues/20442 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are currently investigating issues with CI pipelines where jobs are in a pending state and not being picked up. More details about this incident can be found in gitlab.com/gitlab-com/gl-infra/production/-/issues/20442 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We consider this incident resolved as the errors are no longer seen in our production environment. See gitlab.com/gitlab-com/gl-infra/production/-/issues/20434 for all the details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The fix is now in our production environment, we are now monitoring for any new reports of the error before considering this incident resolved. See gitlab.com/gitlab-com/gl-infra/production/-/issues/20434 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The test results in our pre-production environments are positive. The 500 error is no longer seen. We now wait for the fix to be deployed to production. Follow gitlab.com/gitlab-com/gl-infra/production/-/issues/20434 for further details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We expect to have more information in our test results in ~30 minutes; this investigation continues. See gitlab.com/gitlab-com/gl-infra/production/-/issues/20434 for more details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We believe the originally identified root cause is the correct one for this incident. We continue testing the fix in our testing infrastructure to confirm this. See gitlab.com/gitlab-com/gl-infra/production/-/issues/20434 for more detals. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Investigation is still in process as a clear cause has not been identified yet. Please review gitlab.com/gitlab-com/gl-infra/production/-/issues/20434 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material updates to share at the moment. We continue investigating the root cause of these errors. Follow gitlab.com/gitlab-com/gl-infra/production/-/issues/20434 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
While testing the fix in our staging environment we have determined the root cause has not been fully identified. We continue to investigate this issue. Follow gitlab.com/gitlab-com/gl-infra/production/-/issues/20434 for updates. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Customers who have secret detection enabled and are pushing a file rename, may encounter a 500 error. The issue has been identified and a fix is being deployed. Please see the issue for details and workaround: gitlab.com/gitlab-com/gl-infra/production/-/issues/20434 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are no longer seeing errors related to GitLab Duo Agentic chat. This incident is resolved. More information in gitlab.com/gitlab-com/gl-infra/production/-/issues/20424 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The fix has been merged and we are seeing signs of recovery. We are now monitoring. For further details please see gitlab.com/gitlab-com/gl-infra/production/-/issues/20424 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are currently seeing increased errors and availability issues with the GitLab Duo Agentic chat when using the GitLab web interface. Regular GitLab Duo Chat is unaffected. We have identified the issue and preparing a fix. For further details please se... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The account verification issue on gitlab.com has been resolved. Users should now be able to complete account verification normally. More details: gitlab.com/gitlab-com/gl-infra/production/-/issues/20420 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Account verifications are now succeeding. We're monitoring closely to ensure continued success. More details: gitlab.com/gitlab-com/gl-infra/production/-/issues/20420 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Investigation continues with our service provider on the account verification issue. More details: gitlab.com/gitlab-com/gl-infra/production/-/issues/20420 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We’ve opened a support case with the upstream service provider and continue to investigate. More details: gitlab.com/gitlab-com/gl-infra/production/-/issues/20420 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're investigating an issue causing account verification failures on gitlab.com. Users may be unable to complete verification at this time. More details: gitlab.com/gitlab-com/gl-infra/production/-/issues/20420 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Scheduled maintenance to upgrade our Gitaly storage nodes has been postponed. The upcoming scheduled maintenance for Gitaly storage nodes is proceeding as planned. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
This incident has now been resolved. Please find more details here: gitlab.com/gitlab-com/gl-infra/production/-/issues/20398 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have now mitigated the issue and the error spike has subsided. We'll continue to monitor the situation. More details here: gitlab.com/gitlab-com/gl-infra/production/-/issues/20398 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have now identified the root cause and are in the process of reverting it. More details here: gitlab.com/gitlab-com/gl-infra/production/-/issues/20398 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material updates as of now, we're still investigating. More details here: gitlab.com/gitlab-com/gl-infra/production/-/issues/20398 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have noticed a spike of 400 errors on the /oauth/token endpoint. We're currently investigating. More details here: gitlab.com/gitlab-com/gl-infra/production/-/issues/20398 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Scheduled maintenance to upgrade our Gitaly storage nodes will begin in 2 days. There may be brief, short-lived disruptions during the upgrade. No action is required from users before or after the upgrade. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
GitLab is no longer seeing 500 errors on the gitlab-org/gitlab repository; our monitoring shows that our mitigations have resolved the incident. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're seeing 500 errors on the gitlab-org/gitlab repository, which may impact operations which try to download repository data from the gitlab-org/gitlab repository. We have implemented a mitigation and we are monitoring to ensure the repository is hea... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're seeing 500 errors on the gitlab-org/gitlab repository, which may impact operations which try to download repository data from the gitlab-org/gitlab repository. We believe we have identified the cause of the issue and we are implementing mitigatio... status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We're seeing 500 errors on the gitlab-org/gitlab repository, which may impact operations which try to download repository data from the gitlab-org/gitlab repository. We're currently investigating the root cause of this issue.
More information about ... status.gitlab.com -
GitLab.com Status
@gitlabstatus
This incident has been mitigated. For more information, see: gitlab.com/gitlab-com/gl-infra/production/-/issues/20305 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The team has enabled mitigation and the performance of the affected Shared Linux Runners has improved. We're monitoring the situation.
More: gitlab.com/gitlab-com/gl-infra/production/-/issues/20305 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We believe to have identified the source of the delays in job processing for Shared Linux Runners on gitlab.com, and the team is working on a solution.
More: gitlab.com/gitlab-com/gl-infra/production/-/issues/20305 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We've received reports of long job queue times for shared runners on gitlab.com. The team is currently working to rectify the behavior.
See: gitlab.com/gitlab-com/gl-infra/production/-/issues/20305 status.gitlab.com -
GitLab.com Status
@gitlabstatus
We are concluding our monitoring period and considering this incident resolved. Please review gitlab.com/gitlab-com/gl-infra/production/-/issues/20290 for all the details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
As of 19:00 UTC the fix for this issue was deployed to production. The affected features should be operational now. We will continue monitoring for any reports before considering this resolved. See gitlab.com/gitlab-com/gl-infra/production/-/issues/20290 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have started deploying the fix. Our next update will be in 3 hours. For more information and temporary workaround see: gitlab.com/gitlab-com/gl-infra/production/-/issues/20290 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Continuing with the tests in preparation for a rollout. Our next update will be in 3 hours. For more information and temporary workaround see: gitlab.com/gitlab-com/gl-infra/production/-/issues/20290 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have the MR ready and are running tests in preparation for a rollout. Our next update will be in 1 hour. For more information and temporary workaround see: gitlab.com/gitlab-com/gl-infra/production/-/issues/20290 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No materials updates at this time. We are continuing to work on a fix. Our next update will be in 1 hour. For more information and temporary workaround see: gitlab.com/gitlab-com/gl-infra/production/-/issues/20290 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
No material updates at this time. We are continuing to work on a fix. For more information and temporary workaround see: gitlab.com/gitlab-com/gl-infra/production/-/issues/20290 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
This incident is now resolved. For more information see: gitlab.com/gitlab-com/gl-infra/production/-/issues/20289 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have identified the root cause of the token error in GitLab Duo Chat, Duo Agent Platform, Agentic Duo Chat, and WebIDE. We are working on a fix. For more information and temporary workaround see: gitlab.com/gitlab-com/gl-infra/production/-/issues/20290 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are currently investigating the token error in GitLab Duo Chat, Duo Agent Platform, Agentic Duo Chat, and WebIDE. For more information and temporary workaround see: gitlab.com/gitlab-com/gl-infra/production/-/issues/20290 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The fix has been deployed and we are switching this incident to monitoring. For more information see: gitlab.com/gitlab-com/gl-infra/production/-/issues/20289 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Our team is in the process of reverting a recent deployment caused this issue. For more information see: gitlab.com/gitlab-com/gl-infra/production/-/issues/20289 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
[Investigating] We are currently investigating the G3002 error code issue in GitLab Duo Chat. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We consider this incident resolved. Please review the issue at gitlab.com/gitlab-com/gl-infra/production/-/issues/20287 for post-mortem information and follow-up tasks. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
Job activity continues to be normal. We will monitor this for half an hour more and consider it resolved if the issue does not reoccur. Follow gitlab.com/gitlab-com/gl-infra/production/-/issues/20287 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
As of 16:25 UTC our CI/CD job queue has gone back to operational levels. We continue to work with Google for any information on the cause. See gitlab.com/gitlab-com/gl-infra/production/-/issues/20287 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We will now update this incident as we receive information from our colleagues at Google. Follow gitlab.com/gitlab-com/gl-infra/production/-/issues/20287 for details. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have contacted Google to check on the capacity issues. This is being investigated on their end. See gitlab.com/gitlab-com/gl-infra/production/-/issues/20287. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have identified some capacity issues in our Google Cloud infrastructure as the cause of this problem. For more information see: gitlab.com/gitlab-com/gl-infra/production/-/issues/20287 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
The amount of queued jobs is steadily dropping, we continue working to identify the root cause. For more details please see : gitlab.com/gitlab-com/gl-infra/production/-/issues/20287 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are seeing a delay in jobs being scheduled on shared runners. For more information see: gitlab.com/gitlab-com/gl-infra/production/-/issues/20287 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
This incident has been resolved and the system is now operational. Details in gitlab.com/gitlab-com/gl-infra/production/-/issues/20279 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have merged the fix for this issue and are now awaiting its deployment to gitlab.com. Details in gitlab.com/gitlab-com/gl-infra/production/-/issues/20279. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
A fix has been developed and is currently undergoing QA testing. Until the fix is deployed, a workaround can be used. Workaround details in gitlab.com/gitlab-com/gl-infra/production/-/issues/20279. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have identified a merge request from a recent deployment as the root cause. Details in gitlab.com/gitlab-com/gl-infra/production/-/issues/20279. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are currently investigating issues with creating and forking projects from templates. Details in gitlab.com/gitlab-com/gl-infra/production/-/issues/20279. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
This incident has been mitigated. For more information check gitlab.com/gitlab-com/gl-infra/production/-/issues/20278 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We see that the jobs are being picked up in a timely manner. We are still monitoring the situation. For more information check gitlab.com/gitlab-com/gl-infra/production/-/issues/20278 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are seeing recovery of the CI/CD runners but the performance is still degraded. We are looking into it. For more information check gitlab.com/gitlab-com/gl-infra/production/-/issues/20278 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have now identified the root cause of the issue and are taking steps to mitigate it. For more information check gitlab.com/gitlab-com/gl-infra/production/-/issues/20278 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We are seeing slowness issue with CI/CD - Hosted runners on Linux. For more information check gitlab.com/gitlab-com/gl-infra/production/-/issues/20278 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
This incident is now resolved. After a monitoring period we have observed no recurrence of the issue and our upstream provider has confirmed that they resolved the issue. Details are available in gitlab.com/gitlab-com/gl-infra/production/-/issues/20261 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
GitLab is currently seeing increased errors rates related to an issue with an upstream provider. We are currently monitoring error rates. This can impact GitLab Duo related services such as GitLab Duo Chat, Agentic Duo Chat, and Duo Agent Platform. status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We see no new error rate. The incident is resolved. See details in gitlab.com/gitlab-com/gl-infra/production/-/issues/20244 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We've observed that error rates have been addressed and stability has been restored. We are currently monitoring. For details see gitlab.com/gitlab-com/gl-infra/production/-/issues/20244 status.gitlab.com
-
GitLab.com Status
@gitlabstatus
We have observed decreasing error rates and are continuing to monitor
For details, see gitlab.com/gitlab-com/gl-infra/production/-/issues/20244"
status.gitlab.com











































































































































































































































































































































































