|
From help message in EC2Cloud Configuration, I need to let spot instance notify Jenkins master know this slave alive after it is available.
As My AMI is based on CentOS, I cannot take the script it mentioned.
Here is my understanding on the callback process.
Jenkins Master does the spot instance request also with a default parameter in instance userdata, like:
JENKINS_URL=http://1.1.1.1:8080/&SLAVE_NAME=XXXXXXX&USER_DATA=
Then the callback script will first download the "slave.jar" and use it to notify Jenkins Master know this slave alive:
java -jar slave.jar -jnlpUrl http://1.1.1.1:8080/XXXXXXX/slave-agent.jnlp
However, due to my Jenkins master deployed internally with no public access, so it makes Jenkins master considers this slave not ready.
I also try to run these commands into an internal machine and wish Maser could let it go. But with 403 forbidden response.
Could you please help me on this issue?
I feel this deployment is also quite common.
Thanks
Henry
|
