Huh, that's a good thought. My confusion centered around how to expire the cache from the controller standpoint when each individual project decides for itself when to build - expiring through the Build action wouldn't work, I think, because not every build event falls through that action. Right? But caching on the filesystem level makes sense. I'll take a stab at it.
Brian On Wed, Jan 27, 2010 at 9:15 AM, Alexey Verkhovsky <[email protected]> wrote: >> controller action level I don't know how much Rails caching buys us. > > Two thoughts on the subject: > > * anything that bypasses reading data from the file system would make a lot > of difference. > > * you can see if the data needs to be re-read by loking at the mtime of > ~/.cruise/projects/MyProject directory. If that directory changed, it means > there is new state. > > So, just caching Project#builds for as long as mtime of Project#path stays > the same may be the ticket. > > -- > Alexey Verkhovsky > http://alex-verkhovsky.blogspot.com/ > CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com] > > > _______________________________________________ > Cruisecontrolrb-developers mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers > > _______________________________________________ Cruisecontrolrb-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers
