El Capitan Buildbot

[Joshua Root]

On 2015-8-18 00:23 , Arno Hautala wrote:
> On Mon, Aug 17, 2015 at 5:03 AM, Mojca Miklavec <mojca at macports.org> wrote:
>> I don't want to be pessimistic, but I will be enormously happy if
>> we'll get the buildbot up and running at all.
>> Given how long the 10.6 and 10.7 buildbots have been broken ...
>>
>> And yes, it would make a lot of sense to start the process now if
>> there is anyone at Apple who is willing and able to look into it.
> 
> Given the time it's taken in the past to get a build slave set up and
> the difficulty with fixing errors when is it worthwhile to start
> looking at setting up a slave that's under closer control?
> This could run the gamut from a hosted VM to a spare machine that
> someone is willing to keep in a closet.

Running your own buildbot instance purely for CI testing purposes is
fine. But...

> I already archive all my packages on a home NAS and, if everyone was
> trusted on the Internet, MacPorts could just accept package uploads
> from anyone to be shared to all. Conceptually, there's no real
> difference with any of the committers (maybe just the management team
> or elder council) being able to share packages and someone from the
> team being able to configure the official build slave.

Our hosting is pretty tightly configured such that packages.macports.org
won't accept uploads from outside the Apple firewall (or even the
macosforge VLAN). That probably won't change purely due to Apple infosec
policies, but also shouldn't change just yet because buildbot (at least
the version we're currently using) doesn't have the ability to use TLS
when uploading files from the slaves to the master.

> I suppose I'd be personally happy just running a VM slave on my NAS.
> Though that doesn't contribute anything to anyone else and not
> everyone has the means to host their own buildbot. Are the buildbots
> just using MPAB?

Yes, this is the config:
<https://trac.macports.org/browser/contrib/buildbot>

Technically, if you hosted your archives somewhere publicly accessible,
signed them, and published the public key, others could decide that they
trust you, and add the URL to their archive_sites.conf and the key to
their pubkeys.conf.

- Josh