Stewart X Addison

I've restarted the jenkins agent on the `-1` machine in case it wasn't in the correct docker group before. I've been able to run docker operations from the `jenkins` user...

I've switched `docker` and `dockerBuild` for `dockerX` and `dockerBuildX` to avoid problems until someone can fix this on the machines.

Memo to self: Retry when the machines are refreshed as a part of https://github.com/adoptium/infrastructure/issues/3719

Removing from the current plan on the assumption that this will get resolved as part of the reinstalls in https://github.com/adoptium/infrastructure/issues/3719

Another option could be to have the AQA_Test_Pipeline job disaplay a suitable markdown table at the end that can be cut and pasted with the links and job status into...

A couple of notes on this: - It will require a devkit rebuild for the GCC11 (jdk21u) and GCC14 (jdk25+) devkits - When we rebuild we should consider modifying the...

We've already had a bit of work done with people to experiment with trestle functionality previously but I would suggest that for a documented phase one we aim for: -...

While I am initially proposing running the jobs twice with different parameters for normal and fastdebug builds there are other options for the future: - Allow the `-hotspot` build to...

Understood - it becomes a matter of whether we consider the complexity of allowing the top level one to kick off and manage the results of the others is appropriate...

> Building it means that if needed, the builds can be tested 'in post' using Grinders and/or downloading and running tests locally, if the fast debug tests run, and reveal...