From users-return-49396-archive-asf-public=cust-asf.ponee.io@activemq.apache.org Thu Feb 15 06:09:00 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 38073180621 for ; Thu, 15 Feb 2018 06:09:00 +0100 (CET) Received: (qmail 90320 invoked by uid 500); 15 Feb 2018 05:08:58 -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 90308 invoked by uid 99); 15 Feb 2018 05:08:58 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Feb 2018 05:08:58 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id BF5DEC29ED for ; Thu, 15 Feb 2018 05:08:57 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.498 X-Spam-Level: ** X-Spam-Status: No, score=2.498 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-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 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id aIJPziWtF6Fz for ; Thu, 15 Feb 2018 05:08:56 +0000 (UTC) Received: from mail-wr0-f170.google.com (mail-wr0-f170.google.com [209.85.128.170]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 95EB05F180 for ; Thu, 15 Feb 2018 05:08:55 +0000 (UTC) Received: by mail-wr0-f170.google.com with SMTP id s5so2092206wra.0 for ; Wed, 14 Feb 2018 21:08:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to; bh=JVw/SqgPUnBbH0zud/LwY4pvJQRjPa2Nvl2IebcbrcQ=; b=E8XjU2p5QdDEe0UqP16QVYadfRa+fktH8Mz+JiRT/f7cwGNzBtVPVkaJVIyAtbSlHm abZIGtu+bHKoqBcpMtlhlTRYHQNoknrtbzt3BXh49vMhpmZZU02Sn5h1kbX7H1GHe2so ZaJ0g0TboCwTTD96ND8eZBhbQS1OhEJAahxfp8LD6teUdsvfGi8Z+6RUKeIHNqhfK7NH ESAlvc16vgrZvq34lUjcvkXaLhknoYAIqh1RzxOblCk28vJgF9GEleWSJlxKB2oilVpG q/o97zo933WO7ccMaAuV0ECoTvVTh6/ACtLH9VHHcijms4N18qr/+MPcWtfKBbjwhy3f cm8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=JVw/SqgPUnBbH0zud/LwY4pvJQRjPa2Nvl2IebcbrcQ=; b=DukhwYESiFEuzcy3uEc3GgpR9Dpv7V9hWtsRAgeYtc6DLbvmu4j0tR/9Ss0im1zwA/ k3Efny12k1vqvKkPEg+SEa1j+FBE4uZMHoXhlh7FgEwSNKZEWUxSh4FVo8y0vikOdV5I DKxE8tmUB/zakpIUHL+tXI8OqzuvaP6j/yrBXqGXyFhRDYQrEM+Iil3Jtc4OBQcci/pq twDKoxUPmoF0wevJVLxiRtcStbEndc+F8z1fOFUBjAo4F3U8w/IPA0EDWpQsqHP6bnHU LR71LEDiOKQD08054OOZBCVOBGRymDlZuClzTcaWfGGewszSWNXmQmF45pO/cWw4ARpT XGUw== X-Gm-Message-State: APf1xPD+fH+0yVu6DFOcw/MHGFdKM2mjHs/ILp7jQnmf7ipDcgRME86P EhqSoBRfBu4N+BY1WyGuyibREBYgO9FXon0RkyVkVQ== X-Google-Smtp-Source: AH8x227bI8AFDUzDg5nazZGZy3/t20jONjyQfv8G8W/+gXjq3xpa2L9cKYC0SDWQ8L6TbzxUrgPhXNNmTFmJ/yLovc4= X-Received: by 10.223.175.44 with SMTP id z41mr1112856wrc.129.1518671329036; Wed, 14 Feb 2018 21:08:49 -0800 (PST) MIME-Version: 1.0 Sender: tbain98@gmail.com Received: by 10.223.134.149 with HTTP; Wed, 14 Feb 2018 21:08:28 -0800 (PST) In-Reply-To: <62964162-A731-4387-AE2D-9C3C0681A05D@me.com> References: <62964162-A731-4387-AE2D-9C3C0681A05D@me.com> From: Tim Bain Date: Wed, 14 Feb 2018 22:08:28 -0700 X-Google-Sender-Auth: 25HXqQJgp4X9HZfnRFA77GX2fl8 Message-ID: Subject: Re: [DISCUSS] Using Travis CI for Artemis PR builds To: ActiveMQ Users Content-Type: multipart/alternative; boundary="f403045f4f42190d9a05653939b7" --f403045f4f42190d9a05653939b7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I'm in no way trying to discourage you guys from evaluating Travis CI. However... There are currently 4 builds that are in a failed state on the history of that job: - https://builds.apache.org/view/A/view/ActiveMQ/job/ActiveMQ-Artemis-PR-B= uild/5111/consoleFull - Failed due to "Could not transfer artifact com.google.code.maven-replacer-plugin:replacer:pom:1.5.3 from/to central= ( https://repo.maven.apache.org/maven2): /home/jenkins/.m2/repository/com/google/code/maven-replacer-plugin/repla= cer/1.5.3/replacer-1.5.3.pom.part.lock (No such file or directory)" - This might in fact be environmental, it's hard to tell. - https://builds.apache.org/view/A/view/ActiveMQ/job/ActiveMQ-Artemis-PR-B= uild/5103/console - Failed due to "failed to write new configuration file /home/jenkins/jenkins-slave/workspace/ActiveMQ-Artemis-PR-Build/.git/con= fig.lock" - It looks like you've got your builds configured to use the same direct= ory for all builds of the Jenkins job, rather than using a different directo= ry for each build (5103, 5104, etc.), and if that's true, it seems very expected that concurrent builds would fail with errors like this one. Is there a reason you're not checking out the code into a directory that's specific to the individual build being done, to allow them to operate in parallel without interfering with one another? Or am I misreading someth= ing about the log output? - https://builds.apache.org/view/A/view/ActiveMQ/job/ActiveMQ-Artemis-PR-B= uild/5104/consoleFull - Failed due to checkstyle violations. Seems bona fide, and would not be fixed by a move to Travis CI. - https://builds.apache.org/view/A/view/ActiveMQ/job/ActiveMQ-Artemis-PR-B= uild/5105/console - Failed due to checkstyle violations. Seems bona fide, and would not be fixed by a move to Travis CI. This is obviously a very small sample size, and you guys have been watching these builds for far longer than the 10 minutes I've put into it just now, so there's definitely a chance that today's builds aren't representative. But do consider whether the "environmental" problems you're running into with Jenkins are in fact Jenkins's doing, or whether maybe they're the result of a misconfiguration that you'd have the power to fix yourselves. Again, I'm not lobbying against considering Travis CI (I've got no experience with it), just suggesting based on a very small sampling that maybe some of the problems being laid at Jenkins' feet might not actually be Jenkins's fault and might be solvable within Jenkins, so factor that into any discussion of the pros and cons of moving vs. staying. Tim On Tue, Feb 13, 2018 at 3: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. +1= 00 > > 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 thinkin= g this > validates bat files etc and ensures not Linux specific paths being used i= n > 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 all. Ev= en > > 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 P= R > > 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? Do= es > > anybody in the community have experience with Travis CI? > > > > > > Justin > --f403045f4f42190d9a05653939b7--