From owner-freebsd-stable@FreeBSD.ORG Sun Aug 5 17:37:37 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3BF2F1065670 for ; Sun, 5 Aug 2012 17:37:37 +0000 (UTC) (envelope-from decke@bluelife.at) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 702658FC0A for ; Sun, 5 Aug 2012 17:37:35 +0000 (UTC) Received: by wgbds11 with SMTP id ds11so1929320wgb.31 for ; Sun, 05 Aug 2012 10:37:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bluelife.at; s=google; h=mime-version:sender:x-originating-ip:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=FtSvZcKo/sqiJ4EMS/1y1QISOthWdmFEkvPnH5CFpPQ=; b=a9P8J9OWs4yKGzpo0hSoSRcJV2BVGG5N9D96g9U5ibuI4q3JOyXQrVQ3Jnbb4EBRor Fj8hrIbY4ItmVOzBek090nMOuw6iYzlijy3ETTL0v/v8Qj2A2remaPRnq7bxArMEuw1f eCVi2hMyxgKbJzoiiI0quToOcCpP3AoitzUo8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:x-originating-ip:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding:x-gm-message-state; bh=FtSvZcKo/sqiJ4EMS/1y1QISOthWdmFEkvPnH5CFpPQ=; b=G3WrDM/DxP73XbeI1hdRe9/8OovXe/O9yyMr8OFl6wjvMpju/QDlmCg6KrZoOICMh3 6gAx3bBkcPLPE9fWFj09OPXCBfXkw/3NW/+6f+L0oipFsAsZTYZ2gVMvbpUsgrOpUE7r VqsUoPsr1h/wb3e6JTxQzvo0yB/GP6P+9yZqvLnv9phTO2M661UdZKwBhTEaIdQZ53Ne zr6nxVPOJpLCbPB6kI55nJiMEKbllpQ8VGh1SPZJwf2RWlGjMOTVlUveXeVzpO6mdLiX +8qBqM65OxwE4QjBhBqUdHJoBownZtn0ZM9ZCVq8c960vNw237XCG9MuO12a6wKyC1+j A1nA== MIME-Version: 1.0 Received: by 10.180.86.226 with SMTP id s2mr11878060wiz.9.1344188254352; Sun, 05 Aug 2012 10:37:34 -0700 (PDT) Sender: decke@bluelife.at Received: by 10.180.106.71 with HTTP; Sun, 5 Aug 2012 10:37:34 -0700 (PDT) X-Originating-IP: [93.111.10.40] In-Reply-To: References: Date: Sun, 5 Aug 2012 19:37:34 +0200 X-Google-Sender-Auth: ECIOUVZ7ww_4bz9_nCc0LuqOLZo Message-ID: From: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= To: Marin Atanasov Nikolov Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQnATm+mxKLkC9SjS6NGwOXtoOJjn0nvG99rXmC7R9g5bHTNJRJvAh9UXKh2GMou9vTrdJR5 Cc: ml-freebsd-stable , freebsd-ports@freebsd.org Subject: Re: Jenkins+FreeBSD handbooks X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Aug 2012 17:37:37 -0000 On Fri, Aug 3, 2012 at 9:33 PM, Marin Atanasov Nikolov w= rote: > On Fri, Aug 3, 2012 at 10:14 PM, Bernhard Fr=F6hlich = wrote: >> > > 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 ther= e? > > 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. 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. Bitten looked simpler and less complex but would also work for standard things but it got me on the right track to use Trac as webinterface and jus= t extend Trac with a custom plugin that includes a few simple pages to have an overview of jobs and add new ones. > 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. Yeah that is nice and there is almost everything that you can think of but none of them did what I needed. A simple web interface for average people that don't want to learn Jenkins internals and is easily customizable. Prob= ably there is a plugin for that but I didn't find it. Writing some glue code aro= und tinderbox to schedule new jobs, checkout repositories and such stuff is custom code anyway. >> 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 :) I'm sure we could. Examples? --=20 Bernhard Froehlich http://www.bluelife.at/