Two modules in a repository had near-identical Azure DevOps build and release definitions. A third would have required another pair. The delivery chain used five definitions: one change decider, two builds, and two releases. I consolidated it into one decider, one generic build, and one release with a deployment stage for each onboarded module. The count excludes package and pull request validation. Figure 1. The consolidation removed one duplicated build and one duplicated release. The Decider Passes the Module as a Run Parameter The old builds repeated the same image and chart tasks with different module values. The releases repeated the same deployment tasks with different variable groups. A shared build change required matching edits in both build definitions, and a shared deployment change required matching edits in both release definitions. Adding another module would have required another build and release pair. I named the shared definitions by product, service, scope, an...
Splunk is gearing up to make an artificial intelligence (AI) model for analyzing log data available on Hugging Face under an open source license. Additionally, Splunk at its .conf26 conference this week revealed it is developing a Universal Collector, expected to be available in beta in 2027, to streamline collection of all types of telemetry data using an instance of OpenTelemetry. Raja Mukhopadhyay, vice president of observability cloud for the Splunk arm of Cisco, said a large language model (LLM) that has been trained to reason across log data will make it possible for DevOps teams to observe AI applications and agents at scale. The Universal Collector, meanwhile, lays the foundation for unifying DevOps, IT operations and security operations by making it simpler to correlate events without having to deploy separate repositories for different types of telemetry data. Previously, Splunk has made available an open source Cisco Time Series Model 1.0 on Hugging Face that has been s...