-
Bug
-
Resolution: Won't Fix
-
Minor
-
None
From the possible combinations of the fields "usePrivateDnsName" and "connectUsingPublicIp", only three connection strategies are taken into account. See https://github.com/jenkinsci/ec2-plugin/pull/329
The previous and actual behaviour for Unix are:
- privateDns: false publicIP: false
- public DNS o private IP if the previous one was empty
-
- now: private IP
- privateDns: false publicIP: true
- public DNS, if empty then public IP, if empty then private IP
- now: public IP
- privateDns: true publicIP: false
- private DNS
- now: private DNS, otherwise private IP
- privateDns: true publicIP: true
- private DNS
- now: public IP
For Windows:
- privateDns: false publicIP: false
- If there's public DNS, host is that and IP is the public one. If there isn't, host is private DNS and IP is the private one.
- now: private IP
- privateDns: false publicIP: true
- The same than previous one
- now: public IP
- privateDns: true publicIP: false
- The host is private DNS and IP is private IP
- now: private ip
- privateDns: true publicIP: true
- SAme than previous one
- AHORA: public IP
There are clear behaviour changes, but they seem to be pretty obvious to be forgotten. So maybe I'm not aware of something and that's why this behaviour changed?
CC dgarzon