Checking for problems before committing

[Brandon Allbery]

On Thu, Mar 10, 2016 at 1:48 AM, Mojca Miklavec <mojca at macports.org> wrote:

>
> When I was testing wxWidgets, discovered a problem and submitted a
> patch, I noticed what they are doing now (which is some light years
> more advanced compared to what they did a few years back when most of
> the tickets were stuck ignored at their Trac; similar to what happens
> in many cases in MacPorts).


Much of this now comes "for free" with github these days; just create a
data file in the repo with config information and add some "canned" commit
triggers. Apple/MacOSForge has the infrastructure but not the connections
you'd need to automate it quickly and cleanly.

(No, moving to github would not help us. They can build on El Cap only ---
and that service often simply disappears since Travis CI only offers the
free github service when they have spare capacity, and unlike the other
platforms they must use dedicated Apple hardware for the build slaves --
this due to Apple licensing. So there's a limited number of OS X
buildslaves, and if they're all in use for the commercial Travis customers
the free service on OS X gets dropped.)

-- 
brandon s allbery kf8nh                               sine nomine associates
allbery.b at gmail.com                                  ballbery at sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad        http://sinenomine.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20160310/b201f815/attachment-0001.html>