From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Mark Wielaard <mjw@gnu.org>
Cc: libc-alpha@sourceware.org, DJ Delorie <dj@redhat.com>,
Carlos O'Donell <carlos@redhat.com>
Subject: Re: patchwork upgrade week
Date: Thu, 23 Jun 2022 07:46:18 +0530 [thread overview]
Message-ID: <551277bc-975d-0b2e-670b-679db68e604b@gotplt.org> (raw)
In-Reply-To: <YrOJWSiIyV5+BYuN@wildebeest.org>
On 23/06/2022 02:57, Mark Wielaard wrote:
> So I was hoping to integrate the buildbot with the patchwork based
> trybot. But it would be good to have some way to authenticate the
> patch as genuine before throwing it at the buildbot-worker. I was
> hoping that could be done by a project admin setting the state of the
> patch to some "please-try" value. But it looks like a (rogue) user can
> set the state on their own patch. So relying on the patchwork patch
> state seems not secure.
>
> Or is there a state (maybe a check state?) that we can make sure can
> only be set by project admins?
>
> If not, how else can we authenticate a patch as "OK to let the
> buildbot do a try build?"
DJ is working on an email based workflow. Another method (that Frank
proposed on IRC recently) could be for a trybot to track namespace
branches for all committers on sourceware and trigger builds on specific
names, e.g. siddhesh/buildbot/*. That way maintainers can manually
trigger builds by pushing their changes to that specific branch namespace.
Sid
next prev parent reply other threads:[~2022-06-23 2:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 10:26 Siddhesh Poyarekar
2022-06-22 6:53 ` Siddhesh Poyarekar
2022-06-22 21:27 ` Mark Wielaard
2022-06-23 2:16 ` Siddhesh Poyarekar [this message]
2022-06-23 7:55 ` Mark Wielaard
2022-06-23 8:39 ` Siddhesh Poyarekar
2022-06-27 17:23 ` DJ Delorie
2022-07-01 11:04 ` Mark Wielaard
2022-07-01 21:01 ` DJ Delorie
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=551277bc-975d-0b2e-670b-679db68e604b@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=carlos@redhat.com \
--cc=dj@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=mjw@gnu.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).