gitlab-omnibus

问题 I’ve been having some fun setting up GitLab and after spending quite a while hacking away at it, I’ve become relatively used to setting it up, now having done that on two machines, the second time around with much more ease than originally… However, I am faced with a rather large problem, on both machines: My CI pipeline is broken. Somehow, somewhere, my setup is providing a 403 to artifacts once builds are completed, meaning that each and every job that ever technically succeeds will only be

问题 I'm trying to install GitLab on a Debian 8.5.0. I folow the installation guide but the last step fail and I don't find any information in documentation. The gitlab-ctl reconfigure finish by Running handlers: Running handlers complete Chef Client failed. 3 resources updated in 02 seconds I have this error in the logs : Error executing action `run` on resource 'execute[/opt/gitlab/embedded/bin/initdb -D /var/opt/gitlab/postgresql/data -E UTF8]' The generated gitlab.rb is enterely commented

问题 I installed gitlab in a docker container from the official image gitlab/gitlab-ce:latest . This image has all config in the file gitlab.rb . Https is done by a nginx reverse proxy. My problem is, that when gitlab has an absolute link to itself, it links always to https://gitlab/ . This host also can be seen in the "New group" dialog: Docker call: docker run \ --name git \ --net mydockernet \ --ip 172.18.0.2 \ --hostname git.mydomain.com \ --restart=always \ -p 766:22 \ -v /docker/gitlab

问题 I get this error on a fresh install of gitlab. The message looks like: fatal: unable to access 'https://gitlab-ci- token:xxxxxxxxxxxxxxxxxxxx@gitlab.example.com/something.git/': Peer's Certificate issuer is not recognized.ERROR: Job failed: exit status 1 Any suggestions on how to fix it? 回答1: Had faced the same problem after enabling verbose mode by following command export GIT_CURL_VERBOSE=1 and found the following issue: NSS error -8179 (SEC_ERROR_UNKNOWN_ISSUER) Found this following site

问题 I just upgraded my gitlab-ce version to the latest version using this command sudo yum install gitlab-ce-12.1.3-ce.0.el7.x86_64 the upgrade works well, but after restart the gitlab service won't start, when I run this command sudo gitlab-ctl start fail: alertmanager: runsv not running fail: gitaly: runsv not running fail: gitlab-monitor: runsv not running fail: gitlab-workhorse: runsv not running fail: grafana: runsv not running fail: logrotate: runsv not running fail: nginx: runsv not

问题 I did setup a new GitLab instance on Ubuntu 16.04.4 LTS. Installing the package went fine and GitLab seems to be up and running. I then started to configure the instance and setup SMTP in /etc/gitlab/gitlab.rb . Afterwards I ran sudo gitlab-ctl reconfigure . It failed with the following error message: Starting Chef Client, version 13.6.4 Running handlers: There was an error running gitlab-ctl reconfigure: Unable to determine node name: configure node_name or configure the system's hostname

问题 Facing issue with gitlab repository not available. When accessing project form gitlab page it shows below error No repository The repository for this project does not exist. This means you can not push code until you create an empty repository or import existing one. When check over project details from root login below is problem Project info: Name: app Namespace: Administrator Owned by: Administrator Created by: Administrator Created on: May 20, 2016 9:08am http: http://192.168.1.123/root

问题 Yesterday I upgraded from Gitlab 7.x to 8.0.4 and almost everything went smoothly. I was using the CI before without issue and after the upgrade had to migrate or start fresh. I chose to start fresh since I only had one project. I have added a new shell runner (tried both gitlab-ci-multi-runner and gitlab-runner) multiple times and registration is successful and the runner shows it's active in the web console. But when I try to build my code the only output in the browser is the black

问题 Summary After backup and migrate, some repositories return "No Repository" error in the web console, and cannot be cloned. The repository is verified to exist as specified in the git_data_dirs folder. As a test I can clone the "No repository" project from the repositories/ folder directly, so there seems to be nothing wrong with the repo itself. Steps to reproduce Not sure how it can be reproduced, but here are the steps i've gone through: backup project on primary server restore tarball on

问题 I have several web sites running in docker with LetsEncrypt credentials and routed via traefik. I would like to run a local gitlab-ce in docker similarly with LetsEncrypt and traefik. So I added this to my traefik.toml file: [[acme.domains]] main = "gitlab.mydomain.com" And this to config/gitlab.rb: external_url "http://gitlab.mydomain.com" And I start gitlab with: docker run -d --restart=always \ --hostname gitlab.mydomain.com \ --expose 80 \ --volume /srv/gitlab/config:/etc/gitlab \ -