Ma77Ball commented on issue #4290:
URL: https://github.com/apache/texera/issues/4290#issuecomment-4300446297
### Options:
1. External CI service (e.g., Azure Pipelines)
- Offload CI to an external service like Azure Pipelines. Untrusted code
never runs on shared infrastructure, but free tiers limit parallel execution
and have monthly minutes.
2. Contributor runs CI on their own fork (Apache Spark model)
- Contributors run CI on their forked repository before submitting a PR,
and committers review the results. Most common pattern across Apache projects,
and is considered the most secure approach.
3. Self-hosted runners
- Possible if resources are available, but not recommended. Runners
persist across jobs, potentially leaving malicious code behind. Most Apache
projects avoid this without dedicated infrastructure expertise.
---
**Recommendation:** Option 2
> **Note:** Apache also allows each repository to have up to 10
non-committers trigger CI automatically.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
