From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6669723628337102848 X-Received: by 2002:a1c:f514:: with SMTP id t20mr609319wmh.25.1553065944551; Wed, 20 Mar 2019 00:12:24 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a1c:4083:: with SMTP id n125ls221453wma.4.canary-gmail; Wed, 20 Mar 2019 00:12:24 -0700 (PDT) X-Google-Smtp-Source: APXvYqwvWtGl20WQdMuTZ+7qH3qk+5ZP2mKqNQpUB1bvSblqI4bEO+9Tfho2kbqsSMqvT4OuR0JL X-Received: by 2002:a7b:cc14:: with SMTP id f20mr646562wmh.5.1553065943903; Wed, 20 Mar 2019 00:12:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553065943; cv=none; d=google.com; s=arc-20160816; b=Mf98QewW6+kQdDPGDZDWkBYt28XI9VIrmyRP/jKRVdanHYWmtTLlZoxSbsWAYG/JSg LgvoJj/gpl7XCCGzCVh7Fi+EFGKEPUJZLHwWMLMoyYrJMAIlwYfCU3kTzUjO8BJjOb4z NnxY3MEQhPHuE6BbWyPUVaaTRdKj8imZvAlp/fYHyriUv+KOtow2Taor8zLh5aDv3xiJ 9bdZ1P/P9ap2txO2pdjmURcS0kNSNiEgvFvJMsog74hXcGd7O7ZommeC4n1Kp1pMxJMG jQeGJmCcJ2Kxm/0aWJfBiOjHf5KuBBjsI+7qEZT+wYsbnN5p0GLe3uutV5mthrCFnzQh z+EQ== 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=Qr4v5CYKhT6oe1MUBn5I5vUt3/GVjqfIf2CiRXrPgEU=; b=usIgvvWuHxi1C/C1k06xoApOrFoyCnk/SEeYNImCD67FCAgv1l3qETHEUYGd4gXDy3 2CI+JAv1g5QMkv2FEBf3qBze536hy539CoFF8NwHOKGzh+JaO80DW5wnPb1s+OR26s1p PPDZqygmhC4ZtCo/KRWjgVkWc9Um4mfmgHfHPNY801WYKivjURNgrbtVZWQLR0TDMiow beMyy8aj820HQSDIg1Au/5y05Q/Rq1/rjpwvhJXgHibT36sT+Ua57qszRMBy90xQHqHP nbJJFM6j8v/lvBsf/iotKSmsLJYkr62ztfJZWHDdvKtaPHCb2AREkZZTv5AfaK94fEE3 6qNw== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Return-Path: Received: from thoth.sbs.de (thoth.sbs.de. [192.35.17.2]) by gmr-mx.google.com with ESMTPS id z129si174865wmc.2.2019.03.20.00.12.23 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Mar 2019 00:12:23 -0700 (PDT) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.2 as permitted sender) client-ip=192.35.17.2; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by thoth.sbs.de (8.15.2/8.15.2) with ESMTPS id x2K7CNad014263 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 20 Mar 2019 08:12:23 +0100 Received: from [139.22.38.235] ([139.22.38.235]) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id x2K7CLHo025690; Wed, 20 Mar 2019 08:12:23 +0100 Subject: Re: [PATCH v7 0/5] Fix usage of additional apt keys and repos To: "Maxim Yu. Osipov" , "Andreas J. Reichel" , isar-users@googlegroups.com References: <20190319133523.32456-1-andreas.reichel.ext@siemens.com> <1d5477ce-2bf8-e734-c50a-6281c7d85959@siemens.com> <688943e7-4acc-94a1-810d-00f75fe6a070@ilbers.de> From: Jan Kiszka Message-ID: Date: Wed, 20 Mar 2019 08:12:21 +0100 User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 In-Reply-To: <688943e7-4acc-94a1-810d-00f75fe6a070@ilbers.de> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: a72lOpqwpgjG On 20.03.19 07:48, Maxim Yu. Osipov wrote: > Hi Jan, > > On 3/20/19 7:26 AM, Jan Kiszka wrote: >> On 19.03.19 22:58, Maxim Yu. Osipov wrote: >>> Hi Andreas, >>> >>> CI build ('scripts/ci_build.sh -q') failed. See >>> http://isar-build.org:8080/job/isar_mosipov_next/165/console >>> >> >> This is the same error I saw yesterday ("..isar-bootstrap-target/rootfs/dev: >> not mounted"). And given that this and my build had no overlap in our own >> patches, it must be something else you should examine because it may affect >> your patches (next..e13be9cefd87). > > Yep, when I tested my patches CI build passed OK, > but now I see the same error in overnight build of 'next'. > OK, that makes more sense again. > >>> We may create project for you on isar-build.org so you can run CI build on >>> isar-build.org before submitting patches to the mailing list. >>> We just need your github repo name (like >>> https://github.com/henning-schild-work/isar/) >> >> We rather need to find a way to make CI public, the current state is rather >> suboptimal. It's also not very well integrated with github. >> >> In fact, we need to find a way to build Isar in the cloud in general, also for >> use cases such as https://gitlab.com/cip-project/cip-core/isar-cip-core. And >> our internal CI is not scaling either. We do know how to do that better >> (container-based builds, controlled e.g. by gitlab-ci), but not yet how to >> deploy economically. > > Agreed. To be honest I'm not a big fan of gitlab - it's rather slow. > Do you have any suggestions regarding other alternatives to gitlab/jenkins? The speed of gitlab is primarily a matter of how you deploy it (ok, when you have >25K users and >40K projects like we do at Siemens, there are also other limits). But this is about where to run the CI builds and tests and how to make those results available. Unfortunately, our builds take long and require root permissions. So we cannot simply use any of the public CI services, that scale well but are limited in those regards. We need hosting in VMs that we control (and likely also pay for), but that can also be cloned by other users (copy&paste of deployment recipes). We played with AWS as well as Google Compute and Kubernetes clusters that spawn up powerful runners on demand (you can afford running them 24/7). These recipes aren't complete yet, unfortunately, and tuning them takes some time. That's why this isn't ready yet. I'll try to prioritize that topic as it is becoming a bottleneck in many projects. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux