public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: Mark Wielaard <mark@klomp.org>
Cc: Overseers mailing list <overseers@sourceware.org>
Subject: Re: [PATCH] buildbot: come up with vm_workers variable
Date: Thu, 26 May 2022 10:40:56 +0200	[thread overview]
Message-ID: <745ec640-0335-9ba8-5605-6c5f2578d551@suse.cz> (raw)
In-Reply-To: <Yo6eoBx7zG5OrrrO@wildebeest.org>

On 5/25/22 23:24, Mark Wielaard wrote:
> Hi Martin,
> 
> On Wed, May 25, 2022 at 10:00:09PM +0200, Martin Liška wrote:
>> Btw. can one somehow run the master.cfg validation locally?
> 
> Yes! And it is even documented in the README:
> 
> = Local hacking
> 
> buildbot runs in a python virtual environment that can be replicated
> locally:
> 
> - python3 -m venv buildbot-env
> - source buildbot-env/bin/activate
> - python3 -m pip install -r buildbot.requirements
> 
> [ ... ]
> 
> Create a local buildbot-master:
> 
> - buildbot create-master builder
> 
> You will also need a ~/buildbot.config file which contains the
> passwords for workers and users. You can use the
> buildbot.config.sample file for that. DO NOT USE AS IS! Change the
> password 'frob' to something real so local users and workers cannot
> connect to your local buildbot (if there are other local users and/or
> no firewall).
> 
> Now after changing master.cfg you can run:
> 
> - buildbot checkconfig builder

Works for me, thanks for sharing the knowledge.

Cheers,
Martin

> 
> Cheers,
> 
> Mark
> 


      reply	other threads:[~2022-05-26  8:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-25 12:55 Martin Liška
2022-05-25 14:46 ` Mark Wielaard
2022-05-25 20:00   ` Martin Liška
2022-05-25 21:24     ` Mark Wielaard
2022-05-26  8:40       ` Martin Liška [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=745ec640-0335-9ba8-5605-6c5f2578d551@suse.cz \
    --to=mliska@suse.cz \
    --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).