Return-Path: X-Original-To: apmail-builds-archive@minotaur.apache.org Delivered-To: apmail-builds-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 82C25184F5 for ; Wed, 22 Jul 2015 16:46:34 +0000 (UTC) Received: (qmail 88070 invoked by uid 500); 22 Jul 2015 16:46:25 -0000 Delivered-To: apmail-builds-archive@apache.org Received: (qmail 88000 invoked by uid 500); 22 Jul 2015 16:46:25 -0000 Mailing-List: contact builds-help@apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: builds@apache.org Delivered-To: mailing list builds@apache.org Received: (qmail 87973 invoked by uid 99); 22 Jul 2015 16:46:24 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Jul 2015 16:46:24 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 454361A7665 for ; Wed, 22 Jul 2015 16:46:24 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.9 X-Spam-Level: ** X-Spam-Status: No, score=2.9 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 1tvJN9uh1SQo for ; Wed, 22 Jul 2015 16:46:15 +0000 (UTC) Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com [209.85.212.179]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id DC9F943DF3 for ; Wed, 22 Jul 2015 16:46:14 +0000 (UTC) Received: by wibxm9 with SMTP id xm9so171825401wib.0 for ; Wed, 22 Jul 2015 09:46:14 -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 :content-type; bh=9eJDAWjFOXUz7lcQ24H/RDc0tYg7inJYuibLOAyd2yU=; b=UetA8T5DxU8JJDfEGrhEgHeslHUb/PKdubW7wjxp2n4cq5NZufCRXm/fGKfW+WJgYA lJHxVQavikWNnOS8dTQ+lQpO5HBK8Xw5ij/W8Cj+EV5nDdUkkVdTO7NmkvlFPzM9Ej1j UO4YiCwX6WACdzE9bK+XRJBeNVxg2uTrkwuUWMqv1Kwr/TmpPXcx5NdLDyCwf2q0QEjC K1dDg1MoqSKX+O3TWFsxW9++JZWJI0/luGGw3lMoxL/AVlMKnCfWRExL58B0Ev/ctQs6 sBzR7YLa4U3HbBHwlydja3V8qbfjK8OLo8nTepY98BApimTGprbws69IYLkArt+meL4B Wa3A== MIME-Version: 1.0 X-Received: by 10.194.89.72 with SMTP id bm8mr6942433wjb.116.1437583574116; Wed, 22 Jul 2015 09:46:14 -0700 (PDT) Received: by 10.194.135.230 with HTTP; Wed, 22 Jul 2015 09:46:14 -0700 (PDT) In-Reply-To: References: Date: Wed, 22 Jul 2015 18:46:14 +0200 Message-ID: Subject: Re: Triggering CI rebuilds for GitHub pull requests From: Andrew Bayer To: "builds@apache.org" Content-Type: multipart/alternative; boundary=089e010d868c4530ab051b79824b --089e010d868c4530ab051b79824b Content-Type: text/plain; charset=UTF-8 I think it only triggers on changes to the pull request - i.e., a new commit. I'll talk to the cloudbees people (we are using the Jenkins Enterprise GH PR plugin, not the open source one) and see if they have any ideas. On Wednesday, July 22, 2015, Ismael Juma wrote: > Hi, > > Any feedback on the below? "retest this please" did not seem to work when a > committer tried it. > > On Mon, Jul 20, 2015 at 4:15 PM, Ismael Juma > wrote: > > > Hi, > > > > At Kafka, we intend to change our contribution flow to be based on GitHub > > pull requests. An important part of this flow is running CI builds on > pull > > requests. The basics are now working[1] thanks to Andrew Bayer's help. I > > have a few questions that I could not find an answer for (if this is > > information is already available somewhere, a reference is appreciated) > and > > I was hoping that someone here could help: > > > > 1. Is it possible to trigger a rebuild with "retest this please"? > > 2. Who is allowed to trigger a rebuild? Is it any committer or only > > those with access to Jenkins? > > 3. Can we use "add to whitelist" to add another user to the authorised > > list? > > 4. Out of curiosity, are we using > > > https://wiki.jenkins-ci.org/display/JENKINS/GitHub+pull+request+builder+plugin > > or something custom? > > > > Normally, I would just figure it out by trying these things, but I am not > > a committer and I don't have access to Jenkins, which makes things a bit > > harder! > > > > Thanks, > > Ismael > > > > [1] https://builds.apache.org/job/kafka-trunk-git-pr/ > > > --089e010d868c4530ab051b79824b--