gitlab

GitLab runner unable to clone repository via http

主宰稳场 提交于 2019-12-19 06:29:56
问题 I have the latest docker image of GitLab running in a test environment and I'm running into an issue with the GitLab runner. It's unable to clone via the HTTP link, yielding the following message: Running on runner-bd27e50b-project-1-concurrent-0 via machine... Cloning repository... Cloning into '/builds/my/awesome-project'... fatal: unable to access 'http://gitlab-ci-token:xxxxxx@127.0.0.1/my/awesome-project.git/': Failed to connect to 127.0.0.1 port 80: Connection refused ERROR: Build

GitLab runner unable to clone repository via http

ⅰ亾dé卋堺 提交于 2019-12-19 06:29:07
问题 I have the latest docker image of GitLab running in a test environment and I'm running into an issue with the GitLab runner. It's unable to clone via the HTTP link, yielding the following message: Running on runner-bd27e50b-project-1-concurrent-0 via machine... Cloning repository... Cloning into '/builds/my/awesome-project'... fatal: unable to access 'http://gitlab-ci-token:xxxxxx@127.0.0.1/my/awesome-project.git/': Failed to connect to 127.0.0.1 port 80: Connection refused ERROR: Build

GitLab remote repository with a non standard port

﹥>﹥吖頭↗ 提交于 2019-12-19 04:05:11
问题 I have the following error: ssh: connect to host git.limeworks.eu port 22: Connection refused fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. Now, the configuration I have in my local .ssh/config file is: host limeworks user git port 6565 hostname git.limeworks.eu; and in the remote gitlab.yml: gitlab: ## Web server settings host: git.limeworks.eu port: 6565 Also, here's the nginx setup (/sites-enabled/gitlab):

Jenkins系列之三——centos7.4+GitLab+Jenkins部署

 ̄綄美尐妖づ 提交于 2019-12-19 02:22:57
GitLab介绍 GitLab 是一个用于仓库管理系统的开源项目,使用 Git 作为代码管理工具,并在此基础上搭建起来的web服务。 系统环境准备 建议:内存4G以上不然带不动 [root@hejianlai-jenkins ~]# cat /etc/redhat-release CentOS Linux release 7.4.1708 (Core) [root@hejianlai-jenkins ~]# uname -r 3.10.0-693.el7.x86_64 #关闭firewalld和NetWorkManager [root@hejianlai-jenkins ~]# systemctl stop firewalld [root@hejianlai-jenkins ~]# systemctl stop NetWorkManager #永久关闭 [root@hejianlai-jenkins ~]# systemctl disable firewalld [root@hejianlai-jenkins ~]# systemctl disable NetWorkManager #关闭selinux [root@hejianlai-jenkins ~]# sed -i 's/SELINUX=enforcing/SELINUX=disabled/g' /etc/selinux

Strange error in gitlab: fatal: protocol error: bad line length character: Depl

送分小仙女□ 提交于 2019-12-19 02:09:42
问题 On one of my servers, when I'm try to pull/ls-remote fresh-created repo on gitlab, I'm getting these error: git ls-remote git@gitlab.com:mas-vem/dinnerdelivery.git fatal: protocol error: bad line length character: Depl If I'm trying to ls-remote one of earliest created repositories, all is fine. When I'm run this command: ssh git@gitlab.com git-receive-pack mas-vem/dinnerdelivery.git I'm getting this error: Deploy key not allowed to push But I doesn't want to push =/ What it could be? Does it

docker-gitlab-runner

久未见 提交于 2019-12-18 20:06:31
【推荐】2019 Java 开发者跳槽指南.pdf(吐血整理) >>> 拉取镜像 docker pull gitlab/gitlab-runner:latest 生成容器 docker run -d \ --name gitlab-runner \ --restart always \ -v /gitlab-runner/config:/etc/gitlab-runner \ -v /var/run/docker.sock:/var/run/docker.sock \ gitlab/gitlab-runner:latest 进入容器 docker exec -it gitlab-runner /bin/bash 注册runner,并按如下提示输入: gitlab-runner register > Please enter the gitlab-ci coordinator URL https://code.weflys.com > Please enter the gitlab-ci token for this runner in1dadgmRQMyso-C9bzW > Please enter the gitlab-ci description for this runner gitlab-runner > Please enter the gitlab-ci tags

docker-compose 搭建gitlab

早过忘川 提交于 2019-12-18 18:39:36
搭建步骤 1、安装docker及docker-compose 2、编写dokcer-compose文件 并且启动 version: '3.7' services: gitlab: container_name: mygitlab image: 'gitlab/gitlab-ce:11.9.6-ce.0' restart: always hostname: 'yujuan.com' environment: - TZ=Asia/Shanghai ports: - '3080:80' - '3443:443' - '3022:22' volumes: - ./config:/etc/gitlab - ./logs:/var/log/gitlab - ./data:/var/opt/gitlab network_mode: "bridge" privileged: true docker-compose up -d 3、访问localhost:3080 进入GitLab页面 localhost:3080 我们首次进入时,会让初始化管理员的密码,这里初始化完成后使用 root/初始化密码 进入gitlab页面(如下),按照对应的提示创建项目、创建用户、创建组即可 注意事项 权限问题 在构建镜像时,有时候会遇到权限不足导致gitlab启动失败的问题,如果遇到该错误,需要在docker

vue-cli+gitlab代码管理时,vue项目配置文件设置

ぃ、小莉子 提交于 2019-12-18 18:19:52
【推荐】2019 Java 开发者跳槽指南.pdf(吐血整理) >>> vue-cli生成的项目,使用gitlab进行代码管理,怎样忽略项目配置文件的提交(避免每次合并分支代码冲突,而且每次修改配置文件只需修改服务器上测试环境地址即可,无需每次修改后提交) 项目配置文件:config/prod.env.js文件,配置访问后台路由地址的文件 1、本地代码将config/prod.env.js文件改名为config/prod.env.js.example,并将文件中代码注释即可。 2、使用git status,git add,git commit, git push等命令提交此工程。 3、修改.gitignore中内容,新增config/prod.env.js文件,即以后情况忽略此文件的提交。然后git status,git add,git commit, git push等命令提交此工程。 4、本地复制config/prod.env.js.example文件,并更名为config/prod.env.js文件,此时修改此文件,使用git status将不会看到更新,提交时也不会进行提交了。 5、其他分支按此方法,只不过prod.env.js.example在各分支统一即可。 其他方式: 为Vue项目添加配置文件,便于维护全局变量 来源: oschina 链接: https://my

How to update GitLab in Bitnami stack

China☆狼群 提交于 2019-12-18 18:07:34
问题 I am trying BitNami GitLab Stack 5.1.0-2, and while I was doing that 5.1.0-3 was released. How to update GitLab in Bitnami stack? Related to BitNami GitLab Stack 5.1.0-2 with LDAP 回答1: Look at this: https://github.com/gitlabhq/gitlabhq/tree/master/doc/update This how to's explains about upgrading the gitlab. But there are certain concerns. Gitlab can be upgraded but gitlab-shell throws an error as "fatal: Not a git repository (or any of the parent directories): .git" which I guess needs

Gitlab加入LDAP认证

两盒软妹~` 提交于 2019-12-18 17:11:06
如果企业大大小小系统较多,每个系统都给用户单独配置一账户。这样各个系统的账户信息都要单独记忆,比较繁琐,而且账户信息易忘。所以加入集成 LDAP 统一认证,域控管理。这里对Gitlab应用系统结合LDAP认证,前提是企业内部已搭建好AD域服务。 Gitlab配置LDAP Gitlab已安装好,安装的CE版本。Gitlab配置LDAP服务要在配置文件中修改,无法像Jenkins加入LDAP那样安装一LDAP插件,然后配置LDAP信息即可。Gitlab中需在默认的配置文件/etc/gitlab/gitlab.rb中修改LDAP配置项。默认LDAP服务是关闭的,配置项 gitlab_rails['ldap_enabled'] = false。现开启LDAP服务并配置,修改以下配置项: gitlab_rails['ldap_enabled'] = true ###! **remember to close this block with 'EOS' below** gitlab_rails['ldap_servers'] = YAML.load <<-'EOS' main: # 'main' is the GitLab 'provider ID' of this LDAP server label: 'LDAP' host: '10.10.10.60' port: 389 uid: