Date: Mon, 06 Aug 2012 14:43:11 +0200 From: =?ISO-8859-1?Q?Tilman_Keskin=F6z?= <arved@FreeBSD.org> To: freebsd-ports@freebsd.org Cc: dnaeon@gmail.com Subject: Re: Jenkins+FreeBSD handbooks Message-ID: <501FBBDF.6040606@FreeBSD.org> In-Reply-To: <CAJ-UWtQjPU0ZSC6kHA6rtsT7jqhVyFzaqowqywAjzzXRGy=rJg@mail.gmail.com> References: <CAJ-UWtRRBr%2B1fBJTFjdo6KRJzEivD0WXi%2BG2bASRWFyX9c4ziQ@mail.gmail.com> <CAE-m3X39heTNZJWms%2B0S7HEL=vZFHkvosDO_ouN=VnCyDVFbBQ@mail.gmail.com> <CAJ-UWtT52019uivXw1zEaX%2BeJ3GKv4n3fRHkvWfS4v6eTrrraQ@mail.gmail.com> <CAE-m3X0wLb6nc10aYsiTgO4SyO9C8EivuBQh=DHk-Xgrp_cE3A@mail.gmail.com> <CAJ-UWtQjPU0ZSC6kHA6rtsT7jqhVyFzaqowqywAjzzXRGy=rJg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* Marin Atanasov Nikolov [Mon, 6 Aug 2012 13:40:52 +0300]: >> Redports is a public compile testing environment for FreeBSD ports. So like >> Ports Tinderbox but with a nice multiuser GUI, cluster functionality for >> scaling and an own Subversion tree for the users to commit their ports to. >> >> Before I decided to write the code myself I had a closer look at Bitten and >> Jenkins. Both could be made into what redports is now but they all have >> their weak spots. Jenkins GUI looks very cluttered and is quite hard to >> understand if you just want to manually schedule a few new jobs for your >> ports as Joe Average. It's also quite hard to understand and complex as a >> developer and administrator so I was concerned that fixing it if it breaks is >> non trivial. Not to talk about all the special customizations that we need >> which would require me to write extensions in Java and understand how >> all that jenkins internals work. >> > > Like any other system Jenkins has it's own learning curve as well, but > once you get to know it, > you see how intuitive it is to use the system. > > I agree with you on the Java stuff. That's the one thing I don't like > about Jenkins being Java.. > > But I can tell from my experience with it so far, that I haven't had > any issues with it, e.g. breaking and spending lots of time figuring > out how to fix it. Maybe one day I will, but so far I'm quite happy > with it :) >>> 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. I am surprised you haven't run into any plugin incompatibilities. We use Jenkins at work and have frequently hard to debug issues with plugins being incompatible with certain jenkins versions or with other plugins. Sometimes a broken plugin manages to take down the whole Jenkins, sometimes there are just random Java backtraces causing build failures in projects. IMHO the whole Jenkins architecture is way too fragile to be used for large projects like FreeBSD.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?501FBBDF.6040606>