Generate property file with SHA info

[llxia]

Currently, we generate SHA.txt for capture test repo shas. This file is easy to read, but it can not be used directly to set env value.

Maybe it is easier to create a property file with key and value pairs. The key should match with get.sh parameters and values in ant build.xml. For example in testenv.properties file, we have

TKG_REPO=https://github.com/adoptium/TKG.git
TKG_BRANCH=3f1b8746bb6dd25870cac3fc116ad4754ec5d700
JDK_REPO=xxx
JDK_BRANCH=xxx
...

In get.sh, we can simply add source ./testenv.properties to load the variables (i.e., TKG_REPO, TKG_BRANCH, etc).
For ant (build.xml) to work, the variables need to be set as env variables (i.e., JDK_REPO, JDK_BRANCH, etc).

• option1: use Jenkins readProperties. Similar to https://github.com/adoptium/aqa-tests/blob/master/buildenv/jenkins/JenkinsfileBase#L460
• option2: add a warper script for make compile in Jenkinsfilebase

source ./testenv.properties
make compile

or

while read line; do
    export $line
done < testenv.properties
make compile

IMO, option2 seems better as it will cover the local run as well.

In Grinder, add a boolean flag USE_TESTENV_PROPERTIES. If it is set to true, ignore the params in Grinder, read testenv.properties and set values as env variable (override params if set) for ant scripts and run get.sh.
And If the flag is set to true, we are expecting to find the file under root testenv.properties. Print error and exit the build if this file cannot be found. This logic should be in get.sh.
If it is set to false, proceed as a regular run (that is take the parameters from Grinder).

Please test both the local and Grinder run.

Update: broken into several steps:

• generate the testenv.properties file and archive testenv.properties
• add USE_TESTENV_PROPERTIES flag, consume testenv.properties in get.sh
• consume testenv.properties in system tests
• consume testenv.properties in openjdk tests

[psaunderualberta]

I will take this for now, I'll likely end up breaking it into smaller issues like recommended.

[llxia]

Thanks @psaunderualberta . Please check meeting recording for details.

For the first issue - generate the testenv.properties file and archive testenv.properties
I think it is easier just update the existing logic of generating SHA.txt :
https://github.com/adoptium/aqa-tests/blob/master/get.sh#L619
https://github.com/adoptium/aqa-tests/blob/master/get.sh#L626
https://github.com/adoptium/TKG/blob/07171520f8b0849d922125d35380d45193f9c5bf/scripts/getSHA.sh

[llxia]

preliminary testenv.properties is created: #2921

[smlambert]

I believe this one is now addressed, closing as complete.