Re: Update strategy and timing

On Fri, May 8, 2026, at 8:48 AM, bob prohaska wrote:
> Is there a preferred strategy to timing updates
> for self-hosted FreeBSD systems? 
>
> On the stable branches it's easy; just update when
> updates are announced and build/install. Once caught
> up, things can be left alone for days at least..
>
> With -current there's essentially no pause in the
> stream of fresh commits, so git finds a new commit
> by the time buildworld finishes.
>
> Is there some marker or indicator that signals the
> -current tree is at least nominally consistent and
> buildable? I'm not asking if it'll work, just whenter
> it's worth a try.

I'm also interested in this question. One resource that hasn't been mentioned up to this point is https://ci.freebsd.org/

I don't know much about it, so I'm just inferring things based on the job names and activity log. For example, https://ci.freebsd.org/job/FreeBSD-main-amd64-test/ looks like the job that I would care about the most. Presumably you can take the commit from https://ci.freebsd.org/job/FreeBSD-main-amd64-test/lastSuccessfulBuild/parameters/ as representing the most recent commit that successfully built and passed the test suite.

One thing that's a bit confusing is that as I write this, build #28475 is listed as both the most recent successful _and_ unsuccessful build, which I don't understand.

The jobs are defined in https://github.com/freebsd/freebsd-ci/tree/main/jobs

Pat