Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for custom executors #689

Open
haampie opened this issue Aug 31, 2020 · 3 comments
Open

Support for custom executors #689

haampie opened this issue Aug 31, 2020 · 3 comments
Labels
enhancement New feature or request future Feature work that we haven't prioritized

Comments

@haampie
Copy link

haampie commented Aug 31, 2020

Gitlab has a nice feature where you can easily create a custom executor, it's documented here https://docs.gitlab.com/runner/executors/custom.html.

This allows one to easily support custom container runtimes such as podman, plain runc, singularity, or whatever container runtime you can think of.

At its core, gitlab gives you a script.sh with all the commands for a job, and you are supposed to make it execute somewhere.

Is such a feature possible with github as well? It would be incredibly useful for clusters where you would have e.g. slurm + rootless containers instead of kubernetes/docker.

@ad-m
Copy link

ad-m commented Nov 22, 2020

Using your own executors would be a very interesting solution. I see that this would allow to create a fully secure worker based on ephemeral virtual machines (like hosted one). Currently, the worker relies on trust as previous tasks may interfere with subsequent tasks and only safe code execution should be executed.

This is important restriction, especially for public repositories and open-source projects that cannot guarantee the execution of only safe code. Some open source project – such as Apache Airflow – require additional computing power that cannot be provided by hosted GitHub Actions workers too.

It allows to execute jobs on AWS Fargate for serverless jobs: https://about.gitlab.com/blog/2020/05/11/introducing-autoscaling-gitlab-runners-on-aws-fargate/

If it is possible to guarantee that the workflow is small (especially based only on JavaScript actions), it could allow extremely fast execution of jobs in Azure Functions. I have a few workflows that regularly only execute a little JavaScript script. Creating an entire Virtual Machine for them is not effective.

@ruvceskistefan ruvceskistefan added the future Feature work that we haven't prioritized label Mar 16, 2022
@vsoch
Copy link

vsoch commented Sep 16, 2022

@vsoch
Copy link

vsoch commented Sep 16, 2022

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request future Feature work that we haven't prioritized
Projects
None yet
Development

No branches or pull requests

4 participants