gitlab-ci-multi-runner | Please go | Continuous Deployment library

by ayufan Go Version: Current License: MIT

X-Ray Key Features Code Snippets Community Discussions(10)Vulnerabilities Install Support

kandi X-RAY | gitlab-ci-multi-runner Summary

gitlab-ci-multi-runner is a Go library typically used in Devops, Continuous Deployment, Docker applications. gitlab-ci-multi-runner has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

This repository is a mirror for automated DockerHub builds. Please go to:

Support

Quality

Security

License

Reuse

Support

gitlab-ci-multi-runner has a low active ecosystem.

It has 367 star(s) with 136 fork(s). There are 17 watchers for this library.

It had no major release in the last 6 months.

gitlab-ci-multi-runner has no issues reported. There are 11 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of gitlab-ci-multi-runner is current.

Quality

gitlab-ci-multi-runner has no bugs reported.

Security

gitlab-ci-multi-runner has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

gitlab-ci-multi-runner is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

gitlab-ci-multi-runner releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of gitlab-ci-multi-runner

Get all kandi verified functions for this library.

gitlab-ci-multi-runner Key Features

No Key Features are available at this moment for gitlab-ci-multi-runner.

gitlab-ci-multi-runner Examples and Code Snippets

No Code Snippets are available at this moment for gitlab-ci-multi-runner.

Community Discussions

Trending Discussions on gitlab-ci-multi-runner

Using docker-compose in a GitLab CI pipeline

GitLab CI runner can't connect to unix:///var/run/docker.sock in kubernetes

Gitlab-CI runner: ignore self-signed certificate

How to execute a script located in the runner from the ci-pipeline?

How to install maven for a docker shell gitlab runner

GitLab CI - Cache not working

xcodebuild: error: 'APP.xcworkspace' does not exist

Unable to access docker-compose containers created inside docker

ERROR: Registering runner… failed runner=38BUk9-k status=404 Not Found

Gitlab-ci-token user unable to clone repositories

QUESTION

Using docker-compose in a GitLab CI pipeline

Asked 2019-Nov-13 at 14:53

I'm trying to implement a GitLab continuous integration (CI) pipeline with the following .gitlab-ci.yml file:

...

ANSWER

Answered 2017-Feb-19 at 02:07

The problem

This is complex problem.

The docker:latest image is based on alpine (Alpine Linux), which is built using musl-libc. This system is very barebones, and as such doesn't have everything a full-fledged desktop Linux might have. In fact, dynamic executables need to be compiled specifically for this system.

docker-compose is a Python application, bundled into a Linux executable using PyInstaller. These executables are really only expected to be able to run on the system which they were built. If you run an alpine container, and apk add file, you can see that the (dynamically-linked) executable you downloaded is expecting a specific interpreter.

Source https://stackoverflow.com/questions/42295457

QUESTION

GitLab CI runner can't connect to unix:///var/run/docker.sock in kubernetes

Asked 2019-Oct-25 at 13:57

GitLab's running in kubernetes cluster. Runner can't build docker image with build artifacts. I've already tried several approaches to fix this, but no luck. Here are some configs snippets:

.gitlab-ci.yml

...

ANSWER

Answered 2017-Mar-18 at 05:37

When using Kubernetes, you have to adjust your Build image to connect with the Docker engine.

Add to your build image:

Source https://stackoverflow.com/questions/42867039

QUESTION

Gitlab-CI runner: ignore self-signed certificate

Asked 2019-Oct-03 at 08:42

gitlab-ci-multi-runner register

...

ANSWER

Answered 2017-Jun-16 at 10:43

Currently there is no possibility to run the multi runner with an insecure ssl option.

There is currently an open issue at GitLab about that.

Still you should be able to get your certificate, make it a PEM file and give it to the runner command using --tls-ca-file

To craft the PEM file use openssl.
openssl x509 -in mycert.crt -out mycert.pem -outform PEM

Source https://stackoverflow.com/questions/44458410

QUESTION

How to execute a script located in the runner from the ci-pipeline?

Asked 2019-Aug-21 at 10:59

I have a gitlab-runner image as follows:

Dockerfile

...

ANSWER

Answered 2017-Aug-10 at 06:08

I continued my research and found the repository of the official maven docker images.

They solved a similar problem by creating a mvn-entrypoint.sh. So I tried the same:

entrypoint.sh

Source https://stackoverflow.com/questions/45588426

QUESTION

How to install maven for a docker shell gitlab runner

Asked 2019-May-10 at 11:35

(Please note i'm a total beginner in all Docker and CI in general)

I am trying to set up a simple CI environment with GitLab. I'm using a local GitLab runner which is configured to build and test in Docker. In registering the runner I chose the 'shell' option. This installation succeeded.

After pushing my code I got an email saying 'build failed'. In the build log I found the following:

...

ANSWER

Answered 2019-May-10 at 11:35

I'm using a local GitLab runner which is configured to build and test in Docker. In registering the runner I chose the 'shell' option

From the sounds of it, you have registered the gitlab-runner incorrectly for the mode you are after. You said you want to use a runner to build and test in Docker, however you have registered the runner in shell mode.

To use the runner in Docker, follow the instructions set in the documentation. Make sure to set the runner executor to Docker when registering.

You'd also ideally remove the shell runner you have created.

If you have issues registering the runner, see this answer, which may also help with setting up your environment.

Source https://stackoverflow.com/questions/56076614

QUESTION

GitLab CI - Cache not working

Asked 2019-May-02 at 15:21

I'm currently using GitLab in combination with CI runners to run unit tests of my project, to speed up the process of bootstrapping the tests I'm using the built-in cache functionality, however this doesn't seem to work.

Each time someone commits to master, my runner does a git fetch and proceeds to remove all cached files, which means I have to stare at my screen for around 10 minutes to wait for a test to complete while the runner re-downloads all dependencies (NPM and PIP being the biggest time killers).

Output of the CI runner:

...

ANSWER

Answered 2019-May-02 at 15:21

Turns out that I was doing some things wrong:

Your script can't cache files outside of your project scope, creating a virtual environment instead and caching that allows you to cache your pip modules.
Most important of all: Your test must succeed in order for it to cache the files.

After using the following config I got a -3 minute time difference:

Currently my configuration looks like follows and works for me.

Source https://stackoverflow.com/questions/44798794

QUESTION

xcodebuild: error: 'APP.xcworkspace' does not exist

Asked 2019-Jan-04 at 17:47

I am trying to set up CI with gitlab. When I try to build locally, I get this error : xcodebuild: error: 'APP.xcworkspace' does not exist. "APP" not being the real name. I am also using CocoaPods.

This happens after I run this command in terminal: gitlab-ci-multi-runner exec shell build_project

I have checked and the file does exist in the same folder I call the command.

This is my .gitlab-ci.yml file:

...

ANSWER

Answered 2017-Feb-24 at 07:53

I have solved this now!!

I just had to update the cocoapods repo, se this link: https://github.com/CocoaPods/CocoaPods/issues/5077

Looks like your specs repo was edited at some point, and now git can't update it. I'd recommend deleting and re-creating your Specs repo: pod repo remove master and running pod setup

Source https://stackoverflow.com/questions/42426358

QUESTION

Unable to access docker-compose containers created inside docker

Asked 2018-Nov-29 at 10:26

I have a docker-compose.yml file that starts up a simple HTTP echo service on port 8800.

...

ANSWER

Answered 2018-Nov-29 at 10:26

The container is running on the "docker host" which is, in your case, the other container that is supporting the Gitlab build:

Source https://stackoverflow.com/questions/45389116

QUESTION

ERROR: Registering runner… failed runner=38BUk9-k status=404 Not Found

Asked 2018-Jun-27 at 07:28

I'm trying to register a gitlab runner on a new installation of gitlab (based on the omnibus rpm for centos7) but registration fails like this:

...

ANSWER

Answered 2017-Mar-28 at 17:21

You seem to be running Gitlab Runner v9.x. This error occurs when you match a V9 runner with a Gitlab below V9. They are incompatible.

Gitlab Runner v9 started using the V4 API, but that is only available with Gitlab V9. Downgrade to 1.11.1, should work again.

In particular, if you are starting your Runner using the official docker image, don't use :latest tag, switch to

Source https://stackoverflow.com/questions/42489197

QUESTION

Gitlab-ci-token user unable to clone repositories

Asked 2018-May-16 at 00:37

I am trying to setup a docker runner and successfully registered the runner with gitlab-ce. However, when the job runs it always fails with the follow:

...

ANSWER

Answered 2017-Sep-12 at 15:28

Note that there might be two issue.

Regarding the token itself (and fatal: Authentication failed ), see this thread

The CI token is now securely generated for each build. It's available in $CI_BUILD_TOKEN.
If you're cloning a different repository from .gitlab-ci.yml (like we were) your best bet is to use SSH.

Another solution is to use your personal private token:

Source https://stackoverflow.com/questions/41881882

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install gitlab-ci-multi-runner

Install using GitLab's repository for Debian/Ubuntu/CentOS/RedHat (preferred)
Install on OSX (preferred)
Install on Windows (preferred)
Install as Docker Service
Install in Auto-scaling mode
Use on FreeBSD

Support

Contributions are welcome, see CONTRIBUTING.md for more details. GitLab is growing very fast and we have a limited resources to deal with reported issues and merge requests opened by the community volunteers. We appreciate all the contributions coming from our community. But to help all of us with issues and merge requests management we need to create some closing policy.

Find more information at: