Complete Trestle_Pipeline wrapper script

[smlambert]

To simplify the launching of Trestle pipelines (listed below), we intend to create a parent job that allows for launching certain features and backports from developers who work for Adoptium Working Group members.

Need to connect Trestle_Pipeline job (https://ci.adoptium.net/job/Trestle_Pipeline/) to launch the sub-jobs (listed below):

https://ci.adoptium.net/job/build-scripts/job/trestle-openjdk8-pipeline/ https://ci.adoptium.net/job/build-scripts/job/trestle-openjdk11-pipeline/ https://ci.adoptium.net/job/build-scripts/job/trestle-openjdk17-pipeline/ https://ci.adoptium.net/job/build-scripts/job/trestle-openjdk21-pipeline/ https://ci.adoptium.net/job/build-scripts/job/trestle-openjdk23-pipeline/ https://ci.adoptium.net/job/build-scripts/job/trestle-openjdk24-pipeline/

• May also want an option to pull a JDK from a pre-submit test run of an OpenJDK PR run, but that is outside of the scope of the initial wrapper script feature set.

[smlambert]

Current proposed set of inputs:

[sxa]

I would suggest that we try to limit most of these parameters to selection boxes instead of free-form text fields for the purposes of this (which would also prevent people running it on platforms we're not fully set up to handle). I would also include a field for the person running it to specify the SHA of the commit that is at the HEAD of the branch. If "Alice" was running Trestle against "Bob"'s PR and Alice had been diligent in looking over it and verified it was sane, ensuring that the SHA matched what had been reviewed and that there hadn't been subsequent pushes to the branch before it running would add a good level of security.

[smlambert]

yes, the screenshot there is from the prototype config. The plan is to limit the parameters as much as possible. Many will become checkboxes.