git repositories for cygwin packaging - please test
Mon Nov 16 22:16:02 GMT 2020
On 16/11/2020 21:54, Brian Inglis wrote:
> On 2020-05-27 16: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  (URL subject to change)
>>  https://cygwin.com/cgi-bin2/jobs.cgi
>> To allow experimentation without messing up the version history
>> - All package repositories allow the maintainer(s) to create, push,
>> rewind and delete a branch named 'playground'.
>> - An additional package repository called 'playground' exists, that
>> all maintainers can do anything to.
> Could anyone please check and advise if the attached .git/config will
> allow me to push to the playground repo and later branch for testing, or
> demo the appropriate .git/config entries or git config commands to do so
To push to the playground repo, I generally just use 'git push
The URLs in that config don't look quite right, since they seem to have
hostname of just 'cygwin'?
> Is there any way to move tags to a later commit once pushed?
> I have one in wget that can't be deleted or forced because of the hook
tags don't have any particular significance, at the moment.
I removed the wget '1.20.3-2' tag for you.
> Finally are there other CI jobs.cgi?params=... other than id, e.g.
Not at this time. I agree it would be nice if you could filter by the
The jobs.cgi script script is tiny (see ), if you want to make
More information about the Cygwin-apps