Univention Bugzilla – Bug 40579
Expose IPs from Jenkins cfg to ucs-test environment
Last modified: 2023-07-26 15:02:55 CEST
Some test cases need another client host to check the effectiveness of server settings, for example a Windows client for GPO evaluation. More effective tests could be created if the test cases would have access to the IPs of the other hosts in the test setup. Sure, they can lookup things from UDM or OpenLDAP but it would be good for the test to know which of the computer objects actually is the one that it should use for its purpose. ucs-ec2-create (and ucs-kvm-create) could simply pass the IPs into the ucs-test environment. They are already available in the cfg files as <HOSTLABEL>_IP. The two additional steps would be: 1. Use a convention for the HOSTLABEL, like [WINDOWS_CLIENT] ec2_ami: ami-a1d607d6 windows: true 2. expose the IP with a suitable prefix like: TESTSETUP_WINDOWS_CLIENT_IPV4
<https://git.knut.univention.de/univention/dist/ucs-ec2-tools#variables> You can use `[$vm_IP]` inside a .cfg to get the IP for any (other) VM.