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.

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

Remove bundler install during Appveyor tests #217

Merged
merged 1 commit into from
Nov 20, 2017
Merged

Conversation

adamleff
Copy link
Contributor

@adamleff adamleff commented Nov 20, 2017

It appears that the Appveyor images changed recently and the Ruby
installs for all version (2.2, 2.3, and 2.4) already include Bundler
installed. Attempting to install it will hang the tests at an
interactive prompt asking if you want to override the install, and
--force'ing the install causes path issues and Rubygems won't be able
to activate the gem.

Removing the bundler install appears to solve the problem nicely.

@adamleff adamleff requested a review from a team November 20, 2017 16:45
It appears that the Appveyor images changed recently and the Ruby
installs for all version (2.2, 2.3, and 2.4) already include Bundler
installed. Attempting to install it will hang the tests at an
interactive prompt asking if you want to override the install, and
--force'ing the install causes path issues and Rubygems won't be able
to activate the gem.

Removing the bundler install appears to solve the problem nicely.

Signed-off-by: Adam Leff <[email protected]>
@adamleff adamleff changed the title DO NOT MERGE: Testing appveyor without hardcoded bundler path Remove bundler install during Appveyor tests Nov 20, 2017
Copy link
Contributor

@chris-rock chris-rock left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @adamleff

@chris-rock chris-rock merged commit f2c0ab9 into master Nov 20, 2017
@chris-rock chris-rock deleted the adamleff/appveyor branch November 20, 2017 17:08
adamleff added a commit that referenced this pull request Nov 21, 2017
It appears that the Appveyor images changed recently and the Ruby
installs for all version (2.2, 2.3, and 2.4) already include Bundler
installed. Attempting to install it will hang the tests at an
interactive prompt asking if you want to override the install, and
--force'ing the install causes path issues and Rubygems won't be able
to activate the gem.

Removing the bundler install appears to solve the problem nicely.

Signed-off-by: Adam Leff <[email protected]>
adamleff added a commit that referenced this pull request Nov 21, 2017
It appears that the Appveyor images changed recently and the Ruby
installs for all version (2.2, 2.3, and 2.4) already include Bundler
installed. Attempting to install it will hang the tests at an
interactive prompt asking if you want to override the install, and
--force'ing the install causes path issues and Rubygems won't be able
to activate the gem.

Removing the bundler install appears to solve the problem nicely.

Signed-off-by: Adam Leff <[email protected]>
chris-rock pushed a commit that referenced this pull request Nov 21, 2017
* Add unix_mode_mask method to Train::File::Local::Unix (#215)

* Add unix_mode_mask method to Train::File::Local::Unix

During the refactor, the `#unix_mode_mask` method for Unix files was
only added to the Remote class. It's still needed for the Local class.

Signed-off-by: Adam Leff <[email protected]>

* Use the sanitized file path for remote linux files (#218)

Had a test start failing recently and tracked it down to remote linux file
resources no longer handling spaces in paths as of the refactor in 0.29.0.

The test passes again after applying this change.

Signed-off-by: Jonathan Hartman <[email protected]>

* Adding branches for testing

Signed-off-by: Adam Leff <[email protected]>

* Remove bundler install during Appveyor tests (#217)

It appears that the Appveyor images changed recently and the Ruby
installs for all version (2.2, 2.3, and 2.4) already include Bundler
installed. Attempting to install it will hang the tests at an
interactive prompt asking if you want to override the install, and
--force'ing the install causes path issues and Rubygems won't be able
to activate the gem.

Removing the bundler install appears to solve the problem nicely.

Signed-off-by: Adam Leff <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants