Re: [DISCUSS] Move to GitHub Actions

Oleksandr Porunov <alexand...@...>


Moving to GitHub actions seems to be a good idea but we need to understand our limitations. This link says that GitHub actions gives us 2000 minutes per month:

Best regards,

On Wednesday, November 18, 2020 at 12:24:51 PM UTC+2 fa...@... wrote:

I did a small evaluation of GitHub Actions in February. GitHub Actions didn't allowed to run to open source project unlimited time at this time. This changed in April.

Old results can be foundĀ here.


On Wednesday, November 18, 2020 at 11:05:41 AM UTC+1 Florian Hockmann wrote:

Travis CI has recently announced that they will only offer 1000 build minutes / month for OSS projects. Given that our builds currently take ~10h, we would only be able to execute around 2 builds per month of our main repository. While the linked
blog post also mentions the possibility to request more free build minutes, I'm not sure whether we want to rely on that and how realistic it is that they will provide us with enough build minutes. (Just to give an example: We would need around 50,000 build minutes per month to be able to execute 3 builds per day.)

To make matters worse, we're still on which will be abandoned at the end of this year in favor of So, even if we want to stay with Travis, we would need to migrate our projects over from to

Given these policy changes by Travis CI, I propose that we migrate to GitHub Actions which seems to be much more OSS friendly nowadays and which probably also allows us to better parallelize and therefore speed up our builds. It allows up to 20 concurrent jobs with a maximum runtime of 6h per job. This should also make it easier to execute the TinkerPop tests for more backends.

Any thoughts or concerns on this topic?

PS: For a bit more context about the changes in Travis CI for OSS projects, I recommend this blog post which made me aware of this in the first place.

Join to automatically receive all group messages.