gitlab-ci-runner | GitLab Runner PROJECT IS DEPRECATED NOW , PLEASE | Continous Integration library

by gitlabhq Ruby Version: Current License: MIT

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

kandi X-RAY | gitlab-ci-runner Summary

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

GitLab Runner PROJECT IS DEPRECATED NOW, PLEASE USE NEW GitLab Runner written in Go (previously named GitLab CI Multi Runner) INSTEAD

Support

Quality

Security

License

Reuse

Support

gitlab-ci-runner has a low active ecosystem.

It has 190 star(s) with 126 fork(s). There are 60 watchers for this library.

It had no major release in the last 6 months.

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

It has a neutral sentiment in the developer community.

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

Quality

gitlab-ci-runner has 0 bugs and 0 code smells.

Security

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

gitlab-ci-runner code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

gitlab-ci-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-runner releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

gitlab-ci-runner saves you 198 person hours of effort in developing the same functionality from scratch.

It has 486 lines of code, 53 functions and 9 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed gitlab-ci-runner and discovered the below as its top functions. This is intended to give you an instant insight into gitlab-ci-runner implemented functionality, and help decide if they suit your requirements.

Execute a shell command with the given options
Gets all builds for a build
Run the git command
Encrypts a message using a string
Register a runner
Update a build
register a runner
Push a message to the build
Unregister a runner
Initialize configuration object

Get all kandi verified functions for this library.

gitlab-ci-runner Key Features

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

gitlab-ci-runner Examples and Code Snippets

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

Community Discussions

Trending Discussions on gitlab-ci-runner

rootless podman can not run some commands

Running local GitLab CI with shell executor and flag --user $USER for gitlab-runner

Gitlab Self-Hosted: ERROR: Uploading artifacts as "archive" to coordinator... too large archive

GitLab CI: how to connect to the docker container started in .gitlab-ci.yml script?

QUESTION

rootless podman can not run some commands

Asked 2021-Nov-22 at 14:47

I had a problem with gitlab running podman commands with gitlab-runner user and I could not see the created containers with my user. I chaned the user as described in Change Gitlab CI Runner user. I ran the gitlab pipeline again and it went successfully through 3 steps and created a podman pod and 2 other containers in it. Suddenly it stoped by a podman run for the last container. I checked the server and gave podman ps -a but nothing happend after pressing enter and I could still write in command line! I wrote podman images list and I could see the images list (2 images have the same id and I can not remove them!!). I tried sudo podman ps and it worked! Some commands just work and some commands are not working as rootless. my user can not do podman run from Gitlab but on the server my user can run podman run hello-world! I get no error just it remains in that state and I have to cancle the job.

I am using centos 8, podman 3.3.1. sudo podman info:

...

ANSWER

Answered 2021-Nov-18 at 19:56

Is this problem reproducible? Why I am asking because I think it should not be the case with podman but a specific issue at your end.

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

QUESTION

Running local GitLab CI with shell executor and flag --user $USER for gitlab-runner

Asked 2021-Oct-03 at 08:54

I try to set up a CI environment on a local GitLab install. I am testing basic shell commands that need to be run within the regular user (the value of $USER) environment. By default the gitlab-runner service is configured with --user gitlab-runner. So first I followed the answer provided at Change Gitlab CI Runner user to assign another user. This seemed to work as the output of ps aux | grep runner is as expected and I hit the clear_console error from .bash_logout described at https://gitlab.com/gitlab-org/gitlab-runner/-/issues/4559. After commenting out the content of .bash_logout I now get the following error.

...

ANSWER

Answered 2021-Oct-03 at 00:35

As Davide mentioned in the comments, when you update the user for gitlab-runner, you also need to update its working directory to ensure that it has permissions to that directory. Alternatively, you could grant the new user access to /home/gitlab-runner, it's your choice. To install the gitlab-runner with a different user and working directory, the command is: gitlab-runner install --user=my_user --working-directory=/home/my_user (reference)

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

QUESTION

Gitlab Self-Hosted: ERROR: Uploading artifacts as "archive" to coordinator... too large archive

Asked 2020-Oct-13 at 05:30

Some time ago, our Gitlab (self-hosted) instance started to throw errors that the archives are too big:

ERROR: Uploading artifacts as "archive" to coordinator... too large archive id=something responseStatus=413 Request Entity Too Large status=413 token=something FATAL: too large
ERROR: Job failed: exit code 1

The only resolution ideas we found was to set the max build artifact size (it's under /admin/application_settings). This did not work for us, the error still occurred.

Reference articles:

...

ANSWER

Answered 2020-Oct-13 at 05:30

The solution to this issue is to set the max build artifact size (under /admin/application_settings) and to increase the Gitlab NGINX client_max_body_size property in the configuration file to something higher.

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

QUESTION

GitLab CI: how to connect to the docker container started in .gitlab-ci.yml script?

Asked 2020-Feb-25 at 16:10

Initial task

In my GitLab CI build, I want to:

Start a docker container with local AmazonDB. Standard port layout: port 8000 in docker, port 8000 exposed. Of course, everything works locally, I can connect (curl, awc-cli, Java code for Amazon DB, whatever you wish).
Use it for tests, i.e. connect to it as --endpoint-url http://localhost:8000 (or any other mapped IP instead of localhost).

Problem

.gitlab-ci.yml looks like this:

...

ANSWER

Answered 2020-Feb-25 at 16:10

There is actually no need in writing such a complex solution with manual docker run / docker stop inside the -script section. The slim and simple way is to use the local DynamoDB as service.

With this script, local DynamoDB will be accessible via url from alias of the services element, i.e. dynamodb-local for this example:

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

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

Vulnerabilities

No vulnerabilities reported

Install gitlab-ci-runner

The easiest and recommended way to install the runner is with the GitLab Runner Omnibus package.
Install the gems for the runner:.

Support

This projects officially support these Linux distributions:. Mac OSX and other POSIX operating systems are not supported but will work with adaptations. Under Windows the runner will only work under POSIX compliant environments like Cygwin. Also see the alternative Runners for Windows, Scala/Java and Node please see the runner section of the GitLab CI page on the website.

Find more information at: