Hi KIK,
but still it it can be understood and seems to be the right approach :)
That was also my first thought of a solution as I read the thread.
Am Montag, 14. Mai 2012 16:04:55 UTC+2 schrieb KIK:
>
> I have one idea.
>
> 1.install another master jenkins, it's not slave.
> 2.wget build url on a
I have one idea.
1.install another master jenkins, it's not slave.
2.wget build url on another master jenkins, from first master jenkins.
3.if finish build job, notice e-mail, publish any or wget build url on
first master jenkins.
I'm sorry my broken English.I'm not native.
Unfortunately this is how Jenkins slaves work. They are called "dumb slaves"
for a reason, they cannot work without connection to the master.
I think you should maybe look into the type of jobs described in here:
https://wiki.jenkins-ci.org/display/JENKINS/Monitoring+external+jobs
-- Sami
Kris
My company is auditing Jenkins as a build system, and our use case
requires us to run long builds (12 hours) on slave machines. Because a
persistent network connection must be maintained with the slave
machine during this whole duration, sometimes our builds fail because
of network hiccups. This ca
