You mentioned in the latest release notes that DRONE_NETWORKS has been fixed I have setup an external in docker compose that brings up drone and selenium I have also set DRONE_NETWORK in my env to be selenium should all drone tests now have access to the containers on this network with no extra work ?
Obviously my goal is to have selenium running permanently and be available to my tests, do I need to change anything in my drone.yaml files ?
Thinking about this a bit more it makes a bit more sense, guessing drone could never work like this because your test suites can be running more than once so the names would conflict, Guess you need to work out the current ip inside the container and pass that on to selenium.
This is likely not deterministic as you have no idea what range is attached to which interface so eth0 and eth1 can switch.
will try and work a way around this but still open to better ideas, also any way you can get information about containers from with in a container or write a plugin that could get this kind of information ?
This will resolve the service to get an ip address knock of the last two octets and use the first two to grep out the matching ip for the current container and push <> matching ip into a file called interfaces.txt.