Using Jenkins to Vet New Build Environment

[Mark Bidewell]

I am thinking about how to begin moving some projects on old JDKs to supported JDKs.  I was wondering if there was a to run a build with normal settings, but then run a report-only (no artifact retention) build with a newer build environment to capture any compile or behavioral changes.  Artifacts would still be generated by the older environment.  Is there a way to do this without resorting to making all jobs matrix jobs?

Thanks.