From owner-freebsd-hackers@freebsd.org Thu Feb 23 22:57:58 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 24130CEB69D for ; Thu, 23 Feb 2017 22:57:58 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-qk0-x22f.google.com (mail-qk0-x22f.google.com [IPv6:2607:f8b0:400d:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D4C04C38; Thu, 23 Feb 2017 22:57:57 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by mail-qk0-x22f.google.com with SMTP id x71so5454818qkb.3; Thu, 23 Feb 2017 14:57:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=MIf/Z6MXK9f8HSXQVyXDZKWkP015lTRMfMie9D/RYH8=; b=d/PvnBTDrKIS5KMdsxvkRjPmbEtkQuawETMyS1xMwg7Tv+8qvR73f4lfrC6K5jutvF f58L4F+kzp4WAC0zT0ITV1pf2RV13pqced4kli5itYYQcdzpZQGORTNpG3U3eBf7idT/ MLN5/iSGplTt1KmUxRKIm4SXKfnw54LaM2XerfVjmva5SQM7YVe4Ga0QKfcdkhIDu0a6 bYPVs14eQVlDAnScSpkSX8RV9WK5zdjsM45iOCGpqN4cAwf4IolrQ7B5dTW2gVfYYDyq OSSBHdosbGPegBvNvk+c9/+p+ltUcqtxrTUWscu3VR7GCfhcDtJe+hRAnIy5EgkKxaS0 AIwA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=MIf/Z6MXK9f8HSXQVyXDZKWkP015lTRMfMie9D/RYH8=; b=qbRcokKvfF/IhbQ6lYYqsvL4/xF5CFrb4FDn1RxL2ga1kX7VIplq+fOqcFnENUoWPk ICy9Jxt3kOWqfzwfBZl233EbOk9M2iUp6CTXjgqoQEOaJOiiVpX1Ge1899p6RL87o0gL lZAG2rppP5vzcHs3OG2LfjxZktMpk75gp6jKsXzfkjVioc6l/mN+X7ja2VfxveVyJks1 CvV4+NbJOtyQxZaA3umnN9NaQJd0Bxs6r7zHi4KUMyr8I2mSjg/RGWZiHjRbXTqiHQAA FMYHkiOzAGLdYtyYy9CjBHLSWH0e1qHf0ADL2+FbwGLauGBKeGhoLFAybNKl+AVKNA7m b09A== X-Gm-Message-State: AMke39nvRq646XIg3FbDP956ehf96ZW8aYlkFKgsyQ357HCSGbt+rXCz9ctmgH+u0o1Pa4pihAre4C9Tbna0Gg== X-Received: by 10.55.123.5 with SMTP id w5mr44310698qkc.76.1487890676759; Thu, 23 Feb 2017 14:57:56 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.84.230 with HTTP; Thu, 23 Feb 2017 14:57:56 -0800 (PST) In-Reply-To: References: <91A98293-35F0-4C27-993D-01F40B28B92E@computing.com> From: Ngie Cooper Date: Thu, 23 Feb 2017 14:57:56 -0800 Message-ID: Subject: Re: TravisCI vs BuildBot vs Bamboo vs Jenkins To: Alan Somers Cc: Jim Rowan , "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Feb 2017 22:57:58 -0000 On Wed, Feb 22, 2017 at 10:12 AM, Alan Somers wrote: > I think I need to emphasize more that the key feature for me is Github > integration. I want to use one of these tools with a project that is > hosted in Github. It's not my project, so I can't move it even if I > wanted to. WJW's example gets half of the integration I would like; > he shows how Jenkins can pull information out of Github. But it > doesn't show how to push information back into Github. Does anybody > have any examples of using Jenkins, Bamboo, Buildbot etc to push build > pass/fail notifications back into Github? Having seen other integrations done, I think Buildbot/TravisCI are the most functional builder types out of the box with GitHub, but as you noted before, getting them to work with FreeBSD requires jumping through hoops. Here are some notes I found quickly with GitHub/Jenkins integration: https://jenkins.io/solutions/github/ . Personally, I don't care for the flat text file format with Jenkins for the following reasons: 1. It doesn't scale longterm, in particular it requires data retention policies/pruning to ensure that you don't slow down your Jenkins master too much with data. 2. IIRC writing the results/config isn't atomic. 3. Backups are harder to deal with. 4. Job files/templates a more painful to deal with, depending on how you design the Jenkins jobs. IMHO, it was a mistake I think for the Jenkins folks to not implement more intelligent database backends and storage methods for the logs. Also, Jenkins loves RAM (#thanksJava). Otherwise, I think Jenkins is fine for most tasks. My 2 cents, -Ngie