On Mon, Oct 15, 2012 at 12:11 PM, Daniel Willmann <[email protected]> wrote: > Hello, > > On 10/15/2012 01:05 PM, Gustavo Sverzut Barbieri wrote: >> On Mon, Oct 15, 2012 at 5:45 AM, Stefan Schmidt <[email protected]> >> wrote: >>> Hello. >>> >>> On 14/10/12 17:25, Vincent Torri wrote: >>>> >>>> i would like to know what the status of buildbot is. It seems just not >>>> functional while it was working some months ago >>> >>> The machine it is running on got a new installation and the buildbot >>> backup got restored as far as showing what was there before. Not active >>> at the moment. > >> As usual I can help to get it back, or explain any required details. >> >> What I can't is maintain it running... as it seems nobody cares about >> it, it was dead for a while without people noticing... people were not >> checking it for bugs or warnings, etc. > > I would like to lend a hand in setting things up again and keeping them > running once I get access. I used a Jenkins setup in my university's > diploma thesis so I know how useful a CI tool can be. I don't know > buildbot yet, but how hard can it be? :-)
it's super simple now. The hard bit was to get the whole thing to build, as it's composed of lots of different projects and dependencies. Then I've setup a "makefile generator" that one specify the package, dependencies and options for every platform. It will create what we have now "Makefile.linux" and "Makefile.win" in trunk. Buildbot will just call this makefile with proper options, dependencies are handled automatically. the think is that when it breaks, it needs someone to step up and solve the problems. It happened in the past more than it does now, like failure to svn checkout, or when "po" files were causing merge issues (but this shouldn't happen anymore). The last thing that was breaking that I recall is the incremental build (fast build) that would need a cleanup to do a full build when things went really bad (there was a build type that would actually clean the fast build). Last but not least I was doing the steps to automatically build docs and gcov reports, uploading them to some server. >> IMO the only way to make it work is if bot mail e-devel/e-svn and send >> issues to #edevelop as they happen. > > True, it's no use if nobody actually knows/cares about it. that's the hardest bit :-/ -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -------------------------------------- MSN: [email protected] Skype: gsbarbieri Mobile: +55 (19) 9225-2202 ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
