After 18 months of working on Ocuroot, I think it's time to move on. It's been a heck of a ride and quite the learning experience!

CI/CD pipelines are code too. In this post we'll explore some testing strategies so you're not always left waiting for feedback. We'll also look at what Ocuroot is doing to make it even easier!

With Ocuroot's new cascade mode, you can roll out a complex environment with a single command!

The Ocuroot client. Contribute to ocuroot/ocuroot development by creating an account on GitHub.

An update on how Ocuroot SDK v0.3 will handle dependencies, enabling seamless asset sharing and cross-deployment references.

A deeper look at the latest refinements to Ocuroot SDK v0.3: ordered phases, direct work specification, and flexible artifact creation.

At some point, many organizations will need to expand beyond a single production environment. Let's look at how you might arrive at this fork in the road!

A sneak peek at v0.3 of the Ocuroot SDK, featuring deterministic release ordering, state-machine deployment chaining, and non-blocking delays—with canary deployments as a primary example.

How imperative code in CI/CD configurations can unlock powerful workflows that declarative YAML simply can't handle.

How a good local testing workflow can accelerate your development cycle, approaches you can take today and how Ocuroot can help in the future.

Ship faster and more reliably with flexible, dynamic CI/CD

CI/CD that scales with you

CI/CD that scales with you

CI/CD that scales with you