After 18 months working on Ocuroot, it's time to move on. I've had quite a ride but there's no better time than a new year to make changes and try something different.
This post goes into why things didn't work out, what I learned, and why it was totally worth it.
www.ocuroot.com/blog/winding...
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!
www.ocuroot.com/blog/how-do-...
Ocuroot v0.3.16 introduces cascade mode, which allows one command to run all the work associated with a release or intent update, even across different config files, commits or repos.
Final impact? Faster releases and simpler, more reliable CI integration.
www.ocuroot.com/blog/cascade...
In the v0.3.14 release post for @ocuroot.com, I mentioned that CI integration isn't as simple as it could be - so that's been my focus since.
Ocuroot can now perform work across multiple repos and commits in a single run, meaning less setup and faster time to stability.
#openstandup #buildinpublic
Short and sweet update today! Added a little detail on the config being loaded to help with debugging.
At a conference today, but keep an eye out for a new release tomorrow!
github.com/ocuroot/ocur...
#openstandup #buildinpublic
Cleaned up those annoying UI issues from yesterday and cut v0.3.13. See github.com/ocuroot/ocur...
I don't want to stay on 13 too long (superstitious), so will make some more tweaks today to cut a new version ready to announce later this week.
#openstandup #buildinpublic
Trying something new, a video open standup! Added a couple of new features to clear up some confusion in the quickstart, a dryrun flag and comprehensive mode.
Still has a few improvements needed, that I'll work on today.
#openstandup #buildinpublic
Silly milestone alert! The Ocuroot client repo just hit 10 stars.
This is from sharing with a few friends for feedback. Broader announcements to come, but why not celebrate the tiny wins along the way?
Thanks to @travisirby.bsky.social for putting it into double-digits.
github.com/ocuroot/ocur...
Tired of connecting related CI/CD pipelines with duct tape and bubble gum?
In this week's post, I'm introducing the inputs model for dependency management in the upcoming Ocuroot SDK v0.3. No more manual coping of configuration or painfully complex conventions for naming resources.
✨ New Ocuroot SDK blog post! ✨
I've been refining the v0.3 design so it's time to share some improvements to release definition.
The biggest change? Phases now run in sequential order - no more complex dependency graphs to mentally untangle!
Find out why I made this choice here:
Referrer stats for a website, with 1 view from ChatGPT.
Here's a first, got a visitor to the @ocuroot.com site from ChatGPT!
Also interesting to see DuckDuckGo and Brave in the list - the former has been pretty consistently appearing. Wonder if that's a developer thing, or a "people doing research" thing.
#buildinpublic
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!
buff.ly/hKu6pAQ
#DevOps #CloudArchitecture #SRE #PlatformEngineering
Following on from my previous post about configuring CI/CD workflows with imperative code, I've got some examples for you!
As a sneak preview of v0.3 of the Ocuroot SDK, let's put the release/deployment model into practice by creating a canary deployment workflow.
YAML has become something of a de-facto language for CI/CD and perhaps even DevOps in general. But for Ocuroot I'd like to avoid it as much as possible. This week's post discusses why and how.
Kicking off bi-weekly posts from @ocuroot.com!
Today, I'll be talking about why local testing would be a big win for CI/CD pipelines, what makes it difficult, how you can move in that direction today and what I'm building to make it even easier!
New look Ocuroot site!
I've been working on a revamp of the @ocuroot.com site to highlight some of the areas where the tool can help. It's been a lot of fun brainstorming the different ways Ocuroot could be used in different situations - and making images for them 😅
www.ocuroot.com
#buildinpublic
The real challenge was coming up with instructions and making sure they worked 😅
A screenshot of Windows installation instructions for Ocuroot
I onboarded my first Windows user today! Although I didn't realize he used Windows ahead of time and hadn't included a Windows binary 😱
Cue some build updates and a hasty search for a Windows VM for testing, and Windows support is now available!
#buildinpublic
Early users have been asking for the ability to visualize their deployment pipelines in Ocuroot.
This required a few tweaks to the SDK and a slight rethink of how deployments relate to the pipeline. This post outlines the changes I made and why.
#buildinpublic
I've been cooking up something fun over the holidays: an online playground for Ocuroot config!
I wish I'd done this months ago. It's prompted a ton of refactors that make my life easier, and shook out a confusing bug around sync order.
Plus Monaco is surprisingly easy to work with!
#buildinpublic
CI/CD pipelines come in all shapes and sizes, but you can describe almost every step using four key concepts: builds, deployments, environments and tests.
www.ocuroot.com/blog/06-four...
Ocuroot builds on these concepts so you can build the CI/CD workflows that suit your business more rapidly.
Screenshot of a UI showing 0 environments, repos and packages, with a warning bar suggesting that the user try the quickstart guide.
Seeing how new users interact with your product is an amazing experience.
You see things that you'd never considered because you know how everything works.
I saw a new user sign into an empty org and they weren't sure where to go. So I put in a with an overview and call to action for new accounts.
Photo by Rakicevic Nenad: www.pexels.com/photo/man-wi...
Fireworks behind a silhouetted figure holding a sparkler.
Sharing a mini milestone, yesterday I onboarded the first Ocuroot user who wasn't me!
We worked through the quickstart on a call and everything worked pretty much as expected. But I also got some useful feedback on UX and documentation improvements to prepare for the next set of users.
Screenshot of the Ocuroot UI showing a secrets managment page with secrets listed for Infisical credentials.
Bonus update, Ocuroot now has built-in secret support!
Secrets are set in the UI, encrypted at rest and can be read in builds/deploys in any environment.
This is intended just to get you started, and we'd recommend combining with a more robust tool. As in the screenshot, I'm using Infisical.
Ocuroot now has a blog! I've added some previous updates and an all-new post about why I'm building a new CI/CD tool:
www.ocuroot.com/blog/04-why-...
The documentation site preview for Ocuroot is now live!
All feedback welcome, I want to make sure the onboarding experience is as smooth as possible, and the docs are a huge part of that.
Take a look at docs.ocuroot.com
Short and sweet update to start the week: redeploying successful builds in any environment!
