Boost logo

Boost :

Subject: Re: [boost] [outcome] Outcome v2 has reached stability, WG21 paper will be P0762R0
From: Niall Douglas (s_sourceforge_at_[hidden])
Date: 2017-07-31 15:31:21

>>> What's the rationale in having it run as a cronjob instead of
>>> having the CI do the boostification upon a successful build?
>> Outcome runs on both Travis and Appveyor. Each cannot know if the other
>> succeeded. So a cronjob which already exists scans nightly the CDash for
>> Outcome, and figures out the last commit with all tests passing on all
>> platforms. It then updates master branch to that commit, and publishes a
>> tarball. That same cronjob will eventually also Boostify Outcome into
>> the Boost.Outcome repo if and only if all tests pass i.e. master branch
>> got updated.
> While the two CI systems don't know of each other, you can actually get
> notified when a commit status update occurs. That would require some
> service to listen on those status updates and logic to determine if all
> builders passed (which is moot if you have testers not running on travis
> or appveyor). So I guess a cron job is the only alternative for the lack
> of proper CI support on this.

Oh for sure. But that would be more work for not actually a huge gain.
Having to wait till midnight GMT for update to
known-working-on-all-platforms is okay for 99% of end users.


ned Productions Limited Consulting

Boost list run by bdawes at, gregod at, cpdaniel at, john at