Date: Fri, 3 Aug 2012 22:33:59 +0300 From: Marin Atanasov Nikolov <dnaeon@gmail.com> To: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= <decke@freebsd.org> Cc: ml-freebsd-stable <freebsd-stable@freebsd.org>, freebsd-ports@freebsd.org Subject: Re: Jenkins+FreeBSD handbooks Message-ID: <CAJ-UWtT52019uivXw1zEaX%2BeJ3GKv4n3fRHkvWfS4v6eTrrraQ@mail.gmail.com> In-Reply-To: <CAE-m3X39heTNZJWms%2B0S7HEL=vZFHkvosDO_ouN=VnCyDVFbBQ@mail.gmail.com> References: <CAJ-UWtRRBr%2B1fBJTFjdo6KRJzEivD0WXi%2BG2bASRWFyX9c4ziQ@mail.gmail.com> <CAE-m3X39heTNZJWms%2B0S7HEL=vZFHkvosDO_ouN=VnCyDVFbBQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Aug 3, 2012 at 10:14 PM, Bernhard Fr=F6hlich <decke@freebsd.org> wr= ote: > Hello Bernhard, > Thanks a lot for that tutorials. They look very interesting and I was > always curious how much work it would have been to implement something > like redports.org on top of Jenkins. But obviously my decision was > correct that jenkins would not fit in such a situation. > Could you clarify a bit more why you think Jenkins does not fit well there? I don't know how redports.org is designed and how it scales, but with Jenkins it's quite easy to create a package build farm for distributed building. Jenkins comes with lots of ready-to-use plugins as well, which makes it easier to integrate a particular thing easier as well and not re-invent the wheel. > A more suitable place for jenkins would be automatic building our doc > tree on every commit. But I don't know if that doesn't already exist. Yep, that's one of the things we could use Jenkins for, but I would say we could use it for lots of other stuff as well :) Best regards, Marin > > -- > Bernhard Froehlich > http://www.bluelife.at/ --=20 Marin Atanasov Nikolov dnaeon AT gmail DOT com http://www.unix-heaven.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-UWtT52019uivXw1zEaX%2BeJ3GKv4n3fRHkvWfS4v6eTrrraQ>