Is anyone using CI/CD with baseline sites (and their children) on Umbraco Cloud?
I have a single site, I want to use CI/CD with, and not sure about the best way to handle it.
On one hand, I can do CI/CD deployments only to the parent site, and then use the portal to update the child sites. But I don’t really want that.
I think I can (by using transfer to any environment), set up branches for each child site in my main repo, and then merge any changes into each child-site branch and deploy using CI/CD from there.
We’ve been through a similar discussion internally, and I’d be cautious about maintaining a separate long-lived branch for every child site. It works at first, but over time merges become repetitive and it’s easy for one child to drift behind the others. If most of the codebase is shared, I’d keep a single main branch as the source of truth and only introduce child-specific configuration where absolutely necessary. The portal update step isn’t ideal, but it’s at least predictable. If you do go with CI/CD per child, I’d try to automate the promotion process as much as possible so you’re not manually merging the same changes into multiple branches every release. I’m curious whether anyone has found a cleaner pattern that scales well once you have more than just a couple of child sites, because that’s where the maintenance overhead really starts to show.