I have implemented a small CI for my translation efforts on the pt_BR build, using Jenkins. So far, so good. I'm messing around with some of the scripts in available in doc-base, but some of their output has to be customized in order to actually provide useful information for Jenkins.
I believe that a full Jenkins-based CI for the official documentation and it's translations would be great, however, be prepared for some very intensive processes. It's going to be hard on the servers. On Fri, Nov 11, 2011 at 10:10 PM, Hannes Magnusson < hannes.magnus...@gmail.com> wrote: > On Sat, Nov 12, 2011 at 00:56, Ferenc Kovacs <tyr...@gmail.com> wrote: > >> > Sorry, I don't get the "correct" part, but about the multiple > platforms: > >> > >> Our usage of libxml2 requires minimum 2gb ram (on success). > >> On failures.. ~8gb ram should "work". > >> > > > > thats somehow in line what I remembered, thanks for the clarification > > though! > > > >> > >> > Running concurrent builds on every slave/platform isn't > a necessity just > >> > a > >> > possibility, so if running the docbuilds on one specific platform is > >> > enough, > >> > then we can do that of course. > >> > >> > >> You are talking about the ci.qa.php.net jenkins builds here, right? > >> > > > > yeah, I tried to be clear on that "As I mentioned in the Jenkins RFC > [..] > > The setup would be easy imo (only reporting success/error making the > console > > output/logs available for debuging the issue), but the memory > requirements > > make it in-feasible for the current cluster. > > Daniel: > Something you can help us with? > > -Hannes > -- Klaus Silveira (011) 8564-2492 www.klaussilveira.com
