From: Jakub Jelinek <jakub@redhat.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Florian Weimer <fweimer@redhat.com>,
"Carlos O'Donell via Libc-alpha" <libc-alpha@sourceware.org>,
"Carlos O'Donell" <carlos@redhat.com>,
Joseph Myers <joseph@codesourcery.com>,
"Ryan S. Arnold" <ryan.arnold@gmail.com>,
Paul Eggert <eggert@cs.ucla.edu>,
Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>,
Andreas Schwab <schwab@suse.de>
Subject: Re: Core Toolchain Infrastructure - Services for glibc
Date: Tue, 18 Jul 2023 14:26:44 +0200 [thread overview]
Message-ID: <ZLaFBGygP/n+uFY9@tucnak> (raw)
In-Reply-To: <2b743481-4dc3-07a1-fe65-a32a9d1df09a@gotplt.org>
On Tue, Jul 18, 2023 at 07:47:37AM -0400, Siddhesh Poyarekar wrote:
> On 2023-07-14 11:34, Konstantin Ryabitsev via Libc-alpha wrote:
> > > Can we keep using the AdaCore hooks? Or would they have to run on the
> > > side somehow? Who is going to implement changes to the AdaCore scripts?
> >
> > This is the main point of contemplation -- we do not currently support custom
> > hooks on the server side:
> >
> > - they tend to significantly slow down pushes
> > - they run extensive codebases with the same permissions as the owner of the
> > repositories, significantly increasing security risks
> >
> > Our recommendation was to move all CI tasks to a system that is better suited
> > for it. For example, CI can run on a patchwork system and the pre-commit hook
> > can then check that each commit matches a patchwork entry that passed CI.
>
> This would mean porting AdaCore hooks to a patchwork trybot. This would be
> an acceptable solution for glibc, but I'm not sure how useful this would be
> on the whole since gcc doesn't use patchwork as extensively at the moment.
> Also, we need to figure out who's going to do this.
It is definitely not acceptable for gcc, we strongly rely on server side
pre-commit hooks for various different tasks.
Jakub
next prev parent reply other threads:[~2023-07-18 12:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 21:58 Carlos O'Donell
2023-07-14 11:38 ` Florian Weimer
2023-07-14 15:34 ` Konstantin Ryabitsev
2023-07-18 11:47 ` Siddhesh Poyarekar
2023-07-18 12:26 ` Jakub Jelinek [this message]
2023-07-18 13:19 ` Jeff Law
2023-07-18 13:24 ` Siddhesh Poyarekar
2023-07-20 17:43 ` Joseph Myers
2023-07-18 13:38 ` Konstantin Ryabitsev
2023-08-03 10:10 ` Florian Weimer
2023-07-14 15:58 ` Mark Wielaard
2023-08-22 15:53 ` Frank Ch. Eigler
2023-08-23 7:57 ` Sourceware Infrastructure " Mark Wielaard
2023-08-29 20:45 ` Core Toolchain Infrastructure - " Carlos O'Donell
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=ZLaFBGygP/n+uFY9@tucnak \
--to=jakub@redhat.com \
--cc=carlos@redhat.com \
--cc=eggert@cs.ucla.edu \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=konstantin@linuxfoundation.org \
--cc=libc-alpha@sourceware.org \
--cc=maxim.kuvyrkov@linaro.org \
--cc=ryan.arnold@gmail.com \
--cc=schwab@suse.de \
--cc=siddhesh@gotplt.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 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).