From users-return-49424-archive-asf-public=cust-asf.ponee.io@activemq.apache.org Fri Feb 16 18:18:18 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 004EE180647 for ; Fri, 16 Feb 2018 18:18:17 +0100 (CET) Received: (qmail 75376 invoked by uid 500); 16 Feb 2018 17:18:16 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 75346 invoked by uid 99); 16 Feb 2018 17:18:15 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Feb 2018 17:18:15 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 84630180495 for ; Fri, 16 Feb 2018 17:18:15 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.121 X-Spam-Level: X-Spam-Status: No, score=-0.121 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 3s6ExgxbXKbB for ; Fri, 16 Feb 2018 17:18:14 +0000 (UTC) Received: from mail-qt0-f177.google.com (mail-qt0-f177.google.com [209.85.216.177]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 8EF915F523 for ; Fri, 16 Feb 2018 17:18:13 +0000 (UTC) Received: by mail-qt0-f177.google.com with SMTP id f18so4613456qth.11 for ; Fri, 16 Feb 2018 09:18:13 -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 :content-transfer-encoding; bh=DKOrLVaC6p5QC+8yRhQ1avhN+pHPmlvnfUznhaW0VCw=; b=G2itg5G1F/hhHYvAkQt3ERj3z5tFxIyAIjtb9NtRmVTgDB/9N6b2xFvE0z0x6pHxNd 2nclzBJkyFHWKe2lwy/yjtwOT15jIQGnz7ilH/DMxLhstNRBXPGZCkzOrCZ4Z0fI8Ry8 2GlXu6jUh7NzdgUmJlhqdvfwA7UneJ1yLwuQTLOpi7E85lwi7wXMLPjPdKLrXx9+qQOE Lodo5p4NVjYrpoyxNr//pBDq9+T7NISOOBgChnvYiHFY5MV4wdjcICb/qQAoQOYWIAKv LnmuvUCs8W+9kjPeSp/JKKuAmQNoem0J7RQTm1w4nKO+9Qvz894QKBg9sBrVRcJFletW WaNw== 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:content-transfer-encoding; bh=DKOrLVaC6p5QC+8yRhQ1avhN+pHPmlvnfUznhaW0VCw=; b=kel3jzrHAHHcZ9kwLIw1EgYcVVCwjVg2CRZrUG60Xf+VvZWXr3zmVkgK1snyw+fszE ITpU+59jIKxiPAv6cRxQsd162ioKC3aBdF/4k1UMiR4nBilWwqCVm+GJGB4u8WFvw2M+ o52cCkmITZCk1WktfqSB0pGyOVaVVqKBzdS+crTeRbPGmybBT9xv0Ge+TeA30J2h5Qdw uuRGAVB3Gjp7/VxrLpcEa9lhOnH/i5SyN8tknz8nb4oVJrq8KVuZUm0zTkn2NOiHihsc CMReQ3M59QCKpKfG1Jv/wUuzYsfC3SKYoQ6EzKdlLiz5DwK1JMBqfLsglsud0fnjNsbB 1YOA== X-Gm-Message-State: APf1xPApWDFXK98qq3Vg+adqhf2xPO35oyqQZClmgR+Q1sXhgTrRfEVe gyYUDKZ5BXPXJbf3F8f92FCbzvpEpyE4FYZp52j6bw== X-Google-Smtp-Source: AH8x225g57Mmqr0jH0SF+gWRUnTcmnMwUIYysbT+PJ2rS3L2mf1C4McmCLThKgO1PKuoeha/f0/v4qfYmlX4rl+CfuU= X-Received: by 10.237.59.232 with SMTP id s37mr7755077qte.83.1518801486187; Fri, 16 Feb 2018 09:18:06 -0800 (PST) MIME-Version: 1.0 Received: by 10.200.47.251 with HTTP; Fri, 16 Feb 2018 09:18:05 -0800 (PST) In-Reply-To: References: <62964162-A731-4387-AE2D-9C3C0681A05D@me.com> From: Robbie Gemmell Date: Fri, 16 Feb 2018 17:18:05 +0000 Message-ID: Subject: Re: [DISCUSS] Using Travis CI for Artemis PR builds To: users@activemq.apache.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I believe the mirrors in the apache github org have a shared resource pool at Travis, while jobs for your personal forks run in the global resource pool. Its not unusual for the latter to be quicker off the mark, but even then its usually just seconds of difference. Occasionally there can be a backlog from having really large jobs or many jobs from other projects but typically its not been an issue for long. Using Appveyor as well can help too as they tend not to be backlogged at the same time and the additional env is useful in itself. Robbie On 16 February 2018 at 16:00, Justin Bertram wrote: > I may have spoken too soon. The UI on the Travis website apparently take= s > awhile to update or got out of sync or something. The PR build looks to = be > taking around 25 minutes consistently which I think is pretty good. > > > Justin > > On Thu, Feb 15, 2018 at 3:18 PM, Justin Bertram wro= te: > >> Initial results are not encouraging. >> >> I got Apache infrastructure to enable Travis CI builds [1] after which I >> disabled the current Jenkins-based PR build and sent a PR with the >> necessary .travis.yml file to trigger a Travis CI build [2]. I had also >> enabled Travis CI builds on my own GitHub repo so the Travis CI build wa= s >> triggered on both the Apache PR as well as my own GitHub branch. After = an >> hour I got an email saying the build for my personal GitHub branch >> succeeded, but after almost an hour and a half the build for the Apache = CI >> failed for no clear reason. Later I updated the PR branch and performed= a >> push -f to trigger more builds. The build on my personal GitHub branch >> finished without issue in about 20 minutes while the Apache PR build is >> still waiting to actually start. >> >> This looks like a fail to me. >> >> >> Justin >> >> [1] https://issues.apache.org/jira/browse/INFRA-16042 >> [2] https://github.com/apache/activemq-artemis/pull/1872 >> >> On Tue, Feb 13, 2018 at 4:56 PM, Michael Andr=C3=A9 Pearce < >> michael.andre.pearce@me.com> wrote: >> >>> This is great idea! I get so frustrated with these environment issues. >>> +100 >>> >>> Some other advantages I could see we could implement if successful. >>> >>> run a Linux build and a macOS build eg to check bits like kqueue and or >>> other os specific behaviours (aio fallback to nio) >>> >>> look to use appveyor for a windows build validation. (I=E2=80=99m think= ing this >>> validates bat files etc and ensures not Linux specific paths being used= in >>> code by mistake) >>> >>> Sent from my iPhone >>> >>> > On 14 Feb 2018, at 03:17, Justin Bertram wrote: >>> > >>> > Over the last several months I've noticed that the Jenkins-based buil= ds >>> > used to validate GitHub pull-requests for Artemis are failing at a >>> > significant rate for illegitimate reasons (e.g. environmental issues, >>> > timing out because they're too slow, etc.) or not being run at all. >>> Even >>> > as I type this there are 4 PR builds listed on >>> https://builds.apache.org/ >>> > which have been waiting for hours. >>> > >>> > I'd like to solve this problem so we have relatively quick & reliable= PR >>> > builds. I'm vaguely familiar with Travis CI, and I know other Apache >>> > projects use it for PR builds. I think it would be worth investigati= ng >>> > whether or not it would solve our problem. What do you guys think? >>> Does >>> > anybody in the community have experience with Travis CI? >>> > >>> > >>> > Justin >>> >> >>