MilikMilik

GitLab 19.0 Brings Agentic DevSecOps, Built-In Secrets Management, and Self-Hosted AI Models

GitLab 19.0 Brings Agentic DevSecOps, Built-In Secrets Management, and Self-Hosted AI Models

Tackling the AI Paradox with Agentic DevSecOps Workflows

GitLab 19.0 targets the so‑called AI paradox: AI accelerates code creation, but leaves review, security, and compliance workflows straining to keep up. The release deepens GitLab’s “agentic core,” embedding AI-driven workflows directly into merge requests and CI/CD so teams can move from code to production with fewer manual handoffs. Rather than treating automation, security, and governance as bolt‑ons, the platform orchestrates them on the same DevSecOps surface developers already use. Agentic merge request workflows can help enforce pipeline standards, structure reviews, and guide changes without constant human coordination. This unification matters for enterprises that are scaling AI code generation while trying to avoid fragmented tooling and inconsistent policies. By aligning intelligent automation with intelligent infrastructure orchestration, GitLab 19.0 positions itself as a DevSecOps platform where AI code review tools, governance, and deployment pipelines operate as a single, managed system.

Secrets Manager Redefines Credential Security in CI/CD Pipelines

The new GitLab Secrets Manager, now in public beta for Premium and Ultimate tiers, is the standout security change. Historically, placing a credential in a CI/CD variable exposed it to every job in a project, including future ones. GitLab 19.0 flips that default with job‑scoped secrets that embody least‑privilege access. When developers create a credential, they define exactly which branches, environments, and protected branches can use it. Anything outside that scope cannot see the secret, sharply limiting blast radius if a job is compromised. Secrets are stored in the same platform that runs code and pipelines, and access control plus audit logging reuse GitLab’s existing group and project model, avoiding separate permission systems. If a credential leaks, responders can track every job and originating pipeline tied to that secret from a single audit trail. The feature complements existing integrations with major external secrets management software, rather than replacing them.

Developer Flow: AI Assistance That Respects Team Standards

GitLab 19.0 significantly extends Developer Flow, its AI-powered workflow for turning issues into merge requests and keeping programmers in a focused state of work. Instead of generating generic code suggestions, Developer Flow reads project-specific standards from AGENTS.md and agent-config.yml, so its actions reflect each team’s conventions, architectural decisions, environment quirks, and tooling. The agent gets a fully prepared environment to run tests and pre‑commit hooks before committing, reducing rework and ensuring its output aligns with existing pipelines. New beta capabilities include a Resolve with Duo button that compares both branches, proposes a fix, commits it, and leaves a summary for reviewers, plus a one-click rebase‑and‑merge option for semi‑linear or fast‑forward strategies. Available across Free, Premium, and Ultimate tiers, Developer Flow effectively turns AI code review tools into context-aware collaborators that can address feedback, split oversized merge requests, and move features forward without breaking established DevSecOps practices.

Self-Hosted Duo Models and Supply Chain Visibility for Enterprises

For organizations wary of vendor lock‑in and data residency issues, GitLab 19.0 expands support for self-hosted AI within GitLab Duo Agent Platform. Agents can now run on four open-source models—Mistral Devstral 2 123B, GLM-5.1, Kimi-K2.6, and MiniMax-M2.7—evaluated for multi-step tool use, code generation quality, and reasoning over large code diffs. This self-hosted AI model approach gives enterprises more control over where inference runs and how data is handled, easing compliance concerns while retaining advanced AI capabilities. On the platform engineering side, Components Analytics increases visibility into which CI/CD catalog components are running across the organization and which versions are in use. Combined with broader supply chain insights, this helps teams understand dependency usage and potential vulnerabilities end‑to‑end. Together, self-hosted AI models and supply chain analytics reinforce GitLab’s positioning as a DevSecOps platform that unifies AI, governance, and software supply chain security.

Comments
Say Something...
No comments yet. Be the first to share your thoughts!