summaryrefslogtreecommitdiff
path: root/spec/bundler/support
AgeCommit message (Collapse)Author
2020-03-27Merge bundler-2.1.4Hiroshi SHIBATA
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-19Fix glob base in bundler.gemspecKazuhiro NISHIYAMA
Notes: Merged: https://github.com/ruby/ruby/pull/2683
2019-11-19Skip some tests if extracted from tarballKazuhiro NISHIYAMA
Notes: Merged: https://github.com/ruby/ruby/pull/2683
2019-11-13Merge Bundler 2.1.0.pre3 released versionHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/2674
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-08-21The investigation is going on...Nobuyoshi Nakada
2019-08-21[bundler/bundler] Share test fixtures with parallel_testsHiroshi SHIBATA
https://github.com/bundler/bundler/commit/a38161c5be
2019-08-21[bundler/bundler] Try to use RunTimeLogger for parallel_testsHiroshi SHIBATA
https://github.com/bundler/bundler/commit/faccc522d1
2019-08-21[bundler/bundler] Parallelize test suiteDavid Rodríguez
https://github.com/bundler/bundler/commit/23007cb107
2019-08-21[bundler/bundler] Fix a couple of typosDavid Rodríguez
https://github.com/bundler/bundler/commit/52b6b94068
2019-08-20Investigation of a sporadic error at Github ActionsNobuyoshi Nakada
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-18[bundler/bundler] Remove unnecessary rubygems monkeypatchDavid Rodríguez
Instead, make sure we always load the local copy of bundler during specs, and never end up using the default copy. https://github.com/bundler/bundler/commit/ac655ffeda
2019-08-18[bundler/bundler] Remove a bunch of unneeded rubygems requiresDavid Rodríguez
https://github.com/bundler/bundler/commit/f9cb39e614
2019-08-17[bundler/bundler] Extract a `gemspec_dir` helperDavid Rodríguez
https://github.com/bundler/bundler/commit/71a29e286a
2019-08-17[bundler/bundler] Extract yet another helper methodDavid Rodríguez
https://github.com/bundler/bundler/commit/948a863bd8
2019-08-17[bundler/bundler] Extract a `root_gemspec` local variableDavid Rodríguez
https://github.com/bundler/bundler/commit/a4beba4cbf
2019-08-17[bundler/bundler] Extract a `with_root_gemspec` helperDavid Rodríguez
https://github.com/bundler/bundler/commit/f20c2bdf6a
2019-08-17[bundler/bundler] Remove unneeded `to_s` callsDavid Rodríguez
They are implicit inside `gem_command!`. https://github.com/bundler/bundler/commit/6bdb13c899
2019-08-17[bundler/bundler] Consistently use `Path` over `Spec::Path`David Rodríguez
https://github.com/bundler/bundler/commit/a4cca66b79
2019-08-17[bundler/bundler] Extract single gem installation logicDavid Rodríguez
https://github.com/bundler/bundler/commit/7888d621c8
2019-08-17[bundler/bundler] Unalias `install_gem`David Rodríguez
Since I plan to reuse it for something else. https://github.com/bundler/bundler/commit/5379382198
2019-08-17[bundler/bundler] Use `join` consistentlyDavid Rodríguez
https://github.com/bundler/bundler/commit/096e53dfe6
2019-08-17[bundler/bundler] Extract a `lib_tracked_files` path helperDavid Rodríguez
https://github.com/bundler/bundler/commit/028dc46f5a
2019-08-17[bundler/bundler] Extract a `tracked_files` path helperDavid Rodríguez
https://github.com/bundler/bundler/commit/d35e31d2e0
2019-08-17[bundler/bundler] Reuse `gem_bin` helper inside `gem_command`David Rodríguez
The logic for choosing `gem_bin` should work here too even if it's not identical. https://github.com/bundler/bundler/commit/6ca0271b27
2019-08-17[bundler/bundler] Always use `--backtrace` when invoking `gem` CLIDavid Rodríguez
For debuggability. https://github.com/bundler/bundler/commit/ac3e8db658
2019-08-17[bundler/bundler] Extract a `gem_bin` path helperDavid Rodríguez
https://github.com/bundler/bundler/commit/8eedbecac0
2019-08-17[bundler/bundler] Remove more dead codeDavid Rodríguez
https://github.com/bundler/bundler/commit/17d4d0de8e
2019-08-17[bundler/bundler] Remove dead codeDavid Rodríguez
https://github.com/bundler/bundler/commit/cae948f514
2019-08-17[bundler/bundler] Remove unnecessary rubygems requireDavid Rodríguez
https://github.com/bundler/bundler/commit/039604ff95
2019-08-17[bundler/bundler] Move `lib` helper together with path helpersDavid Rodríguez
https://github.com/bundler/bundler/commit/f2df73bdb4
2019-08-17[bundler/bundler] Reuse `lib` methodDavid Rodríguez
https://github.com/bundler/bundler/commit/4589a57852
2019-08-17[bundler/bundler] Remove duplicated methodDavid Rodríguez
https://github.com/bundler/bundler/commit/afdacd62ac
2019-08-16[bundler/bundler] Commit man pages to source controlDavid Rodríguez
This has the benefit that: * Allows the installation of bundler as a default gem from rubygems to include man pages. * Removes the need to build man pages during our tests. * Makes working with the manifest easier, because we only have source controlled files, and not a mix of source control and generated files. To make sure they never fall out of sync, we replace the previous `man:build` CI task with a `man:check` task that makes sure the generated man pages are up to date. https://github.com/bundler/bundler/commit/23de1d0177 Notes: Merged: https://github.com/ruby/ruby/pull/2366
2019-08-16[bundler/bundler] Bump rspec dependency to 3.8David Rodríguez
Because we're using `config.bisect_runner` which is only available from 3.8. https://github.com/bundler/bundler/commit/304a187f72 Notes: Merged: https://github.com/ruby/ruby/pull/2366
2019-08-16[bundler/bundler] Revert "make system_bundle_bin_path helper and resolve ↵David Rodríguez
failing tests for ruby < 2.6" This reverts commit e63e844bc7444c6a489fcde0dc7011c6c4807edd. It was introduced to resolve some failing tests at the cost of making the intention of the spec much less clear. Thanks to the previous fixes we have added to this spec, we can revert that patch now. https://github.com/bundler/bundler/commit/b29a40820f Notes: Merged: https://github.com/ruby/ruby/pull/2366
2019-08-16[bundler/bundler] Bump rack and sinatra to latest versionsDavid Rodríguez
https://github.com/bundler/bundler/commit/09ecaf04fa Notes: Merged: https://github.com/ruby/ruby/pull/2366
2019-08-16[bundler/bundler] Normalize style with other artifice filesDavid Rodríguez
https://github.com/bundler/bundler/commit/f11c9a2b3f 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-03[bundler/bundler] The keys for RbConfig::CONFIG was String.Hiroshi SHIBATA
https://github.com/bundler/bundler/commit/ffc5e76335
2019-08-03[bundler/bundler] Bump rubocop to 0.74.0David Rodríguez
And reenable exclusion because the bug why we added them has been fixed. See https://github.com/rubocop-hq/rubocop/issues/6861. https://github.com/bundler/bundler/commit/bda63fcffc
2019-08-03[bundler/bundler] Bump automatiek to 0.2.0David Rodríguez
https://github.com/bundler/bundler/commit/cd1abf8b3f
2019-08-03[bundler/bundler] Fully remove compatibility guardDavid Rodríguez
https://github.com/bundler/bundler/commit/2a7a5daba0
2019-08-03[bundler/bundler] Remove development dependencies from gemspecDavid Rodríguez
And refactor development setup. https://github.com/bundler/bundler/commit/f288806d02
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] Remove now unused logicDavid Rodríguez
https://github.com/bundler/bundler/commit/5b285685a4
generated by cgit v1.2.3 (git 2.25.1) at 2026-01-17 13:32:16 +0000