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
  • #9409

Closed
Open
Created Jun 24, 2015 by Administrator@rootOwner

Web UI + custom hook + ruby

Created by: iakovgan

Hi, I need to use some ruby tools from custom hook and i find that ruby bahaves differently for commits made from Web-UI and classic http/ssh push.

Ruby script shows varios exceptions, generally related to the fact that some ruby gems are not found. The issue appears only for Web-UI commits.

I used following workaround for this issue:

# my .../custom_hooks/post-receive:
# clean up GitLab Web-UI env variables 
unset GEM_PATH
unset RUBYOPT

# start my ruby tool.
...

This works fine, but still this is a workaround for an unexpected GitLab behavoir. Can GitLab Web-UI clean up env varibles before calling custom_hook script?

Regards, Iakov

Assignee
Assign to
Time tracking