Travis CI timeouts for MacPorts builds

[Ruben Di Battista]

I was wondering... Would à Linux machine with some virtualization method
(libvirt?) be acceptable as CI runner? Any of you has experience in terms
of performance?

Also, Gitlab CI allows to attach personal runners to project very easily
(just a package to install from the os package manager) . How does it work
for Github?

On Mon, 7 Sep 2020, 15:50 Mojca Miklavec, <mojca at macports.org> wrote:

> On Mon, 7 Sep 2020 at 10:46, Ralph Seichter wrote:
> >
> > I fail to remember the last time one of my builds successfully passed
> > Travis CI. All I see are timeouts [1]. Other peoples' jobs apparently
> > make it through Travis OK, so I wander what I can do to increase my
> > chances?
>
> By far the best thing would be to implement the functionality that
> would allow firing up a clean VM, do the build, close the VM & destroy
> it, and run this on our own buildbot workers.
>
> This requires both manpower to implement the functionality as well as
> additional hardware resources to run the builds.
> If we solve the first part, I guess we should be able to solve the
> second one as well.
> If you volunteer to do some research / work in this area ... that
> would likely be the most significant step in "increasing your chances"
> ... probably up to 100% for the ports that have no chance in building
> in < 50 minutes on a super slow hardware owned by Travis :)
>
> Mojca
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20200907/4398c622/attachment.htm>