tbcleanup feature requests :)

[Ion-Mihai Tetcu]

On Wed, 09 Jul 2008 00:04:44 -0400
Joe Marcus Clarke <marcus at marcuscom.com> wrote:

> On Tue, 2008-07-08 at 14:39 +0300, Ion-Mihai Tetcu wrote:
> > Hi,
> > 
> > 
> > I had to run ./tc tbcleanup on QA Tindy, because I was getting some
> > package failures when building some ports.
> > 
> > There are 2 things I'd like it to have:
> > - clean all stale logs but _not_ failure logs which correspond to
> > current ports tree.
> 
> This is trivial.  I could just add a new option to tbcleanup.

Thanks. This way I don't have to back-up QA Tindy logs before running
tbcleanup (which, of course, I managed to forget yesterday).

> > - clean stale distfiles (a la portupgrade -D)
> 
> Yeah, I'd like this as well.  It's doable.

Nice. For full package set, full distfiles set the disk space tends to
disappear  :-)

> > - clean stale packages
> 
> This is already there.

Cool.

Other things that would make my life easy for QA Tindy:

- 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.

- 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'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.


Thanks,

-- 
IOnut - Un^d^dregistered ;) FreeBSD "user"
  "Intellectual Property" is   nowhere near as valuable   as "Intellect"
FreeBSD committer -> itetcu at FreeBSD.org, PGP Key ID 057E9F8B493A297B
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://marcuscom.com/pipermail/tinderbox-list/attachments/20080709/0f46d008/attachment.bin>