[Pharo-dev] VM acceptance tests

I am still struggling with the VM acceptance test. Currently we're loading Seaside and Moose, two very big projects which hopefully stress many parts of the VM. The problem is, that these two projects evolve by themselves, adding another axis of freedom which I would like to avoid. So is there an easy way to freeze a configuration and store it on our fileserver, so that we have a fixed reference? (Note, we use a 2.0 image) If we have that, I can even integrate the validation process into the travis build which should make contributions to the pharo-vm much easier...