AI 服務暫時不可用，以下為來源正文，待恢復後補全翻譯。
When new CloudBees CEO Mo Plassnig took the job earlier this year, his board of directors handed him a mandate that left little room for interpretation: Do not stay the course. In an era when generative AI is radically reshaping how software is written, deployed, and managed, keeping things business-as-usual for an enterprise continuous integration/delivery (CI/CD) stalwart like CloudBees would be a ticket to irrelevance. Last week at the WeAreDevelopers Conference in San Jose, California, Plassnig unpacked for The New Stack podcast how he plans to steer the company through its biggest transformation yet: Pivoting CloudBees into an AI-first organization built to survive a world drowning in machine-generated code. A homecoming driven by generative AI Plassnig first joined CloudBees eight years ago when the company acquired CodeShip, the DevOps CI/CD startup he co-founded. After spending several post-acquisition years building CloudBees products, he took a hiatus to work in security. “…when generative AI emerged, it reignited my passion.” “I didn’t think much about DevOps or CI/CD for several years,” Plassnig says. “However, when generative AI emerged, it reignited my passion. I became extremely excited about what we could achieve in our domain, which ultimately brought me back to CloudBees.” That excitement stems from a stark reality: AI is creating an order-of-magnitude shift in code volume. While hype merchants on social media obsess over autonomous agents taking over software engineering jobs entirely, enterprise leaders face a more immediate problem: How on earth do you manage the deluge of software currently pouring out of AI models? Enterprise reality vs. social media hype Having spent his first few months as CEO touring Fortune 500 enterprises, large public organizations, and global enterprises, Plassnig tells us in the interview that he saw a distinct mismatch between internet hot takes and ground-level enterprise execution. “What they are doing on the ground differs significantly from conference hype or public commentary on social media,” Plassnig says. “While everyone recognizes that agentic coding represents the future, adopting these technologies within large enterprises requires extensive, hard work. It isn’t strictly a technology problem; it demands process transformation, governance, and stringent security.” How he plans to carry out his reinvention of CloudBees and its popular open-source Jenkins automation server is a story worth hearing. Invest 25 minutes here and learn about it. The post CloudBees just committed to an AI-first pivot. Here’s why it matters for enterprise DevOps teams appeared first on The New Stack.