Travis CI timeouts for MacPorts builds

Clemens Lang cal at
Tue Sep 8 20:42:57 UTC 2020


On Tue, Sep 08, 2020 at 06:48:58PM +0000, Zero King wrote:
> On Tue, Sep 08, 2020 at 06:39:41PM +0200, Mojca Miklavec wrote:
> > After a while Azure came around with 6 hours of timeout which was a
> > lot more useful, and the same solution was ported from Travis to
> > Azure. I forgot why we never switched from Azure to GitHub Actions.
> Done in commit db7b40d8691e1fcd8b6be5e3c2a2a00a7ce0bdf4. We should
> remove Travis CI and Azure Pipelines soon.

I'm not sure this was a good choice. GitHub recently announced stricter
limits on CPU minutes available though GitHub actions. IIRC those limits
will be per project per month, which is especially bad for us because
most of our CI usage is in a single project, and we usually need many
minutes per build. Additional minutes will require payment.

I'm not aware of any such limitation with Azure at the moment, except
for the per-build time limit, so I would prefer to stay with them, since
it scales with the number of PRs we get. I do agree on dropping Travis,
though. It just fails too often to be useful and is generally slow.

> GitHub Actions' IPs should be added to the pastebin allowlist. Logs
> are uploaded as artifacts, but they are zipped[1], so uploading to
> is still preferred.

Is there a documented IP block used by GitHub Actions?


More information about the macports-dev mailing list