On Mar 13, 2018, at 09:50, Mojca Miklavec wrote:
> Dear Ryan,
>
> Please take a look at the discussion summary we just had at the meeting:
>
> https://trac.macports.org/wiki/Meetings/MacPortsMeeting2018/BuildbotRestructuring
So...
> Ryan's proposal
>
> Ryan asked us to get rid of the
Dear Ryan,
Please take a look at the discussion summary we just had at the meeting:
https://trac.macports.org/wiki/Meetings/MacPortsMeeting2018/BuildbotRestructuring
Regarding emails: we figured out that it makes no sense to make our
design decisions based on how annoying it would be to write
On Mar 11, 2018, at 17:48, Rainer Müller wrote:
> On 2018-03-11 10:25, Ryan Schmidt wrote:
>> The current buildbot setup has a number of problems that I believe could be
>> solved by combining the currently separate portwatcher and portbuilder
>> schedulers into a single ports scheduler.
>>
>>
On 2018-03-11 10:25, Ryan Schmidt wrote:
> The current buildbot setup has a number of problems that I believe could be
> solved by combining the currently separate portwatcher and portbuilder
> schedulers into a single ports scheduler.
>
> I am not suggesting that we return to the behavior of
Dear Ryan,
Conceptually I like the approach a lot.
*However*, this will generate an incomprehensible amount of emails
when a new build slave gets added or when some revbumps are done etc.
In particular from the 10.5/ppc machine. The individual emails will be
a lot more helpful, but the amount of
The current buildbot setup has a number of problems that I believe could be
solved by combining the currently separate portwatcher and portbuilder
schedulers into a single ports scheduler.
I am not suggesting that we return to the behavior of the ports scheduler on
the old macOS forge buildbot
