How to setup AQA_Test_Pipeline in Jenkins
One way to generate and leverage the AQAvit test pipelines in Jenkins is to use the aqaTestPipeline.groovy script.
Once you have setup this pipeline in your Jenkins server, it acts as a parent job that generates AQAvit test pipeline jobs as child jobs in Jenkins.
The set of parameters that this 'parent job' takes are defined in the groovy script.
The hierarchy of the job tree is determined by the parameters you provide to the AQA_Test_Pipeline, for example, this instance #254 was launched with
- PLATFORMS=x86-64_linux
- TARGETS=sanity.functional,extended.functional,special.functional,sanity.openjdk,extended.openjdk,sanity.system,extended.system,sanity.perf,extended.perf
- JDK_VERSIONS=17,8,22,11,21
- SDK_RESOURCES=releases
This resulted in the following test jobs being triggered. If those jobs were not present on the Jenkins server ahead of this parent pipeline #254 being run, they would be automatically generated using a standardized naming convention which is described here.
Use the list found in this plugins-list.txt file as the set of plugins that are used by the AQAvit test pipeline code and ensure they are installed on the Jenkins server where you wish to run the AQA_Test_Pipeline and other test jobs.
The AQA_Test_Pipeline job is defined in the buildenv/jenkins/aqaTestPipeline.groovy in the https://github.com/aqa-tests repo. See the parameters that are used in this job here.
The AQA_Test_Pipeline job calls Test_Job_Auto_Gen which is a DSL template. The Test_Job_Auto_Gen job is defined in buildenv/jenkins/testJobTemplate.
To manually add these jobs to your Jenkins server, first ensure you have installed the required set of plugins listed above.
Work in progress. This section to be completed soon.