Gitlab version: 6.6.5 on CentOS 6.7 (yes I need to upgrade - see end of
post)
At some point recently, I realized that all our Jenkins build jobs were not
triggering when code was merged. Today I was doing some testing, and
clicking on any of the "Test Hook" buttons does nothing, but if I take the
URL it calls and request it in a browser, it triggers properly. That let me
know the problem was on the Gitlab side and not the Jenkins side.
Then I deleted the web hooks for a particular project, and started to
recreate them, thinking they might be corrupted somehow. Well, I can no
longer create any web hooks. As soon as I click the "Add Web Hook" button
in Gitlab, I get a 500 error page, and this is the trace I see in the
production log:
Started POST "/connect-lib/lib-vaadin/hooks" for 209.211.140.37 at
2016-04-18 19:00:58 +0000
Processing by Projects::HooksController#create as HTML
Parameters: {"utf8"=>"✓",
"authenticity_token"=>"KCOZ4abci8bHiCngahhxtApNRtRDKvowzjay5YXEGe4=",
"hook"=>{"url"=>"", "push_events"=>"1", "issues_events"=>"0",
"merge_requests_events"=>"0"}, "project_id"=>"connect-lib/lib-vaadin"}
Rendered projects/hooks/index.html.haml within layouts/project_settings
(26.5ms)
Completed 500 Internal Server Error in 151ms
ActionView::Template::Error (No route matches {:action=>"test",
:controller=>"projects/hooks", :project_id=>#<Project id: 827, name:
"lib-vaadin", path: "lib-vaadin", description: "", created_at: "2014-06-04
17:51:07", updated_at: "2014-06-04 17:51:07", creator_id: 34,
issues_enabled: true, wall_enabled: true, merge_requests_enabled: true,
wiki_enabled: true, namespace_id: 41, issues_tracker: "gitlab",
issues_tracker_id: nil, snippets_enabled: true, last_activity_at:
"2016-04-18 17:43:43", imported: false, import_url: "", visibility_level:
0, archived: false>, :id=>#<ProjectHook id: nil, url: "", project_id: 827,
created_at: nil, updated_at: nil, type: "ProjectHook", service_id: nil,
push_events: true, issues_events: false, merge_requests_events: false>,
:format=>nil} missing required keys: [:id]):
51: - @hooks.each do |hook|
52: %li
53: .pull-right
54: = link_to 'Test Hook', test_project_hook_path(@project,
hook), class: "btn btn-small grouped"
55: = link_to 'Remove', project_hook_path(@project, hook),
data: { confirm: 'Are you sure?'}, method: :delete, class: "btn btn-remove
btn-small grouped"
56: .clearfix
57: %span.monospace= hook.url
app/views/projects/hooks/index.html.haml:54:in `block in
_app_views_projects_hooks_index_html_haml___3520384923032099676_69866642072880'
app/views/projects/hooks/index.html.haml:51:in
`_app_views_projects_hooks_index_html_haml___3520384923032099676_69866642072880'
app/controllers/projects/hooks_controller.rb:22:in `create'
app/controllers/application_controller.rb:57:in
`set_current_user_for_thread'
Any ideas what might be causing this, or how I might be able to fix?
To the matter of upgrading. I'd really love to upgrade. Unfortunately the
current version wasn't installed by me, and apparently it was created from
a pre-built VM image running on CentOS 6.7. The previous admin tried
cloning the VM and performing the 6->7.x process, and it completely hosed
everything. I'm not sure what to do at this point. We may end up installing
the latest version on a new (debian-based) machine properly, and then just
importing all the git projects again from scratch. We'd lose all the merge
request and other Gitlab-specific metadata, but at least it would get us
out of the no-upgrade situation we are in. I may inquire about that in a
separate post when I have time to think about upgrading. Right now I just
need to get web hooks working again, if possible.
-Scott
--
You received this message because you are subscribed to the Google Groups
"GitLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to gitlabhq+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/gitlabhq/052dec30-7431-4acd-ad0d-b74e2419d062%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
