Most RecentMost ViewedMost LikesJenkins Environment Variables not available in Tests Hi, I'm using Jenkins to trigger scheduled tests and have recently started to use parameters in Jenkins. The parameters are set as environment variables by Jenkins and can easily be accessed by scripts executed on the Jenkins slave but not from the tests run by TestExecute in the same job. I need to parameters to be able to control which test system I should access from my tests. Sure I could copy the tests, one for each target, and hard code the target in each test, but that would quickly lead to a maintenance nightmare, thus I thought of using Jenkins parameters (and Multi-configuration variables) to do the job for me. Anyone tried this and found a solution to get this working? My setup is as follows: Jenkins, TestComplete Jenkins plugin, Java Web Start as service (on Jenkins slaves), TestExecute, Test written in python. Issue filed in support request: Case #00181940: "Environment variables form Jenkins not available in TestExecute" BR, Johan SolvedDynamic server monitoring It would be awesome to be able to writean environment variable on the textbox of the server monitor address, so we can define a variable that changes with the environments, in order to change the servers to monitor depending on the environment we are pointing at.
