Stamatis>overcome these limitations for Calcite but I am not yet sure we need this
Just in case, GitHub team works together with DockerHub, so GitHub-based runners won't be affected by DockerHub limits. The quick summary is as follows: a) Infra (Garvin?) talks to many vendors. For instance, tomorrow there will be a meeting with GitHub to figure out if ASF can query resource usage (e.g. GitHub Actions minutes spent per project) b) ASF account (I guess "apache") is not limited on DockerHub. In other words, it is not subject to rate limiting, image retention, etc. c) ASF account is something like enterprise on GitHub, so build minutes are "unlimited", however, the limit is 180 executors for all ASF projects d) Infra is open to discuss various technologies, and projects can ask Infra to approach vendors e) Everybody wanted to see some data/reports on CI usage. Hopefully, that could be implemented. f) There was BuildGrid engineer (see https://gitlab.com/BuildGrid/buildgrid ), and it might be a test instance would appear in ASF. In practice, it is a hermetic remote build and cache execution engine. g) There was a question to explore "on-demand executors" to add more isolation to the current ASF Jenkins executors. Infra is even open to trying Kubernetes, however, they don't have much experience, so someone should help/guide/clarify. An interesting flip was that ASF has Apache CloudStack project which targets similar use cases. Vladimir
