* On 2024-07-14 at 18:31 BST, Greg Troxel wrote:
We are increasingly using tools that parse build output, and I'm finding some things harder than I think they need to be.
The problem is that the tools parse the email reports, and I don't think that's a good idea for many reasons.
Each bulk build generates a meta/status file which contains some proper fields that can be parsed by tools. I've just committed an change to log more fields to this file as well as making them more consistent.
As there's no good way to identify the branch simply based on the checkout, I suggest we add an optional $branch variable to pbulk.conf, write BRANCH=$branch to meta/status, and if branch is unset we default to "trunk".
If there are any other variable suggestions I would strongly encourage them to be proposed now given the very long delay, at least for NetBSD builds, between making the change and it being active in reports.
-- Jonathan Perkin - mnx.io - pkgsrc.smartos.org Open Source Complete Cloud www.tritondatacenter.com