One project reported a problem with the enumeration mixin when upgrading to Rails 2.2. The problem was with the all method.

The enumerations mixin allows you to treat instances of your ActiveRecord models as though they were an enumeration of values.

The proposed solution is to switch to in memory enumeration instead of using ActiveRecord.

Ask for Help

A new project would like to find a useful deploy.rb for Engine Yard. Preferably using git. There were a few suggestions from other projects to view theirs.

Interesting Things

RSpec

Do not create records in a

before(:all)

The transactional wrapper around the tests don't apply to the before(:all).

Ask for Help

"How can asset_host and retardation_inhibitor could work together nicely?"

ActionController::Base.asset_host

Tells your Rails application to generate external resources’ links pointing to the host of your choosing.

The general opinion was that any sophistication should be handled by asset_host configurations in the appropriate rails environment files.

This lead to the sticky problem of our CI process running the Selenium tests in the development environment rather than the test environment. The asset_host using the development environment configuration rather than the test environment.

Everyone agreed that this wasn't the best way to run the selenium tests.

A desperate request to rename the Pivotal project "retardation_inhibitor" met with no resistance, much to the delight of the Pivot responsible for explaining it's usefulness.

"New Relic & Desert?"

Ruby & Rails can sometimes appear to be moving so quickly that not advancing feels like standing still. A project found problems with the latest versions of New Relic and Desert.

Every page request resulted in a stack trace in the log.

The general consensus was that the latest version of New Relic would solve this problem. Of course the team had already tried this along with several other versions.

Some Pivots in New York had apparently encountered and solved similar problems. Hopefully they can help out.

Another Pivotal project had similar problems and had to upgrade to 2.7.3. They used these update steps. http://sites.google.com/a/newrelic.com/rpm-docs/installing-the-agent.

They originally tried to just install the latest without following the steps outlined in the link above and still had problems.

Interesting Things

Look out for a public Pivotal Pulse announcement soon.

A google gadget is built, tested and deployed to the target environment. What about regression testing that google gadget? Things change that could cause the gadget to start to fail. The suggestion made was to fake out a test to look like a browser. If the test is faked out enough, google will think the gadget is running in a browser.