Menu

Dimensional Data

DevSecOps
DevSecOps GitLab Duo Agent Platform

GitLab Duo Agent Platform 2026: Revoluția AI Agentic în DevSecOps

Noutați, Software

În ultimii ani, inteligența artificială a promis o revoluție în dezvoltarea software, însă realitatea din teren a scos la iveală o problemă neașteptată: „Paradoxul AI”. Deși dezvoltatorii scriu cod mai rapid cu ajutorul asistenților generativi, viteza de livrare a produselor finite nu a crescut proporțional. Motivul? Codarea reprezintă doar 20% din munca unui programator. Restul de 80% este blocat în procese de planificare, securitate, recenzii de cod și depanare. Lansarea generală a GitLab Duo Agent Platform marchează sfârșitul acestei ere a câștigurilor incrementale. Nu mai vorbim despre un simplu chatbot, ci despre o platformă integrată de agenți AI capabili să execute sarcini complexe în mod autonom, transformând întregul ciclu de viață al dezvoltării software (SDLC). Ce este GitLab Duo Agent Platform? GitLab Duo Agent Platform este prima soluție de tip „Agentic AI” creată special pentru mediul enterprise, care unifică inteligența artificială cu fluxurile de lucru DevSecOps. Spre deosebire de instrumentele AI tradiționale care oferă doar sugestii pasive, această platformă utilizează agenți software care pot „raționa”, pot lua decizii și pot executa acțiuni multi-pas pe baza contextului complet al proiectului tău. De ce este nevoie de o platformă agentică acum? Echipele de inginerie se confruntă cu un volum de muncă fără precedent. Creșterea vitezei de scriere a codului a dus, paradoxal, la blocaje în aval: GitLab Duo Agent Platform rezolvă aceste provocări prin orchestrare inteligentă, acționând ca un multiplicator de forță pentru fiecare membru al echipei. Caracteristici Cheie: Cum funcționează GitLab Duo Agent Platform 1. Agentic Chat: Dincolo de conversațiile simple Inima platformei este noul Agentic Chat. Acesta nu se limitează la a răspunde la întrebări teoretice. Datorită accesului la contextul complet din GitLab — inclusiv issue-uri, merge requests (MRs), pipeline-uri și rezultate de securitate — Agentic Chat poate: 2. Agenții Fundaționali: Specialiștii tăi 24/7 Platforma include agenți pre-construiți de experții GitLab pentru cele mai critice sarcini: 3. AI Catalog și Agenți Personalizați Fiecare organizație are propriile standarde de inginerie. Prin intermediul AI Catalog, echipele pot crea și partaja proprii agenți personalizați. Aceștia pot fi instruiți să urmeze regulile specifice de conformitate sau stilul de codare al companiei tale, asigurând un nivel de consistență imposibil de atins manual. 4. Integrarea cu Modele Externe (Anthropic, OpenAI) GitLab Duo Agent Platform este agnostică din punct de vedere al modelului. Poți utiliza puterea unor instrumente de top precum Claude Code (Anthropic) sau Codex CLI (OpenAI) direct din interfața GitLab, beneficiind în același timp de securitatea și guvernanța oferite de platformă. Impactul asupra Productivității: Cifre și Viziune Conform datelor colectate, dezvoltatorii care folosesc AI raportau deja creșteri de productivitate la nivel de codare. Însă, cu GitLab Duo Agent Platform, obiectivul este accelerarea „Velocity of Innovation” (viteza inovației). Etapa SDLC Metodă Tradițională Cu GitLab Duo Agent Platform Planificare Ore de ședințe și documentare Generare automată de tichete de către Planner Agent Securitate Verificări manuale post-factum Scanare și remediere asistată în timp real Code Review Așteptare de zile pentru feedback Analiză AI-native instantanee pentru erori logice Depanare CI/CD Căutare manuală în log-uri Identificare automată a cauzei eșecului Arhitectura și Securitatea: Pilonii GitLab Duo Agent Platform Într-un mediu enterprise, securitatea datelor este nenegociabilă. GitLab a construit această platformă pe principiul transparenței și controlului total. Model Selection Framework Administratorii au puterea de a alege ce Large Language Model (LLM) doresc să folosească. Poți opta pentru: Guvernanță și Conformitate Toate […]

Read More

Diffblue Integrates Generative AI-Based Testing Platform With GitLab

Noutați

Diffblue this week generally made available an integration between its automated unit testing platform for Java and the DevSecOps platform from GitLab. The Diffblue Cover platform makes use of generative artificial intelligence (AI) to automatically create unit tests based on reinforcement learning technologies that don’t rely on LLMs—avoiding their drawbacks of sometimes introducing hallucinations and also requiring human review. Diffblue CEO Mathew Lodge said the integration with the continuous integration capabilities found in the premium and ultimate editions of the GitLab platform would, for example, streamline regression testing in a way that should ultimately improve both application quality and security. Diffblue Cover, for example, can update tests as much as 250 times faster than a human developer can write them manually without developer review. That approach also serves to reduce the level of friction many DevSecOps teams encounter when bottlenecks involving testing processes emerge, noted Lodge. The overall goal is to make it simpler for developers to test as much of their own code as possible before integrating it into a build, he added. Otherwise, developers will get fed up because testing is continuously breaking the build, noted Lodge. Ultimately, instead of having to write unit tests, developers become supervisors of a platform that automatically generates them on their behalf, said Lodge. The job of a developer doesn’t go away, but it does fundamentally change, he added. To achieve that goal, developers need to be able to access a platform that writes the tests and can then also execute them automatically. If it takes too long to create the test, chances are high that most developers won’t run it. On average, writing and evaluating a single unit test can take a developer 10 minutes. Over the course of any project, thousands of tests need to be written, so the amount of time testing takes away from coding is often much greater than most IT leaders fully appreciate. Automating those tests should improve developer productivity as more time is available to focus on writing code rather than testing. That doesn’t necessarily eliminate the need for a dedicated testing team, but it does mean that more tests will be run without slowing down the overall pace of application development. Developers naturally want to be able to test code at the very instant they create it. AI platforms can make that happen by, for example, employing reinforcement learning to write unit regression tests. Most developers are not going to resist assuming more responsibility for testing if the tools to automate that task are more accessible. Instead of merely shifting responsibility for testing left toward developers, DevOps teams need to find ways to streamline the process. Otherwise, testing just becomes one in a series of tasks that are being shifted to developers in ways that many of them are coming to resent. It may take some time before AI is fully integrated into software engineering but it’s clear with each passing day more previously manual tasks are being automated. Among the lowest hanging fruit for applying AI to software engineering are clearly testing processes that, if truth be told, few indeed enjoy conducting.

Read More

Digital.ai Update Extends Scope and Reach of DevSecOps Platform

Noutați

Digital.ai this week made generally available a Denali update to its DevSecOps platform that promises to make it simpler to integrate custom artificial intelligence (AI) models with the AI models developed by the company. At the same time, the company is adding self-guided workflows and templates to generate tests and implement DevSecOps best practices along with integrations with Terraform by Hashicorp, Azure Bicep, Azure Key Vault and AWS Secrets Manager. Finally, Digital.ai is adding an ARM Protection feature to better secure iOS applications without requiring embedded bitcode or integrations into the build system. DevOps teams can, via a single command, protect compiled applications locally with support for obfuscation, run-time active protections and application monitoring without uploading them to a third-party service. Greg Ellis, general manager for application security for Digital.ai, said the overall goal is to make it simpler for software engineering teams to invoke capabilities that have been embedded within the company’s DevSecOps platform. In the case of AI models, that also means instead of requiring DevOps teams to only use AI models developed by Digital.ai, the company is moving to make it simpler for DevOps teams that adopt its platform to incorporate custom AI models as they see fit as part of an ongoing effort to democratize intelligence at scale, he noted. In general, it’s already apparent organizations will be employing heterogeneous approaches to incorporating AI models into DevOps workflows, said Ellis. The challenge now is moving beyond experimenting with AI to embedding them within DevOps workflows, he added. It’s already clear developers are using generative AI to develop code at increasingly faster rates. The challenge now is to manage that accelerated pace of development when many organizations are already struggling to manage existing DevOps workflows at scale. Hopefully, AI technologies will also one day help software engineers find ways to manage that volume of code moving across their DevOps pipelines. In the meantime, organizations will also need to better define where the machine learning operations (MLOps) workflows that data scientists use to build AI models end and where DevOps workflows that will be used to embed AI models into applications begin. As is often the case when it comes to emerging technologies, cultural issues are just as challenging as the implementation hurdles that need to be overcome. At this point, like it or not, the generative AI genie is out of the proverbial bottle. Just about every job function imaginable will be impacted to varying degrees. In the case of DevOps teams, the ultimate impact should involve less drudgery as many of the manual tasks that conspire to make managing DevOps workflows tedious are eliminated. Less clear is to what degree AI may drive organizations that have already embraced DevOps to adopt an alternative platform, but savvy DevOps teams are, at the very least, starting to map out which processes are about to be automated so they can have more time to focus on issues that add more value to the business.

Read More
Kiuwan-Romania-DevOpsApproachto Code Security

Understanding the DevOps Approach to Code Security

Noutați

DevOps generally means integrating software development (dev) and information technology operations (ops) to speed the lifecycle, deliver better features, updates and fixes, and more. What’s sometimes missing from this perspective? Code Security. Here’s a description of how to bring security fully into this picture, and integrate it all the way from design, through development and test, and into production. DevOps is a set of software development practices that combines software development (Dev) and information technology operations (Ops) to shorten the systems development life cycle while delivering features, fixes, and updates frequently in close alignment with business objectives. Most experts agree that DevOps actually combines three key ingredients: People, meaning developers and their hangers-on (testing, QA, and so forth), IT professionals, and other “interested parties” – usually stakeholders in what’s being developed and maintained. Process, meaning a deliberate and calculated focus on the software development lifecycle as a formal process, that uses methods like Scrum to codify and stimulate team communications among all the people involved (not just developers, but everybody) with CI/CD (Continuous Integration and Continuous Deployment) to continuously integrate code changes and deploy applications to production as needed, scheduled, or available. Tools, meaning software tools used to help the people fully implement the process. Tools to enable IT automation are essential to making DevOps work properly According to The DevOps Handbook, the real essence of DevOps depends on “applying the most trusted principles from the domain of physical manufacturing and leadership to the IT value stream.” It goes on to mention a slew of bodies of knowledge that include Lean, Theory of Constraints, resilience engineering, learning organizations (continuous learning and continuous improvement)Kiu, safety culture, human factors, and more. On the leadership side, it cites to high-trust management cultures, servant leadership, and organizational change management. DevOps isn’t just a combination of Dev and Ops, it’s actually an entire frame of reference for doing development and IT correctly, responsibly, and repeatedly. Where Does Code Security Come Into DevOps? The short, flippant answer to this question is correct, but overly brief – namely “Everywhere.” That is, security has to be part of the process used for DevOps, it has to be built into the tools used to do DevOps (or make it happen), and, above all, it needs to be high up in the minds of the people involved in DevOps. Kiuwan offers a way to bring security in throughout the entire DevOps lifecycle. It offers the ability to scan code for vulnerabilities and even to automate relevant remediation (where available). But because the Kiuwan tools integrate with various well-known development environments, this makes scanning code for security vulnerabilities, adoption of security coding standards, and automatic error prevent part and parcel of the development, test, and update/maintenance processes across the entire lifecycle. Kiuwan’s IDE integrations encompass the following families and items: Eclipse-based IDEs: Luna, RAD, IBM Rational Developer) Microsoft Visual Studio and Visual Studio Code JetBrains-based IDEs: Intellij IDEA, PhpStorm, PyCharm, Android Studio, and CLion Thus, organizations gain lots of traction to build security (and code scanning) into all phases of their development, maintenance, and deployment efforts. This is why some refer to the most productive mindset in this arena not simply as DevOps but rather as DevSecOps to put security on par with the equally important frameworks that help to formalize and […]

Read More
DevSecOps COVID-19 in Romania

What DevSecOps Teams Can Learn from COVID-19

Noutați

Over the last few months, the whole world has fundamentally changed due to the emergence of a novel coronavirus, COVID-19. The highly infectious nature of the virus, its devastating impact on vulnerable individuals who catch it, and the lack of a vaccine have allowed COVID-19 to become a global pandemic. Institutions of all types have been closed and life as we know it has been fundamentally changed. Officials argue about the “right” way to emerge from this self-imposed shutdown, but all agree that our world is different now. DevSecOps is one tiny part of the global economy, but it can benefit from the lessons this crisis can teach us. At its core, a DevSecOps philosophy exists to prevent a major disruption like COVID-19 from threatening an organization’s survival. That is not to say the DevSecOps could prevent a real-world virus, but how we approach an emergency should shape the way our DevSecOps teams approach their charters. We can all learn a great deal by looking at the COVID-19 crisis and examining how we can do things better next time.  The element of surprise Don’t underestimate the humanness of any team. Group dynamics affect every team’s performance and its ability to function effectively, and DevSecOps is no different. In fact, the degree to which a DevSecOps team adds value to its organization depends on its ability to function productively. Contentious competition rarely results in positive team outcomes. The fact is that we — as a community, a nation, and a global population — were not ready for COVID-19. There were a few qualified individuals who warned of such a pandemic for many years, but their warnings didn’t gain much traction. Traditional risk management had placed a pandemic like COVID-19 too low on the priority list to warrant a sufficient preparation budget. We flat out missed it. Hindsight is 20/20, and it is so easy to criticize others in retrospect. That isn’t the purpose here, and analysis for criticism is not very productive. Critical analysis, on the other hand, can be very productive. Those are very different approaches. Critical analysis of how we prepared for and managed the COVID-19 pandemic can provide DevSecOps teams with valuable insight into how to handle crises.  This novel virus took everyone by surprise. We had not properly recognized the threat, we had not invested in preparing for such a threat to be realized, and we failed to understand the gravity of the problem in its early stages. Analysts depended on limited and incomplete data to fuel models that were speculative and dynamic. Traditional data and models built for other similar outbreaks weren’t able to provide the granular results necessary to take decisive action. Authorities at all levels took good-faith action based on their interpretation of the latest models, but interpretations differed, and the resulting actions weren’t coordinated in many cases.  The DevSecOps takeaway is that our teams exist primarily to avoid competing for jurisdictional mandates. Cohesiveness is more than a happy feeling; it provides the ability to react uniformly to a crisis. The focus of an effective DevSecOps team should be to invest extensively in risk assessment, including exhaustive threat modeling, to understand its organization’s attack surface. Preparation is expensive, but being surprised costs a lot more.  Unplanned change isn’t easy The Project Management Institute’s (PMI) […]

Read More

Abonează-te la noutăți

Primiți noutăți și oferte despre SDLC tools

Close Menu