Activity (RSS)

Could not reproduce.

Per title.

This was resolved via another means: warningshot --list-deps warningshot --build-deps

Currently all additional resolvers are loaded when pload or oload are specified. Works correctly for the core resolvers

The new Config system is pooping out when you use Resolver specific command line arguments.

Nate, were you seeing this with a particular resolver or all resolverS?

See title

This is stubbed, but there was a catch22 issue w/ this, uncomment to see in config.rb

Essentially in addition to 'environments' dependencies could be set for a host (using hostname) or a platform (linux,mac,win,etc).

Would this be useful or just ...

WarningShot should have its own set of config files so it can test its self (for WS Developers). So if you have the current warningshot installed you can test y...

At 0.9.5 100% of the code should be tested.

This is slightly stubbed the way YAML files are pulled in, finish making the file types to processing 'pluggable' so other config file types and how to process ...

if this gets adopted as an LARuby project, put it at warningshot.laruby.com?

about 50% implemented...

These are created and available at rubyforge, they do nothing but provide a bunch of versions to write rspecs with. https://rubyforge.org/frs/?group...

It'd be sweet if GemResolver had a method that could list all the gem requirements the app found, that way in gem specs you could just do something like...

requ...

This will need a cli extension in FileResolver to accept username/password

part of deployments; should conditionally deploy based on percentage of tests passed.

{test_bed: "staging", target: "production", passed: "80%"}

If deployed to ...

Will be part of deployments.

Should be able to specify Percentage for code coverage to allow deployment to different environments

Should be able to test pages for yslow grades

Add mount resolver, should at least be able to mount NFS drives

Add Apt, yum, ports support

broke into multiple tickets...

Create multiple version to test gem installation with version conditions.

Create a rubygem called 'ws-dummy' for testing gem_resolver.

Status: in progress, requested project @ rubyforge.

Did it.

Each dependency resolver gets its own logger and assigns it to the resolvers it loads

Complete.

WarningShot.before do;end; WarningShot.after do;end;

Each Resolver can do:

MyResolver.before :test do;end; MyResolver.after :test do;end; MyResolver.b...

Most of the command line options values aren't actually consumed, I threw together the cli pretty quick and put static values in.

Example: verbose, logging, and...