gauntlet version 2.0.2 has been released!
Gauntlet is a pluggable means of running code against all the latest
gems and storing off the data.
Changes:
2.0.2 / 2013-06-28
-
1 bug fix:
- Keep stderr output from gem unpack in case there are problems…
Some gems are corrupt or something
Hi, Ryan,
(Thanks for all you seattlerb’ers do!)
I don’t know what this is used for. How do you use gauntlet in your
workflow?
On Jun 28, 2013, at 19:24 , Tamara T. [email protected]
wrote:
Hi, Ryan,
(Thanks for all you seattlerb’ers do!)
I don’t know what this is used for. How do you use gauntlet in your
workflow?
Right now I just use gauntlet to update a directory of tarballs of all
the latest gems. For ruby_parser my workflow is too complex to run
through gauntlet. I have a bunch of rake tasks to unpack tarballs, merge
into a 2 level hashed directory structure, remove all non-ruby files,
and de-dupe all files across all directories.
Regular workflow is to finish dev on a project and then to “run the
gauntlet”. Rdoc does this to test that it hasn’t regressed across any
projects, for example.