From owner-freebsd-ports@FreeBSD.ORG Mon Aug 6 18:02:27 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9879C106564A; Mon, 6 Aug 2012 18:02:27 +0000 (UTC) (envelope-from dnaeon@gmail.com) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id F2E318FC0A; Mon, 6 Aug 2012 18:02:26 +0000 (UTC) Received: by eaak11 with SMTP id k11so918828eaa.13 for ; Mon, 06 Aug 2012 11:02:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=pn6/8BGqFnI32WVFQsXJwzfgVYYTdQiQOLq0YWan7mw=; b=SW7PxM7tWbMJLwFirE1hTkXQ5xopEVbNBM8ctXWcfENWjVWIt+ZYLlrqn5pkKuCP34 0e/LGW8Yxry7GA3z0sDtsBfUngAxSltdlpib7S3gOI9SGUO5psYCZRRLdZ0AjG3BEb3w KBvmytpy8Go7mXLYYjSSqJvP2yt9JVGZDd5STBTsbdyGjWnmexcaL6dFfZTlmL5VpLQv lzIGquoRKAch0KZNm5h7OdxcCi7NTJE+ovDa03t+ag6nxQok8buFtG29tM2nF4LgS+cs mODZ1aN7yUPutLXAG1YcQZxxD4ObKjgeP0E292qCetnMIm8tkKJHhnltmYtkWgVxAsVx xLtQ== MIME-Version: 1.0 Received: by 10.14.182.134 with SMTP id o6mr14019061eem.26.1344276145571; Mon, 06 Aug 2012 11:02:25 -0700 (PDT) Received: by 10.14.216.70 with HTTP; Mon, 6 Aug 2012 11:02:25 -0700 (PDT) In-Reply-To: <501FBBDF.6040606@FreeBSD.org> References: <501FBBDF.6040606@FreeBSD.org> Date: Mon, 6 Aug 2012 21:02:25 +0300 Message-ID: From: Marin Atanasov Nikolov To: =?ISO-8859-1?Q?Tilman_Keskin=F6z?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-ports@freebsd.org Subject: Re: Jenkins+FreeBSD handbooks X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Aug 2012 18:02:27 -0000 On Mon, Aug 6, 2012 at 3:43 PM, Tilman Keskin=F6z wrote= : > * 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 fo= r >>> 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 you= r >>> 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 bre= aks is >>> non trivial. Not to talk about all the special customizations that we n= eed >>> 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. > Hi Tilman, > I am surprised you haven't run into any plugin incompatibilities. > So far not. I always try to keep my Jenkins and plugins to the latest versions and so far didn't have any issues. If a newer version of a plugin appears to be broken then just downgrading it solves the issue, but such issues are noticed quickly. > 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. > We use Jenkins at work quite extensively as well for quite some time alread= y. The only major failure with Jenkins I had by this moment is when a Jenkins instance went out of memory, but the problem itself was that Jenkins was running on an old machine with very low resources. Migrating it to a more recent system with enough memory solved the issue. We run Jenkins under a Debian GNU/Linux and FreeBSD systems. > IMHO the whole Jenkins architecture is way too fragile to be used for > large projects like FreeBSD. I have to say that we use Jenkins in some very critical parts of our infrastructure and it's been doing well so far. Jenkins like almost every system has it's weak and strong spots and maybe you had a different experience with it than I did. Thank you for the feedback Tilman :) Best regards, Marin > > --=20 Marin Atanasov Nikolov dnaeon AT gmail DOT com daemon AT unix-heaven DOT org http://www.unix-heaven.org/