Hi, No problem for me, but be careful, some Apache projects are complaining about the number of GitHub Actions jobs started (it’s the case at least on Beam and Airflow).
I guess that by development process you mean the fact that GHA can work on fork, right ? I don’t see why GHA would improve releases quality comparing to Jenkins (they execute the same mvn build). So, what’s your arguments (other than managed service) for GHA compared to Jenkins ? Regards JB > Le 9 févr. 2021 à 11:41, Mohamed-Tayeb BENTERKI <[email protected]> a écrit : > > Hello, > > I propose to move the CI from Jenkins to GithubActions, the idea behind it, > to centralise all the interaction and PR validation process in one place > and also the stability and speed of execution of the GHA as Jenkins does. > IMHO, I think this will really simplify the development process and > increase the quality of the releases. > > Note: > - There is no impact on the Unomi code base. > - If you like the idea and the benefit, I will take care of the > implementation and its finalisation (at the moment I am adding PR so that > this can be checked and I have also asked the infra team to provide us with > credentials for nexus deployment). > > Thoughts? > Regards
