As you can probably imagine, it takes a lot of resources in order to CI for all the Apache projects. Periodically this becomes an issue, as the donated resources from cloud CI providers ( Travis and now GitHub Actions ) end up queuing and delaying builds across Apache projects because of larger projects and their requirements.
The discussions center around a few common themes: - the CI requirements of large complex projects dominate the Apache Queue - how those projects can supplement their builds in a way acceptable to ASF INFRA - how those projects can have per project metering such that a project can pay for hours over the ’norm’ - how to optimize projects This issue is currently being discussed again on the @builds apache list. I’m sending this over to the Nifi Dev community because Nifi itself has been mentioned as one of the top users of GitHub action resources by some measure. Many of the other projects are actively taking measures to decrease or optimize their usage, and we should probably think about how we can do so as well. Here is the *current* thread: https://mail-archives.apache.org/mod_mbox/www-builds/202104.mbox/%3cCAMFhwAbyoDPM8V7bt6=40m++GTdbXK64Q5LjwD=cvrghs7d...@mail.gmail.com%3e <https://mail-archives.apache.org/mod_mbox/www-builds/202104.mbox/%3CCAMFhwAbyoDPM8V7bt6=40m++GTdbXK64Q5LjwD=cvrghs7d...@mail.gmail.com%3E> Here is the message where 13 projects are listed https://mail-archives.apache.org/mod_mbox/www-builds/202104.mbox/%[email protected]%3e <https://mail-archives.apache.org/mod_mbox/www-builds/202104.mbox/%[email protected]%3E> There are many other threads regarding GitHub Action limits and resources if you start scrolling back through the archives. I’m posting this to hopefully kick off some discussions.
