How to use GitLab with your Orka environment. MacStadium provides seamless integration between Orka and GitLab. Both Shell and custom executors are supported. MacStadium provides scripts and a template configuration for custom executors.Documentation Index
Fetch the complete documentation index at: https://docs.macstadium.com/llms.txt
Use this file to discover all available pages before exploring further.
Set Up a Shell Executor
Shell executors are useful when you need permanent executors that you can reuse across builds. For the latest information about how to work with a Shell executor in Orka, see Using a GitLab Shell Executor to Run CI/CD Pipelines in Orka.Set Up a Custom Executor
Custom executors are useful when you need to work with ephemeral executors and automate their management. With a custom executor, an executor is created before the pipeline is run and destroyed after the pipeline is complete. For the latest information about how to work with a custom executor in Orka, see Using a GitLab Custom Executor to Run CI/CD Pipelines in Orka.Cache restoration and artifact downloading require the
gitlab-runner binary to be present inside the Orka VM. If your pipeline logs show “Missing gitlab-runner. Extracting cache is disabled.” or “Missing gitlab-runner. Artifacts downloading is disabled.”, install the gitlab-runner binary in your base image before creating your VM config.Run concurrent builds
By default, the config template setsconcurrent = 1, which means only one build runs at a time. To run multiple builds simultaneously, update two settings in your config.toml:
concurrent(global): the total number of jobs that can run at the same time across all runners.limit(per runner, under[[runners]]): the maximum number of jobs this specific runner handles concurrently.

