public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Jose E. Marchesi" <jemarch@gnu.org>
To: Mark Wielaard <mark@klomp.org>
Cc: Overseers mailing list <overseers@sourceware.org>
Subject: Re: poke and autobuilder
Date: Fri, 18 Nov 2022 19:02:18 +0100	[thread overview]
Message-ID: <87iljc9m51.fsf@gnu.org> (raw)
In-Reply-To: <edb86194c78bf2929251755e8ac00878b36d3de9.camel@klomp.org> (Mark Wielaard's message of "Fri, 18 Nov 2022 18:50:42 +0100")


> On Fri, 2022-11-18 at 17:30 +0100, Jose E. Marchesi via Overseers
> wrote:
>> Currently we are using the CI facilities at gitlab for GNU poke.
>> However, it seems we keep running out of tokens/cycles/whatever every
>> month.
>> 
>> We would like to explore the possibility of using the sourceware
>> builder
>> for poke?  Note the sources are hosted in savannah (like many other
>> GNU
>> programs) git://git.savannah.gnu.org/poke.git.
>> 
>> What would we need to do?
>
> Join the builder project :)
>
> git clone https://sourceware.org/git/builder.git
>
> Read the README part about "How to add a new project"
>
> Either know python enough to prepare a perfect patch following that
> guide and sent it to buildbot@sourceware.org
> Or almost get what is needed and provide some details to the
> mailinglist asking if someone could turn that into valid python.
>
> https://sourceware.org/mailman/listinfo/buildbot

Will do, thanks.

      reply	other threads:[~2022-11-18 17:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18 16:30 Jose E. Marchesi
2022-11-18 17:50 ` Mark Wielaard
2022-11-18 18:02   ` Jose E. Marchesi [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=87iljc9m51.fsf@gnu.org \
    --to=jemarch@gnu.org \
    --cc=mark@klomp.org \
    --cc=overseers@sourceware.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).