I know my voice does not count much, but I talked about jenkins too a while ago and even made a try myself: https://github.com/chickenkiller/jenkins-efl I worked quite nicely. If you want to take some pieces of it...
Lionel On Wed, Jan 30, 2013 at 11:53 AM, Stefan Schmidt <s.schm...@samsung.com> wrote: > Hello. > > On 30/01/13 06:46, Carsten Haitzler (The Rasterman) wrote: >> On Wed, 30 Jan 2013 00:27:47 +0100 Bertrand Jacquin <be...@meleeweb.net> >> said: >> >> this is good - though we'll need a collection of vm's for buildbot, not >> just >> one as we need to test builds on many os's (and architectures eg 32 vs >> 64bit, >> arm etc.), so just assume we'll get more vm's running a whole myriad of >> os's. > > Maybe it is a good time to chime in here as Daniel and myself have been > doing all the buildbot related work over the last months. > > We both think that buildbot is not the right tool for the job. Before we > started CI here I suggested to use jenkins but then buildbot was setup > and I wanted at least to try it out again and see if we can make it work > for E (I used buildbot at another job before and happily switched to > jenkins). After this months I have come to the conclusion that buildbot > and I are not made for each other. > > The biggest problem we see is that you have to code everything in > python. Even the configuration is python. We had to fetch some svn > buildbot python class from the internet just to make sure we do > incremental checkouts and don't overload our svn server. The lack of a > web UI for configuration is also quite annoying and hinders people to help. > > We have setup jenkins here locally and are doing some builds with this > setup gcc, clang, warnings catcher, cpplint, sloccount, etc. Covering > all functionality we have currently with buildbot builds is easy enough > to do. > > I also want to get rid of the generated Makefiles as they do not mimic > how developer and packagers use our code. Using the same command we use > on the commandline is way easier to maintain. With the merged tree our > dependency handling is way easier so I don't think we need a script to > do all the magic here and makes it more complicated for others to chime > in and help. Seems nobody but k-s and myself ever touched the generated > Makefiles... > > This brings up the question if anyone has strong opinions on that (I bet > k-s has) and is also willing to maintain the buildbot setup. I would be > happy to hand it over if someone wants to keep buildbot and want to > maintain it. On the other hand I, and Daniel as well, would be happy to > setup jenkins and maintain it. > > The installed compilers and the need for different vm's is the same for > both as they can handle slaves fine. > > Ready for flames now. > > regards > Stefan Schmidt > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_jan > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
