I have a jenkins production job which involves multiple nodes/slaves and when we run the job it utilizes them based on the slave mentioned. And also, it has access to some machines shared folders.So from master, it is trying to access shared folders like \machine1\c$\sharefolder1 \machine2\c$\sharefolder2
So for my test environment, I installed jenkins and want to keep everything in a single slave. But,I don't want to modify the jobs.
So, I added entries in my local machine where jenkins is running and added entries to hosts file for machine1 and machine2. \localhost\c$ is opening but not with \machine1\c$ or \machine2\c$ even after adding entries to hosts file.
# localhost name resolution is handled within DNS itself.
127.0.0.1 localhost machine1 machine2
ping is redirecting to 127.0.0.1 loopback address only. But with localhost or 127.0.0.1 it is not prompting for password.But for machine1 or machine2 it is prompting for credentials and typing the machine's credentials is not working.
Add these hosts,
machine1
machine2
and such, to DNS.Perhaps the test environment has its own zone,
test.example.net
. Then configure DNS Suffix Search List on test hosts to include that. Resulting inmachine1
resolvingmachine1.test.example.net
Ideally configure a routable IP address for the DNS, not loopback. Gets mildly confusing if anyone forgets that loopback is this host. However nothing technically prevents an AAAA record having the value ::1.