summaryrefslogtreecommitdiff
path: root/spec/bundler/bundler
AgeCommit message (Collapse)Author
2019-12-15Fixed test failures with gem command path on ruby core repo.Hiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/2753
2019-12-15Prepare to release bundler-2.1.0Hiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/2753
2019-11-11Merge Bundler 2.1.0.pre.3Hiroshi SHIBATA
Features: - Add caller information to some deprecation messages to make them easier to fix [#7361](https://github.com/bundler/bundler/pull/7361) - Reconcile `bundle cache` vs `bundle package` everywhere. Now in docs, CLI help and everywhere else `bundle cache` is the preferred version and `bundle package` remains as an alias [#7389](https://github.com/bundler/bundler/pull/7389) - Display some basic `bundler` documentation together with ruby's RDoc based documentation [#7394](https://github.com/bundler/bundler/pull/7394) Bugfixes: - Fix typos deprecation message and upgrading docs [#7374](https://github.com/bundler/bundler/pull/7374) - Deprecation warnings about `taint` usage on ruby 2.7 [#7385](https://github.com/bundler/bundler/pull/7385) - Fix `--help` flag not correctly delegating to `man` when used with command aliases [#7388](https://github.com/bundler/bundler/pull/7388) - `bundle add` should cache newly added gems if an application cache exists [#7393](https://github.com/bundler/bundler/pull/7393) - Stop using an insecure folder as a "fallback home" when user home is not defined [#7416](https://github.com/bundler/bundler/pull/7416) - Fix `bundler/inline` warning about `Bundler.root` redefinition [#7417](https://github.com/bundler/bundler/pull/7417) Notes: Merged: https://github.com/ruby/ruby/pull/2668
2019-09-18[bundler/bundler] Fix comments and messages to refer to https urlTakayuki Nakata
https://github.com/bundler/bundler/commit/a86b49f1b9
2019-08-21[bundler/bundler] Freeze time to avoid failures at midnightlolwut
Specify just a string set @built_at as nil before testing https://github.com/bundler/bundler/commit/578ec96c9c
2019-08-21[bundler/bundler] Parallelize test suiteDavid Rodríguez
https://github.com/bundler/bundler/commit/23007cb107
2019-08-21[bundler/bundler] Remove old rubies stuff no longer neededDavid Rodríguez
https://github.com/bundler/bundler/commit/36fb3287f4
2019-08-20Fix some bundler specs (#2380)David Rodríguez
* These seem to consistenly pass already * Show actual command when running `make test-bundler` Current the setup command that installs the necessary gems for testing bundler was printed, but not the actual command that runs the tests. That was a bit confusing. * Borrow trick from setproctitle specs * A title that long doesn't get set sometimes No idea why, but the test doesn't need that the title is that long. * Fix most gem helper spec ruby-core failures * Fix the rest of the gem helper failures * Fix version spec by improving the assertion * Remove unnecessary `BUNDLE_RUBY` environment var We can use `RUBY` when necessary, and `BUNDLE_RUBY` is not a good name because bundler considers `BUNDLE_*` variables as settings. * Rename `BUNDLE_GEM` to `GEM_COMMAND` This is more descriptive I think, and also friendlier for bundler because `BUNDLE_` env variables are interpreted by bundler as settings, and this is not a bundler setting. This fixes one bundler spec failure in config specs against ruby-core. * Fix quality spec when run in core Use the proper path helper. * Fix dummy lib builder to never load default gems If a dummy library is named as a default gem, when requiring the library from its executable, the default gem would be loaded when running from core, because in core all default gems share path with bundler, and thus they are always in the $LOAD_PATH. We fix the issue by loading lib relatively inside dummy lib executables. * More exact assertions Sometimes I have the problem that I do some "print debugging" inside specs, and suddently the spec passes. This happens when the assertion is too relaxed, and the things I print make it match, specially when they are simple strings like "1.0" than can be easily be part of gem paths that I print for debugging. I fix this by making a more exact assertion. * Detect the correct shebang when ENV["RUBY"] is set * Relax assertion So that the spec passes even if another paths containing "ext" are in the load path. This works to fix a ruby-core issue, but it's a better assertion in general. We just want to know that the extension path was added. * Use folder structure independent path helper It should fix this spec for ruby-core. * Fix the last failing spec on ruby-core * Skip `bundle open <default_gem>` spec when no default gems
2019-08-18[bundler/bundler] No need to activate the `fileutils` default gemDavid Rodríguez
The version we're vendoring actually relaxed this restriction back to 2.3.0+, so we can always use the vendored version. https://github.com/bundler/bundler/commit/d366cbfe5d
2019-08-17[bundler/bundler] Use path helpers to find bundle binDavid Rodríguez
https://github.com/bundler/bundler/commit/7985bb8e92
2019-08-17[bundler/bundler] Fix bundle bin location in core repoDavid Rodríguez
https://github.com/bundler/bundler/commit/9437568ab4
2019-08-17[bundler/bundler] Reuse more shared path helpersDavid Rodríguez
https://github.com/bundler/bundler/commit/79fdebd868
2019-08-16Revert "[bundler/bundler] Fixup #7297"Hiroshi SHIBATA
This reverts commit b8d759806ff825e1b9344ba34b1a2bc4809d0988. It's accidentally picked from the upstream repository.
2019-08-16[bundler/bundler] Fixup #7297Hiroshi SHIBATA
https://github.com/bundler/bundler/commit/1a0161b970 Notes: Merged: https://github.com/ruby/ruby/pull/2366
2019-08-16[bundler/bundler] Add initial Bundler::BuildMetadata Spectommy
https://github.com/bundler/bundler/commit/c6458b2727 Notes: Merged: https://github.com/ruby/ruby/pull/2366
2019-08-16[bundler/bundler] Use the standard RUBY_ENGINE_VERSION instead of JRUBY_VERSIONBenoit Daloze
* RUBY_ENGINE and RUBY_ENGINE_VERSION are defined on every modern Ruby. * There is no such constant as TRUFFLERUBY_VERSION or RBX_VERSION. https://github.com/bundler/bundler/commit/f9d910403b Notes: Merged: https://github.com/ruby/ruby/pull/2366
2019-08-12Re-use GITHUB_ACTION variables for filtering bundler examples.Hiroshi SHIBATA
2019-08-03[bundler/bundler] Bump net-http-persistent to 3.0.1David Rodríguez
* Adds an extra artifice task to vendorize new `connection_pool` dependency. * Cherry-pick's needed Windows fix not yet merged into master branch of `net-http-persistent`. * Update bundler usages to be compatible with the new version, and fix unit specs. https://github.com/bundler/bundler/commit/0575baa6bb
2019-08-03[bundler/bundler] Enable `Style/UnneededInterpolation` copDavid Rodríguez
https://github.com/bundler/bundler/commit/4c6a3c3cf7
2019-08-03[bundler/bundler] RUBY_ENGINE should always be defined after 1.8.7David Rodríguez
https://github.com/bundler/bundler/commit/d6c9196d18
2019-08-03[bundler/bundler] Check for generic lockfilesDavid Rodríguez
https://github.com/bundler/bundler/commit/344a881592
2019-08-03[bundler/bundler] spec/bundler/shared_helpers_spec.rb - fixup after 7248MSP-Greg
PR 7248 incorrectly changed a path calculation. This reverts. After running Azure Pipelines CI in my ruby/ruby fork and checking the 'bundler' jobs, the error was apparent... https://github.com/bundler/bundler/commit/811755b413
2019-08-03[bundler/bundler] fix nested bundle exec's when bundler is a default gemMSP-Greg
https://github.com/bundler/bundler/commit/537c0ab712
2019-08-03[bundler/bundler] dsl_spec.rb - fix for Ruby coreMSP-Greg
https://github.com/bundler/bundler/commit/33892e1ed2
2019-08-03[bundler/bundler] Fix typosDavid Rodríguez
https://github.com/bundler/bundler/commit/1bd9660780
2019-08-03[bundler/bundler] Add missing mockDavid Rodríguez
I'm not sure this test is useful but since it's there, it should be complete. https://github.com/bundler/bundler/commit/3e350089db
2019-08-03[bundler/bundler] Improve spec to be more realisticDavid Rodríguez
https://github.com/bundler/bundler/commit/ca96316b97
2019-08-03[bundler/bundler] Clearer MissingRevision git errorsDavid Rodríguez
https://github.com/bundler/bundler/commit/b47d23edf5
2019-08-03[bundler/bundler] Don't re-resolve locked platform specific gemsDavid Rodríguez
https://github.com/bundler/bundler/commit/7da2bf75f5
2019-08-03[bundler/bundler] Fix thread leak in compact index specsDavid Rodríguez
This spec was not stopping threads after itself. That would cause the previous spec in the file (that checks that no threads are left behind) to fail. https://github.com/bundler/bundler/commit/81ad85b92d
2019-08-03[bundler/bundler] Fix `rake release` not prompting for OTP codeDavid Rodríguez
Co-authored-by: Colby Swandale <me@colby.fyi> Co-authored-by: Kevin Deisz <kevin.deisz@gmail.com> https://github.com/bundler/bundler/commit/1b2bbc7364
2019-08-03[bundler/bundler] Normalize file:// handling in specsDavid Rodríguez
https://github.com/bundler/bundler/commit/5946d62ad0
2019-08-03[bundler/bundler] Use a clean gemspec for gem helper specsDavid Rodríguez
https://github.com/bundler/bundler/commit/f694fe7f67
2019-08-03[bundler/bundler] Move "on releasing" to a RSpec contextDavid Rodríguez
So we can later add more tests with the same setup. https://github.com/bundler/bundler/commit/21b4b6c49c
2019-08-03[bundler/bundler] Skip specs that need coloring on WindowsDavid Rodríguez
ANSI codes don't work there. https://github.com/bundler/bundler/commit/4f05417ca7
2019-08-03[bundler/bundler] Add missing no-color source specsDavid Rodríguez
For consistency. https://github.com/bundler/bundler/commit/279603ab42
2019-08-03[bundler/bundler] Be explicit about coloring in specs that need thatDavid Rodríguez
https://github.com/bundler/bundler/commit/a4d04506ab
2019-08-03[bundler/bundler] Respect color option when instantiating shellsDavid Rodríguez
Thor's base shell will be memoized the first time it is set. So if we instantiate a no-color shell first, further instantiations of a bundler shell will be initialized with a no-color shell by default. This is caused some sources specs to fail, depending on the order they run. See for example https://travis-ci.org/bundler/bundler/builds/500328994. What we do to fix it is to reset the shell unless no-color is explicitly specified. That way, further instantiations will rerun thor's internal logic to choose the default shell. https://github.com/bundler/bundler/commit/786b5d9894
2019-08-03[bundler/bundler] Added Ruby 2.6 to dsl.Hiroshi SHIBATA
https://github.com/bundler/bundler/commit/1892626858
2019-06-09Fixed wrong BUNDLE_BIN_PATH for ruby core.Hiroshi SHIBATA
2019-06-09Added the condition for ruby_core repository.Hiroshi SHIBATA
2019-06-09Merge bundler master from upstream.Hiroshi SHIBATA
Pick from 8dd59e3ba97eb80a599f8149f31bf40773b69dc0
2019-06-05spec/bundler/bundler/dsl_spec.rb: fix exception to raiseNobuyoshi Nakada
When describing "Runtime errors", raise a `RuntimeError` as-is.
2019-04-14Skip to failing examples on ruby core repository.hsbt
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67541 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2019-04-14Merge Bundler 2.1.0.pre.1 as developed version from upstream.hsbt
https://github.com/bundler/bundler/commit/a53709556b95a914e874b22ed2116a46b0528852 git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67539 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2019-03-14Skip Bundler's test made fail by r67226k0kubun
Possible fix would be https://github.com/bundler/bundler/pull/7038, but Ruby script ending with `^~~` could be wrongly stripped by that? git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67257 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2019-02-27skip to not support color tty environment.hsbt
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67138 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2019-02-05Ignore to add bundler lib direcotry if it is same as rubylibdir.hsbt
[Bug #15469][ruby-core:90742] git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67006 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2019-01-04Merge Bundler 2.0.1 from upstream.hsbt
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66710 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-12-11Merge Bundler 1.17.2 from upstream.hsbt
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66338 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-26 16:07:12 +0000