Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

'bundler' is not recognized as an internal or external command #1944

Closed
ashmaroli opened this issue Nov 19, 2017 · 11 comments
Closed

'bundler' is not recognized as an internal or external command #1944

ashmaroli opened this issue Nov 19, 2017 · 11 comments
Labels
bug Visual Studio 2013 Visual Studio 2015 Visual Studio 2017
Milestone
14-jan-2018

Comments

@ashmaroli
Copy link

I'm guessing this has something to do with the Nov 19 update because Bundler 1.16.0 still ships with the bundler executable, and that it works fine on my local system..

Suddenly, all of my tests fail with following error:

bundler --version
'bundler' is not recognized as an internal or external command,
operable program or batch file.
@ashmaroli
Copy link
Author

Refer #1926 (comment) for related discussion..

@FeodorFitsner FeodorFitsner added this to the next-images-update milestone Nov 19, 2017
@FeodorFitsner
Copy link
Member

Quick fix has been deployed. Should be fine now.

@ashmaroli
Copy link
Author

Thank you very much!! I'll check and close this.. 😃

@FeodorFitsner
Copy link
Member

Yes, but do not close issue yet - just post an update. Let's keep it opened until the root cause if understood.

@ashmaroli
Copy link
Author

CI is running normally again.. 👍

@koic
Copy link

koic commented Nov 19, 2017

I was also encountering the same problem. When I saw it has not been resolved yet.
https://ci.appveyor.com/project/bbatsov/rubocop/build/1542/job/6r99udd3vv85df5w

@FeodorFitsner
Copy link
Member

This looks like related: rubygems/rubygems#2058

Bundler 1.16.0 is now pre-installed on build workers. You can just use pre-installed one or try adding --force switch to gem install bundler command.

@koic
Copy link

koic commented Nov 19, 2017

Thanks for the advise. I will try it!

koic added a commit to koic/rubocop that referenced this issue Nov 19, 2017
@koic
Workaround for bundle conflict in AppVeyor
aff1797 
Follow up of appveyor/ci#1944 (comment)

This is a workaround patch to AppVeyor config.
This change attempts to resolve the following error.

```console
gem install bundler --no-document
bundler's executable "bundle" conflicts with C:/Ruby23/bin/bundle
Overwrite the executable? [yN]
```

https://ci.appveyor.com/project/bbatsov/rubocop/build/1540/job/f8gxj2m6b53qe3tg#L23

This causes the job to fail with a timeout of 60 min.

> Build execution time has reached the maximum allowed time for your plan (60 minutes).

https://ci.appveyor.com/project/bbatsov/rubocop/build/1540/job/f8gxj2m6b53qe3tg/messages

This change attempt to solve by forcibly updating the bundler by adding
`--force` option.
@koic koic mentioned this issue Nov 19, 2017
Merged
@koic
Copy link

koic commented Nov 19, 2017

With your advice I got a workaround and ran successfully. Thank you!

bbatsov pushed a commit to rubocop/rubocop that referenced this issue Nov 19, 2017
@koic @bbatsov
Workaround for bundle conflict in AppVeyor
ae8a37d 
Follow up of appveyor/ci#1944 (comment)

This is a workaround patch to AppVeyor config.
This change attempts to resolve the following error.

```console
gem install bundler --no-document
bundler's executable "bundle" conflicts with C:/Ruby23/bin/bundle
Overwrite the executable? [yN]
```

https://ci.appveyor.com/project/bbatsov/rubocop/build/1540/job/f8gxj2m6b53qe3tg#L23

This causes the job to fail with a timeout of 60 min.

> Build execution time has reached the maximum allowed time for your plan (60 minutes).

https://ci.appveyor.com/project/bbatsov/rubocop/build/1540/job/f8gxj2m6b53qe3tg/messages

This change attempt to solve by forcibly updating the bundler by adding
`--force` option.
@btm btm mentioned this issue Nov 22, 2017
Merged
@FeodorFitsner
Copy link
Member

Referencing related Rubygems issue: rubygems/rubygems#2083

@ashmaroli
Copy link
Author

Thank you so much, for getting the problem solved at the root location 👍

shirosaki added a commit to shirosaki/win32-api that referenced this issue Nov 28, 2017
@shirosaki
Fix to install bundler on CI
33e087f 
appveyor/ci#1944
@sawanoboly sawanoboly mentioned this issue Dec 20, 2017
Merged
koic added a commit to koic/rubocop that referenced this issue Jan 24, 2018
@koic
Revert "Workaround for bundle conflict in AppVeyor"
8244909 
This reverts commit ae8a37d.

appveyor/ci#1944 has been resolved. This PR will revert the workaround.
@koic koic mentioned this issue Jan 24, 2018
Merged
bbatsov pushed a commit to rubocop/rubocop that referenced this issue Jan 24, 2018
@koic @bbatsov
Revert "Workaround for bundle conflict in AppVeyor"
3b8fe7d 
This reverts commit ae8a37d.

appveyor/ci#1944 has been resolved. This PR will revert the workaround.
aycabta added a commit to aycabta/rdoc that referenced this issue Mar 8, 2019
@aycabta
Add workaround Bundler update
9ce362d 
appveyor/ci#1944 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Visual Studio 2013 Visual Studio 2015 Visual Studio 2017
Projects
None yet
Milestone
14-jan-2018
Development

No branches or pull requests
3 participants
@koic @FeodorFitsner @ashmaroli