Return-Path: X-Original-To: apmail-falcon-dev-archive@minotaur.apache.org Delivered-To: apmail-falcon-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E0C6718411 for ; Fri, 19 Feb 2016 16:32:13 +0000 (UTC) Received: (qmail 82760 invoked by uid 500); 19 Feb 2016 16:32:08 -0000 Delivered-To: apmail-falcon-dev-archive@falcon.apache.org Received: (qmail 82713 invoked by uid 500); 19 Feb 2016 16:32:08 -0000 Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@falcon.apache.org Delivered-To: mailing list dev@falcon.apache.org Received: (qmail 82701 invoked by uid 99); 19 Feb 2016 16:32:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Feb 2016 16:32:08 +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 1B3191A0A27 for ; Fri, 19 Feb 2016 16:32:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.95 X-Spam-Level: X-Spam-Status: No, score=0.95 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.329, SPF_PASS=-0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id Ut_w0S0dumME for ; Fri, 19 Feb 2016 16:32:05 +0000 (UTC) Received: from BLU004-OMC4S3.hotmail.com (blu004-omc4s3.hotmail.com [65.55.111.142]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 908B45FB68 for ; Fri, 19 Feb 2016 16:32:04 +0000 (UTC) Received: from BLU179-W14 ([65.55.111.135]) by BLU004-OMC4S3.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Fri, 19 Feb 2016 08:32:03 -0800 X-TMN: [KXe+POgcB2QlLpn1zX4bzXdoXvwCRaHs] X-Originating-Email: [sriksun@hotmail.com] Message-ID: Content-Type: multipart/alternative; boundary="_61e60d6b-38ba-420d-a02a-810d214e16b4_" From: Srikanth Sundarrajan To: "dev@falcon.apache.org" Subject: RE: github pull request model - Pre commit build timeout Date: Fri, 19 Feb 2016 22:02:02 +0530 Importance: Normal In-Reply-To: References: ,,,,, MIME-Version: 1.0 X-OriginalArrivalTime: 19 Feb 2016 16:32:03.0546 (UTC) FILETIME=[108A53A0:01D16B33] --_61e60d6b-38ba-420d-a02a-810d214e16b4_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I believe build setup is configured on apache infra resources and are secur= ed with apache login. This is by design and something individual projects c= an't change. For more details on build infrastructure=2C please see http://= wiki.apache.org/general/Jenkins?action=3Dshow&redirect=3DHudson Regards Srikanth Sundarrajan > Subject: Re: github pull request model - Pre commit build timeout > From: sramesh@hortonworks.com > To: dev@falcon.apache.org > Date: Thu=2C 18 Feb 2016 19:41:57 +0000 >=20 > +1 >=20 > If all the users/contributors cannot be provided Jenkins access then its > committers responsibility to monitor failed pull request builds and rerun > it for intermittent build failures. Is this the workflow we want to follo= w? >=20 > Thanks! >=20 > On 2/18/16=2C 11:32 AM=2C "Balu Vellanki Bala" > wrote: >=20 > >Hi Srikanth=2C > > > >I was unable to login using github account "bvellanki". Ying Zheng > >(yzheng-hortonworks) could not do so either. I could login and trigger = a > >re-run using committer account (balu@). Is this by design? > > > >If yes=2C I believe we should allow all contributors to be able to re-ru= n > >failed builds.=20 > > > >Thanks > >Balu=20 > > > >On 2/17/16=2C 6:53 PM=2C "Srikanth Sundarrajan" wr= ote: > > > >>Hi Sowmya=2C > >> You should have permissions to re-run I believe. Were you logged int= o > >>the build system using your apache-id. I often missed this step and > >>wondered why dont see an option to run a job. If you had indeed logged = in > >>and yet dont have permissions to run the job=2C do report back. > >> > >>Regards > >>Srikanth Sundarrajan > >> > >>> Subject: Re: github pull request model - Pre commit build timeout > >>> From: sramesh@hortonworks.com > >>> To: dev@falcon.apache.org > >>> Date: Thu=2C 18 Feb 2016 01:25:40 +0000 > >>>=20 > >>> Raghav - I didn=B9t have the permissions to rebuild the failed job. > >>> I agree rebuilding will suffice but will all the users/contributors > >>>have > >>> Jenkins access? > >>>=20 > >>> Thanks!=20 > >>>=20 > >>> On 2/17/16=2C 5:06 PM=2C "Raghav Kumar Gautam" > >>>wrote: > >>>=20 > >>> >Hi Sowmya=2C > >>> > > >>> >Just rerunning the job suffices. I have started it for your pull > >>>request > >>> >and the new job is making progress. > >>> > > >>> >Thanks=2C > >>> >Raghav. > >>> > > >>> > > >>> >Raghav Kumar Gautam > >>> >http://www.linkedin.com/in/raghavg > >>> > > >>> >On Wed=2C Feb 17=2C 2016 at 1:07 PM=2C Sowmya Ramesh > >>> > >>> >wrote: > >>> > > >>> >> Hi All=2C > >>> >> > >>> >> For one of my pull request=2C build failed and in the console buil= d > >>>log I > >>> >> see below issue where build timed out and was aborted. > >>> >> > >>> >> ""Build timed out (after 90 minutes). Marking the build as failed. > >>> >> Build was aborted" > >>> >> > >>> >> I don't think user/contributor will have the permissions to rebuil= d. > >>> >> Any ideas on how to handle these kind of build failures? > >>> >> > >>> >> Thanks! > >>> >> > >>> >> > >>> >> > >>>=20 > >> =20 > > >=20 = --_61e60d6b-38ba-420d-a02a-810d214e16b4_--