Releases: customink/strainer
v3.4.0
v3.3.0
v3.2.2
v3.2.1
- Return true/false from
Strainer#run
and refactor success reporting to make Strainer more library-like (@wingrunr21) - Add
--color
and--no-color
option to disable colored output (@wingrunr21)
v3.1.1
v3.1.0
-
Logically decide which commands are run inside the cookbook and which are run inside the sandbox (#31)
Certain commands should be run from inside a cookbook (like RSpec and Test Kitchen), but others must be run in the sandbox (Knife and Foodcritic). This change attempts to intelligently detect what command the user wants and execute that command in the correct context.
-
Throw a fatal error when 'strainer test' is called on a chef_repo with no arguments
Potentially a CI bug, if
strainer test
is called with no arguments on a chef_repo, the build would be marked as passing (when in reality, nothing was tested). This change does not affect cookbook_repos. -
Various README updates
v3.0.5
-
Fix issue with
Strainer::VERSION
not being loaded -
Remove autoload in favor of require_relative for Window's folks
One of the main problems experienced with threading is that
Kernel.autoload
is not threadsafe. It also provides no time benefits on Windows. Switching torequire_relative
increases the overall load time (by about 0.03s in benchmarking), but reduces loadtime on Windows by 2 seconds. As an added benefit, the code is now threadsafe.