Runner

1. Add the Gitlab Helm repository:

   helm repo add gitlab https://charts.gitlab.io

2. If you are unable to access to the latest versions of GitLab Runner, you should update the chart. To update the chart, run:

   helm repo update gitlab

3. To view a list of GitLab Runner versions you have access to, run:

   helm search repo -l gitlab/gitlab-runner

4. Once you have configured Gitlab Runner in your values.yaml file, run the following:

   helm install --namespace NAMESPACE gitlab-runner -f CONFIG_VALUES_FILE gitlab/gitlab-runner

   Where:

   • NAMESPACE is the Kubernetes namespace where you want to install the GitLab Runner.

   • CONFIG_VALUES_FILE is the path to values file containing your custom configuration. See the Configuring GitLab Runner using the Helm Chart section to create it.

If you want to install a specific version of GitLab Runner Helm Chart, add --version RUNNER_HELM_CHART_VERSION to your helm install command. You can install any version of the chart this way, however more recent values.yml may not work with an older version of the chart.

1. Download the binary for your system:

   • For Intel-based systems:

     sudo curl --output /usr/local/bin/gitlab-runner "https://gitlab-runner-downloads.s3.amazonaws.com/latest/binaries/gitlab-runner-darwin-amd64"

   • For Apple Silicon-based systems:

     sudo curl --output /usr/local/bin/gitlab-runner "https://gitlab-runner-downloads.s3.amazonaws.com/latest/binaries/gitlab-runner-darwin-arm64"

2. Give it permissions to execute:

   sudo chmod +x /usr/local/bin/gitlab-runner

3. As the user who will run the runners:

   1. Register a runner. When you build iOS or macOS applications on macOS, use the shell executor. Jobs will run directly on the host and use the identity of the logged-in user. The jobs will not run in a container, which is less secure than using container executors. For details, see the security implications documentation.

   2. Open a terminal and switch to the current user.

      su - USERNAME

   3. Install GitLab Runner as a service and start it:

      cd ~ gitlab-runner install gitlab-runner start

4. Reboot your system.

If you followed these instructions, the GitLab Runner configuration file (config.toml) is in /Users/USERNAME/.gitlab-runner/. Learn more about configuring runners.

Before upgrading GitLab Runner, pause the runner in GitLab and ensure any jobs have completed. Pausing the runner prevents problems arising with the jobs, such as authorization errors when they complete.

Once your GitLab Runner Chart is installed, configuration changes and chart updates should be done using helm upgrade:

Where:

• NAMESPACE is the Kubernetes namespace where GitLab Runner is installed.

• CONFIG_VALUES_FILE is the path to values file containing your custom configuration. See the Configuring GitLab Runner using the Helm Chart section to create it.

• RELEASE-NAME is the name you gave the chart when installing it. In the Installing GitLab Runner using the Helm Chart section, we called it gitlab-runner.

If you want to update to a specific version of GitLab Runner Helm Chart instead of the latest one, add --version RUNNER_HELM_CHART_VERSION to your helm upgrade command.

1. Stop the service:

   gitlab-runner stop

2. Download the binary to replace the GitLab Runner executable:

   • For Intel-based systems:

     sudo curl -o /usr/local/bin/gitlab-runner "https://gitlab-runner-downloads.s3.amazonaws.com/latest/binaries/gitlab-runner-darwin-amd64"

   • For Apple Silicon-based systems:

     sudo curl -o /usr/local/bin/gitlab-runner "https://gitlab-runner-downloads.s3.amazonaws.com/latest/binaries/gitlab-runner-darwin-arm64"

3. Give it permissions to execute:

   sudo chmod +x /usr/local/bin/gitlab-runner

4. Start the service:

   gitlab-runner start