[ 
https://issues.jenkins-ci.org/browse/JENKINS-7947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163199#comment-163199
 ] 

Florian Villard commented on JENKINS-7947:
------------------------------------------

I have the same problem, did someone manage to fix it ?

thanks
                
> Rake plugin can't always find Rake with rvm installed
> -----------------------------------------------------
>
>                 Key: JENKINS-7947
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-7947
>             Project: Jenkins
>          Issue Type: Bug
>          Components: rake
>    Affects Versions: current
>         Environment: Ubuntu Linux Version 9.04
> Hudson 1.381
> Rake Plugin 1.7.1
> rvm installed globally under /usr/local/rvm
>            Reporter: ranlauf
>            Assignee: david_calavera
>
> With rvm installed globally for all users, the rake plugin has difficulties 
> to find rake when using gemsets.
> RVM is installed as a global installation under /usr/local/rvm with the 
> global /etc/bash.bashrc script modified as advised in the rvm documentation.
> Hudson is running under the tomcat6 user, which has no own bashrc script, 
> since it's a no-login account.
> The "rvm installation path" is set to /usr/local/rvm in the plugin 
> configuration via the Web Interface (Hudson Configuration => System 
> Configuration), and rvm installation (including gemsets) are recognized, 
> since I can choose them in the rake version dropdown in the project 
> configuration.
> However, when I choose a rake version with a gemset, (say 
> ruby-1.8.7-p302@my_rails3_gemset), Hudson reports "FATAL: 
> /usr/local/rvm/bin/rake doesn't exist".
> Issuing the following commands from the Linux shell produces the following 
> output:
> {noformat}
> > rvm ruby-1.8.7-p302@my_rails3_gemset
> > which ruby
> # /usr/local/rvm/rubies/ruby-1.8.7-p302/bin/ruby
> > which rake
> # /usr/local/rvm/gems/ruby-1.8.7-p302@my_rails3_gemset/bin/rake
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to