Is there any way to disable FitNesse page caching?

Question

We are trying to use multiple instances of FitNesse with the same backing store of pages. The intention is that we use command-line variable declarations to set environment-specific variables differently, so that we can run the same test suites against different environments.

This all works great, except that we find that FitNesse seems to cache pages in memory, specifically the following use case doesn't work for us:

1. Go to FitNesse instance 1 and delete or rename a page.
2. Go to FitNesse instance 2 - observe that page (if it had been previously accessed) still appears to be there.
3. Restart FitNesse instance 2 - page is gone (as expected).

We'd gladly pay the (I assume small) hit to performance of page rendering if we could disable this caching behavior.

Any ideas how to do it?

Answer 1

There are a number of recent changes to FitNesse that are in the edge, but not in the release, that might improve the behavior for you. I know that one feature directly related to the removing of CachingPage. https://cleancoder.ci.cloudbees.com/job/fitnesse/lastStableBuild/

I haven't tried this particular scenario, so I can't guarantee it resolves it. I also don't usually recommend running two instances out of the same folder structure. When I have done so, the second instance really only existed to view results of tests.