Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • slapos slapos
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Merge requests 124
    • Merge requests 124
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedi
  • slaposslapos
  • Merge requests
  • !928

Merged
Created Mar 04, 2021 by Jérome Perrin@jeromeOwner

software/gitlab: unset $GOBIN

  • Overview 3
  • Commits 1
  • Changes 1

gitaly's Makefile forcibly sets $GOPATH to install in _build folder ( here ). Once gitaly is built, it is expected to be in _build/bin/gitaly and copied from there.

With 8eac67a5 (golang: Prepare for future GOPATH removal, 2021-02-26) the env.sh sets GOBIN, to its own $GOPATH/bin

Since gitaly's build does not set $GOBIN, even if it overrides $GOPATH, the final bin/gitaly is not in $GOPATH/bin/gitaly (with $GOPATH from Makefile), but in $GOBIN/gitaly (with $GOBIN from env.sh)

To prevent this, unset $GOBIN before running make, which keeps the old behavior of only using the $GOPATH from the Makefile

Edited Mar 04, 2021 by Jérome Perrin
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: fix/gitlab-gitaly-GOBIN
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7