From users-return-49426-archive-asf-public=cust-asf.ponee.io@activemq.apache.org Fri Feb 16 18:29:06 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 85C1B180647 for ; Fri, 16 Feb 2018 18:29:05 +0100 (CET) Received: (qmail 20263 invoked by uid 500); 16 Feb 2018 17:29:04 -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 20252 invoked by uid 99); 16 Feb 2018 17:29:04 -0000 Received: from mail-relay.apache.org (HELO mailrelay2-lw-us.apache.org) (207.244.88.137) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Feb 2018 17:29:04 +0000 Received: from mail-ot0-f176.google.com (mail-ot0-f176.google.com [74.125.82.176]) by mailrelay2-lw-us.apache.org (ASF Mail Server at mailrelay2-lw-us.apache.org) with ESMTPSA id 17EEB28B for ; Fri, 16 Feb 2018 17:29:02 +0000 (UTC) Received: by mail-ot0-f176.google.com with SMTP id s4so3352706oth.7 for ; Fri, 16 Feb 2018 09:29:02 -0800 (PST) X-Gm-Message-State: APf1xPD7rVzTkzNZ3ueYQAGuaBpXMhrQ59r0LvTYfbU3vyfK879uHIK2 0gMZK1XnUIW8U7aHRM+swMpkRfiJATxL2lASGbonZw== X-Google-Smtp-Source: AH8x226Si3IhvnNmTAk9XsYspXyV8wiQJ/jiE6peMi7TWhetKL2EPgNi9I6k6fh8Gczhbo4mXzvNefh0XL1XZg2hCwk= X-Received: by 10.157.64.198 with SMTP id t6mr5162677oti.154.1518802141719; Fri, 16 Feb 2018 09:29:01 -0800 (PST) MIME-Version: 1.0 Received: by 10.74.62.17 with HTTP; Fri, 16 Feb 2018 09:29:01 -0800 (PST) In-Reply-To: References: <62964162-A731-4387-AE2D-9C3C0681A05D@me.com> From: Justin Bertram Date: Fri, 16 Feb 2018 11:29:01 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [DISCUSS] Using Travis CI for Artemis PR builds To: users@activemq.apache.org Content-Type: multipart/alternative; boundary="94eb2c1c1bde2443e0056557aeb7" --94eb2c1c1bde2443e0056557aeb7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable We're discussing travis-ci.org [1]. Justin [1] https://travis-ci.org/apache/activemq-artemis On Fri, Feb 16, 2018 at 11:21 AM, =D0=98=D0=BB=D1=8C=D1=8F =D0=A8=D0=B8=D0= =BF=D0=B8=D1=86=D0=B8=D0=BD wrote: > Sorry for interrupting (joined mailing list to resolve some issues), are > you talking about travis-ci.org or travis-ci.com? > > On Feb 16, 2018 10:18 PM, "Robbie Gemmell" > wrote: > > > 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 > > takes > > > 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 > > wrote: > > > > > >> 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 buil= d > > was > > >> 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 an= d > or > > >>> other os specific behaviours (aio fallback to nio) > > >>> > > >>> look to use appveyor for a windows build validation. (I=E2=80=99m t= hinking > 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 > > builds > > >>> > 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 al= l. > > >>> 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 > > investigating > > >>> > whether or not it would solve our problem. What do you guys thin= k? > > >>> Does > > >>> > anybody in the community have experience with Travis CI? > > >>> > > > >>> > > > >>> > Justin > > >>> > > >> > > >> > > > --94eb2c1c1bde2443e0056557aeb7--