yum version 3 makes this cookbook to crash. Check https://github.com/opscode-cookbooks/yum/blob/master/CHANGELOG.md#v300

Should we lock to 2.4.4 in the metadata.rb?

Hi,

Still investigating but while running the cookbook (using default attributes), I get an error about an invalid gitlab.pub content which is rendered as empty since the :public_key variable is not set for the erb termplate.

STDOUT:
STDERR: FATAL: errors found before logfile could be created
FATAL: die '/var/git/gitlab.pub' must have exactly one line
---- End output of su - git -c 'perl /var/git/gitolite/src/gitolite setup -pk /var/git/gitlab.pub' ----
Ran su - git -c 'perl /var/git/gitolite/src/gitolite setup -pk /var/git/gitlab.pub' returned 1

So I've added the following to the gitlab.pub template task within the recipe.

variables(
  :public_key => node['gitlab']['public_key']
)

but while it now renders correctly, I might have miss something since I get a problem down the road while performing gitolite setup, which oddly prompt for a password.

Administrator account created:

[email protected]
password......5iveL!fe
git@localhost's password: 

While the installation seems to complete successfully (needs to be run twice), I always get the following error while creating a new project from the interface

GitLab was unable to access your Gitolite system.

which might occurs because of previous permission/pubkeys error.

Thoughts?

In Centos 6.3 64bit the package perl-Time-HiRes is necessary for a successful run of the gitlab::default recipe.

My workaround (before execution of gitlab recipe):

package "perl-Time-HiRes" do
action :install
end

Can you please lock down the version of the redisio cookbook required. Using redisio 1.7.1 it fails. I'm guessing it needs anything better than 2.0

There's a bug if I had install ruby 1.8 package in ubuntu, though the script will install ruby 1.9, it will use 1.8 as default and fail. I think it must switch ruby version before continue.

Why I install ruby 1.8? Because it will be installed by chef apt installation.

I fix it temporarily by using chef gem version with ruby 1.9 package, or specifying ruby version with gitlab['install_ruby'] attribute.

This is the same issue as #52. It looks like missed the inclusion of the sudo cookbook on line 75 in attributes/default.rb. (The case of an unknown platform.)

Hello,

Is this cookbook still supported by somebody?

I am getting the following error on the cookbook:

'''
PTY allocation request failed on channel 0
/usr/bin/env: ruby: Datei oder Verzeichnis nicht gefunden
Connection to gitlab.labor23.org closed.
'''

Seems to be
https://github.com/gitlabhq/gitlab-shell/issues/12

is there a preferred solution fitting to the rvm setup of this cookbook?

Hi,
I have the following error while trying to run "vagrant up" -

[2013-02-26T18:15:55+00:00] INFO: Processing directory[/vagrant/gitlabhq/tmp/repositories] action create (gitlab::vagrant line 125)
[2013-02-26T18:15:55+00:00] INFO: directory[/vagrant/gitlabhq/tmp/repositories] created directory /vagrant/gitlabhq/tmp/repositories
[2013-02-26T18:15:55+00:00] INFO: directory[/vagrant/gitlabhq/tmp/repositories] owner changed to 0

Error executing action create on resource 'directory[/vagrant/gitlabhq/tmp/repositories]'

Errno::EPERM

Operation not permitted - /vagrant/gitlabhq/tmp/repositories

Resource Declaration:

In /tmp/vagrant-chef-1/chef-solo-2/cookbooks/gitlab/recipes/vagrant.rb

124: # share on the virtual machine to the vagrant user.
125: directory "#{node['gitlab']['app_home']}/tmp/repositories" do
126: owner node['gitlab']['host_user_id']
127: group node['gitlab']['host_group_id']
128: mode "0755"
129: recursive true
130: action :create
131: end
132:

Compiled Resource:

Declared in /tmp/vagrant-chef-1/chef-solo-2/cookbooks/gitlab/recipes/vagrant.rb:125:in `from_file'

directory("/vagrant/gitlabhq/tmp/repositories") do
mode "0755"
owner 0
retry_delay 2
path "/vagrant/gitlabhq/tmp/repositories"
retries 0
recipe_name "vagrant"
action [:create]
cookbook_name :gitlab
recursive true
group 0
provider Chef::Provider::Directory
end

[2013-02-26T18:15:55+00:00] ERROR: Running exception handlers
[2013-02-26T18:15:55+00:00] ERROR: Exception handlers complete
[2013-02-26T18:15:55+00:00] FATAL: Stacktrace dumped to /tmp/vagrant-chef-1/chef-stacktrace.out
[2013-02-26T18:15:55+00:00] FATAL: Errno::EPERM: > directory[/vagrant/gitlabhq/tmp/repositories] >(gitlab::vagrant line 125) had an error: Errno::EPERM: Operation not permitted - >/vagrant/gitlabhq/tmp/repositories

I followed the installation instruction from -
https://github.com/gitlabhq/gitlab-vagrant-vm/

I'm overriding the git config file to redirect git protocol requests to use https as this protocol is disabled on our machines.

Error i'm seeing is "STDERR: error: You have local changes to 'doc/workflow/importing/README.md'; cannot switch branches."

Running the cookbook a second time succeeds though.

After cookbook install, Gitlab cannot send emails (e.g. for new account creation, etc). Adding dependency to postfix would fix that.

Add an attribute to allow integration with Redmine.

See:
https://github.com/gitlabhq/gitlabhq/blob/master/config/gitlab.yml.example#L54

it seems that even though we installed ruby 1.9.2 as part of the recipe, it is not being used as default when bundle is run. Bundler is still using 1.8 version on the system which give you a syntax error for the Gemfile

Compiled Resource:
------------------
# Declared in /var/chef/cache/cookbooks/gitlab/recipes/default.rb:241:in `from_file'

execute("gitlab-bundle-rake") do
  cwd "/var/gitlab/gitlab"
  retry_delay 2
  cookbook_name "gitlab"
  backup 5
  command " bundle exec rake gitlab:app:setup RAILS_ENV=production"
  retries 0
  user "gitlab"
  group "gitlab"
  recipe_name "default"
  action "run"
  returns 0
  not_if { #code block }
end

[2012-11-18T03:59:53-05:00] ERROR: Running exception handlers
[2012-11-18T03:59:53-05:00] FATAL: Saving node information to /var/chef/cache/failed-run-data.json
[2012-11-18T03:59:53-05:00] ERROR: Exception handlers complete
[2012-11-18T03:59:53-05:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
[2012-11-18T03:59:53-05:00] FATAL: Mixlib::ShellOut::ShellCommandFailed: execute[gitlab-bundle-rake] (gitlab::default line 241) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '4'
---- Begin output of   bundle exec rake gitlab:app:setup RAILS_ENV=production ----
STDOUT: Gemfile syntax error:
/var/gitlab/gitlab/Gemfile:67: syntax error, unexpected ':', expecting $end
gem "github-markup", "~> 0.7.4", require: 'github/markup'
                                         ^
STDERR:

I am getting an error when trying to install gitolite via chef-solo.

Machine setup

Base CentOS 6.3 x86_64 + Chef 10.14.2 + VirtualBox 4.1.22 (with guest additions) from http://www.vagrantbox.es/

Cookbooks are download by librarian-chef via following Cheffile
https://gist.github.com/4100362

#Chef-solo log
Compiled Resource:
------------------
# Declared in /root/chef-repo/cookbooks/gitlab/recipes/gitolite.rb:64:in `from_file'

execute("gitolite-install") do
  backup 5
  retries 0
  command "/var/git/gitolite/install -ln /var/git/bin"
  cwd "/var/git"
  recipe_name "gitolite"
  returns 0
  action "run"
  cookbook_name :gitlab
  user "git"
  creates "/var/git/bin/gitolite"
  retry_delay 2
end

[2012-11-17T22:01:40+01:00] ERROR: Running exception handlers
[2012-11-17T22:01:40+01:00] ERROR: Exception handlers complete
[2012-11-17T22:01:40+01:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
[2012-11-17T22:01:40+01:00] FATAL: Mixlib::ShellOut::ShellCommandFailed: execute[gitolite-install] (gitlab::gitolite line 64) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '2'
---- Begin output of /var/git/gitolite/install -ln /var/git/bin ----
STDOUT:
STDERR: Can't locate Time/HiRes.pm in @INC (@INC contains: /var/git/gitolite/src/lib /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /var/git/gitolite/src/lib/Gitolite/Common.pm line 76.
BEGIN failed--compilation aborted at /var/git/gitolite/src/lib/Gitolite/Common.pm line 76.
Compilation failed in require at /var/git/gitolite/install line 15.
BEGIN failed--compilation aborted at /var/git/gitolite/install line 15.
---- End output of /var/git/gitolite/install -ln /var/git/bin ----
Ran /var/git/gitolite/install -ln /var/git/bin returned 2

My provision run of the gitlab recipe fails. I'll look in to this issue myself, but since Google didn't turn anything up, I wanted to start some proverbial paper-trail.

Install is on an clean Ubuntu 12.04. Full output of the error:

[2012-11-06T14:38:30+04:00] INFO: Processing execute[gitlab-bundle-rake] action run (gitlab::default line 219)

================================================================================
Error executing action `run` on resource 'execute[gitlab-bundle-rake]'
================================================================================

Mixlib::ShellOut::ShellCommandFailed
------------------------------------
Expected process to exit with [0], but received '1'
---- Begin output of bundle exec rake gitlab:app:setup RAILS_ENV=production ----
STDOUT: 
STDERR: /var/lib/gems/1.9.1/gems/bundler-1.2.1/lib/bundler/spec_set.rb:90:in `block in materialize': Could not find pg-0.14.0 in any of the sources (Bundler::GemNotFound)
    from /var/lib/gems/1.9.1/gems/bundler-1.2.1/lib/bundler/spec_set.rb:83:in `map!'
    from /var/lib/gems/1.9.1/gems/bundler-1.2.1/lib/bundler/spec_set.rb:83:in `materialize'
    from /var/lib/gems/1.9.1/gems/bundler-1.2.1/lib/bundler/definition.rb:113:in `specs'
    from /var/lib/gems/1.9.1/gems/bundler-1.2.1/lib/bundler/definition.rb:158:in `specs_for'
    from /var/lib/gems/1.9.1/gems/bundler-1.2.1/lib/bundler/definition.rb:147:in `requested_specs'
    from /var/lib/gems/1.9.1/gems/bundler-1.2.1/lib/bundler/environment.rb:23:in `requested_specs'
    from /var/lib/gems/1.9.1/gems/bundler-1.2.1/lib/bundler/runtime.rb:11:in `setup'
    from /var/lib/gems/1.9.1/gems/bundler-1.2.1/lib/bundler.rb:116:in `setup'
    from /var/lib/gems/1.9.1/gems/bundler-1.2.1/lib/bundler/setup.rb:17:in `<top (required)>'
    from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
    from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
---- End output of bundle exec rake gitlab:app:setup RAILS_ENV=production ----
Ran bundle exec rake gitlab:app:setup RAILS_ENV=production returned 1

Resource Declaration:
---------------------
# In /var/chef/cache/cookbooks/gitlab/recipes/default.rb

219: execute "gitlab-bundle-rake" do
220:   command "bundle exec rake gitlab:app:setup RAILS_ENV=production"
221:   cwd node['gitlab']['app_home']
222:   user node['gitlab']['user'] 
223:   group node['gitlab']['group']
224:   not_if { File.exists?("#{node['gitlab']['app_home']}/db/production.sqlite3") }
225: end
226: 

Compiled Resource:
------------------
# Declared in /var/chef/cache/cookbooks/gitlab/recipes/default.rb:219:in `from_file'

execute("gitlab-bundle-rake") do
  action "run"
  retries 0
  retry_delay 2
  command "bundle exec rake gitlab:app:setup RAILS_ENV=production"
  backup 5
  cwd "/var/gitlab/gitlab"
  group "gitlab"
  returns 0
  user "gitlab"
  cookbook_name "gitlab"
  recipe_name "default"
  not_if { #code block }
end

[2012-11-06T14:38:32+04:00] ERROR: Running exception handlers
[2012-11-06T14:38:32+04:00] FATAL: Saving node information to /var/chef/cache/failed-run-data.json
[2012-11-06T14:38:32+04:00] ERROR: Exception handlers complete
[2012-11-06T14:38:32+04:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
[2012-11-06T14:38:32+04:00] FATAL: Mixlib::ShellOut::ShellCommandFailed: execute[gitlab-bundle-rake] (gitlab::default line 219) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
---- Begin output of bundle exec rake gitlab:app:setup RAILS_ENV=production ----
STDOUT: 
STDERR: /var/lib/gems/1.9.1/gems/bundler-1.2.1/lib/bundler/spec_set.rb:90:in `block in materialize': Could not find pg-0.14.0 in any of the sources (Bundler::GemNotFound)
    from /var/lib/gems/1.9.1/gems/bundler-1.2.1/lib/bundler/spec_set.rb:83:in `map!'
    from /var/lib/gems/1.9.1/gems/bundler-1.2.1/lib/bundler/spec_set.rb:83:in `materialize'
    from /var/lib/gems/1.9.1/gems/bundler-1.2.1/lib/bundler/definition.rb:113:in `specs'
    from /var/lib/gems/1.9.1/gems/bundler-1.2.1/lib/bundler/definition.rb:158:in `specs_for'
    from /var/lib/gems/1.9.1/gems/bundler-1.2.1/lib/bundler/definition.rb:147:in `requested_specs'
    from /var/lib/gems/1.9.1/gems/bundler-1.2.1/lib/bundler/environment.rb:23:in `requested_specs'
    from /var/lib/gems/1.9.1/gems/bundler-1.2.1/lib/bundler/runtime.rb:11:in `setup'
    from /var/lib/gems/1.9.1/gems/bundler-1.2.1/lib/bundler.rb:116:in `setup'
    from /var/lib/gems/1.9.1/gems/bundler-1.2.1/lib/bundler/setup.rb:17:in `<top (required)>'
    from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
    from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
---- End output of bundle exec rake gitlab:app:setup RAILS_ENV=production ----
Ran bundle exec rake gitlab:app:setup RAILS_ENV=production returned 1

Please add support for setting the user_filter ldap setting in the gitlab.yml config file, such that i can specify:
node.default['gitlab']['ldap']['user_filter'] = '(memberOf=cn=group1,dc=subdom,dc=example,dc=com)'

Mysql cookbook >= 5.0.0 does not have ruby recipe. Set cookbook dependency to mysql <=4.1.2 or upgrade to be compliant with 5.0.0 release.

See:
include_recipe 'mysql::ruby' in mysql.rb

I use RHEL6, my /etc/sudoers is set with default value:

Defaults requiretty

When I redirect the console output to a log file and run chef-client in cloud-init to install gitlab (cookbook version 6.4.6), it fails to start gitlab service at the last step:

Mixlib::ShellOut::ShellCommandFailed
------------------------------------
Expected process to exit with [0], but received '1'
---- Begin output of /sbin/service gitlab start ----
STDOUT: 
STDERR: sudo: sorry, you must have a tty to run sudo
---- End output of /sbin/service gitlab start ----
Ran /sbin/service gitlab start returned 1

After google, I found a page reported similar issue at https://github.com/WASdev/ci.chef.wlp/issues/9%E2%80%8E

Hence I change the template file gitlab.init.erb from

# Switch to the app_user if it is not he/she who is running the script.
if [ "$USER" != "$app_user" ]; then
  sudo -u "$app_user" -H -i $0 "$@"; exit;
fi

to

# Switch to the app_user if it is not he/she who is running the script.
if [ "$USER" != "$app_user" ]; then
  exec su - "$app_user" -- $0 "$@"; exit;
fi

it seems to slove my problem.

Which repository is mysql++ from? Doesn't seem to be in the default repos on CentOS 6.3:

================================================================================
Error executing action `install` on resource 'package[mysql++-devel]'
================================================================================

Chef::Exceptions::Package
-------------------------
No version specified, and no candidate version available for mysql++-devel

Resource Declaration:
---------------------
# In /tmp/chef-solo/cookbooks/gitlab/recipes/default.rb

 55:   package pkg
 56: end

Compiled Resource:
------------------
# Declared in /tmp/chef-solo/cookbooks/gitlab/recipes/default.rb:55:in `block in from_file'

package("mysql++-devel") do
  action :install
  retries 0
  retry_delay 2
  package_name "mysql++-devel"
  cookbook_name :gitlab
  recipe_name "default"
end

The default cookbook install uses sqlite, but this support was removed in gitlab 4.0, so a default install fails when it attempts to link the sample database.sqlite file to database.yml.

Using this cookbook with on Vagrant with the following box:

config.vm.box_url = "https://dl.dropbox.com/u/31081437/Berkshelf-CentOS-6.3-x86_64-minimal.box"

It crashes with the error: Could not find rake-10.1.0 in any of the sources (Bundler::GemNotFound), when running the resource execute 'gitlab-bundle-precompile-assets'. Please find the full stacktrace below.

I think the problem is that the resource execute 'gitlab-bundle-install' should be the very first thing after cloning the gitlab repo, before execute 'gitlab-bundle-precompile-assets'. I wonder in your case works because the boxes you use for testing already include rake and the required dependencies.

So far I workaround the problem using a wrapper-cookbook that subscribes the bundle install to the git clone:

include_recipe "mysql::server"
include_recipe "gitlab::default"
resources("execute[gitlab-bundle-install]").subscribes :run, "git[#{node['gitlab']['app_home']}]", :immediately

Stacktrace output:

================================================================================
Error executing action `run` on resource 'execute[gitlab-bundle-precompile-assets]'
================================================================================

Mixlib::ShellOut::ShellCommandFailed
------------------------------------
Expected process to exit with [0], but received '1'
---- Begin output of bundle exec rake assets:precompile RAILS_ENV=production ----
STDOUT: 
STDERR: /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/bundler-1.1.5/lib/bundler/spec_set.rb:90:in `block in materialize': Could not find rake-10.1.0 in any of the sources (Bundler::GemNotFound)
    from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/bundler-1.1.5/lib/bundler/spec_set.rb:83:in `map!'
    from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/bundler-1.1.5/lib/bundler/spec_set.rb:83:in `materialize'
    from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/bundler-1.1.5/lib/bundler/definition.rb:127:in `specs'
    from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/bundler-1.1.5/lib/bundler/definition.rb:172:in `specs_for'
    from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/bundler-1.1.5/lib/bundler/definition.rb:161:in `requested_specs'
    from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/bundler-1.1.5/lib/bundler/environment.rb:23:in `requested_specs'
    from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/bundler-1.1.5/lib/bundler/runtime.rb:11:in `setup'
    from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/bundler-1.1.5/lib/bundler.rb:107:in `setup'
    from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/bundler-1.1.5/lib/bundler/setup.rb:17:in `<top (required)>'
    from /opt/chef/embedded/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
    from /opt/chef/embedded/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
---- End output of bundle exec rake assets:precompile RAILS_ENV=production ----
Ran bundle exec rake assets:precompile RAILS_ENV=production returned 1

Resource Declaration:
---------------------
# In /tmp/vagrant-chef-1/chef-solo-1/cookbooks/gitlab/recipes/default.rb

208: # Precompile assets
209: execute 'gitlab-bundle-precompile-assets' do
210:   command 'bundle exec rake assets:precompile RAILS_ENV=production'
211:   cwd node['gitlab']['app_home']
212:   user node['gitlab']['user']
213:   group node['gitlab']['group']
214:   environment('LANG' => 'en_US.UTF-8', 'LC_ALL' => 'en_US.UTF-8')
215:   only_if { Dir["#{node['gitlab']['app_home']}/public/assets/*"].empty? }
216: end
217: 

Compiled Resource:
------------------
# Declared in /tmp/vagrant-chef-1/chef-solo-1/cookbooks/gitlab/recipes/default.rb:209:in `from_file'

execute("gitlab-bundle-precompile-assets") do
  action "run"
  retries 0
  retry_delay 2
  command "bundle exec rake assets:precompile RAILS_ENV=production"
  backup 5
  cwd "/srv/git/gitlab"
  environment {"LANG"=>"en_US.UTF-8", "LC_ALL"=>"en_US.UTF-8"}
  group "git"
  returns 0
  user "git"
  cookbook_name :gitlab
  recipe_name "default"
  only_if { #code block }
end

[2014-02-07T14:14:18+00:00] ERROR: Running exception handlers
[2014-02-07T14:14:18+00:00] ERROR: Exception handlers complete
[2014-02-07T14:14:18+00:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
[2014-02-07T14:14:18+00:00] FATAL: Mixlib::ShellOut::ShellCommandFailed: execute[gitlab-bundle-precompile-assets] (gitlab::default line 209) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
---- Begin output of bundle exec rake assets:precompile RAILS_ENV=production ----
STDOUT: 
STDERR: /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/bundler-1.1.5/lib/bundler/spec_set.rb:90:in `block in materialize': Could not find rake-10.1.0 in any of the sources (Bundler::GemNotFound)
    from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/bundler-1.1.5/lib/bundler/spec_set.rb:83:in `map!'
    from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/bundler-1.1.5/lib/bundler/spec_set.rb:83:in `materialize'
    from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/bundler-1.1.5/lib/bundler/definition.rb:127:in `specs'
    from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/bundler-1.1.5/lib/bundler/definition.rb:172:in `specs_for'
    from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/bundler-1.1.5/lib/bundler/definition.rb:161:in `requested_specs'
    from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/bundler-1.1.5/lib/bundler/environment.rb:23:in `requested_specs'
    from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/bundler-1.1.5/lib/bundler/runtime.rb:11:in `setup'
    from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/bundler-1.1.5/lib/bundler.rb:107:in `setup'
    from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/bundler-1.1.5/lib/bundler/setup.rb:17:in `<top (required)>'
    from /opt/chef/embedded/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
    from /opt/chef/embedded/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
---- End output of bundle exec rake assets:precompile RAILS_ENV=production ----
Ran bundle exec rake assets:precompile RAILS_ENV=production returned 1
Chef never successfully completed! Any errors should be visible in the
output above. Please fix your recipes so that they properly complete.

https://gist.github.com/3832281

Any hint?

The ports are not completely forwarded. Only the last defined one in .kitchen.yml (443 => ) is visible in virtualbox graphic client.

Any ideas if there is a new syntax in driver configuration on kitchen-vagrant?

I have run a pip install pygments and it pass manually.

[2013-01-24T15:56:00+01:00] FATAL: Saving node information to /var/chef/cache/failed-run-data.json
chef client failed. 107 resources updated
[2013-01-24T15:56:00+01:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
[2013-01-24T15:56:00+01:00] FATAL: Mixlib::ShellOut::ShellCommandFailed: python_pip[pygments](gitlab::default line 76) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
---- Begin output of pip freeze | grep -i '^pygments==' ----
STDOUT:
STDERR:
---- End output of pip freeze | grep -i '^pygments==' ----
Ran pip freeze | grep -i '^pygments==' returned 1

The Chef deploy resource is inspired by Capistrano and would allow us to continually upgrade by just performing another Chef run. It would take care of running bundle install, rake assets:precompile, and rake db:migrate. This approach is successfully used by the Errbit cookbook. Please see my fork for the best example.

At:
https://github.com/atomic-penguin/cookbook-gitlab/blob/ae4ee230be9b05228e64959d6788b31b468a48be/recipes/default.rb#L53

execute "#{username}: disable password expiration" do
  #command "chage -M -1 '#{username}'"
  command "chage --lastday 0 --expiredate -1 --inactive -1 --mindays 0 --maxdays 99999 --warndays 7 #{username}"
  only_if do
    require 'shadow'
    Shadow::Passwd.getspnam(username).sp_max != -1 }
  end
end

STDERR: the primary link for ruby must be /usr/bin/ruby
aws_instance.gitlab (chef): ---- End output of update-alternatives --install /usr/local/bin/ruby ruby /srv/git/bin/ruby 10 ----
aws_instance.gitlab (chef): Ran update-alternatives --install /usr/local/bin/ruby ruby /srv/git/bin/ruby 10 returned 2
aws_instance.gitlab (chef): Resource Declaration:
aws_instance.gitlab (chef): ---------------------
aws_instance.gitlab (chef): # In /var/chef/cache/cookbooks/gitlab/recipes/default.rb
aws_instance.gitlab (chef):
aws_instance.gitlab (chef): 107: execute 'update-alternatives-ruby' do
aws_instance.gitlab (chef): 108: command "update-alternatives --install /usr/local/bin/ruby ruby #{node['gitlab']['install_ruby_path']}/bin/ruby 10"
aws_instance.gitlab (chef): 109: not_if { ::File.exist?('/usr/local/bin/ruby') }
aws_instance.gitlab (chef): 110: end
aws_instance.gitlab (chef): 111:
aws_instance.gitlab (chef):
aws_instance.gitlab (chef): Compiled Resource:
aws_instance.gitlab (chef): ------------------
aws_instance.gitlab (chef): # Declared in /var/chef/cache/cookbooks/gitlab/recipes/default.rb:107:in `from_file'
aws_instance.gitlab (chef):
aws_instance.gitlab (chef): execute("update-alternatives-ruby") do
aws_instance.gitlab (chef): action [:run]
aws_instance.gitlab (chef): retries 0
aws_instance.gitlab (chef): retry_delay 2
aws_instance.gitlab (chef): default_guard_interpreter :execute
aws_instance.gitlab (chef): command "update-alternatives --install /usr/local/bin/ruby ruby /srv/git/bin/ruby 10"
aws_instance.gitlab (chef): backup 5
aws_instance.gitlab (chef): returns 0
aws_instance.gitlab (chef): declared_type :execute
aws_instance.gitlab (chef): cookbook_name "gitlab"
aws_instance.gitlab (chef): recipe_name "default"
aws_instance.gitlab (chef): not_if { #code block }
aws_instance.gitlab (chef): end
aws_instance.gitlab (chef):

I am wondering how can I increase the server_names_hash_bucket_size I do not see any attribute to change the bucket_size.

nginx: [emerg] could not build the server_names_hash, you should increase server_names_hash_bucket_size: 64

If I make any change to any file in the cookbook the cookbook will fail. is this done on purpose? I need to add something to the .gitconfig template but this is preventing me from adding anything. Is there a way around this?

I get this error: Missing setting 'web' in /var/gitlab/gitlab/config/gitlab.yml

The gitlab.yml.erb template needs to be updated: https://github.com/gitlabhq/gitlabhq/blob/master/config/gitlab.yml.example

This is using the stable 2.7 branch of gitlab.

Frontier Airlines is a low-cost airline that offers flights to destinations throughout the United States, Canada, and Mexico. If you have a question or issue with your flight, you can contact Frontier Airlines en Español at +1-860-364-8556 customer service.

How to Contact Frontier

Frontier no longer has a customer service phone line. You can contact Frontier through the following channels:

• Live chat: You can chat with a Frontier representative 24/7 on their website.
• Social media: You can contact Frontier on Twitter, Facebook, or Instagram.
• WhatsApp: You can message Frontier on WhatsApp.
• Email: You can send an email to Frontier customer service.

Tips for Talking to a Frontier Representative

Here are some tips for talking to a Frontier representative:

• Be prepared: Before you contact Frontier, gather all of the information you need, such as your flight number, reservation number, and the nature of your issue.
• Be clear and concise: When you explain your issue, be clear and concise. The representative will be able to help you more quickly if you can explain your issue clearly and concisely.
• Be patient: It may take some time to get in touch with a representative, so be patient.

Here are some additional tips:

• Use the Frontier website or app to start a chat. This is the quickest way to get in touch with a representative.
• If you are contacting Frontier on social media, use the hashtag #AskFrontier. This will help ensure that a representative sees your message.
• If you are emailing Frontier, be sure to include your name, contact information, and flight information in the subject line. This will help the representative quickly identify your issue and respond to you.

everything except character set is se to be utf8 or unicode (on postgre). However database for a gitlab is being created as latin1. This explicitely rule-out the other encodings, however rest of the mysql deployment is configured to use utf8.

Anybody know how to specify a database character encoding during gitlab deploy?

mysql> show variables like 'char%';
+--------------------------+----------------------------+
| Variable_name            | Value                      |
+--------------------------+----------------------------+
| character_set_client     | utf8                       |
| character_set_connection | utf8                       |
| character_set_database   | latin1                     |

Hi, gitlab-shell binary have the header: #!/usr/bin/env ruby

#!/usr/bin/env ruby

unless ENV['SSH_CONNECTION']
  puts "Only ssh allowed"
  exit
end

require_relative '../lib/gitlab_init'

#
#
# GitLab shell, invoked from ~/.ssh/authorized_keys
#
#
require File.join(ROOT_PATH, 'lib', 'gitlab_shell')
GitlabShell.new.exec

exit

But the ruby is installed on git_home/bin so whe you try a clone it will fail:

Cloning into 'your_repo_name'...
/usr/bin/env: ruby: No such file or directory
fatal: Could not read from remote repository.

Anyone can reproduce?

Hello,

I want to install rvm on my server using chef, how can I use this cookbook with the version of ruby from rvm?

Thank you

I propose we make the cookbook into more than one.

There should be one "base" cookbook that would deploy the app without provisioning any dependency deamon/infrastructure.

This is good in many ways as people have different opinions on how to provisioning things, and will make it more reusable.

Some ideas:

• GitLab-base - install ruby / deploys the app to specified folder, configure database/redis yaml based on attributes
• GitLab-local - depends on GitLab-base, install redis / postgres or mysql / nginx (all on the same machine)
• GitLab-HA - depends on GitLab-base, install and provision a HA setup using multiple machines, etc
• GitLab-AWS - depends on GitLab-base, provision AWS managed services and changes base's attributes to match these values

By refactoring it to this style, we can cleanup cookbook, and people can reuse it with their own infra-structure requirements.

When installing the gitlab cookbook using 'knife supermarket install gitlab', the install crashes due to an error in a deprecated cookbook, zlib:

user@host:~/chef/repo/cookbooks$ knife supermarket install gitlab
Installing gitlab to /home/user/chef/repo/cookbooks
Checking out the master branch.
Pristine copy branch (chef-vendor-gitlab) exists, switching to it.
Downloading gitlab from Supermarket at version 7.7.1 to /home/user/chef/repo/cookbooks/gitlab.tar.gz
Cookbook saved:
...
Checking out the master branch.
Installing zlib to /home/user/chef/repo/cookbooks
Checking out the master branch.
Pristine copy branch (chef-vendor-zlib) exists, switching to it.
ERROR: TypeError: no implicit conversion of nil into String

Currently zlib is officially deprecated and other cookbooks with lack of updates listed in the metadata.rb. Probably this should be cleaned up as there's no way to actually use this cookbook right now without doing a workaround.

https://gist.github.com/3838511

it looks whether there is a further error. when i create this file it the chef run works.

Regards,

Hans

After the cookbook installs GitLab and all related packages, it fails to start via the provided init.d script on Ubuntu 14.04. The issue is that bundle isn’t in the PATH. The solution is to either extend the PATH variable in the init script (PATH="$PATH:/srv/git/bin") or to create a symbolic link inside a PATH folder to the bundle command:

link "/usr/local/bin/bundle" do
  to "/srv/git/bin/bundle"
end

In templates/default/gitlab.yml.erb

  ## GitLab settings
  gitlab:
    ## Web server settings
    host: <%= @fqdn %>
    port: <%= @port %>
    https: <%= @https_boolean %>

The <%= @port %> is always empty because there is no such variable defined. Instead it should have been <%= node['gitlab']['listen_port'] %>.

Things that breaks due to this includes:

1. The HTTPS git repository URL generated in the project overview page does not include the port number
2. Pushing through the git HTTPS URL fails even after adding the port number

on ubuntu 12.04 (did not tested others) the /etc/sudores file gets changed while using this cookbook (it's set back to only allow root access to root). This breaks the server pretty much since root access is disabled by default.

@JohannesBecker

I have made some changes over the weekend. This converges for me on RHEL6, however the init script does not properly bring up gitlab. I have added a test-kitchen skeleton to the target-6-1-stable branch. Please see if there are any issues pending for Ubuntu 13, which need to be addressed prior to release.

* Add certificate/key for integration testing
* Build 1.9.3-p448 per Gitlab requirements.md
* Add no-ri/no-rdoc options, per installation.md,
  also speeds up convergence.
* Re-order steps per installation.md
* Add autocrlf option to gitconfig, per installation.md
* Update mysql privileges per database.md

TODO:

* Gitlab init not working on RHEL 6
* Update README.md

EDIT: clarification, the init script does not work properly on RHEL6.

Hello guys,

Today, I started to test this amazing recipe (that saved me some days of work here). But I want to report a tricky error with the admin default e-mail.

As seen on initial readme, at cookbook homepage, the dev says that the initial admin user is [email protected]. After some time after banging my head, thinking what I did wrong, I ran the following command (logged as git user on terminal)

~/bin/bundle exec rake db:seed_fu RAILS_ENV=production

It returned:

== Seed from /srv/git/gitlab/db/fixtures/production/001_admin.rb
rake aborted!
ActiveRecord::RecordInvalid: Validation failed: Email has already been taken, Email has already been taken, Username has already been taken, Username already exists
(eval):22:in `block (2 levels) in run_file'
Tasks: TOP => db:seed_fu
(See full trace by running task with --trace)

Okay, so see that the user was created successfully. So, I toke a look at /srv/git/gitlab/db/fixtures/production/001_admin.rb

So, due this, I saw the real e-mail, set as [email protected].

admin = User.create(
email: "[email protected]",
(... snip...)

Maybe, I'm wondering that it's just a matter to correct this mistake(type). I'm posting this issue, just to notice the dev, btw.

Att,

Whe i try to test with kitchen ubuntu 12.04 it doesnt works with redisio > 1.7.1

================================================================================       
Recipe Compile Error in /tmp/kitchen/cookbooks/gitlab/recipes/default.rb       
================================================================================       


NoMethodError       
-------------       
undefined method `each' for nil:NilClass       


Cookbook Trace:       
---------------       
  /tmp/kitchen/cookbooks/redisio/recipes/enable.rb:23:in `from_file'       
  /tmp/kitchen/cookbooks/gitlab/recipes/default.rb:40:in `block in from_file'       
  /tmp/kitchen/cookbooks/gitlab/recipes/default.rb:39:in `each'       
  /tmp/kitchen/cookbooks/gitlab/recipes/default.rb:39:in `from_file'       


Relevant File Content:       
----------------------       
/tmp/kitchen/cookbooks/redisio/recipes/enable.rb:       

 16:  # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.       
 17:  # See the License for the specific language governing permissions and       
 18:  # limitations under the License.       
        19:  #
        20:  
        21:  redis = node['redisio']
        22:  
        23>> redis['servers'].each do |current_server|
        24:    server_name = current_server["name"] || current_server["port"]
        25:    resource = resources("service[redis#{server_name}]")
        26:    resource.action Array(resource.action)
        27:    resource.action << :start
        28:    resource.action << :enable
        29:  end
        30:  


       [2014-11-11T13:18:54+00:00] ERROR: Running exception handlers

[2014-11-11T13:18:54+00:00] ERROR: Exception handlers complete       
       [2014-11-11T13:18:54+00:00] FATAL: Stacktrace dumped to /tmp/kitchen/cache/chef-stacktrace.out

Chef Client failed. 0 resources updated       
[2014-11-11T13:18:54+00:00] ERROR: undefined method `each' for nil:NilClass       
[2014-11-11T13:18:54+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)

Like a charm with redisio 1.7.1

I found the solution and feel foolish.

On the recipe you use the gitlab.database.password attribute:

# Write the database.yml
template "#{node['gitlab']['app_home']}/config/database.yml" do                                                       
  source 'database.yml.erb'
  owner node['gitlab']['user']
  group node['gitlab']['group']                                                                                       
  mode '0644'                                                                                                         
  variables(
      adapter: node['gitlab']['database']['adapter'],
      encoding: node['gitlab']['database']['encoding'],                                                               
      host: node['gitlab']['database']['host'],
      database: node['gitlab']['database']['database'],                                                               
      pool: node['gitlab']['database']['pool'],
      username: node['gitlab']['database']['username'],                                                               
      password: node['gitlab']['database']['password']                                                                
  )                                                                                                                   
end                                                                                  

But there is no such attribute on defaults.rb, should i need to create database manually and set the password on an encrypted databag and put it on an attribute throug a recipe or what?

First time installing gitlab, so sorry if im asking something onvious

I tried to use the following cookbook to provision a Vagrant machine but unfortunately it didn't work. One of the main reasons this happened is because this cookbook sets by default:

node['gitlab']['branch'] = 'stable'

This branch is constantly updated with the most up-to-date stable version of gitlab. Some changes are introduced from version to version, but cookbook-gitlab doesn't follow those changes ending up with the problem mentioned above. What I suggest is that node['gitlab']['branch'] should be fixed to one specific branch in attributes/default.rb, for example 3.1-stable. This way we can lock all dependencies and be sure that we can reproduce an exact state.

Whenever a new version of gitlab is released, cookbook-gitlab could make the necessary changes in a separate branch and bump the version. When the new pair of gitlab and cookbook-gitlab are tested to be working properly, merge it to master.

And of course, I am willing to help in everything is necessary to make such change. ;)

Hello,

yumrepo cookbook no longer has an epel recipe and is now using yum::epel recipe for rhel platform family. As such, it should not be explicitly included in default recipe.

Best regards

I am working on a refactor that is cross platform and uses the omnibus install. Gitlab provides a cookbook for this, but I think it could be more cross platform and not depend on data bags.

Here is the gitlab one: https://gitlab.com/gitlab-org/cookbook-omnibus-gitlab

Eric, any plans to update this cookbook to latest gitlab?

As of omnibus is now an official install method and a chef cookbook exist to employ it https://gitlab.com/gitlab-org/cookbook-omnibus-gitlab/blob/master/README.md (even not properly updated)

Optionally does anybody has any comments what's needed to switch from this cookbook to the cookbook-omnibus-gitlab?

Thanks