My understanding is that the queue and quota for GitHub actions is shared across all or almost all of Apache so any project can make the service unavailable for everyone by overloading it, and this frequently happens. GH actions are great but I would investigate this before spending a lot of time on it. IIRC there’s discussion on the builds mailing list.
I didn’t use GH actions for the Aries website build because of this. Jenkins is worse documented and somewhat harder to set up but seems to have better sharing behavior, at least reviewed and possibly controlled by infra. David Jencks Sent from my iPhone > On May 15, 2021, at 10:18 PM, Jean-Baptiste Onofre <[email protected]> wrote: > > No objection. However, be careful about the number of jobs created on GH > Actions. I know that some projects (Beam) reach max number of allowed jobs on > a period. > I think we won’t have any problem at Felix at we won’t launch bunch of jobs > (per PR/commits/scheduled jobs), but just in case ;) > > Regards > JB > >> Le 15 mai 2021 à 03:00, Raymond Augé <[email protected]> a >> écrit : >> >> Would folks be offended if I added github actions and dependabot to some of >> the subprojects? >> >> I personally feel this motivates me to continue making small updates. >> >> -- >> *Raymond Augé* (@rotty3000) >> Senior Software Architect *Liferay, Inc.* (@Liferay) >> OSGi Fellow >
