Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C950611616 for ; Wed, 17 Sep 2014 08:53:17 +0000 (UTC) Received: (qmail 30038 invoked by uid 500); 17 Sep 2014 08:53:17 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 29997 invoked by uid 500); 17 Sep 2014 08:53:17 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 29985 invoked by uid 99); 17 Sep 2014 08:53:16 -0000 Received: from tyr.zones.apache.org (HELO tyr.zones.apache.org) (140.211.11.114) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Sep 2014 08:53:16 +0000 Received: by tyr.zones.apache.org (Postfix, from userid 65534) id B4BF1A18049; Wed, 17 Sep 2014 08:53:16 +0000 (UTC) From: lsimons To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack pull request: CLOUDSTACK-7143: Refactoring of the syste... Content-Type: text/plain Message-Id: <20140917085316.B4BF1A18049@tyr.zones.apache.org> Date: Wed, 17 Sep 2014 08:53:16 +0000 (UTC) Github user lsimons commented on the pull request: https://github.com/apache/cloudstack/pull/16#issuecomment-55866128 Hey Rohit, like I thought, a ruby issue.....I'm surprised RVM isn't enabled already since the build was already using it (I think...). The fix should be along the lines of http://rvm.io/integration/jenkins . The other part of the fix is making sure that the inline shell scripts act as login scripts so that rvm is loaded, i.e. they need to start with ``` #!/bin/bash -l ``` --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---