From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from re-prd-fep-044.btinternet.com (mailomta6-re.btinternet.com [213.120.69.99]) by sourceware.org (Postfix) with ESMTPS id 005D33858D32 for ; Sat, 18 Feb 2023 16:21:40 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 005D33858D32 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=dronecode.org.uk Authentication-Results: sourceware.org; spf=none smtp.mailfrom=dronecode.org.uk Received: from re-prd-rgout-005.btmx-prd.synchronoss.net ([10.2.54.8]) by re-prd-fep-044.btinternet.com with ESMTP id <20230218162139.WQWW11053.re-prd-fep-044.btinternet.com@re-prd-rgout-005.btmx-prd.synchronoss.net> for ; Sat, 18 Feb 2023 16:21:39 +0000 Authentication-Results: btinternet.com; auth=pass (PLAIN) smtp.auth=jonturney@btinternet.com; bimi=skipped X-SNCR-Rigid: 613A91244F064B0E X-Originating-IP: [81.153.98.246] X-OWM-Source-IP: 81.153.98.246 (GB) X-OWM-Env-Sender: jonturney@btinternet.com X-VadeSecure-score: verdict=clean score=0/300, class=clean X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgedvhedrudejuddgkeehucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuueftkffvkffujffvgffngfevqffopdfqfgfvnecuuegrihhlohhuthemuceftddunecunecujfgurhepkfffgggfuffvfhfhjggtgfesthejredttdefjeenucfhrhhomheplfhonhcuvfhurhhnvgihuceojhhonhdrthhurhhnvgihsegurhhonhgvtghouggvrdhorhhgrdhukheqnecuggftrfgrthhtvghrnhepheduueevueejueejgeeufeehtddtkeevtdduieelfeetteeffeejjedukeefgffgnecuffhomhgrihhnpegthihgfihinhdrtghomhenucfkphepkedurdduheefrdelkedrvdegieenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhephhgvlhhopegludelvddrudeikedruddruddtiegnpdhinhgvthepkedurdduheefrdelkedrvdegiedpmhgrihhlfhhrohhmpehjohhnrdhtuhhrnhgvhiesughrohhnvggtohguvgdrohhrghdruhhkpdhnsggprhgtphhtthhopedupdhrtghpthhtoheptgihghifihhnqdgrphhpshestgihghifihhnrdgtohhm X-RazorGate-Vade-Verdict: clean 0 X-RazorGate-Vade-Classification: clean Received: from [192.168.1.106] (81.153.98.246) by re-prd-rgout-005.btmx-prd.synchronoss.net (5.8.716.04) (authenticated as jonturney@btinternet.com) id 613A91244F064B0E for cygwin-apps@cygwin.com; Sat, 18 Feb 2023 16:21:39 +0000 Message-ID: Date: Sat, 18 Feb 2023 16:21:36 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: git repositories for cygwin packaging - please test To: "cygwin-apps@cygwin.com" References: <20e2f046-af24-14b8-b6c4-263f859042b8@dronecode.org.uk> <181ea3fa-1a50-7db4-0009-47ea9af77cdc@dronecode.org.uk> <5ff5073b-03a7-95e5-6d8b-fbd6436fe1c4@dronecode.org.uk> <7dc70a3b-d3bd-d9a7-7c02-05e1eb1aef7e@dronecode.org.uk> <28908241-9144-d7d0-41d3-828b14cae613@dronecode.org.uk> Content-Language: en-GB From: Jon Turney In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1191.3 required=5.0 tests=BAYES_00,FORGED_SPF_HELO,KAM_DMARC_STATUS,KAM_LAZY_DOMAIN_SECURITY,NICE_REPLY_A,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_NONE,TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On 05/07/2022 14:12, Jon Turney wrote: > On 22/06/2021 20:52, Jon Turney wrote: >> On 09/05/2021 15:39, Jon Turney wrote: >>> On 23/08/2020 22:01, Jon Turney wrote: >>>> On 27/05/2020 23:27, Jon Turney wrote: >>>>> On 04/08/2019 21:08, Jon Turney wrote: >>>>>> To remedy this lack, using the same ssh key you use for sftp >>>>>> package upload, package maintainers can now also push to git >>>>>> repositories, like so: >>>>> >>>>> Package maintainers may have noticed that the output from pushing >>>>> to these git repositories now includes a line like: >>>>> >>>>> "remote: scallywag: build nnn queued" >>>>> >>>>> This is a *prototype* of a system to automatically build the >>>>> packages, where the results appear (some time later) at [1] (URL >>>>> subject to change) >>>>> >>>>> [1] https://cygwin.com/cgi-bin2/jobs.cgi >>>>> >>>> I now have built an (opt-in) system which fetches the packages built >>>> by this into your upload area and triggers calm to process them, >>>> which I'm looking for a volunteer to test. >>> >>> Since that seems to be working about as well as can be expected, I've >>> bodged together something so maintainers can now opt themselves in >>> (and out) of this, by uploading (or removing) a file called >>> '!scallywag' containing 'deploy' in the root of their upload area. >>> >>> I've updated the brief documentation at [1] to mention this. >>> >>> [1] https://cygwin.com/packaging/build.html >> >> I've updated that page to document the fact that the behaviour for an >> individual push can now be controlled with 'git push >> --push-option='. >> >>>> Currently, these packages are built using 'cygport all-test', and so >>>> will always be marked test: > > Since my concerns about this producing horribly broken packages seem to > be moot, I've changed the default so this now produces stable packages > (i.e. uses 'cygport all' rather than 'cygport all-test''). > > You can request the previous behaviour of labelling as test using the > token 'label'. You can now interact with your build jobs in some ways which require authentication using 'ssh cygwin@cygwin.com jobs'. Currently, available sub-commands are: cancel (request termination of an unwanted build job) deploy (get a job to deploy (if it's suitable: i.e. successfully built, from master, etc.) (e.g. if you forgot to set the deploy option before hand) rebuild (rebuild a job if it failed due to some transient condition, or optionally with different token options) I've updated the brief documentation at [1] to mention this. [1] https://cygwin.com/packaging/build.html