gitlab-ci-runner

Gitlab CI gradle dependency cache

我们两清 提交于 2019-12-03 08:02:24
问题 I'm building android on Gitlab CI and downloading dependencies each time is annoying. I tried caching: $HOME/.gradle/ $HOME/.gradle/caches/ $GRADLE_HOME/caches/ $HOME/.m2/ .gradle/ build/ app/build/ The 26594th iteration of my .gitlab-ci.yml is here. I've installed gradle in my build environment because without caching gradlew downloads it every time, which takes even more time. The image I use for building is here. My CI server startup script can be found here. I assume that, if caching

What is the special gitlab-ci-token user?

99封情书 提交于 2019-12-03 04:46:36
The docs for gitlab's container registry ( https://gitlab.com/help/container_registry/README.md ) provide a config example with this instruction: - docker login -u gitlab-ci-token -p $CI_BUILD_TOKEN registry.example.com and this explanation: You have to use the credentials of the special gitlab-ci-token user with its password stored in $CI_BUILD_TOKEN in order to push to the Registry connected to your project. This allows you to automated building and deployment of your Docker images. I cannot find any documentation about this special gitlab-ci-token user, nor about the $CI_BUILD_TOKEN var.

How can I let the gitlab-ci-runner DinD image cache intermediate images?

谁都会走 提交于 2019-12-03 04:08:44
问题 I have a Dockerfile that starts with installing the texlive-full package, which is huge and takes a long time. If I docker build it locally, the intermedate image created after installation is cached, and subsequent builds are fast. However, if I push to my own GitLab install and the GitLab-CI build runner starts, this always seems to start from scratch, redownloading the FROM image, and doing the apt-get install again. This seems like a huge waste to me, so I'm trying to figure out how to

GitLab-CI: Cannot link to a non running container

不羁岁月 提交于 2019-12-03 03:33:52
I've tried to get my setup work with gitlab-ci. I have a simple gitlab-ci.yml file build_ubuntu: image: ubuntu:14.04 services: - rikorose/gcc-cmake:gcc-5 stage: build script: - apt-get update - apt-get install -y python3 build-essential curl - cmake --version tags: - linux I want to get a ubuntu 14.04 LTS with gcc and cmake (apt-get version is to old) installed. If i use it locally (via docker --link command) everything works, but when the gitlab-ci-runner will process it i get the following waring (which is in my case an error) Running with gitlab-ci-multi-runner 9.2.0 (adfc387) on xubuntuci1

Gitlab CI gradle dependency cache

孤人 提交于 2019-12-02 23:12:33
I'm building android on Gitlab CI and downloading dependencies each time is annoying. I tried caching: $HOME/.gradle/ $HOME/.gradle/caches/ $GRADLE_HOME/caches/ $HOME/.m2/ .gradle/ build/ app/build/ The 26594th iteration of my .gitlab-ci.yml is here . I've installed gradle in my build environment because without caching gradlew downloads it every time, which takes even more time. The image I use for building is here . My CI server startup script can be found here . I assume that, if caching works, I won't see a list of my dependencies downloading on every build. Build log: gitlab-ci-multi

Gitlab-CI runner: ignore self-signed certificate

本秂侑毒 提交于 2019-12-02 22:48:46
gitlab-ci-multi-runner register gave me couldn't execute POST against https://xxxx/ci/api/v1/runners/register.json: Post https://xxxx/ci/api/v1/runners/register.json: x509: cannot validate certificate for xxxx because it doesn't contain any IP SANs Is there a way to disable certification validation ? I'm using Gitlab 8.13.1 and gitlab-ci-multi-runner 1.11.2. Based on Wassim's answer, and gitlab documentation about tls-self-signed and custom CA-signed certificates , here's to save some time if you're not the admin of the gitlab server but just of the server with the runners (and if the runner

Kubernetes executor on Gitlab - ERROR: Job failed (system failure): Post *api/v1/namespaces/gitlab/pods: x509: certificate signed by unknown authority

社会主义新天地 提交于 2019-12-02 02:56:06
问题 I'm trying to set up Kubernetes executor for Gitlab but I get this error: ERROR: Job failed (system failure): Post https://api.kubernetes.de/api/v1/namespaces/gitlab/pods: x509: certificate signed by unknown authority This is my configmap.yml: apiVersion: v1 kind: ConfigMap metadata: name: gitlab-runner namespace: gitlab data: config.toml: | concurrent = 4 [[runners]] name = "Kubernetes Runner" url = "http://########/ci" token = "############" executor = "kubernetes" [runners.kubernetes] host

Kubernetes executor on Gitlab - ERROR: Job failed (system failure): Post *api/v1/namespaces/gitlab/pods: x509: certificate signed by unknown authority

青春壹個敷衍的年華 提交于 2019-12-02 00:19:34
I'm trying to set up Kubernetes executor for Gitlab but I get this error: ERROR: Job failed (system failure): Post https://api.kubernetes.de/api/v1/namespaces/gitlab/pods : x509: certificate signed by unknown authority This is my configmap.yml: apiVersion: v1 kind: ConfigMap metadata: name: gitlab-runner namespace: gitlab data: config.toml: | concurrent = 4 [[runners]] name = "Kubernetes Runner" url = "http://########/ci" token = "############" executor = "kubernetes" [runners.kubernetes] host = "https://api.kubernetes.de" namespace = "gitlab" namespace_overwrite_allowed = "ci-.*" privileged =

How do I create 2 jobs that run on different platforms?

北城余情 提交于 2019-12-01 22:18:35
问题 I'm using the Gitlab-ci-multi-runner, using an OSX machine (bash shell) and a Windows 7 machine (batch commands). Whenever I push I want it to build and test on both runners. But obviously the commands need to be slightly different for each platform. I do not wish to use docker. I've been looking at http://doc.gitlab.com/ci/yaml/README.html but there doesn't seem to be anything about specific runner coupling for a stage. 回答1: You can use the tag system for runner. I suppose that you have two

GitLab CI preserve environment between build stages

老子叫甜甜 提交于 2019-12-01 16:54:25
I am working on a python project and using miniconda to manage my environment. I am using GitLab for CI with the following runner configuration stages: - build - test build: stage: build script: - if hash $HOME/miniconda/bin/conda 2>/dev/null; then export PATH="$HOME/miniconda/bin:$PATH"; else wget http://repo.continuum.io/miniconda/Miniconda-latest-Linux-x86_64.sh -O miniconda.sh; bash miniconda.sh -b -p $HOME/miniconda; export PATH="$HOME/miniconda/bin:$PATH"; fi - conda update --yes conda test: stage: test script: - conda env create --quiet --force --file environment.yml - source activate