gitlab-runner | Please open new issues in our issue tracker | Continous Integration library
kandi X-RAY | gitlab-runner Summary
kandi X-RAY | gitlab-runner Summary
This is the repository of the official GitLab Runner written in Go. It runs tests and sends the results to GitLab. GitLab CI is the open-source continuous integration service included with GitLab that coordinates the testing. The old name of this project was GitLab CI Multi Runner but please use "GitLab Runner" (without CI) from now on.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- createOverwrites creates a new overwrites object
- getPodPhase returns the phase of the pod
- NewServer returns a new server instance .
- createResourceList creates and returns a list of resources .
- userModeWarning logs a warning message .
- SplitNameAndVersion splits a service description into a Service .
- GetInstallFlags returns a set of cli flags
- prepareTable prepares a ffjson table .
- newMachineProvider creates a new machine provider .
- createServicesHostAlias returns an api . HostAlias for all services .
gitlab-runner Key Features
gitlab-runner Examples and Code Snippets
Community Discussions
Trending Discussions on gitlab-runner
QUESTION
I'm running gitlab-ce on-prem with min.io as a local S3 service. CI/CD caching is working, and basic connectivity with the S3-compatible minio is good. (Versions: gitlab-ce:13.9.2-ce.0, gitlab-runner:v13.9.0, and minio/minio:latest currently c253244b6fb0.)
Is there additional configuration to differentiate between job-artifacts and pipeline-artifacts and storing them in on-prem S3-compatible object storage?
In my test repo, the "build" stage builds a sparse R package. When I was using local in-gitlab job artifacts, it succeeds and moves on to the "test" and "deploy" stages, no problems. (And that works with S3-stored cache, though that configuration is solely within gitlab-runner.) Now that I've configured minio as a local S3-compatible object storage for artifacts, though, it fails.
ANSWER
Answered 2021-Jun-14 at 18:30The answer is to bypass the empty-string test; the underlying protocol does not support region-less configuration, nor is there a configuration option to support it.
The trick is able to work because the use of 'endpoint' causes the 'region' to be ignored. With that, setting the region to something and forcing the endpoint allows it to work:
QUESTION
The executor for the project gitlab-runner is docker. I try to run docker-in-docker and I get the following Error from pipeline:
ERROR: Job failed (system failure): Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: process_linux.go:508: setting cgroup config for procHooks process caused: resulting devices cgroup doesn't match target mode: unknown (docker.go:385:0s)
I followed this guide: https://www.digitalocean.com/community/tutorials/how-to-set-up-a-continuous-deployment-pipeline-with-gitlab-ci-cd-on-ubuntu-18-04 and after I read the docs of gitlab CI/CD and gitlab-runner, but I can't find out how to solve this problem.
This is currently my config.toml file:
...ANSWER
Answered 2021-Jun-10 at 21:28I solved it with a downgrade of docker:
sudo apt-get install --reinstall docker-ce=5:18.09.9~3-0~ubuntu-bionic docker-ce-cli=5:18.09.9~3-0~ubuntu-bionic docker-ce-rootless-extras containerd.io=1.3.9-1
The problem was that I run on a V-Server (Virtuozzo) with Ubuntu 18. It seems that Virtuozzo does not support currently the newest Docker Engine.
QUESTION
I want to use Testcontainers for my JUNIT tests and so I created this:
...ANSWER
Answered 2021-Jun-04 at 08:49It looks like a bug indeed: CI_REGISTRY_PASSWORD variable is not present at all in the container running DinD service, where it's properly set in job container.
I reproduced your issue by re-using your example in a simplified way:
QUESTION
My overall goal is to install a self-hosted gitlab-runner that is restricted to use prepared docker images from my own docker registry only.
For that I have a system.d configuration that looks like:
/etc/systemd/system/docker.service.d/allow-private-registry-only.conf
...ANSWER
Answered 2021-May-20 at 20:36gitlab-runner-helper image is used by GitLab Runner to handle Git, artifacts, and cache operations for docker, docker+machine or kubernetes executors.
As you prefer pulling an image from a private registry, you can override the helper image. Your configuration could be :
QUESTION
We have a Gitlab setup with Sysbox (link to the setup) to avoid running the docker executor on priviledged mode. Currently the services attribute works and we can communicate to it, but containers started with dind are inaccessible. Here's a minimal .gitlab-ci.yml file to reproduce the problem:
ANSWER
Answered 2021-May-18 at 09:54Can you try 0.0.0.0 instead of localhost? Also, the network_mode property for the runner should be host (https://docs.gitlab.com/runner/executors/docker.html)
QUESTION
I have GitLab CI/CD integration, and use follow yaml as project CI config:
...ANSWER
Answered 2021-May-17 at 17:29/bin/sh: eval: line 113: ./project/build.sh: not found
QUESTION
I'm using the following docker-compose.yml to run a dockerized GitLab instance with one runner. Both are in the same network. (The bridge name is set explicitly because the firewall rules depend on it.)
...ANSWER
Answered 2021-May-11 at 14:45Figured it out:
My setup causes the runner to fetch the sources from gitlab.example.com:443 which is the port served by the Nginx proxy on the host. This worked on Docker 19, however, as of Docker 20 the runner container can't connect via the host anymore. This is totally okay, the solution: Tell the runner to contact the GitLab server in web directly when cloning the source. Each runner in config.toml has to contain:
QUESTION
When attempting to pull public images (e.g. python:3.6, node:latest) from Docker, our GitLab runner failed with the following error message:
ANSWER
Answered 2021-May-06 at 12:17The cause was we exceeded Dockers pull rate limit:
- Free plan – anonymous users: 100 pulls per 6 hours
- Free plan – authenticated users: 200 pulls per 6
See https://docs.docker.com/docker-hub/download-rate-limit/#how-can-i-check-my-current-rate
How to increase the rate limit?Authenticate with Docker Hub to increase to 200 pulls per 6 hours:
QUESTION
I am running a pipeline job on a Windows VM, with default executor as shell. In this job, I wish to run a powershell script, which is located in a directory called CICD, by the following lines:
...ANSWER
Answered 2021-Apr-22 at 11:26You need a / instead of a \:
QUESTION
I want to run my Jupyter notebooks with my pipeline. To do this i need runipy. And to install runipy on the gitlab runner i need python. But when i want to run the .gitlab-ci.yml script it gets stuck at printing the python version because python is not recognized.
.gitlab-ci.yml:
...ANSWER
Answered 2021-Apr-06 at 12:58Based on your log, you're using the shell executor. This will run commands on your local shell, just like you would yourself. The problem is the runner does not use your OS environment variables, so you need to add your python, git, etc. paths to the runner's path environment variable.
The best way to do this is to configure the path variables explicitly in the environment variable in the [[runners]] section of your runner's config.toml. The config.toml file can either be in /etc/gitlab-runner/, ~/.gitlab-runner or / root. This StackOverflow thread shows how to do this. Please read Advanced Configurations for more info.
If you want to download and use a custom docker image, like python:3.9, you need to use the Docker Executor.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install gitlab-runner
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page
