From users-return-49427-archive-asf-public=cust-asf.ponee.io@activemq.apache.org Fri Feb 16 18:36:25 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 518A0180647 for ; Fri, 16 Feb 2018 18:36:24 +0100 (CET) Received: (qmail 34910 invoked by uid 500); 16 Feb 2018 17:36:23 -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 34893 invoked by uid 99); 16 Feb 2018 17:36:22 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Feb 2018 17:36:22 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id ECCA1C0238 for ; Fri, 16 Feb 2018 17:36:21 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.879 X-Spam-Level: * X-Spam-Status: No, score=1.879 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, 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: spamd4-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 (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id jmFY3q3gn1zS for ; Fri, 16 Feb 2018 17:36:19 +0000 (UTC) Received: from mail-lf0-f53.google.com (mail-lf0-f53.google.com [209.85.215.53]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id C5F7B5F19C for ; Fri, 16 Feb 2018 17:36:18 +0000 (UTC) Received: by mail-lf0-f53.google.com with SMTP id 37so5051933lfs.7 for ; Fri, 16 Feb 2018 09:36:18 -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; bh=+9j+I9mM/9P1TBDEQr5bc/7/IkeHeHRDh8v8UtQad5A=; b=lY3aqa/eF3B4NyPxnMg222kHvI1/y20/03iaHIlqChKpGWUH3zNW793f6uyY20N3lL T3ujV2InCy1j1f9gHKOVxnssSD2yNQ7rzSX1wW0EF0WFYGcd4i7iVezflNTCjryKbc/X zgGkG4WDYL/HfJ3qpQ2kjc09NfgXHkEl+t1aJL6nwIJ5WY8gxNrBGjtfFi4HoTeZvShz XPUuIilES6YW7LHcpYrzOpCMbmpuM8dcmcQyjv73ERaTnvi/SNs/BfYlklVlYmpwIatW XZBc8XkiqAME71OxwoAlm7Yv3DX8mFaQFWpa0Y7xrY+9UlqlHhNvt7xfIukMx1ABn4v+ jG7g== 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; bh=+9j+I9mM/9P1TBDEQr5bc/7/IkeHeHRDh8v8UtQad5A=; b=YJIr61PRNe9IwtvrhBsNFCI+3NiYLJCVeuvZv3b+fDUSCL6c++kaS1aq7E1xd4HQWN 85eI0Hh9F5z56UOH5d+p4BJpsqDphoFW1ILg/VETXSJXjgcoYdFQme61WL8rSIgXP1dz 6LV+qf+e9XONvtGYDu/31sT0sf1oaWnVxUEvuvl+IzH7gHbSiXwl2fos5RpN47GKlymA i/QNqz7msgTqARdhelAb2ZLBlWb4dbe+0+xF6uLy7N2e+s0nEc1OBT6EEp1+EWYBuiMZ wEIvlBOPGxzwvUwQEQjTc97n63h713LdMgLCPU44PYfagk6PfVaSNfIT+scG79J3xsI+ e+Dw== X-Gm-Message-State: APf1xPAzf9D0XaUZYTrGNTFos1TOc5AMLD/t9HraRvgi+qn/k5k6ormK xtnawg5l2cpi8otUtX1xmxcE6H4Qy6iEfIoeSbEL4Q== X-Google-Smtp-Source: AH8x224ht9TKxGOYKNZu3NuNzfvgXu+mY1Pfp60mhKMAQ7Q//Kmozapu0doWO+PZo/cSzRg9cLsRR/c/qDdzVFPmovw= X-Received: by 10.46.48.10 with SMTP id w10mr4326034ljw.76.1518802578164; Fri, 16 Feb 2018 09:36:18 -0800 (PST) MIME-Version: 1.0 Received: by 10.46.1.90 with HTTP; Fri, 16 Feb 2018 09:36:17 -0800 (PST) Received: by 10.46.1.90 with HTTP; Fri, 16 Feb 2018 09:36:17 -0800 (PST) In-Reply-To: References: <62964162-A731-4387-AE2D-9C3C0681A05D@me.com> From: =?UTF-8?B?0JjQu9GM0Y8g0KjQuNC/0LjRhtC40L0=?= Date: Fri, 16 Feb 2018 22:36:17 +0500 Message-ID: Subject: Re: [DISCUSS] Using Travis CI for Artemis PR builds To: users@activemq.apache.org Content-Type: multipart/alternative; boundary="089e082f548827d0a3056557c8e1" --089e082f548827d0a3056557c8e1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable It turned out that ms SQL jdbc is not being tested (both documentation is bad, SQL statements are also broken). Do you accept patches for app veyor as well? On Feb 16, 2018 10:29 PM, "Justin Bertram" wrote: > 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), ar= e > > 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 apparentl= y > > > takes > > > > awhile to update or got out of sync or something. The PR build loo= ks > > 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 ha= d > > also > > > >> enabled Travis CI builds on my own GitHub repo so the Travis CI > build > > > 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 bui= ld > > 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 successfu= l. > > > >>> > > > >>> 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= thinking > > this > > > >>> validates bat files etc and ensures not Linux specific paths bein= g > > > 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-base= d > > > builds > > > >>> > used to validate GitHub pull-requests for Artemis are failing a= t > 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 > > > investigating > > > >>> > whether or not it would solve our problem. What do you guys > think? > > > >>> Does > > > >>> > anybody in the community have experience with Travis CI? > > > >>> > > > > >>> > > > > >>> > Justin > > > >>> > > > >> > > > >> > > > > > > --089e082f548827d0a3056557c8e1--