Note: lists.lfaidata.foundation will be down for maintenance on Monday, September 26th, starting at 9AM Pacific Time (4PM Monday September 26, 2022 UTC), for approximately one hour.
- [DISCUSS] Move to GitHub Actions
Re: [DISCUSS] Move to GitHub Actions
Oleksandr Porunov <alexand...@...>
toggle quoted messageShow quoted text
If that's the case, as for me it's obvious way to go.
+1 for moving to GitHub Actions
On Thursday, November 19, 2020 at 11:38:32 PM UTC+2 Ja...@... wrote:
I’m pretty sure about our limitations, which are just 20 concurrent runner at the same time for all public repos. The 2000 minutes are just for private repos (no build time limit for public repos).
On 19. Nov 2020, at 21:55, Oleksandr Porunov <alex...@...> wrote:
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:
On Wednesday, November 18, 2020 at 12:24:51 PM UTC+2 fa...@...
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
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.)
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.
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 email@example.com to automatically receive all group messages.