gitlab-runner | GitLab Runner | Continuous Deployment library
kandi X-RAY | gitlab-runner Summary
kandi X-RAY | gitlab-runner Summary
GitLab Runner (Docker image) for ARM devices, this is a mirror repository of
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of gitlab-runner
gitlab-runner Key Features
gitlab-runner Examples and Code Snippets
Community Discussions
Trending Discussions on gitlab-runner
QUESTION
I'm trying to setup a gitlab kubernetes agent and runner for my in-cluster CICD pipeline. My gitlab.ci is something on the line of:
...ANSWER
Answered 2022-Apr-14 at 21:31In short: In your gitlab-runner values file, add the setting service_account = "gitlab"
under [runners.kubernetes]
.
Explanation: The actual pod that executes the job is not the gitlab-runner pod, nor the gitlab agent pod. Gitlab runner kubernetes executor spawns a new pod for each job. The place to set the service account name for these pods is in the above setting.
The error message above shows that the pod running the job was using the default service account for the gitlab
namespace. this service account doesn't (and shouldn't) have the required permissions.
The section runners.config
in the values file, ends up in the config.toml file that configures the runner. Here is the documentation about config.toml for kubernetes executor: https://docs.gitlab.com/runner/executors/kubernetes.html#other-configtoml-settings
And here is the Kubernetes executor interaction diagram
QUESTION
I have created a windows image that I pushed to a custom registry.
The image builds without any error. It also runs perfectly fine on any machine using the command docker run
.
I use a gitlab runner configured to use docker-windows, on a windows host.
The image also runs perfectly fine on the windows host when using the command docker run
in a shell.
However, when gitlab CI triggers the pipeline, I get the following log containing an error :
...ANSWER
Answered 2022-Mar-24 at 20:50I have the same problem using Docker version 4.6.0 and above. Try to install docker 4.5.1 from here https://docs.docker.com/desktop/windows/release-notes/ and let me know if this works for you.
QUESTION
I am trying to create a build pipeline for a small project I do on my free time. For this, I utilize Spring-Boot and Angular. Locally I build it with ./gradlew clean build
. This works perfectly fine on my local machine, but I run into issues I can't pinpoint on gitlab. The build is done on gitlab, utilizing it's own shared runners.
My .gitlab-ci.yml
looks like this:
ANSWER
Answered 2022-Mar-23 at 19:45It worked as sytech suggested - I've just built & pushed the docker-image using gitlab and pushed it into its container repository. I then used it in my application build - and it works as expected.
The .gitlab-ci.yml
in the Dockerfile
repository looks like this:
QUESTION
ci, and i-ve installed my gitlab-runner on a ec2 machine Ubuntu Server 18.04 LTS t2.micro, and when im pushing my code to start the build i get this
But it keeps stucked like this and after 1 hour it timeouts
I really don't know what to do about this problem knowing that i can clone successfully the project manually in my ec2 machine.
Any help is much appreciated if you ever encountered this problem and thanks in advance.
...ANSWER
Answered 2022-Mar-22 at 08:28check your job config or your timeout
QUESTION
I setup a GitLab runner on EC2 which triggers jobs on a Fargate ECS cluster. I followed this tutorial step by step: https://docs.gitlab.com/runner/configuration/runner_autoscale_aws_fargate
During my CI/CD I build docker image then I want to reuse them during other stages of my CI/CD. So when I used shared runner I used docker dind:
...ANSWER
Answered 2022-Mar-16 at 16:45docker:dind
requires privileged execution. It is not possible to use privileged containers on Fargate, so this is not directly possible.
However, you may be able to use daemonless image builders, such as kaniko to build docker images and, optionally, use those images as the build image for later jobs.
You can also explore alternatives, like using CodeBuild to build images with the fargate executor.
QUESTION
Asked a similar question before, but I marked it answered, and I have other information.
Here is the structure:
...ANSWER
Answered 2022-Feb-14 at 09:33Since you're doing
QUESTION
Recently i tried to install Gitlab on Ubuntu machine using docker and docker-compose. This was only done for testing so i can later install it on other machine.
However, i have a problem with removing/deleting gitlab containers.
I tried docker-compose down and killing all processes related to gitlab containers but they keep restarting even if i somehow manage to delete images.
This is my docker-compose.yml file
...ANSWER
Answered 2022-Feb-08 at 15:07I found the solution. Problem was that i didn't use
QUESTION
I've googled few days and haven't found any decisions. I've tried to update k8s from 1.19.0 to 1.19.6 In Ubuntu-20. (cluster manually installed k81 - master and k82 - worker node)
...ANSWER
Answered 2022-Jan-28 at 10:13The solution for the issue is to regenerate the kubeconfig file for the admin:
QUESTION
Bonjor,
Hi All, hope all good.
From past days, I was setting up the coverage visualization on the multi-module gradle
project with the gitlab instance using gitlab-CI
and jacoco
test reports and cobertura
conversion analysis. And need a small assistance in setting up the gitlab-CI for the visualization task.
My current gitlab-ci.yaml
file is as below:
ANSWER
Answered 2022-Jan-28 at 03:53I ended up developing my own plugin jacotura-gradle-plugin that converts the jacoco
reports to cobertura
reports and executed as gradle
task.
Reference: Jacotura @ Github
QUESTION
I try to make a pretty basic GitLab CI job.
I want:
When I push to develop, gitlab builds docker image with tag "develop"
When I push to main, gitlab checks that current commit has tag, and builds image with it or job is not triggered.
ANSWER
Answered 2022-Jan-24 at 19:45Gitlab CI/CD has multiple 'pipeline sources', and some of the Predefined Variables only exist for certain sources.
For example, if you simply push a new commit to the remote, the value of CI_PIPELINE_SOURCE
will be push
. For push
pipelines, many of the Predefined Variables will not exist, such as CI_COMMIT_TAG
, CI_MERGE_REQUEST_SOURCE_BRANCH_NAME
, CI_EXTERNAL_PULL_REQUEST_SOURCE_BRANCH_NAME
, etc.
However if you create a Git Tag either in the GitLab UI or from a git push --tags
command, it will create a Tag pipeline, and variables like CI_COMMIT_TAG
will exist, but CI_COMMIT_BRANCH
will not.
One variable that will always be present regardless what triggered the pipeline is CI_COMMIT_REF_NAME
. For Push sources where the commit is tied to a branch, this variable will hold the branch name. If the commit isn't tied to a branch (ie, there was once a branch for that commit but now it's been deleted) it will hold the full commit SHA. Or, if the pipeline is for a tag, it will hold the tag name.
For more information, read through the different Pipeline Sources (in the description of the CI_PIPELINE_SOURCE
variable) and the other variables in the docs linked above.
What I would do is move this check to the script
section so we can make it more complex for our benefit, and either immediately exit 0
so that the job doesn't run and it doesn't fail, or run the rest of the script.
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