![]() |
|
|
|
|
Change By:
|
Henry Huang
(03/Aug/13 11:28 AM)
|
|
Description:
|
From
the
help message in EC2Cloud
Configuration
configuration
, I need to let spot instance notify
the
Jenkins master
know
that
this slave
alive after it
is available.
As
My
my
AMI is based on CentOS, I cannot take the script
directly as
it mentioned.
Here
So I have gone through the script and here
is my understanding on the callback process.
Jenkins
Master
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
that
this slave
is
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
will keep considering
this slave not ready.
I also try to run these commands
into
on
an internal machine and wish
Maser
Master
could let it go. But
with
only get the "
403 forbidden
"
response.
Could you please help me on this issue?
I feel this deployment is also quite common
then
.
Thanks
Henry
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/groups/opt_out.
