Upgrading Ruby to ruby-1.9.3-p327 results in Ruby Version: unknown

Created by: malayamanas

Testing in master branch.

output of bundle exec rake gitlab:env:info RAILS_ENV=production

gitlab@gitlabhost:~/gitlab$ bundle exec rake gitlab:env:info RAILS_ENV=production

System information System: Ubuntu 12.04 Current User: gitlab Using RVM: no Ruby Version: unknown Gem Version: 1.8.23 Bundler Version:1.2.3 Rake Version: 10.0.1

GitLab information Version: 4.0.0pre Revision: d476bc01 Directory: /home/gitlab/gitlab DB Adapter: mysql2 URL: http://gitlabhost.onmobile.com HTTP Clone URL: http://gitlabhost.onmobile.com/some-project.git SSH Clone URL: git@gitlabhost.onmobile.com:some-project.git Using LDAP: no Using Omniauth: no

Gitolite information Version: v3.04-4-g4524f01 Admin URI: git@localhost:gitolite-admin Admin Key: gitlab Repositories: /home/git/repositories/ Hooks: /home/git/.gitolite/hooks/ Git: /usr/bin/git gitlab@gitlabhost:~/gitlab$ ruby --version ruby 1.9.3p327 (2012-11-10 revision 37606) [i686-linux]

Created by: riyad

do you have a RUBY_VERSION environment variable set?

By Administrator on 2012-12-10T17:38:16 (imported from GitLab project)

By Administrator on 2012-12-10T17:38:16 (imported from GitLab)

Created by: riyad

Thank you :)

By Administrator on 2012-12-10T21:59:07 (imported from GitLab project)

By Administrator on 2012-12-10T21:59:07 (imported from GitLab)

Created by: malayamanas

@Riyad

I want to run master branch all the time. What steps will I take after fetching new code. I mean rake task, reverting to old state if it fails.

By Administrator on 2012-12-11T05:13:57 (imported from GitLab project)

By Administrator on 2012-12-11T05:13:57 (imported from GitLab)

Created by: riyad

@malayamanas I wouldn't recommend you to upgrade to master in a production environment at the moment. We still have to write the upgrade documentation. There are some big incompatible changes, so there will be no reverting, sorry. Once you are on 4.0, you can't go back. But the script should be compatible (although I've not tested it on stable) ... you can get it raw and put it into the lib/tasks/gitlab dir yourself.

By Administrator on 2012-12-11T15:46:07 (imported from GitLab project)

By Administrator on 2012-12-11T15:46:07 (imported from GitLab)

Created by: malayamanas

@Riyad I can see the change..now project repositories are per USER. There are lot of UI changes too.

If admin@local.host creates a repository, it resides inside /home/git/repositories/root/$projectName

But we are all worried about GITLAB's stability.

By Administrator on 2012-12-12T03:15:00 (imported from GitLab project)

By Administrator on 2012-12-12T03:15:00 (imported from GitLab)

Created by: dzaporozhets

@malayamanas I care of stability. 4.0 will be ok

By Administrator on 2012-12-13T17:21:43 (imported from GitLab project)

By Administrator on 2012-12-13T17:21:43 (imported from GitLab)

Created by: malayamanas

@randx Thank you for your BIG assurance..

I can not wait upto 22 this month and want to put master in production in two days.. with only one repository of 2.5 GB and 10 users. Will it be OK ?

By Administrator on 2012-12-14T11:58:17 (imported from GitLab project)

By Administrator on 2012-12-14T11:58:17 (imported from GitLab)

Created by: dzaporozhets

@malayamanas Master is still in progress but you may use this rev 44209861 Of course at your own risk

By Administrator on 2012-12-14T12:25:34 (imported from GitLab project)

By Administrator on 2012-12-14T12:25:34 (imported from GitLab)