Date: Mon, 23 Sep 2019 15:31:33 +0200 From: =?UTF-8?Q?Bernhard_Fr=C3=B6hlich?= <decke@freebsd.org> To: Matthew Seaman <matthew@freebsd.org> Cc: FreeBSD Ports ML <freebsd-ports@freebsd.org> Subject: Re: Ansible playbooks for building a poudriere test system Message-ID: <CAE-m3X2S-JW3Hmt-=MKa%2Bgqnm55v9tMcXNv11qKDUfUDAr9f2g@mail.gmail.com> In-Reply-To: <db34a9aa-fd4a-0859-99ca-f23bec0b8826@FreeBSD.org> References: <db34a9aa-fd4a-0859-99ca-f23bec0b8826@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Sep 23, 2019 at 10:27 AM Matthew Seaman <matthew@freebsd.org> wrote: > > Hi, > > I put this together as the basis of the class I gave at EuroBSDCon a few > days ago, and I thought I'd share it as it might prove useful: > > https://github.com/infracaninophile/p4pm > > This should be able to take an 'as installed' FreeBSD machine with just > a local user account added, or the default config of a VM from AWS, > Azure etc. upto a fully configured poudriere build box. Currently it > sets up jails suitable for running build tests on updated ports, but > turning it into a system for managing a private ports repo should be > pretty simple. Sounds like a good base for caronade which would integrate with github and trigger the poudriere build. https://code.bluelife.at/decke/caronade -- Bernhard Froehlich http://www.bluelife.at/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAE-m3X2S-JW3Hmt-=MKa%2Bgqnm55v9tMcXNv11qKDUfUDAr9f2g>