Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #1546

Closed
Open
Created Sep 24, 2012 by Administrator@rootOwner

Improved Logging for better Correlation with Gitolite

Created by: sroth80021

I recently went through an investigation to figure out why a branch was never merged into master (issue #1544 (closed)), even though GitLab seemed to indicate success. (it says 'branch merged')

Unfortunately, I found it difficult to navigate between the GitLab production.log and the Gitolite logfile. I needed to use timestamps for correlation, which in this case were set for different timezones.

Going forward, one thing which would really help is to have GitLab log a) the commitIDs for major events, such as pushing a branch (accepting a merge). and possibly b) the output from its ssh commands which push to the server.

We have several custom hooks (to protect our repositories), and in one of the pushes from GitLab, we can see the custom hook failed, but without any output, it's unclear what happened. Since GitLab uses SSH to push, I presume the SSH output/stderr would be available for logging(?)

Assignee
Assign to
Time tracking