Trigger remote job fails - quick question

[zw]

Hi All

We have 2 jenkins servers in boxes A, and B. Box A has box C as its slave.

We tried triggering 1 job in box A by using wget http://www.arefshg.com:8080/hudson/job/1.0_Build/build in the Build Execute Shell section. 

Console output

Building remotely on slave_linux
[test_svn14] $ /bin/sh -xe /tmp/hudson4435957536083197879.sh
+ wget http://www.arefshg.com:8080/hudson/job/1.0_Build/build
--2013-01-10 00:27:46--  http://www.arefshg.com:8080/hudson/job/1.0_Build/build
Resolving proxy.arefshg.com... 123.45.234.55

Connecting to proxy.arefshg.com|123.45.234.55|:80... connected.
Proxy request sent, awaiting response... 405 Method Not Allowed
2013-01-10 00:27:46 ERROR 405: Method Not Allowed.

What did we do wrong ?

What other methods can we use to trigger a remote build and passes back its build artifacts from B to A ?

Thanks

[Stuart Whelan]

Is the job you are trying to trigger configured to use parameters?

Do you have login security turned on any of the jenkins machines?

I trigger a build on our DR jenkins box using this method on my window
jenkins server:

c:\unix\usr\local\wbin\wget
"http://DRMACHINE:8080/job/DR%%20-%%20Kickoff%%20Db%%20Restore/build?token=MYSECRETTOKEN&cause=Started+By+DR+Process"

[zw]

Hi Stuart

Thanks for responding.

The remote Jenkins does not have security ie no username password to deal with; simply a job configured there.

Do you know how one could pass revision number with a curl command to kick off the remote build ?

[Mark Hudson]

I found that sometimes a workaround to ERROR 405: Method Not Allowed...
...is to change the final part of the URL path from .../build to .../buildWithParameters

[KunLung Hsieh]

Mark Hudson's answer works for me!

Mark Hudson於 2016年2月23日星期二 UTC+8上午9時10分01秒寫道：