Doesn't work with unparameterized builds

[tylerbrandt]

If the remote job doesn't have any parameters it rejects being run with /buildWithParameters:

This results in logging like the following in the remote calling job:

JENKINS_URL: https://jenkins.pci-us-west-2.optimizely.net
JOB_NAME: clientbuildserver-promote-staging-tags
The whole list of values is 'token=[*******]'
PARAMS: token=[*******]
Calling REMOTE_JOB_URL: https://jenkins.pci-us-west-2.optimizely.net/job/clientbuildserver-promote-staging-tags/buildWithParameters?token=[*******]
No QUEUED_URL was found.  Did you remember to set a token (-t)?
Build step 'Execute shell' marked build as failure
[BFA] Scanning build for known causes...
[BFA] No failure causes found
[BFA] Done. 0s
Finished: FAILURE

I had to add a dummy parameter to the job to make it work.

[NizarNi]

Exactly, you have to remove the "/buildWithParameters" from REMOTE_JOB_URL if you want to proceed with jobs non-parameterized. See this for a better basic understanding: https://wiki.jenkins.io/display/JENKINS/Remote+access+API

[dFurman]

They explained in the script that only buildWithParameters is the way to get the job number url.
workaround you can use is to add a dummy parameter to your job.