Greetings. I'm not an E developer at all but thought I'd chime in anyways. I'm probably trying to teach the choir how to sing but it appears to me that what people seem to be looking for here, essentially, is a buildbot. [ http://en.wikipedia.org/wiki/Buildbot ]
If the need is along the lines of : a. Triggering a build of specific components of the e source base in response to a commit (amongst a host of other build triggers) b. Automatic intimation to "culprit" developers, lists etc c. IRC integration for build breakages alerts (which would be cool for #e etc) d. Automated testing where appropriate ..then the buildbot sounds like a good fit. I guess this has probably been discussed in the past and shelved because of the extra work involved in setting this up (among other things) but it does sound like exactly what's needed. That said, I'm a huge fan of the easy_e17.sh project which, it appears, is the cornerstone on which the implementation being discussed currently seems to rest. Cheerio! Robin On Thu, 2007-07-19 at 10:51 +0300, Chady Kassouf wrote: > On 7/19/07, Eugen Minciu <[EMAIL PROTECTED]> wrote: > > > > > Stashing it all on a web page means that people will not bother to look > > > at it. Sending a built/not built summary to this list means that > > > people will actually read it. Stashing the full build logs on the web > > > is good, it doesn't fill the list with tons of shit no one needs to > > > look at, and the one or two people that note that their project is not > > > building know where to find the full build log to investigate further. > > > > > Maybe the the full output could be sent to the CVS mailing list. That > > sounds a bit counterintuitive but if you think about it it's purpose is to > > alert developers of changes to the codebase. This is somewhat similar. > > > Well, not really... > when information get bigger, you will tend to start skipping it. > A summary like this is great, cause all you have to do is skim the list for > ERROR and then you'll know what broke and you go check it out, but trying to > wade through all the output of a build to find an error is painful. > > ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
