From: Junio C Hamano <gitster@pobox.com>
To: Chris Torek <chris.torek@gmail.com>
Cc: Haritha D <Harithamma.D@ibm.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Clarification on GPG preference update prompts during Git test suite execution
Date: Wed, 04 Jun 2025 09:20:28 -0700 [thread overview]
Message-ID: <xmqqtt4vbhrn.fsf@gitster.g> (raw)
In-Reply-To: <CAPx1Gvd9pUbfyq_AuQmqTqNY=mB+=agoreKR5DfphNNgc8md6A@mail.gmail.com> (Chris Torek's message of "Wed, 4 Jun 2025 04:13:58 -0700")
Chris Torek <chris.torek@gmail.com> writes:
> On Wed, Jun 4, 2025 at 2:39 AM Haritha D <Harithamma.D@ibm.com> wrote:
>> I noticed that the ci/run-build-and-tests.sh script in the Git repo does not seem to explicitly handle this scenario (e.g., no --batch, --yes, or other flags related to GPG). I’m curious—how does Git's CI/CD pipeline avoid or suppress these GPG interactive prompts during test execution?
>
> GPG does not go through Git. GPG uses the "grab hold of the user who's
> watching this and ask a question" interface provided by the operating
> system. CI systems disable this interface (or do their best to attempt
> to do so) since there is no user watching.
>
> Since Git is not involved here, Git has no control over this. You need
> to deal with this at the GPG level (or use the same tricks that CI
> systems use, but those are considerably more complex, and
> OS-dependent).
We do redirect our stdin to read from /dev/null but that is the
extent we attempt to go non-interactive while running the tests,
which, as you said, is insufficient to defeat applications opening
up /dev/tty or going GUI.
prev parent reply other threads:[~2025-06-04 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 9:39 Clarification on GPG preference update prompts during Git test suite execution Haritha D
2025-06-04 11:13 ` Chris Torek
2025-06-04 16:20 ` Junio C Hamano [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=xmqqtt4vbhrn.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Harithamma.D@ibm.com \
--cc=chris.torek@gmail.com \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.