From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6693749539433611264 X-Received: by 2002:a17:906:eca3:: with SMTP id qh3mr42600833ejb.139.1558600371977; Thu, 23 May 2019 01:32:51 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a17:906:c116:: with SMTP id h22ls1192334ejz.6.gmail; Thu, 23 May 2019 01:32:51 -0700 (PDT) X-Google-Smtp-Source: APXvYqxOVI2G3tEdSFrBoz2qw4cLt2cje7ZqogajQKCcL5Ad/VNsS2XJfRzisuHX56O2VT0/N9D5 X-Received: by 2002:a17:906:eb97:: with SMTP id mh23mr75507699ejb.69.1558600371489; Thu, 23 May 2019 01:32:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558600371; cv=none; d=google.com; s=arc-20160816; b=ZM8fxk+m51eyXtWaz1jv0wkI9ZawVFBsL7iwtlbJshqV1mtxvG5aHmYgmXDrNCGYvX miQb4b6TauktYM+23hCmv3fxq6spqSaOQIAPjKdgtK5WOqInB79UsirPglvrGq50LtUS eKv7nBHEti+JLOG4GYQDR5WscseLctINE0LKUxXzAEt6fP+PJyUoTVfD/M1xa/ZiF+tE vAWJjRBzKFWP/M5p+kP4bnqNGkqBdG3IdSvRLLU9M2wrWKMPxl1yOnDIaHXwuQ52VrrW az1/0ubUKF2Dy+UWw4+VqZM8xq6zwX5kOIXhew0T4IgK4Rls2ELj2A4HXwRnasOA17bp UEbg== 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:from:references:to:subject; bh=+WpADK8jyf4eHZimgUjRr58P7TG6tBPBIOYo7YkwbRA=; b=MZryMrj0vFerLy+gWFImjp7l+8yVXEUAdjCDVlb84GCah+YZJ36V3CYwa07YcFAFAY SvKAdUhde8S77xFEnHrH9O6wcasZQEfRdQY/JlcssY27tjEDMq8xTZN4jLl8eVXHGai0 BrNGyb+7NQNhzn6IUBD5pMrBnObw30B0kpA1vxxRliFPSS41yFNQhUbMTDs3E9+8PmAo X8TwZLq0bVA1sq2759OagWceWvzsJ53aOTsN0QFiq3+e8N4CurShwsGKdNjPofCPYJVl Vj+KaJtU5YtoBTF9ORS2+l9bOIaXZAwsySdof/X0u38HwTJ+tQdK66nSMqCyrzi+Gxyz Y6Pw== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of claudius.heine.ext@siemens.com designates 194.138.37.39 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 lizzard.sbs.de (lizzard.sbs.de. [194.138.37.39]) by gmr-mx.google.com with ESMTPS id l30si2856316edd.4.2019.05.23.01.32.51 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 23 May 2019 01:32:51 -0700 (PDT) Received-SPF: pass (google.com: domain of claudius.heine.ext@siemens.com designates 194.138.37.39 as permitted sender) client-ip=194.138.37.39; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of claudius.heine.ext@siemens.com designates 194.138.37.39 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 lizzard.sbs.de (8.15.2/8.15.2) with ESMTPS id x4N8WpGQ000938 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Thu, 23 May 2019 10:32:51 +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 x4N8WonN015755; Thu, 23 May 2019 10:32:50 +0200 Subject: Re: [DISCUSSIONS] CI build To: "[ext] Jan Kiszka" , isar-users References: <20190522194410.GC2441@yssyq.m.ilbers.de> From: Claudius Heine Message-ID: Date: Thu, 23 May 2019 10:32:50 +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: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-TUID: bgnEMFrSZojR Hi Jan, hi Baurzhan, On 23/05/2019 06.44, [ext] Jan Kiszka wrote: >>>   - Not transparent configuration/environment: >>>     -> parameters with which ci_build.sh is called are not >>> controllable from >>> the repository >> >> Hmm, the intention actually was that everyone runs the same fixed >> testsuites. >> If desired, we could publish the arguments and gradually move them to >> the isar >> repo. Which is currently not the case, we have a 'normal' build, a 'fast' build, a 'cross' build and a 'repo' build, which can be combined with 'normal', 'fast' and 'cross' IIUC. >> >> >>>     -> difficult to select which test case should be run >> >> This is the motivation for Avocado. >> >> >>>     -> Configuration of the environment is not controllable from the >>> repository: Installed packages, System configuration (locales), >>> Distribution, etc. >> >> Here the intention has also been to have one standard testing >> environment, and >> it is Debian stable + instructions from Quick Start, nothing more. I'd >> welcome >> moving to kas + docker. If desired, we could publish the current setup. >> >> I'd like to have the testsuite be runnable from any CI system with the >> same >> script, without arguments. Then people could deploy any system they like >> (Jenkins, GitLab, Travis CI, AWS...). The same testsuite should also be >> runnable on one's host (already the case with ci_build, >> vm_smoke_test). Under >> the hood, every test case should be defined and runnable individually >> (Avocado). Personally I don't really care about executing the whole CI process locally. I am much more interested in triggering single failed test-cases locally to work on them. So the 'ci_build.sh' is not really useful for me. 'ci_build.sh' is just to unhandy to use locally. [...] >>> -> Cannot be spread over multiple servers >> >> Haven't looked at that, ideas welcome. Jan told us he is preparing >> something, >> but load balancing would spread multiple pipelines, not tasks within one >> pipeline. Depending on the costs, it might or might not be cheaper for >> us to >> throw more physical servers on the task. >> > > https://lists.cip-project.org/pipermail/cip-dev/2019-May/002371.html Would have been nice to have this cross-posted to this ML as well. Will Michael write patches for isar to integrate this, or does he needs anything to do this? >> >>>     -> Patches on ML should be automatically tested and reported back >>> to ML >>> (that only makes sense if the build is reliable though) >> >> I haven't looked at that. Is there a tool that does this? Not really. But I posted a patchwork+jenkins integration howto some time ago: https://that.guru/blog/patchwork-and-ci-in-a-tree/ >>>   - Logs aren't public accessible >> >> Logs are accessible with authentication. Jenkins has public mode, but >> it lists >> the users publicly, that is why we haven't opened it till now. If >> desired, we >> could look at that. Is it that high-priority, given that all major >> contributors >> here have access? >> > > Let's stop wasting thoughts on legacy Jenkins, rather discuss how we can > move on to gitlab-ci, if something is missing there etc. I can only figure out what is missing after I tried it out. regards, 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