From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6693749539433611264 X-Received: by 2002:adf:978b:: with SMTP id s11mr668765wrb.169.1558599059017; Thu, 23 May 2019 01:10:59 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a5d:6904:: with SMTP id t4ls949909wru.12.gmail; Thu, 23 May 2019 01:10:58 -0700 (PDT) X-Google-Smtp-Source: APXvYqxoo3ukc7ytpjVvpc9GVgSNsAIFe9Bay6tOnkU4JktvxWY+dM4/s5Em3hCRxxWjpRnTagZP X-Received: by 2002:adf:ba10:: with SMTP id o16mr4461424wrg.89.1558599058631; Thu, 23 May 2019 01:10:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558599058; cv=none; d=google.com; s=arc-20160816; b=F8ad2ssOEipCsjGe4tGWsH08RrRTM9IuSCTV5pR26eMTunJjoIOOnjSnNivWmmvpry K5+PsPrludJlrW+juN4vcW4hdRk0RTMFZVkFPygIVy3Niv11F1ZpVjaqELkggVWa0OQ6 InN1iiLdNWAyj6+Fkozf0+DP/R4/8wZmqwWJG13ZoDwBG2nMfMaRXCRnl0cFCmEhHBxG e9a1BO1/KhSeJpYTHKZLDmmnu8HMupBTWnuwctywXVCdmQ+TbWw+5IU6DqMFBrnqac8J u+/MAVuxSYEXhndAuvFvXg0H9HVfvkSVWOS/g6a5GAsfXaPYxKCB1OngRoJzPBNwT/pB WDgQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:references:to:from:subject; bh=D03MpazHjUIG/kuEqVgKpF3oC0/zicPJbj7nEgdgYgA=; b=Zkk41bSu00NIzn0jIxJsqAY2qGEsmp1kq/7FJg2QVZTRYsSFYbaRcCCH96BTDOzuqT yziXO82NfnQWxrpPhU9wptI2qEdUdsu9y0uPT/BTRu/E9GJu3uLQv97jpEcPyiJ0x7qa 5+k82Sr4JUNOaVz64NeZzC5pe4tGp5kbMIeRoWMqMJZJ/Q6F2S03tpZm8LL9v9h96wb5 raMXh5L20kh9r5c3WhbCZBdm+ty4Sf2cm1buEKT2AeOR3kWhDIQnKAy94aHySNs+nfG3 mBffRJZqmzv80aKlQ2kCQSXmKjVaDIENR935fDgxAXxOehFiQajH55Hib+T0XZb92iOD pELA== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=claudius.heine.ext@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id j20si542056wme.0.2019.05.23.01.10.58 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 23 May 2019 01:10:58 -0700 (PDT) Received-SPF: pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.14 as permitted sender) client-ip=192.35.17.14; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=claudius.heine.ext@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id x4N8AwtI017461 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 23 May 2019 10:10:58 +0200 Received: from [139.25.69.232] (linux-ses-ext02.ppmd.siemens.net [139.25.69.232]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id x4N8AwjQ023153; Thu, 23 May 2019 10:10:58 +0200 Subject: Re: [DISCUSSIONS] CI build From: Claudius Heine To: "Maxim Yu. Osipov" , isar-users References: <5128c754-55f8-924b-365c-2d529131bd3a@ilbers.de> <16e80d33-4f24-8b5a-de02-c02a90cc2c77@siemens.com> <57463c63-9747-126f-4b98-dc042f2b674a@ilbers.de> <80ac809b-384a-7654-0a13-2723be6eedb7@siemens.com> Message-ID: Date: Thu, 23 May 2019 10:10:58 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <80ac809b-384a-7654-0a13-2723be6eedb7@siemens.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-TUID: thMXYDqYBEQ/ Hi, On 22/05/2019 13.28, [ext] Claudius Heine wrote: [...] >> >>> >>>> >>>>>   - Manually triggering of build jobs >>>>>     -> After pushing of CI branch, build has to be triggered via >>>>> button >>>> >>>> One may enable such build trigger (I believe that such trigger is >>>> enabled for Henning's project). but from my user's experience I >>>> prefer to start the build manually. >>> >>> I normally just push to the ci branch when I want to start tests. >> >> I've enabled the corresponding options for your projects - please try. > > Thanks. But I think I should now have two branches for each different > build parameter set. So that I don't trigger both builds just for one push. I pushed a ch/ilbers-ci-fast branch for the fast build. > >> >>> >>>> >>>> Of course, overnights builds are started periodically. >>>> >>>> See for details: >>>> https://wiki.jenkins.io/display/JENKINS/Building+a+software+project >>>> >>>>>     -> Patches on ML should be automatically tested and reported >>>>> back to ML (that only makes sense if the build is reliable though) >>>> >>>> Do we really want such feature? >>>> My concern is that ML will be polluted by such reports... >>> >>> You are currently testing and reporting back manually, if instead of >>> you some bot would do that automatically, then I don't how that would >>> increase the noise on the ML. But as I said that only makes sense if >>> the false positive and negative rates of CI is lessened. >> >> Manual work is unavoidable as sometimes patches are not merged properly. >> I'll enable reporting to ML when I push a patch set to maintainers >> branches for CI. > > Can you make it so that it emails with the correct email 'in-reply-to' > header, so it lands in the right thread of the patchset? Otherwise > ordering that will be annoying. Just to clarify: In all my points I would prefer a good solution instead of a quick one. If some points are quick to solve without any disadvantages, then ok. But if some quick solution will probably have other undesired side-effects, then take a step back and think about other ways to fix those issues without those, even if that might take a while to work them out. The current system is ok enough to bare with it until a proper solution is in place. Claudius -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de