UPDATE:

*I HAVE FOUND A SOLUTION!*


It looks like there is a regression in configuration of redis for 
gitlab-ci, in which previous configurations defaulted to redis connections 
being TCP port based, instead of the default socket base now.  
The configuration file 
"/opt/$GITLAB_INSTALL/apps/gitlabci/htdocs/config/initializers/3_sidekiq.rb" 
contains the following, which out of the box will default to 
"redis://localhost:6379":

config_file = Rails.root.join('config', 'resque.yml')
resque_url = if File.exists?(config_file)
               YAML.load_file(config_file)[Rails.env]
             else
               #"redis://localhost:6379"
               "unix:/opt/gitlab-7.4.0-0/redis/var/run/redis.sock"
             end

As you can see above, I have commented out the default "redis://" and added 
my hardcoded path to redis socket, restarted the services and now gitlabci 
builds are launching deployment webhooks successfully.  

This is certainly in need of a patch, as obviously it isn't going to be 
safe to hardcode the port.  IMHO, this configuration should be driven by 
the configuration specified within gitlab configuration.  Can I request a 
patch of configuration files that I can apply to officially get this issue 
fixed for 7.4.0.0?



On Sunday, October 26, 2014 10:57:54 AM UTC-7, Gary Wright wrote:

> Hello All,
>
> I have recently installed Bitnami Gitlab 7.4.0.0 image and was hoping to 
> eventually replace an older version we have been using. So I have 
> configured a new project and attached a webhook address pointing at my 
> current build servers.  The gitlabci build execution of unit tests (a 
> couple of small python-nose assertion tests) completes almost immediately, 
> as I can see the output in the gitlabci web window.  It never moves past 
> this point though and remains in the "running" state for hours, until I go 
> into the gitlabci configuration and remove the webhook address, then it 
> instantly completes successfully.
>
> I have verified from my logs that the webhook webserver has never received 
> a HTTP POST from the gitlab instance during the build, however I can curl 
> and reach my webhook listener server from the new gitlab (fresh Ubuntu 
> 14.04LTS) successfully.
>
> I have noted that within gitlabci, clicking the "cancel" button on the 
> "running" gitlabci build yields a HTTP 500 response, along with clicking 
> the "test webhook" button from within gitlabci settings for the project.  
>
> Here is a snippet of the log " 
> /opt/gitlab-7.4.0-0/apps/gitlabci/gitlabci-runner/logs/gitlabci-runner.log":
>
> 2014-10-26 17:24:49 +0000 | Submitting build 8 to coordinator...aborted
> 2014-10-26 17:24:54 +0000 | Checking for builds...nothing
> 2014-10-26 17:24:59 +0000 | Checking for builds...nothing
> 2014-10-26 17:25:04 +0000 | Checking for builds...nothing
> 2014-10-26 17:25:09 +0000 | Checking for builds...nothing
> 2014-10-26 17:25:14 +0000 | Checking for builds...nothing
> 2014-10-26 17:25:20 +0000 | Checking for builds...nothing
> :100000000                                                               
>                                                                             
>                               
> 2014-10-26 17:34:20 +0000 | Submitting build 9 to coordinator...response 
> error: 500
> 2014-10-26 17:34:20 +0000 | Completed build 9, success.
> 2014-10-26 17:34:20 +0000 | Submitting build 9 to coordinator...response 
> error: 500
> 2014-10-26 17:34:25 +0000 | Submitting build 9 to coordinator...response 
> error: 500
> 2014-10-26 17:34:25 +0000 | Completed build 9, success.
> 2014-10-26 17:34:25 +0000 | Submitting build 9 to coordinator...response 
> error: 500
> 2014-10-26 17:34:31 +0000 | Submitting build 9 to coordinator...response 
> error: 500
> 2014-10-26 17:34:31 +0000 | Completed build 9, success.
> 2014-10-26 17:34:31 +0000 | Submitting build 9 to coordinator...response 
> error: 500
> 2014-10-26 17:34:36 +0000 | Submitting build 9 to coordinator...response 
> error: 500
> 2014-10-26 17:34:36 +0000 | Completed build 9, success.
> 2014-10-26 17:34:36 +0000 | Submitting build 9 to coordinator...response 
> error: 500
> 2014-10-26 17:34:41 +0000 | Submitting build 9 to coordinator...response 
> error: 500
> 2014-<span class="styled-by-prettify" style="color: r
> ...

-- 
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/0d9f4e83-31be-49f5-aaed-21048c958505%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to