From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qk1-x736.google.com (mail-qk1-x736.google.com [IPv6:2607:f8b0:4864:20::736]) by sourceware.org (Postfix) with ESMTPS id 23382386EC68 for ; Sun, 17 Jan 2021 15:33:50 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 23382386EC68 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=dinwoodie.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=adam@dinwoodie.org Received: by mail-qk1-x736.google.com with SMTP id n142so16601790qkn.2 for ; Sun, 17 Jan 2021 07:33:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dinwoodie.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=HzpaBa6S+BbB1ZsZRM9YAWiFLbtseLUrGaBgJzNjRk0=; b=nGLaz/QDTosM6erfBCAkFELMh1f65DJ3mvxBIbyO76MdUj1lFYZph5CL5TzUwZudCq fuyKuBJcwzHcBdJkoDqXXdMgVSFSBZYAv8uttBnbrPyME8oMdng/jBmJ5lnw9r8fKmqt x2kOkD+orl5DEG+bMY3y6tQ7XN8U3vOlxz+Bw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=HzpaBa6S+BbB1ZsZRM9YAWiFLbtseLUrGaBgJzNjRk0=; b=iJsTF4PScYT9vy7m48KlB+I+W1p8zAdg/n7piwtio3mq3IG2FwvpqMza11YzUPvXl7 BJjXiRKYBY0/U/+8tL79ahHZMrsEdMFVXoYlR9kTNNkIICsa/0qF6Nxph5IaQDALvmNH NOdKB7LV4ufh4GnEQKQGlVSjdAhlwUHe0G90QZWLNwMGKD+/vRHCzYv2u1kar9z3pcNK VLwWoM+f3wyUPdL/Fg/s0f0puTUSPqJUKipPR/WhVo4gTVH9jYo4RvXkCo4ay8DkacIA ssTvZbdpQ/A5ZXCYiUZ6qrbc/gkzxXLu2epUqpONZ7BFxEGoVztmFv6ZPM+vuHESsE/2 Bosw== X-Gm-Message-State: AOAM533dc16wGCzMP5Kol1DPXH6f0nEMD3NJ4BrN/WU9NkcbSooPJkBF f2CA8IgnmbYsA86UUKuiIF4SXEfHv/enKkwQG/WxERlMmc0= X-Google-Smtp-Source: ABdhPJyEPZaijah4Zd//jWwkK8T4vMkwvCCTHGqbq8ncbe1IyV0wDuhNqhjgRS3BwzgDwP29x36drchNKWA9B4jbYKI= X-Received: by 2002:a37:6f42:: with SMTP id k63mr20483250qkc.291.1610897629562; Sun, 17 Jan 2021 07:33:49 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Adam Dinwoodie Date: Sun, 17 Jan 2021 15:33:13 +0000 Message-ID: Subject: Re: GitHub automation for Cygwin builds [Was: Updated: moreutils v0.65-1] To: cygwin-apps@cygwin.com Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.8 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: cygwin-apps@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Cygwin package maintainer discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jan 2021 15:33:51 -0000 On Sat, 16 Jan 2021 at 22:31, Ken Brown wrote: > On 1/16/2021 3:33 PM, Adam Dinwoodie wrote: > > On Sat, 16 Jan 2021 at 20:22, Adam Dinwoodie wrote: > >> Version 0.65-1 of moreutils has been uploaded and should be coming > >> soon to a distribution server near you. > > > > In case anyone's interested or has thoughts: > > > > As part of working on this release, I've been playing with GitHub's > > automation tools. The entire build / test / package / release / upload > > process was performed using free ephemeral GitHub-managed VMs. At > > least in theory, this reduces the manual work for future releases to: > > > > - Commit a version of the Cygport file with an updated version number. > > - Create a tag and push that tag to GitHub > > - Wait for the confirmation email to arrive > > - Send the announcement email > > > > This is obviously serving a similar purpose to the automated builds > > that Scallywag provides; I'm not sure I'd have bothered with this > > project had I not already been most of the way through it before I > > spotted Scallywag existed. I suspect in theory Scallywag's access to > > the Cygwin servers means it's potentially more powerful, but Scallywag > > also comes with some general caveats ("at this stage, this is only > > probably useful for verifying that BUILD_REQUIRES is correct"), > > I assume you're quoting from https://cygwin.com/packaging/build.html. Scallywag > does have some limitations currently, but I think the statement you quoted is > obsolete. I often have Scallywag deploy my packages, as does Jon Turney. Yes, that was my source here. I experimented with Scallywag briefly, but was put off by (a) that warning and (b) the fact that my first builds failed because I apparently use the wrong quoting style in my Cygport files. And, as I say, that I was already a significant way to a working GitHub Action process. > The limitations I've bumped into are: > > 1. Scallywag will time out after an hour on each arch. This is a killer for me. Getting this working with moreutils was a simple proof-of-concept; the key package where this will likely save me time and energy is Git, and the Git test suite takes multiple hours to run on Cygwin. GitHub actions have a per-job limit of 6 hours, and a per-workflow limit of 72 hours. > 2. Several of my packages fail to build on x86 because of gcc crashes. > > I think these limitations are outweighed by the fact that a Scallywag build is > automatically triggered by a push to an official source repo > (https://cygwin.com/packaging/repos.html). All maintainers can use this without > any special setup. That's clearly incredibly valuable, yes. I'm hoping to reduce the special setup using GitHub Actions requires, but it's clearly going to require more than zero setup. Adam