Open dennispost opened 1 year ago
I guess we should be able to add this support the in the orchard client itself. It will be even easier comparing to the instance level executor since we won't need to manage VM life cycle (Orchard Controller will do it for us):
[[runners]]
# ...
executor = "custom"
[runners.feature_flags]
FF_RESOLVE_FULL_TLS_CHAIN = false
[runners.custom]
prepare_exec = "orchard"
prepare_args = ["gitlab", "prepare"]
run_exec = "orchard"
run_args = ["gitlab", "run"]
cleanup_exec = "orchard"
cleanup_args = ["gitlab", "cleanup"]
@dennispost how many hosts are you planning to have in the Orchard Cluster? Are you planning to have different kind of jobs in terms of resources? Like ones that use all CPU cores of the host and some more light weight?
We're planning to have at least 2 mac minis in the orchard cluster. Yeah a UI test job needs much more resources than an app build job. But that is based one the image right?
Highly interested in this functionality. We are planning to combine 20 mac minis for building our macOS and iOS applications. Sadly there seems to be no good alternative using gitlab runners. Is the feature still planned for the future?
Have you seen https://github.com/cirruslabs/packer-plugin-tart? Will configuring 20 minis as dedicated runners in a group work for you in the meantime?
Also interested in this functionality, happy to contribute to this if some guidance is given?
Hey where should we track support for Gitlab runner? Can we add support for orchard inside the existing Tart Gitlab runner?