Operations | Monitoring | ITSM | DevOps | Cloud

Rob Zuber on why getting hands-on can give every team a better understanding of developers and the problems they’re solving.

AI agents now write, review and ship code, and our supply-chain security can't tell how that code was made. A green build and a clean scan don't tell you which model or tools the agent used, whether it had your security guidelines, or whether a human actually reviewed the change. In this talk I introduce Agentic Process Evidence, a proposed open community standard. It records the AI development process as structured, signed evidence that is attached to the commit and linked back to the full agent session logs, so release policies can enforce it automatically as policy as code.

CircleCI Smarter Testing is now generally available. In this tutorial, we’ll show you how Smarter Testing helps you run fewer tests, get faster feedback, and reduce unnecessary CI compute with three capabilities: Then, we’ll put it to the test. For the same code change, a traditional pipeline ran all 9,716 tests across 15 nodes. With Smarter Testing, CircleCI identified just 44 impacted tests and skipped the other 9,672, cutting test runtime from 3 minutes and 56 seconds to 22 seconds.

One file changed. 9,716 tests in the suite. Only 44 needed to run. See how Smarter Testing uses Test Impact Analysis to cut the unnecessary tests and get to feedback faster.

The old model: build the product, then build the machine to sell it. Now? The tools might change in 48 hours. Time to learn them all over again.

Turns out telling coding agents what to do over and over again doesn't actually make them better at fixing CI failures.