git repositories for cygwin packaging - please test

Brian Inglis
Wed Jun 23 04:22:58 GMT 2021

On 2021-06-22 13: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]
>>> 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]
> 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=<token>'.
>>> Currently, these packages are built using 'cygport all-test', and so 
>>> will always be marked test:

Nit: shouldn't the default value be documented as:

	The default *!scallywag* value is /build test nodeploy/.

Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

More information about the Cygwin-apps mailing list