<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
I have a small stack of Mac Minis I got to use as a buildbot farm
for Octave.app; I might be able to have them pull double duty for
MacPorts depending on your change volume.<br>
<br>
Cheers,<br>
Andrew<br>
<br>
<div class="moz-cite-prefix">On 5/19/21 1:16 PM, Mark Anderson
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CACahOHQ7P3wJBB+xX46k0oLobuGMPdmFzLX6FVzipSTU9i08UQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>Yeah - we are certainly short staffed everywhere - I try to
add more and more of my time to the project but aside from my
ports, I'm still in learning mode digging through all the
asciidoc and tcl and everything. I'm trying to build some
tools to help me, but again, more time.</div>
<div><br>
</div>
<div>Once we move to the latest build bot, we might want to see
if we can get other volunteers to host some hardware, but the
problem is, we're going to have to hit up ebay or something
and the infrastructure will be tougher.</div>
<div><br>
</div>
<div>I'm honestly not sure how we can manage to staff up more at
all - I mean this is a FOSS problem all over for non-company
sponsored projects.</div>
<div><br>
</div>
<div>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">
<div>—Mark<br>
</div>
<div>_______________________<br>
Mark E. Anderson <<a href="mailto:mark@macports.org"
target="_blank" moz-do-not-send="true">mark@macports.org</a>><br>
</div>
<div><a href="https://trac.macports.org/wiki/mark"
target="_blank" moz-do-not-send="true">MacPorts Trac
WikiPage</a><br>
</div>
<div><a href="https://github.com/markemer" target="_blank"
moz-do-not-send="true">GitHub Profile</a><br>
</div>
<div><br>
</div>
</div>
</div>
</div>
<br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, May 18, 2021 at 2:35
AM Ryan Schmidt <<a href="mailto:ryandesign@macports.org"
moz-do-not-send="true">ryandesign@macports.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">MacPorts
is short-staffed in all areas, not just infrastructure.<br>
<br>
Our Buildbot system works. It produces all the binaries we are
able to.<br>
<br>
Our buildbot system was already substantially redesigned when
we took it over from Apple in 2016 and will be substantially
redesigned again as we upgrade to the latest version of the
buildbot software.<br>
<br>
We already have a small infrastructure team who are interested
in working on improving the buildbot system and our other
infrastructure, and do so.<br>
<br>
We already use GitHub Actions for CI. We cannot use it to
replace buildbot because it only offers recent OS versions and
because it does not offer persistent machines.<br>
<br>
I personally am not comfortable adding other build machines to
our buildbot system that I do not control. When I control the
machines, I know what is installed on them and that they are
set up correctly. Having build machines located outside of my
local network also poses additional challenges, as I've
learned by having our Apple Silicon build machine outside of
my network, challenges which I would prefer to minimize, not
increase.<br>
<br>
We currently use one build machine per OS version / arch, and
have the hardware needed to do that. Adding more hardware such
that we have more than one build machine per OS version / arch
is not something our buildbot system was ever designed to
accommodate, and would introduce problems.<br>
<br>
Using Linux and commodity hardware is not applicable because
it the macOS EULA only permits running macOS on Apple
hardware, as we currently do.</blockquote>
</div>
</blockquote>
<br>
</body>
</html>