tbcleanup feature requests :)

[Joe Marcus Clarke]

On Wed, 2008-07-09 at 10:58 +0300, Ion-Mihai Tetcu wrote:

> - have build_ports.Last_Fail_Reason exported to postPortBuild Hook - I
> need it for setting a relevant subject to the BotmMail; right now $STATUS
> only gives me SUCCESS, FAIL and DUDS.

I just did this in HEAD.

> 
> - have a little better failure patterns, especially for ports that fail
> because they need kernel sources. I'm willing to go in in all ports and
> change the failure message to be the same (like 'This port requires the
> kernel source be available') and to fail in the same make target if
> this would help (maybe this could even be implemented via a KNOB in
> b.p.m).

I need to re-sync the failure patterns with pointyhat.  But if you'd
like to add a definitive message to the ports system, that would be
great.

> 
> 
> I'm a little bit at lost how to implement differentiating between
> "regular" and commit triggered builds/errors. The thing is I have to
> send a BotMail each time a port is touched by a commit and it fails,
> but not for the ports that fail because of my regular builds or because
> they are dependencies of an other port (else some people would receive
> a few dozens emails per day about the same port). Right now I queue
> regular port builds with priority 9 and commit-triggered builds with
> priority 5. Maybe it would be possible to export this to the
> postPortBuild hook? Any suggestion is welcomed.

I suppose it would be possible to export the CLI arguments passed to
tinderbuild on the command line to related Hooks.  Would this be
acceptable?

Joe

-- 
PGP Key : http://www.marcuscom.com/pgp.asc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
URL: <http://marcuscom.com/pipermail/tinderbox-list/attachments/20080709/8310eb47/attachment.bin>