toggle quoted messageShow quoted text
Currently, we have 6 repos with CI pipeline. So we have to convert all of the repos with a CI pipeline.
I already checkout how do you convert a dotnet project. I think will be helpful to do a step by step migration.
We should start with the small projects and than go to the main project.
Von: janusgr...@... <janus...@...> im Auftrag von Lakshay Rastogi <laksha...@...>
Gesendet: Freitag, 20. November 2020 04:32:17
Betreff: Re: [DISCUSS] Move to GitHub Actions
What would be required in terms of development in order to move to GitHub actions?
On Fri, Nov 20, 2020, 4:09 AM Oleksandr Porunov <alexand...@...
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
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
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.
You received this message because you are subscribed to the Google Groups "JanusGraph developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To view this discussion on the web visit