Can't run Jenkins Build - bundle: “command not found”
up vote
11
down vote
favorite
I am currently trying to run a jenkins build for some of my cucumber tasks. All of my gems have been installed by using the Bundler. The gems are stored in the vendor folder.
However, when I try and run bundle install --deployment
in the execute shell build step, I get the following error:
Started by user anonymous
Building in workspace /Users/Shared/Jenkins/Home/jobs/cukes/workspace
[workspace] $ /bin/sh -xe/var/folders/zz/zyxvpxvq6csfxvn_n0000004000001/T/hudson4461284045505361460.sh
+ bundle install --deployment
/var/folders/zz/zyxvpxvq6csfxvn_n0000004000001/T/hudson4461284045505361460.sh: line 2: bundle: command not found
Build step 'Execute shell' marked build as failure
Finished: FAILURE
This is driving me crazy! It runs on my local machine with no problems. Why can't Jenkins see my gems?
Any help would be great!
Cheers,
Jon
ruby cucumber jenkins bundler
add a comment |
up vote
11
down vote
favorite
I am currently trying to run a jenkins build for some of my cucumber tasks. All of my gems have been installed by using the Bundler. The gems are stored in the vendor folder.
However, when I try and run bundle install --deployment
in the execute shell build step, I get the following error:
Started by user anonymous
Building in workspace /Users/Shared/Jenkins/Home/jobs/cukes/workspace
[workspace] $ /bin/sh -xe/var/folders/zz/zyxvpxvq6csfxvn_n0000004000001/T/hudson4461284045505361460.sh
+ bundle install --deployment
/var/folders/zz/zyxvpxvq6csfxvn_n0000004000001/T/hudson4461284045505361460.sh: line 2: bundle: command not found
Build step 'Execute shell' marked build as failure
Finished: FAILURE
This is driving me crazy! It runs on my local machine with no problems. Why can't Jenkins see my gems?
Any help would be great!
Cheers,
Jon
ruby cucumber jenkins bundler
add a comment |
up vote
11
down vote
favorite
up vote
11
down vote
favorite
I am currently trying to run a jenkins build for some of my cucumber tasks. All of my gems have been installed by using the Bundler. The gems are stored in the vendor folder.
However, when I try and run bundle install --deployment
in the execute shell build step, I get the following error:
Started by user anonymous
Building in workspace /Users/Shared/Jenkins/Home/jobs/cukes/workspace
[workspace] $ /bin/sh -xe/var/folders/zz/zyxvpxvq6csfxvn_n0000004000001/T/hudson4461284045505361460.sh
+ bundle install --deployment
/var/folders/zz/zyxvpxvq6csfxvn_n0000004000001/T/hudson4461284045505361460.sh: line 2: bundle: command not found
Build step 'Execute shell' marked build as failure
Finished: FAILURE
This is driving me crazy! It runs on my local machine with no problems. Why can't Jenkins see my gems?
Any help would be great!
Cheers,
Jon
ruby cucumber jenkins bundler
I am currently trying to run a jenkins build for some of my cucumber tasks. All of my gems have been installed by using the Bundler. The gems are stored in the vendor folder.
However, when I try and run bundle install --deployment
in the execute shell build step, I get the following error:
Started by user anonymous
Building in workspace /Users/Shared/Jenkins/Home/jobs/cukes/workspace
[workspace] $ /bin/sh -xe/var/folders/zz/zyxvpxvq6csfxvn_n0000004000001/T/hudson4461284045505361460.sh
+ bundle install --deployment
/var/folders/zz/zyxvpxvq6csfxvn_n0000004000001/T/hudson4461284045505361460.sh: line 2: bundle: command not found
Build step 'Execute shell' marked build as failure
Finished: FAILURE
This is driving me crazy! It runs on my local machine with no problems. Why can't Jenkins see my gems?
Any help would be great!
Cheers,
Jon
ruby cucumber jenkins bundler
ruby cucumber jenkins bundler
edited Apr 28 '12 at 18:38
Savara
1397
1397
asked Apr 28 '12 at 17:20
Jonathan Chrisp
1181214
1181214
add a comment |
add a comment |
5 Answers
5
active
oldest
votes
up vote
11
down vote
Depending on the way you installed Jenkins, it might be running as a separate user, typically as user jenkins
. If you have installed bundle
into a nonstandard directory which isn't in the default PATH, like /usr/local/bin
, you need to:
- Add
/usr/local/bin
to the PATH of the jenkins user (check ~jenkins/.bashrc) or - Configure PATH environment variable in Jenkins global configuration (or slave configuration if building on a slave) or
- Modify the build script to refer to
bundle
using a full path name.
Hi, i added /bin/bash instead /usr/bin/bash was not available. I am using centos.
– Chetan kapoor
Jul 14 '17 at 9:28
add a comment |
up vote
3
down vote
If bundle is installed in /usr/local/bin/bundle
(determine this with which bundle
) you could just add a symbolic link to bundle in /usr/bin
like so:
ln -s /usr/local/bin/bundle /usr/bin/bundle
add a comment |
up vote
2
down vote
First things to verify:
- Make sure
bundle
is installed on the machine where Jenkins runs. - If it installed, make sure it's on the path for the user under which Jenkins runs
(To verify path/environment: insert shell build step that runs env
)
add a comment |
up vote
0
down vote
For me I had originally installed it via the war file as that's the way recommended on the Getting Started Guide. However, the user handbook makes it much more clear that there are probably better ways to install Jenkins.
I ended up uninstalling the WAR file of Jenkins on macOS by:
- Deleting the .war file.
- Deleting the ~/.jenkins directory.
I then reinstalled via home-brew, and bundle
started working.
add a comment |
up vote
-1
down vote
You could see where is bundle
is installed by running which bundle
and run the bundle
command from there
add a comment |
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
11
down vote
Depending on the way you installed Jenkins, it might be running as a separate user, typically as user jenkins
. If you have installed bundle
into a nonstandard directory which isn't in the default PATH, like /usr/local/bin
, you need to:
- Add
/usr/local/bin
to the PATH of the jenkins user (check ~jenkins/.bashrc) or - Configure PATH environment variable in Jenkins global configuration (or slave configuration if building on a slave) or
- Modify the build script to refer to
bundle
using a full path name.
Hi, i added /bin/bash instead /usr/bin/bash was not available. I am using centos.
– Chetan kapoor
Jul 14 '17 at 9:28
add a comment |
up vote
11
down vote
Depending on the way you installed Jenkins, it might be running as a separate user, typically as user jenkins
. If you have installed bundle
into a nonstandard directory which isn't in the default PATH, like /usr/local/bin
, you need to:
- Add
/usr/local/bin
to the PATH of the jenkins user (check ~jenkins/.bashrc) or - Configure PATH environment variable in Jenkins global configuration (or slave configuration if building on a slave) or
- Modify the build script to refer to
bundle
using a full path name.
Hi, i added /bin/bash instead /usr/bin/bash was not available. I am using centos.
– Chetan kapoor
Jul 14 '17 at 9:28
add a comment |
up vote
11
down vote
up vote
11
down vote
Depending on the way you installed Jenkins, it might be running as a separate user, typically as user jenkins
. If you have installed bundle
into a nonstandard directory which isn't in the default PATH, like /usr/local/bin
, you need to:
- Add
/usr/local/bin
to the PATH of the jenkins user (check ~jenkins/.bashrc) or - Configure PATH environment variable in Jenkins global configuration (or slave configuration if building on a slave) or
- Modify the build script to refer to
bundle
using a full path name.
Depending on the way you installed Jenkins, it might be running as a separate user, typically as user jenkins
. If you have installed bundle
into a nonstandard directory which isn't in the default PATH, like /usr/local/bin
, you need to:
- Add
/usr/local/bin
to the PATH of the jenkins user (check ~jenkins/.bashrc) or - Configure PATH environment variable in Jenkins global configuration (or slave configuration if building on a slave) or
- Modify the build script to refer to
bundle
using a full path name.
answered May 1 '12 at 18:05
sti
10.1k12025
10.1k12025
Hi, i added /bin/bash instead /usr/bin/bash was not available. I am using centos.
– Chetan kapoor
Jul 14 '17 at 9:28
add a comment |
Hi, i added /bin/bash instead /usr/bin/bash was not available. I am using centos.
– Chetan kapoor
Jul 14 '17 at 9:28
Hi, i added /bin/bash instead /usr/bin/bash was not available. I am using centos.
– Chetan kapoor
Jul 14 '17 at 9:28
Hi, i added /bin/bash instead /usr/bin/bash was not available. I am using centos.
– Chetan kapoor
Jul 14 '17 at 9:28
add a comment |
up vote
3
down vote
If bundle is installed in /usr/local/bin/bundle
(determine this with which bundle
) you could just add a symbolic link to bundle in /usr/bin
like so:
ln -s /usr/local/bin/bundle /usr/bin/bundle
add a comment |
up vote
3
down vote
If bundle is installed in /usr/local/bin/bundle
(determine this with which bundle
) you could just add a symbolic link to bundle in /usr/bin
like so:
ln -s /usr/local/bin/bundle /usr/bin/bundle
add a comment |
up vote
3
down vote
up vote
3
down vote
If bundle is installed in /usr/local/bin/bundle
(determine this with which bundle
) you could just add a symbolic link to bundle in /usr/bin
like so:
ln -s /usr/local/bin/bundle /usr/bin/bundle
If bundle is installed in /usr/local/bin/bundle
(determine this with which bundle
) you could just add a symbolic link to bundle in /usr/bin
like so:
ln -s /usr/local/bin/bundle /usr/bin/bundle
answered Aug 25 '16 at 13:59
Dan Herman
7731718
7731718
add a comment |
add a comment |
up vote
2
down vote
First things to verify:
- Make sure
bundle
is installed on the machine where Jenkins runs. - If it installed, make sure it's on the path for the user under which Jenkins runs
(To verify path/environment: insert shell build step that runs env
)
add a comment |
up vote
2
down vote
First things to verify:
- Make sure
bundle
is installed on the machine where Jenkins runs. - If it installed, make sure it's on the path for the user under which Jenkins runs
(To verify path/environment: insert shell build step that runs env
)
add a comment |
up vote
2
down vote
up vote
2
down vote
First things to verify:
- Make sure
bundle
is installed on the machine where Jenkins runs. - If it installed, make sure it's on the path for the user under which Jenkins runs
(To verify path/environment: insert shell build step that runs env
)
First things to verify:
- Make sure
bundle
is installed on the machine where Jenkins runs. - If it installed, make sure it's on the path for the user under which Jenkins runs
(To verify path/environment: insert shell build step that runs env
)
answered Apr 28 '12 at 19:18
malenkiy_scot
14k64577
14k64577
add a comment |
add a comment |
up vote
0
down vote
For me I had originally installed it via the war file as that's the way recommended on the Getting Started Guide. However, the user handbook makes it much more clear that there are probably better ways to install Jenkins.
I ended up uninstalling the WAR file of Jenkins on macOS by:
- Deleting the .war file.
- Deleting the ~/.jenkins directory.
I then reinstalled via home-brew, and bundle
started working.
add a comment |
up vote
0
down vote
For me I had originally installed it via the war file as that's the way recommended on the Getting Started Guide. However, the user handbook makes it much more clear that there are probably better ways to install Jenkins.
I ended up uninstalling the WAR file of Jenkins on macOS by:
- Deleting the .war file.
- Deleting the ~/.jenkins directory.
I then reinstalled via home-brew, and bundle
started working.
add a comment |
up vote
0
down vote
up vote
0
down vote
For me I had originally installed it via the war file as that's the way recommended on the Getting Started Guide. However, the user handbook makes it much more clear that there are probably better ways to install Jenkins.
I ended up uninstalling the WAR file of Jenkins on macOS by:
- Deleting the .war file.
- Deleting the ~/.jenkins directory.
I then reinstalled via home-brew, and bundle
started working.
For me I had originally installed it via the war file as that's the way recommended on the Getting Started Guide. However, the user handbook makes it much more clear that there are probably better ways to install Jenkins.
I ended up uninstalling the WAR file of Jenkins on macOS by:
- Deleting the .war file.
- Deleting the ~/.jenkins directory.
I then reinstalled via home-brew, and bundle
started working.
answered Nov 11 at 6:36
Senseful
44.5k42197312
44.5k42197312
add a comment |
add a comment |
up vote
-1
down vote
You could see where is bundle
is installed by running which bundle
and run the bundle
command from there
add a comment |
up vote
-1
down vote
You could see where is bundle
is installed by running which bundle
and run the bundle
command from there
add a comment |
up vote
-1
down vote
up vote
-1
down vote
You could see where is bundle
is installed by running which bundle
and run the bundle
command from there
You could see where is bundle
is installed by running which bundle
and run the bundle
command from there
answered Mar 26 '17 at 2:43
Maged Makled
1,3141721
1,3141721
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f10365792%2fcant-run-jenkins-build-bundle-command-not-found%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown