wish help you to fix your issue Since a 500 error is a server-side error, you should look into /var/log/gitlab in order to see if the logs include any clue. A simpler approach would be to declare an empty project in your GitLab instance, then clone locally a GitHub repo and push it back to that new project, as described here.
hope this fix your issue There are two problems here. Firstly, rvm is normally only loaded by the user's shell and that shell isn't being invoked here. Secondly, bundle won't be in the PATH either. To fix both problems, assuming this is a per-user rvm installation, try this...
... --exec /home/gitlab/.rvm/bin/rvm -- default do bundle exec ...
GitLab-CI Multi Runner can't fetch gitlab repo and returns http error
fixed the issue. Will look into that further The problem is related to the timeout of the unicorn engine workers, that is too short to allow big repositories to be cloned/pushed. in /etc/gitlab/gitlab.rb uncomment and set
unicorn['worker_timeout'] = 1200
# gitlab-ctl reconfigure
# gitlab-ctl restart
Julia Pkg.init() error init ERROR: UndefVarError: init not defined
Hope that helps Pkg.init is not a thing since Julia 0.6. You shouldn't have to do anything to initialize the package manager. Consider using a more up-to-date tutorial, or contribute to the one you were following since you figured out the solution!
helm init Error: error installing: deployments.extensions is forbidden when run inside gitlab runner