From nobody Sat Nov 20 06:02:45 2021 X-Original-To: freebsd-git@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id F38021896711 for ; Sat, 20 Nov 2021 06:02:54 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ua1-x929.google.com (mail-ua1-x929.google.com [IPv6:2607:f8b0:4864:20::929]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Hx2y61MDMz4j2L for ; Sat, 20 Nov 2021 06:02:54 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-ua1-x929.google.com with SMTP id r15so25652181uao.3 for ; Fri, 19 Nov 2021 22:02:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=D0KHk+5bAr2HdDyV5oEM7uKVBSsYC/AXWBVXHk5nBq8=; b=Nm2kS9T2aO29RaEomsTGgtpwwPTZgsVtkHj9h+lTmxNo8O4k+HVkvwyLVIqhFZfzN8 c/Tvu9aG6LzXIP2zEh5i+aGGa5J2Qozl6uDH2a2vlmTywiOrNCJbU7LHm9npG0AP9m2M qqBLIGsDLuyFrrY0Rs5VmKJzBNvrQMxcQynm7f1NNKwZIwSD5CqzHB4GaWUjlGJ7xS42 Ayry2jRxlTMSv556GzcLBys5kLkUMaSk5IpLg8BIe3ECqoKng/t7nXMMJwDz4pmeoH6m 39HiaSunuJRGtEiPS+0BNvJ5r0aywi2DtukzFPWJCz2fm1csNiUTTNSc+qoUzpZfZSfZ qNXw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=D0KHk+5bAr2HdDyV5oEM7uKVBSsYC/AXWBVXHk5nBq8=; b=iHSpHUOG/rpR1Ff40AYD3xiVW29QhXLUCjLSRokFeuBrWmJtRhFhok5im6S3E8imvg EAxveNtX2BoK/C04Z1CJLYFjue5NA5xDBAUf+2GcabSj0JQ5vSGSSRBEE989GtlVPxvz rFP3g6PII/Fc3XtDWW9R4PhdkJ0Hc+L4Xj6tT2Ux22ooszq4K1QB5We9tRQlehMhqXCI SIHcayEiYY9WVaT5IYed17e4oVw9UkU8BMnq+d9w40nWpHoVnLRbE6sT9BttWsRoJP3m hCwRCGPtpX0sOshEgTfi/x4Xz+VvYx0DQY35JB9xLfDO1+4nQ1OCnRh4lUioGcPZrReW N/Vg== X-Gm-Message-State: AOAM5328oUY4PQvio5cW8zNPT2ASNNvxwNz/MAYJWm18h53XGPNcDRM5 8zHtajcXtVI+sUGWbnkru1siMIhupm1Q2NMTYfgu3ovnrOpPbA== X-Google-Smtp-Source: ABdhPJwUOTjOGOp5I+4BBNerkhkILkJdvsYwAlETD8t8f2UdYp7Vpf2yvUZdOO5zBjWwqrWmkFDeN8FpYO/Mgrt4hgU= X-Received: by 2002:a05:6102:d94:: with SMTP id d20mr105390839vst.12.1637388173627; Fri, 19 Nov 2021 22:02:53 -0800 (PST) List-Id: Discussion of git use in the FreeBSD project List-Archive: https://lists.freebsd.org/archives/freebsd-git List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-git@freebsd.org MIME-Version: 1.0 References: <6e72c7e11f43c844f44b343f3aadf040@gundo.com> In-Reply-To: <6e72c7e11f43c844f44b343f3aadf040@gundo.com> From: Warner Losh Date: Fri, 19 Nov 2021 23:02:45 -0700 Message-ID: Subject: Re: CI Piplines To: Pau Amma Cc: freebsd-git Content-Type: multipart/alternative; boundary="00000000000072e48a05d1322496" X-Rspamd-Queue-Id: 4Hx2y61MDMz4j2L X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20210112.gappssmtp.com header.s=20210112 header.b=Nm2kS9T2; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::929) smtp.mailfrom=wlosh@bsdimp.com X-Spamd-Result: default: False [1.04 / 15.00]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20210112.gappssmtp.com:s=20210112]; FROM_HAS_DN(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-git@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; NEURAL_SPAM_MEDIUM(1.00)[1.000]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20210112.gappssmtp.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::929:from]; NEURAL_HAM_SHORT(-0.96)[-0.960]; NEURAL_SPAM_LONG(1.00)[1.000]; R_SPF_NA(0.00)[no SPF record]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: Y --00000000000072e48a05d1322496 Content-Type: text/plain; charset="UTF-8" Sorry for my delay in replying... I've been extra busy at work... On Sat, Nov 13, 2021 at 12:16 PM Pau Amma wrote: > On 2021-11-12 21:24, Warner Losh wrote: > > The weekly meetings haven't been as productive as I'd have liked them > > to > > be. That tells me I need to try something else. That's another reason I > > skipped this week, but I'm planning on having one next week at the 1pm > > MST > > time slot (UTC 20:00). More details by Monday. > > I welcome this use of the mailing list as a medium for discussion, and I > hope it becomes the primary, and who knows maybe the only medium, since, > in addition to working across timezones and sleep cycles, it would > enable me to take part in discussions equally. (And before anyone trots > out that trope again, let me repeat: I am talking about ability to take > part at all, not taste or preference.) > Understood. > > First up on that list is before the commit testing. We can do a lot > > more. I > > have done work with other projects that have setup sophisticated > > pipelines > > to ensure that nothing is broken. We have a couple of github and Cirrus > > CI > > jobs defined in the tree for smoke testing, but it would be nice to > > have > > more. > > I had a look at https://github.com/freebsd/freebsd-ci/tree/master/jobs > and although I don't understand most of it, there seems to be 2 pieces > related to docs with different tests being run, FreeBSD-doc-main and > phabric-FreeBSD-doc-main. However, I haven't seen, in the nearly 2 years > since I've had a phabricator account, any evidence that uploading doc > diffs to it for review will trigger CI actions. > There's currently no triggers configured in phabricator to trigger a Jenkins run. All the Jenkins runs are done after the fact to ensure that the docs tree continues to build. > It would be nice IMO to have something that upon submitting or updating > a phabricator doc review (or maybe even before that, eg when committing > to a documenter's local git clone) would do some or all of: > - checking for AsciiDoc markup errors > - checking for bad link targets > - optionally, based on individual preferences and document language, > checking spelling > - rendering, at least to HTML > - checking the result against accessibility guidelines (ideally, this > would use the AsciiDoc source for ease of interpretation and correction > of problems, but most accessibility checkers I know of only deal with > HTML, and some checks, like color and contrast, are only possible when > HTML and CSS are both available) > - reporting to the author in near real-time (an email within a few > minutes would probably be enough) > > I don't know, however, whether that would take phabricator action, CI > action, or both. > Phabricator has the ability to kick off Jenkins runs. https://github.com/uber/phabricator-jenkins-plugin has what looks like the necessary plugin. And https://www.linkedin.com/pulse/using-phabricator-jenkins-git-continuous-automated-pre-commit-tayal has a walkthrough of setting it up. Would you be able to look into what it would take to apply those instructions to our phabricator setup? We have a 'test' phabricator setup that I think you can get access to if you wanted to try to do all the things listed above. Warner --00000000000072e48a05d1322496--