Yes, GEF legacy is being used. I asked about this recently and Carl explained why [1].
Side issue aside, old logs are potentially available if you see them in Jenkins. If you can't find them under artifacts for a given build, then they're gone. Since we haven't previously archived the .log files, they're gone. But for future builds we can fix that.
Setting a longer timeout? Done: I've added -Dsurefire.exitTimeout=180 -Dsurefire.timeout=180 to the maven invocations, and upped the overall build timeout from 150 to 300 mins.
I've also increased the number of sets of artifacts to store in the job from 1 to 4, and the retention rules from 7/5/2/1 to 10/10/10/4. And... I've added **/.log to the list of files to archive for each build so those will be retained. This might have to change again later if we chew up too much disk, but for now it'll help with troubleshooting.
I've also given you (using your email address above) access to configure the job once you're logged in to
ci.eclipse.org. If that's not the email address associated with your
eclipse.org userid, let me know and I can add your other identity.
Job is running with the above config changes: