Skip to content
GitLab
项目 群组 主题 代码片段
  • /
  • 帮助
    • 帮助
    • 支持
    • 社区论坛
    • 提交反馈
  • 登录
  • L large
  • 项目信息
    • 项目信息
    • 动态
    • 标记
    • 成员
  • 仓库
    • 仓库
    • 文件
    • 提交
    • 分支
    • 标签
    • 贡献者统计
    • 分支图
    • 比较修订版本
  • 议题 21
    • 议题 21
    • 列表
    • 看板
    • 服务台
    • 里程碑
  • 合并请求 12
    • 合并请求 12
  • CI/CD
    • CI/CD
    • 流水线
    • 作业
    • 产物
    • 计划
  • 部署
    • 部署
    • 环境
    • 发布
  • 软件包与镜像库
    • 软件包与镜像库
    • 软件包库
    • 容器镜像库
    • Terraform 模块
    • 模型实验
  • 监控
    • 监控
    • 事件
  • 分析
    • 分析
    • 价值流
    • CI/CD
    • 仓库
  • Wiki
    • Wiki
  • 代码片段
    • 代码片段
  • 动态
  • 分支图
  • 创建新议题
  • 作业
  • 提交
  • 议题看板
收起侧边栏
  • 王权利
  • large
  • 议题
  • #480

Display Gitolite Errors in the admin-interface

Created by: ccoenen

I had a problem, where a user (email was: _macdev@example.com) was created in gitlab. The user (and his public key) were setup successfully. But as soon as this user was in place we weren't able to push to any newly created repos anymore. At first, we weren't sure where to look, but it turned out to be a problem in Gitolite, which wasn't visible from Gitlab.

I looked at the gitolite config, which seemed fine, but the compiled config didn't. We found out about the error when we cloned the gitolite-admin.git and tried to push back to the server. The error-message was:

rails@git:/tmp/gitolite-admin$ git push
Counting objects: 7, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (4/4), 364 bytes, done.
Total 4 (delta 1), reused 0 (delta 0)
remote: 
remote: ***** ABORTING *****
remote:         bad username '_macdev_example_com_1330350480'
To git@git:gitolite-admin.git
   b8ee8e1..bec4a69  master -> master

Basically, there's two parts to this request:

  • I suppose, it's the leading underscore, that's throwing off gitolite, but that's just speculation. Please make sure, the username is validated according to gitolite's standards.
  • It would be great to have error-messages that arise from gitolite somewhere in Gitlab. Otherwise, you end up chasing errors a few hours (or days) later.
指派人
分配到
工时统计