Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BBAAD11AFB for ; Wed, 27 Aug 2014 05:03:04 +0000 (UTC) Received: (qmail 12898 invoked by uid 500); 27 Aug 2014 05:03:04 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 12846 invoked by uid 500); 27 Aug 2014 05:03:04 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 12828 invoked by uid 99); 27 Aug 2014 05:03:04 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Aug 2014 05:03:04 +0000 Received: from localhost (HELO mail-ig0-f172.google.com) (127.0.0.1) (smtp-auth username rajani, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Aug 2014 05:03:03 +0000 Received: by mail-ig0-f172.google.com with SMTP id h15so5671904igd.5 for ; Tue, 26 Aug 2014 22:03:03 -0700 (PDT) X-Received: by 10.50.66.197 with SMTP id h5mr27546833igt.34.1409115783067; Tue, 26 Aug 2014 22:03:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.12.202 with HTTP; Tue, 26 Aug 2014 22:02:43 -0700 (PDT) In-Reply-To: References: From: Rajani Karuturi Date: Wed, 27 Aug 2014 10:32:43 +0530 Message-ID: Subject: Re: CI: simulator tests and jenkins To: Rajani Karuturi Cc: dev@cloudstack.apache.org Content-Type: multipart/alternative; boundary=047d7bd6be0eb282d60501955501 --047d7bd6be0eb282d60501955501 Content-Type: text/plain; charset=UTF-8 build failure emails are bothering me. I am ready to help fix it if we agree to give it some attention after each checkin. If not can we at least disable the job? ~Rajani On Mon, Aug 25, 2014 at 2:54 PM, Rajani Karuturi wrote: > We are discussing on the CI infra and the tests/hardware required. It is a > much needed discussion. Its something which everybody agrees that we > require. > > Can we take a step back and look at out existing jenkins setup? > No CI system would help us if we dont look at it. > > We have [simulator-singlerun] job there which I believe runs after every > commit and executes all the simulator based tests. (I am not sure on this. > Can someone confirm?) > This job has been failing for the past 100+ builds with 1 consistent > failure and a few no ones here and there. > Can we give enough attention to this please and fix any failures > immediately? > > We also have a [hotfix-trigger] which is run on any branch with name > matching hotfix* > > Anybody aware of any such job which runs test cases/does sanity checking? > > [simulator-singlerun] > http://jenkins.buildacloud.org/job/simulator-singlerun/ > [hotfix-trigger] > http://jenkins.buildacloud.org/view/simulator/job/simulator-hotfix-trigger/ > > ~Rajani > --047d7bd6be0eb282d60501955501--