From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: git repositories for cygwin packaging - please test
Date: Sat, 18 Feb 2023 12:43:00 -0500 [thread overview]
Message-ID: <a27b9406-dcf3-f2b0-aa8e-8b4b10c703b2@cornell.edu> (raw)
In-Reply-To: <dda84a7b-ccf1-f163-02b2-76040922e929@dronecode.org.uk>
On 2/18/2023 11:21 AM, Jon Turney via Cygwin-apps wrote:
> 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=<token>'.
>>>
>>>>> 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'.
Thanks!
> 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)
I assume we would specify the job id after the cancel or deploy command?
> rebuild (rebuild a job if it failed due to some transient condition, or
> optionally with different token options)
For the second case, would we specify the new tokens on the command
line? After the job id?
Ken
next prev parent reply other threads:[~2023-02-18 17:43 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-04 20:08 Jon Turney
2019-08-05 2:03 ` Ken Brown
2019-08-08 13:47 ` Andrew Schulman via cygwin-apps
2019-08-08 14:04 ` Andrew Schulman via cygwin-apps
2019-08-08 17:09 ` Ken Brown
2019-08-09 16:12 ` Jon Turney
2019-08-09 19:12 ` Ken Brown
2019-08-13 11:55 ` Jon Turney
2019-08-09 16:00 ` Jon Turney
2019-08-09 20:58 ` Brian Inglis
2019-08-13 11:55 ` Jon Turney
2019-08-19 18:36 ` Achim Gratz
2020-05-27 22:27 ` Jon Turney
2020-05-28 11:51 ` szgyg
2020-06-04 16:01 ` Ken Brown
2020-06-04 20:33 ` Brian Inglis
2020-06-09 13:26 ` Jon Turney
2020-06-09 22:44 ` Brian Inglis
2020-08-06 20:20 ` Jon Turney
2020-08-06 21:04 ` Ken Brown
2020-08-07 19:42 ` Achim Gratz
2020-08-07 22:05 ` Ken Brown
2020-08-08 4:26 ` ASSI
2020-08-16 18:05 ` Jon Turney
2020-08-23 21:01 ` Jon Turney
2020-08-26 22:00 ` Ken Brown
2020-08-30 15:00 ` Jon Turney
2020-08-30 15:22 ` Ken Brown
2020-08-30 15:46 ` Jon Turney
2020-08-30 17:25 ` Ken Brown
2020-08-30 20:06 ` Jon Turney
2020-11-12 21:30 ` Jon Turney
2020-08-30 16:44 ` ASSI
2020-08-30 20:08 ` Jon Turney
2020-10-04 10:26 ` Achim Gratz
2020-10-25 18:10 ` Jon Turney
2021-05-09 14:39 ` Jon Turney
2021-06-22 19:52 ` Jon Turney
2021-06-23 4:22 ` Brian Inglis
2022-07-05 13:12 ` Jon Turney
2023-02-18 16:21 ` Jon Turney
2023-02-18 17:43 ` Ken Brown [this message]
2023-02-18 18:40 ` Jon Turney
2020-11-16 21:54 ` Brian Inglis
2020-11-16 22:16 ` Jon Turney
2020-11-16 22:54 ` Brian Inglis
2020-11-17 19:21 ` Achim Gratz
2020-05-29 14:40 ` Alexey Sokolov
2020-06-07 15:06 ` Hamish McIntyre-Bhatty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a27b9406-dcf3-f2b0-aa8e-8b4b10c703b2@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).