gitlab-ci-runner

Gitlab page is stuck at pending

拈花ヽ惹草 提交于 2019-12-12 23:06:45
问题 I set up a Gitlab pages page a couple of days ago. It was building fine till this morning. Now it seems to be stuck at pending and hasn't built despite my attempts to restart it. I checked if there is a shared runner. It currently says: Available shared runners - 1 in the Runner section of Project Settings. This is the .yml file. pages: script: - mkdir .public - cp -r * .public - mv .public public artifacts: paths: - public only: - master This code was recommended in the pages installation

Gitlab CI how to deploy the latest to a specific directory

安稳与你 提交于 2019-12-12 18:17:29
问题 I have two projects in Gitlab where one is a submodule (let's call repo "frontend-templates") of the other (let's call this repo "main"). I have set up a Gitlab CI build for the "frontend-templates" repo. The thing is that I don't need testing or building. I only need deploying for this CI in the needed directory. So, I registered a runner for "frontend-templates" project and added .gitlab-ci.yml to the root directory: job_main: type: deploy script: echo "Do nothing" When I push to my

GitLab CI runner - can't access other repository

允我心安 提交于 2019-12-12 03:28:28
问题 After a recent minor 8.x upgrade, I'm unable to execute GitLab CI tests that also fetch another repository. While everything worked previously, now I get the famous Host key verification failed. error message from ssh. What could be the cause of this? /etc/gitlab-runner/config.toml : concurrent = 1 [[runners]] name = "python-runner@localhost" # ... executor = "docker" [runners.docker] image = "edoburu/python-runner" privileged = false cap_drop = ["DAC_OVERRIDE"] volumes = [ "/cache", "/home

Gitlab CI/CD runner : mvn command not found

橙三吉。 提交于 2019-12-11 09:13:33
问题 Maven is well installed on my gitlab-runner server. When executing mvn clean directly on my repo it works, when running my pipeline using Gitlab UI got this error : bash: line 60: mvn: command not found ERROR: Job failed: exit status 1 I notice that I tried to fix the problem by adding the before_script section in the .gitlab-ci.yml file : before_script: - export MAVEN_HOME=/usr/local/apache-maven I add also the line : environment = ["MAVEN_HOME=/usr/local/apache-maven"] on the config.toml

gitlab-ci: setup every day builds

送分小仙女□ 提交于 2019-12-11 06:08:27
问题 Really do not understand how I can setup daily scheduler in gitlab . I have simple application and I need automatically build it every day at 8.00 morning. I tried with Following https://gitlab.com/help/ci/triggers/README.md , but i do not understand how can I run this crone job? 30 0 * * * curl --request POST --form token=TOKEN --form ref=master https://gitlab.example.com/api/v3/projects/9/trigger/builds This is also unacceptable http://cloudlady911.com/index.php/2016/11/02/how-to-schedule-a

Gitlab CI - Start Shared Runner for normal repos

房东的猫 提交于 2019-12-11 06:02:07
问题 I'm new to Gitlab CI. I have configured .gitlab-ci.yml file, and using CI Lint it has passed the validation process. Based on this documentation, I can see a specific runner should be configured on a virtual machine, a VPS, a bare-metal machine, a docker container or even a cluster of containers. And I can see gitlab has its own shared runners and enabled by default . When I visit the Pipeline page I can only see the blue Get Started with Pipeline button and when clicked I was redirected to

Cannot connect to the Docker daemon at unix:///var/run/docker.sock in gitlab CI

左心房为你撑大大i 提交于 2019-12-11 04:37:15
问题 I looked at any other questions but can't find my own solution! I setting up a CI in gitlab and use the gitlab's shared runner. In build stage I used docker image as base image but when i use docker command it says : Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? I looked at this topic but still don't understand what should I do? .gitlab-ci.yml : stages: - test - build - deploy job_1: image: python:3.6 stage: test script: - sh ./sh_script

gitlab kubernetes runner cannot connect to the docker daemon

狂风中的少年 提交于 2019-12-11 03:59:10
问题 I have configured gitlab runner within kubernetes , which is not able to connect to docker daemon . Showing below error . $ docker build --cache-from "${DOCKER_IMAGE_TAG}" -t "${DOCKER_IMAGE_TAG}" . Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? ERROR: Job failed: command terminated with exit code 1 stages: - push_to_docker docker_image: image: 'docker:latest' services: - docker:dind stage: push_to_docker variables: DOCKER_IMAGE_TAG: 'gcr.io

Two gitlab-ci runners for one project

情到浓时终转凉″ 提交于 2019-12-11 03:32:36
问题 I used to have a project on github with a travis and an appveyor integration service configured. Thus I was able to make sur my project was compiling ok on both OSX and Windows plateform. I'm now working with gitlab and ci runners. I have two runners configured: One on a OSX machine One on a Windows machine Unfortunately when I add both runners in my project settings > CI/CD > Runners settings, only one is triggered upon push (the OSX one). If I disable the OSX runner, the Windows runner is

Gitlab runner not executing jobs docker image

不问归期 提交于 2019-12-11 02:56:31
问题 I created a minimal gitlab CI script to verify this error: docker_execution_test: image: debian:9 script: - pwd - ls The output I would expect is this: db@theia:~/git/docker_test (master*)$ docker run -it --rm debian:9 pwd / db@theia:~/git/docker_test (master*)$ docker run -it --rm debian:9 ls bin dev home lib64 mnt proc run srv tmp var boot etc lib media opt root sbin sys usr However, the output when executed through gitlab-runner is this: db@theia:~/git/docker_test (master)$ gitlab-runner