Is it that important to you?
I'm not sure about the actual importance, because as you might say once CB is configured, it can probably run unattended for awhile. But the main reason for the topic is also mostly based on the lack of 'ssh savvy-ness' on my part (and maybe that I'm a spoiled Mac-user who mostly likes to see a GUI).
But otoh, since CB has become such an important part of DA, I wonder if shouldn't it be 'visible' under DA somewhere? At least maybe it could show a notification or ticket that there are updates available for instance.
Then, under the Updates-page, or even Service Monitor, it would be nice if there was another column with a possible 'update'-button behind the service. But I can imagine having to enter your root-pw to update a service through the DA-website could have security-issues.
Do most folks who are using CB, just let CB upgrade their server to the newest versions automaticly? Or do you usually stay 'one subversion' behind for a while to let others find possible errors?
Given my careful, 'first encounter' with CustomBuild, and still having the server crash on me a week later, I'm still very hesitant to just dive in again and activate CB and let it do it's thing, without knowing if something gets broken again in the process, only for me to find out sometime later (when I can't fall back onto an older snapshot anymore).
And, (showing my novice-carefulness again) I've read that you can't always 'just' update one thing without updating something else first or at the same time.
But I really need to start updating my vps as it's getting pretty outdated by now.
Even if CustomBuild was available under DA somehow, I do understand that with properly maintaining a server one ofcourse has to upgrade other software through SSH that CB doesn't touch.
Wow, became a long story again.