cdCon 2022

Building and delivering software faster and better gained a different meaning with the introduction of pipeline-based technologies like Jenkins. Today, developers can automate the whole software development lifecycle by programmatically implementing build, testing, and deployment to achieve development agility. While this is great on the one hand, it poses an important question to be answered: what if the pipeline has a bug? For this reason, pipeline maintainers ought to have a strategy in place capable of verifying the pipeline code's accuracy, correctness, and reliability. Luckily for us, Jenkins allows this by providing a plugin compatible with OpenTelemetry — a technology that grants developers the ability to evaluate their code using an observability backend. This session will explain how this works and demonstrate how to get value from this.

Today, software delivery is harder than ever. Developers are delivering on top of a mountain of dependencies that they can’t always see. Single sources of change within the pipeline are complicated by an external ecosystem of changes that can be anything. Even the most experienced engineers cannot comprehend all of the components and moving parts that go into the products they build, yet they’re still expected to deliver software incredibly fast with no bugs. The last 10 years were all about code, but given the current complexities, focusing on your code is only half of the solution. The future of software delivery operates in an automated network, alive with dynamic, two-way intelligence. In this talk, Michael Stahnke, Vice President at CircleCI will help you prepare your teams for infinite change, and create a resilient network of software to withstand any amount of constant change.
Takeaways include:

• Organic patterns to break that encourage incompleteness
• How to identify + validate changes from an infinite amount of sources across the software ecosystem
• Ways to empower developers and teams to act on these changes