[temurin-compliance] Enable Parameterized Remote Trigger plugin to trigger jobs on Temurin-compliance Jenkins server
Summary
To automate and expedite the launch of TCK test pipelines on https://ci.eclipse.org/temurin-compliance/ from https://ci.adoptopenjdk.net/ (which has the https://www.jenkins.io/doc/pipeline/steps/Parameterized-Remote-Trigger/ installed).
Steps to reproduce
n/a
What is the current bug behavior?
(What actually happens)
What is the expected correct behavior?
Be able to trigger https://ci.eclipse.org/temurin-compliance/job/AQA_Test_Pipeline/ from the public Jenkins server https://ci.adoptopenjdk.net/ if a certain flag is set in the build pipelines (if build successful and triggerTCK flag is true).
Relevant logs and/or screenshots
Need to know which credentials can be used to trigger jobs.
Edited by Frederic Gurr