From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl1-x632.google.com (mail-pl1-x632.google.com [IPv6:2607:f8b0:4864:20::632]) by sourceware.org (Postfix) with ESMTPS id EE847385E008 for ; Wed, 30 Jun 2021 16:46:11 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org EE847385E008 Received: by mail-pl1-x632.google.com with SMTP id m17so1795903plx.7 for ; Wed, 30 Jun 2021 09:46:11 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:cc:from:subject:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=gUitdKpO57PM12jU4SldBYAmWTodmKBhVNekJf84HgA=; b=gH80UFKCT0FZFJsY+ab1M+uIi5VlmeldLogAcA0t5/AScBrRcfKL6Qhr/ICXlIsGEM acvObpzOfbsTiHU3u1AnIiwwFuyEhJCSRav2Y9sFNQ16BGpAij2/IDxywWfeVSIxoSYg EZS+TnbkERQUL0E62Y24u62GTx/29dZdeCWAyHgWbHboyTS7DnMv/gta0Q7rw/vAzoqs h0Kkzztqp4zR479vOO1Lh68jfJWwmy4K/OFS2t8CCjQEkVlIzFk8WY1MATGEZZmWIe1x gj2cGr88ZqzUs5uq6SOGbjrViwv0TmdWGq6XwJkmnGoAe49PX4eS3QtNzc7BBVlQTABz 9czQ== X-Gm-Message-State: AOAM533gtb7c88G039CYrheYMGKMyHp3s+wb6aGUAmCPCvh2pyCLIwnz x6nht+iYAvgrd7yrMyNpFqr2qZzorRLNAQ== X-Google-Smtp-Source: ABdhPJyC+hHq2Q+uyWpuZlhVki5kyhEh8yCP9+/r0ZeJ1m0ApwLtruKjMIFM2H26ARUZOZlYuKUDlg== X-Received: by 2002:a17:90a:c287:: with SMTP id f7mr5286459pjt.57.1625071570984; Wed, 30 Jun 2021 09:46:10 -0700 (PDT) Received: from ?IPv6:2804:7f0:4841:1e6a:9c39:8c62:a64a:d289? ([2804:7f0:4841:1e6a:9c39:8c62:a64a:d289]) by smtp.gmail.com with ESMTPSA id 133sm20765555pfx.39.2021.06.30.09.46.09 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 30 Jun 2021 09:46:10 -0700 (PDT) To: "gdb@sourceware.org" From: Luis Machado Subject: [RFC] Proposal for hosting GDB CI builds Message-ID: <7bfae273-3887-30c8-dc65-94d5b177db56@linaro.org> Date: Wed, 30 Jun 2021 13:46:07 -0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-6.2 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jun 2021 16:46:16 -0000 Hi, This proposal comes as an attempt to revive the GDB CI builds, given the previous one (buildbot) is no longer being maintained by Sergio (thanks a lot for keeping it working for all these years by the way). CI GDB builds are a great help for spotting regressions without having to do the tedious and time-consuming work of running the GDB testsuite for each git revision, for each architecture and reading through hundreds of lines of summaries. If a regression is spotted, then one needs to bisect to find the culprit. This isn't great, specially for architectures without great availability of desktop hardware. Ideally, for each commit, we'd run full builds to validate the state of the tree, but we're not quite there yet. So meanwhile, having some level of automation to get the builds done without manual intervention sounds like a reasonable step forward. From previous IRC conversations, it seems to be a consensus that availability of processing power is not a problem. It is reasonably easy to find hardware to do some builds. The most difficult resource to find is manpower to setup the CI infrastructure and keep it running. With the above said, I've discussed this internally at Linaro and we can spare some manpower to setup and maintain an isolated Linaro-hosted Jenkins instance for GDB CI builds. Linaro can take care of providing builders and build jobs for ARM. Other architectures would be handled by their respective contributors. Those contributors can write jobs and plug builders as needed. Setting up new jobs doesn't require the use of the web interface. It can be done with yaml files in a git repo. It is reasonably simple. You can see an example of the Linaro CI here: https://ci.linaro.org/ Also, a GDB job for aarch64: https://ci.linaro.org/job/tcwg-gdb/ And also the summaries for GDB testsuite runs: https://ci.linaro.org/job/tcwg-compare-results/13968/artifact/artifacts/logs/0-report.html Of course, this effort only makes sense if the community is OK with using Jenkins as the CI mechanism and if it actually sees value in having a system like this in place. Thoughts? Questions?