Return-Path: X-Original-To: apmail-ignite-dev-archive@minotaur.apache.org Delivered-To: apmail-ignite-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 9080D18B07 for ; Tue, 11 Aug 2015 17:51:25 +0000 (UTC) Received: (qmail 540 invoked by uid 500); 11 Aug 2015 17:51:25 -0000 Delivered-To: apmail-ignite-dev-archive@ignite.apache.org Received: (qmail 499 invoked by uid 500); 11 Aug 2015 17:51:25 -0000 Mailing-List: contact dev-help@ignite.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.incubator.apache.org Delivered-To: mailing list dev@ignite.incubator.apache.org Received: (qmail 486 invoked by uid 99); 11 Aug 2015 17:51:25 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Aug 2015 17:51:25 +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 96A4CDC50D for ; Tue, 11 Aug 2015 17:51:24 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 5.001 X-Spam-Level: ***** X-Spam-Status: No, score=5.001 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=3, KAM_BADIPHTTP=2, NORMAL_HTTP_TO_IP=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id X9j_jpSSodHD for ; Tue, 11 Aug 2015 17:51:16 +0000 (UTC) Received: from mail-io0-f178.google.com (mail-io0-f178.google.com [209.85.223.178]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 14F2B262D4 for ; Tue, 11 Aug 2015 17:51:16 +0000 (UTC) Received: by iodb91 with SMTP id b91so150334950iod.1 for ; Tue, 11 Aug 2015 10:51:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=eXgQ4wA8gjgjjtLzvwrgHHIfX0EEkZLzL8e2vnfuOJo=; b=L7JAQQP+MuadvHU+hzXdUyd5BDpvNMQE1E+WttA3E1srDPvKzr44njbB6vkeh8iNqd LbfbYPExMsZI/E4RpMxnMCRGIdMysIpDjL0QoVumnevmHFwo68F1XX/Ka2KKdlPlak81 xPm6zWHt//tcvl6BaYs31CPGSvEF2bqxnQohFJ/HS89gjusym9brdksBX84EqyYyLf3P kCbLSz6mwcb6nvJVG5vx+bFMQ7mvwBpVoszDO/Hx9HFFTnI+MKGPqeSs3NC2J2bAAl41 82H8SfKyV9+paAnEQEBOnaf8Q63mwPpoz2WfaTl9T1vuJdMxiqTo1icFg0zCL1yUUZkA mMdw== X-Gm-Message-State: ALoCoQnUy99PeBFpfchTnalJNMD6qSH8r/OcVDRlpNo4ID/OYz9ScT0EuTEsfg+Tin0GFoHPatAQ MIME-Version: 1.0 X-Received: by 10.107.166.71 with SMTP id p68mr31727612ioe.67.1439315475412; Tue, 11 Aug 2015 10:51:15 -0700 (PDT) Received: by 10.64.8.65 with HTTP; Tue, 11 Aug 2015 10:51:15 -0700 (PDT) In-Reply-To: References: Date: Tue, 11 Aug 2015 20:51:15 +0300 Message-ID: Subject: Re: TeamCity build on master From: Artem Shutak To: dev@ignite.incubator.apache.org Content-Type: multipart/alternative; boundary=001a1141cfd4a1da90051d0cbfa2 --001a1141cfd4a1da90051d0cbfa2 Content-Type: text/plain; charset=UTF-8 Igniters, I've done some work with TC: fixed something, filed new jira-s on failed tests and mute them, fixed configurations. Now it looks better. Please, keep an eye on it. Left: - Ignite Start Nodes - environment issue (I'm working on it). -- Artem -- On Thu, Aug 6, 2015 at 2:39 PM, Yakov Zhdanov wrote: > Agree. > > -- > Yakov Zhdanov, Director R&D > *GridGain Systems* > www.gridgain.com > > 2015-08-06 12:07 GMT+03:00 Pavel Tupitsyn : > > > I suggest to fix the wording (current is long and not very English): > > "There was triggered next test builds for last attached patch-file:" -> > > "Builds for the latest patch:" > > > > Thanks, > > > > On Wed, Aug 5, 2015 at 7:31 PM, Artem Shutak > wrote: > > > > > Auto triggering of TC build by patches was fixed. > > > > > > let me know, otherwise. > > > > > > -- Artem -- > > > > > > On Tue, Aug 4, 2015 at 7:22 PM, Artem Shutak > > wrote: > > > > > > > Why is it large? It contains only information about triggered builds. > > > > > > > > But it's possible to have any message that we want. These messages > > > created > > > > by our script, not by TC. > > > > > > > > -- Artem -- > > > > > > > > On Tue, Aug 4, 2015 at 6:03 PM, Alexey Kuznetsov < > > > akuznetsov@gridgain.com> > > > > wrote: > > > > > > > >> It is possible that when TC run builds not to add such large > comments? > > > >> > > > >> On Tue, Aug 4, 2015 at 9:15 PM, Artem Shutak > > > >> wrote: > > > >> > > > >> > Auto triggering of TC builds for new patches was broken (it's a > > reason > > > >> why > > > >> > we stopped getting CI builds comments in jira). > > > >> > > > > >> > I've filed ticket on it: > > > >> https://issues.apache.org/jira/browse/IGNITE-1194 > > > >> > . > > > >> > I've already started working on the issue. > > > >> > > > > >> > By the way, there is a possibility to trigger builds for special > > jira > > > >> when > > > >> > auto triggering is broken. Just use > > > >> > > > > http://204.14.53.152/viewType.html?buildTypeId=Ignite_RunAllTestBuilds > > > >> > (with set 'Jira number'). It will add the same CI builds comments > in > > > >> jira > > > >> > issue. > > > >> > > > > >> > > > > >> > -- Artem -- > > > >> > > > > >> > On Tue, Aug 4, 2015 at 3:54 AM, Dmitriy Setrakyan < > > > >> dsetrakyan@apache.org> > > > >> > wrote: > > > >> > > > > >> > > By the way, to add to the injury I think we stopped getting CI > > build > > > >> > > comments in Jira tickets. Were those stopped on purpose? > > > >> > > > > > >> > > D. > > > >> > > > > > >> > > On Mon, Aug 3, 2015 at 5:19 PM, Dmitriy Setrakyan < > > > >> dsetrakyan@apache.org > > > >> > > > > > >> > > wrote: > > > >> > > > > > >> > > > Still seeing many failures. Can the responsible parties please > > > >> respond > > > >> > > > suggesting what broke the build? > > > >> > > > > > > >> > > > D. > > > >> > > > > > > >> > > > On Fri, Jul 31, 2015 at 3:15 PM, Dmitriy Setrakyan < > > > >> > > dsetrakyan@apache.org> > > > >> > > > wrote: > > > >> > > > > > > >> > > >> Igniters, > > > >> > > >> > > > >> > > >> I am a little disappointed with the current state of TC on > > master > > > >> > > branch: > > > >> > > >> http://204.14.53.152/ > > > >> > > >> > > > >> > > >> Most of the builds are RED. Even the Basic test is failing. > > > >> > > >> > > > >> > > >> Are we checking TeamCity before merges? Is TeamCity build > > > >> > automatically > > > >> > > >> triggered for patches? > > > >> > > >> > > > >> > > >> D. > > > >> > > >> > > > >> > > > > > > >> > > > > > > >> > > > > > >> > > > > >> > > > >> > > > >> > > > >> -- > > > >> Alexey Kuznetsov > > > >> GridGain Systems > > > >> www.gridgain.com > > > >> > > > > > > > > > > > > > > > > > > > -- > > -- > > Pavel Tupitsyn > > GridGain Systems, Inc. > > www.gridgain.com > > > --001a1141cfd4a1da90051d0cbfa2--