Child builds of matrix jobs should use the same subversion revision as the parent job to ensure consistent builds across axes.

An example of where this doesn't happen: I use the parameterized-trigger plugin to pass the subversion revision from an upstream build job to a downstream matrix job.

While the parent matrix build correctly picks the revision, the child builds just use the HEAD revision instea,