Brian Guthrie
Brian Guthrie
It needs to be re-recorded as a general part of the 2.0 deliverable.
The documentation needs to be revised. Specifically: - documentation of all new config features, e.g. Bundler - documentation of Builder model - HOWTOs for running and configuring the app -...
Currently CC.rb doesn't integrate with RVM, in the sense that it has no way to automatically handle any .rvmrc files that might be checked into your project. You can handle...
If JUnit test results exist--for example, as generated by a tool like [ci_reporter](https://github.com/nicksieger/ci_reporter)--we should recognize them and use them to render completion rates and build failures. Running the entire build...
In order to update certain elements of the UI in a more dynamic fashion, and in order to support third-party consumers beyond your standard CCTray consumers, it would be nice...
Currently, the code is (inside `script/builder`): ``` CRUISE_OPTIONS[:log_file_name] = "log/#{CRUISE_OPTIONS[:project_name]}_builder.log" ``` It should get changed to place the log file in the Cruise home directory (by default, ~/.cruise).
Right now, CC.rb has no way, either visually or in the config, to break a project's build into multiple stages. Multiple builds that share the same SCM are separated using...
CC.rb should function correctly on Ruby 1.9 and Rails 3 on Windows, which is to say: - backwards-compatible with existing site and project configs - installable and runnable via a...
You should be able to install CC.rb in gem form via Rubygems. Such a gem should expose the cruise executable as an entry point into the app, and should be...
As a CI user, I'd like to be able to copy and paste a URL into CCMenu/CCTray so I can monitor builds from my desktop. Requested by @alexeyv.