Do not trigger dev level testing as part of a release

[smlambert]

What are you trying to do?
Run AQAvit verification against release builds.

Expected behaviour:
To run only these high-level test targets as part of the release: https://github.com/adoptium/aqa-tests/blob/master/testenv/testenv.properties#L23
AQA_REQUIRED_TARGETS=sanity.functional,extended.functional,special.functional,sanity.openjdk,extended.openjdk,sanity.system,extended.system,sanity.perf,extended.perf

Observed behaviour:
We are running the set of tests that get run during weekly testing, which includes the dev level tests (dev.openjdk and dev.system). We do not want to run those dev (tests in development) during a release.

Any other comments:
Grid view of the dry-run release pipeline for JDK17 also shows that naming of build and smoke tests is new and unexpected.

Raised adoptium/aqa-test-tools#765 but would also like to look at improving naming in build pipelines so we do not need to do mapping.

[zdtsw]

looking at the changes, dev.openjdk and dev.system are added into the weeklyDefault by 917c994 which was not in the last release from 2022.Oct

no logic change was made in getTestList() since Oct, so we need find a new solution for different testlist between Weekly and Release https://github.com/zdtsw/ci-jenkins-pipelines/blob/master/pipelines/build/common/build_base_file.groovy#L233-L253

Not really sure where in the pipeline it uses testenv.propertiesfile, seem it was only reading each properties inside of the Test_openjdk* job

[andrew-m-leonard]

Issue #728
will add "dev" to Weekly, or the "EA Beta" tag builds.

[smlambert]

This is now resolved via #849 (adding new testJobType=release).