How to trigger a build with parameters is explained on the /job/JOBNAME/api URL 
in Jenkins -- the wiki page on the topic is a bit weird.

On 17.08.2015, at 22:39, Walter Kelt <[email protected]> wrote:

> Just looked at the Jenkins remote access api. Looks like file and parameters 
> need to be passed into curl in a json format. Not sure what Jenkins version 
> you are using, but you may want to check it out. 
> 
> If you are doing a parametrized build it looks to be a little more 
> complicated and I don't see an example using -F
> 
> Sent from my iPad
> 
> On Aug 17, 2015, at 4:11 PM, Greg Nifor <[email protected]> wrote:
> 
>> The job I'm triggering has two parameters, git and root. The curl sets those 
>> and I'm able to use those in my execute shell step.
>> 
>> On Monday, August 17, 2015 at 12:57:38 PM UTC-7, walter.kelt wrote:
>> Hmmm..when issuing a multipart form submission,  i wouldn't expect the 
>> multipart parameters to become Linux shell variables unless the code 
>> receiving the http request took the parameters and made them so. Does your 
>> http endpoint do so ? Seems I am missing something.
>> 
>> Sent from my iPad
>> 
>> On Aug 17, 2015, at 3:45 PM, Greg Nifor <[email protected]> wrote:
>> 
>>> Linux, there's no errors. The command goes through, but Jenkins doesn't 
>>> pick up on the variables when I echo them out this is the output:
>>> 
>>> 12:31:06 
>>> + echo 
>>> 
>>> 12:31:06 
>>> 12:31:06 
>>> + echo root
>>> 
>>> 12:31:06 root
>>> 
>>> Top one echos git and the second one echoes root (it's default value is 
>>> root)
>>> echo $git
>>> echo $root
>>> 
>>> On Monday, August 17, 2015 at 12:32:48 PM UTC-7, walter.kelt wrote:
>>> What was the error message ?  paste the most current command. Also, windows 
>>> or Linux ?
>>> 
>>> Sent from my iPad
>>> 
>>> On Aug 17, 2015, at 3:27 PM, Greg Nifor <[email protected]> wrote:
>>> 
>>>> That didn't work.
>>>> 
>>>> On Monday, August 17, 2015 at 12:19:24 PM UTC-7, walter.kelt wrote:
>>>> I think you need quote signs around each of the  -F items....such as -F 
>>>> "git=test"
>>>> 
>>>> Sent from my iPad
>>>> 
>>>> On Aug 17, 2015, at 3:15 PM, Greg Nifor <[email protected]> wrote:
>>>> 
>>>>> curl -X POST localhost/job/Test/buildWithParameters -u user:pass -F 
>>>>> git=test -F root=root1
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> On Monday, August 17, 2015 at 12:11:08 PM UTC-7, walter.kelt wrote:
>>>>> Please paste your full curl command
>>>>> 
>>>>> Sent from my iPad
>>>>> 
>>>>> On Aug 17, 2015, at 3:06 PM, Greg Nifor <[email protected]> wrote:
>>>>> 
>>>>>> When I try that the variables are empty.
>>>>>> 
>>>>>> On Monday, August 17, 2015 at 11:49:09 AM UTC-7, walter.kelt wrote:
>>>>>> You need to use -F for file and -F for data.
>>>>>> 
>>>>>> Sent from my iPad
>>>>>> 
>>>>>> On Aug 17, 2015, at 2:41 PM, Greg Nifor <[email protected]> wrote:
>>>>>> 
>>>>>>> Is there a way to use curl to send both a file and string parameter. I 
>>>>>>> can do each individually, but not together.
>>>>>>> 
>>>>>>> Works:
>>>>>>> 
>>>>>>> curl -X POST <jenkins_url>/job/<job>/buildWithParameters -u 
>>>>>>> <user>:<password> -F file=@/path/to
>>>>>>> 
>>>>>>> curl -X POST <jenkins_url>/job/<job>/buildWithParameters -u 
>>>>>>> <user>:<password> --data string0=foo --data string1=bar
>>>>>>> 
>>>>>>> Doesn't Work:
>>>>>>> 
>>>>>>> curl -X POST <jenkins_url>/job/<job>/buildWithParameters -u 
>>>>>>> <user>:<password> -F file=@/path/to --data string0=foo --data 
>>>>>>> string1=bar
>>>>>>> 
>>>>>>> The result I get is: Warning: You can only select one HTTP request!
>>>>>>> 
>>>>>>> 
>>>>>>> Any ideas?
>>>>>>> 
>>>>>>> 
>>>>>>> -- 
>>>>>>> You received this message because you are subscribed to the Google 
>>>>>>> Groups "Jenkins Users" group.
>>>>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>>>>> an email to [email protected].
>>>>>>> To view this discussion on the web visit 
>>>>>>> https://groups.google.com/d/msgid/jenkinsci-users/65067202-61bf-40b8-8509-376d5ae79589%40googlegroups.com.
>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>> 
>>>>>> -- 
>>>>>> You received this message because you are subscribed to the Google 
>>>>>> Groups "Jenkins Users" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>>>> an email to [email protected].
>>>>>> To view this discussion on the web visit 
>>>>>> https://groups.google.com/d/msgid/jenkinsci-users/f0a472a1-78f1-4a96-a15c-cf116565cdf8%40googlegroups.com.
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>> 
>>>>> -- 
>>>>> You received this message because you are subscribed to the Google Groups 
>>>>> "Jenkins Users" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>>>> email to [email protected].
>>>>> To view this discussion on the web visit 
>>>>> https://groups.google.com/d/msgid/jenkinsci-users/235cdbdb-cd11-46e2-ac6e-c51787d835a3%40googlegroups.com.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>> 
>>>> -- 
>>>> You received this message because you are subscribed to the Google Groups 
>>>> "Jenkins Users" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>>> email to [email protected].
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/jenkinsci-users/17aa53ed-c460-4841-b074-4f7e83855dc0%40googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to [email protected].
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-users/473e516e-f421-4b19-8a86-ed6ba6465a9f%40googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected].
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/19157462-71a5-48cc-a14d-aae7272f1559%40googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/ED22D818-1ED7-4217-B112-D2AFC543847F%40comcast.net.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/459746D4-5F2F-43F9-9BAB-8CD9E7A1F9D1%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Reply via email to