Buildfarm try

[James Berry]

I'd like to point out that mpwa, as deployed at http:// 
db.macports.org has schema support for most of what is required for  
this, including problem reports and build output/logs from ports.

James

On Oct 17, 2007, at 2:17 PM, Simon Ruderich wrote:

> On Mon, Oct 15, 2007 at 05:09:52AM -0400, Juan Manuel Palacios wrote:
>>
>> 	Hello again Simon!
>>
>> 	Top posting to make one general and quick comment on this topic.  
>> I am very
>> very interested in this attempt of yours and will look into it in  
>> detail
>> later on, so do expect many questions on what you did coming my  
>> way ;-)
>>
>> 	But in the mean time, would you care to read my entry on logging  
>> support
>> for MacPorts "action targets" (read, those that drive a port  
>> toward its
>> destroot)?
>>
>> http://trac.macports.org/projects/macports/wiki/PortLoggingProposal
>>
>> 	Following the website redesign, this is my number one priority  
>> and would
>> indeed love to spark some interest from our developers base. It is  
>> one of
>> the goals of my proposal to use the results of logs to create  
>> build result
>> pages & summaries like yours on an automated fashion, as detailed  
>> in the
>> Wiki doc, so I hope you'll find it interesting.
>>
>> 	Regards,...
>>
>> -jmpp
>
> Hi Juan,
>
> I'm glad you like my small attempt ;-)
>
> I like your entry very much, it's very interesting and a good idea.  
> Your idea
> with the possibility to send the log messages to macports in case  
> of an error
> is perfect. This makes maintaining much easier as we (the  
> maintainers) have
> all necessary information and don't have to ask the user to use -d or
> something similar.
>
> It would also be easier to handle build failures as -d is no longer  
> necessary,
> which clutters the terminal.
> And of course for a buildfarm it would make parsing the output of  
> port much
> easier and less error prone.
>
> I hope after the website we can work on a design for this and add  
> it to
> macports as it's a real good and I think also important feature.
>
> Simon
> -- 
> + privacy is necessary
> + using http://gnupg.org
> + public key id: 0x6115F804EFB33229
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo/macports-dev