public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Marco Atzeri <marco.atzeri@gmail.com>,
	"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: disk space limit of scallywag ?
Date: Mon, 13 Mar 2023 14:33:51 +0000	[thread overview]
Message-ID: <ef5338a5-7ebd-e786-73d7-cd3fdd374b66@dronecode.org.uk> (raw)
In-Reply-To: <101f788b-d5b2-3b54-81c2-3354e4e3e5f8@gmail.com>

On 12/03/2023 22:27, Marco Atzeri via Cygwin-apps wrote:
> 
> Hi Jon,
> will be possible to pass the token notest to the sub-command rerun ?
> For the time being I used SCALLYWEG="notest"

Yes, e.g. 'jobs rerun --token notest 5594'

Unfortunately, this can run into well known ssh quotation difficulties 
when you want to specify multiple space separated tokens (as the command 
is evaluated by the local shell and the the remote shell), so maybe 
needs some improvement...

(I think maybe something like ssh cygwin@cygwin.com "jobs rerun --token 
'notest label' 5594" works, but I haven't tested it...)

> PS: there is a mismatch in the documentation
> 
> subcommands:
>    {cancel,deploy,help,rerun}
>      cancel              cancel job
>      deploy              deploy job
>      help                this help
>      rerun               re-run job
> 
> While on the web:
> 
> rebuild
> rebuild a job (e.g. if it failed due to some transient condition, or 
> optionally with different tokens).

Thanks for pointing this out. I fixed the documentation.


      reply	other threads:[~2023-03-13 14:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-12 17:08 Marco Atzeri
2023-03-12 17:30 ` Brian Inglis
2023-03-12 17:39 ` Jon Turney
2023-03-12 20:33   ` Marco Atzeri
2023-03-12 21:00     ` Jon Turney
2023-03-12 22:27       ` Marco Atzeri
2023-03-13 14:33         ` Jon Turney [this message]

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=ef5338a5-7ebd-e786-73d7-cd3fdd374b66@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-apps@cygwin.com \
    --cc=marco.atzeri@gmail.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).