Recently, I wrote about the lack of a mature and de facto standard CI tool in the Ruby community. While not everyone will consider CruiseControl on their Ruby development efforts, for those that do, you now have an option. Late last week, CruiseControl 2.6 was released. In addition to some of the other useful features, RakeBuilder was included. It's now easy to invoke Rake build scripts from CruiseControl.
I decided it was time to explore more Ruby, so I decided to implement my standard programming kata using Ruby without Rails. My primary intent was to further familiarize myself with the Ruby platform and some of it's most useful gems. Given that much of my Ruby and Rails work has been with small projects, the secondary intent of this endeavor was to simulate the type of environment in Ruby that I have grown accustomed to working with in Java. That is, large teams and applications, and the environment necessary to support the development effort. I had planned to document my steps and share them on this blog. It was supposed to go something like this:
- Develop my standard loan payment calculator to show the monthly payment of a loan based on a rate, term and principle.
- Use Test::Unit and further explore ways to separate test code from application code, understand directory structures and loadpaths, other environmental issues.
- Add a test suite to aggregate multiple tests into a single test run.
- Introduce a Rake build file to run the test suite and perform any other build related tasks
- Deploy the application as a REST service along with an html front end
- Setup a continuous integration environment with scheduled builds and deploys.
I had a good start, encountering a few rather interesting challenges along the way. Eventually, I hope to compile my notes and share them. However, I got sidetracked. Above all else, there was one glaring deficiency I struggled with tremendously.
- Develop my standard loan payment calculator to show the monthly payment of a loan based on a rate, term and principle.
- Use Test::Unit and further explore ways to separate test code from application code, understand directory structures and loadpaths, other environmental issues.
- Add a test suite to aggregate multiple tests into a single test run.
- Introduce a Rake build file to run the test suite and perform any other build related tasks
- Deploy the application as a REST service along with an html front end
- Setup a continuous integration environment with scheduled builds and deploys.
I had a good start, encountering a few rather interesting challenges along the way. Eventually, I hope to compile my notes and share them. However, I got sidetracked. Above all else, there was one glaring deficiency I struggled with tremendously.
(RSS 2.0)