awesome, thanks Jerry, I'll try it out On 26 Бер, 18:49, Jerry <[email protected]> wrote: > You have your pick of lastBuild, lastCompletedBuild, lastFailedBuild, > lastStableBuild, lastSuccessfulBuild, lastUnsuccessfulBuild, and possibly > others. You will find all this data > inhttp://jenkins.node.com:80/job/api-tests/api/xml. > > -- Jerry > > > > > > > > On Tuesday, March 26, 2013 12:09:15 PM UTC-4, tetlika wrote: > > > thanks for reply Jerry! > > > But how will I know what number has my task which I've triggered? > > > also, maybe this would be easier if I'm trigerring build also from > > jenkins? > > > On 26 Бер, 18:06, Jerry <[email protected]> wrote: > > > Add api/xml or api/json to the end of your URL (e.g. > >http://jenkins.node.com:80/job/api-tests/12/api/xml > > > for build 12) and parse the *result* element out of that. > > > > -- Jerry > > > > On Tuesday, March 26, 2013 11:58:24 AM UTC-4, tetlika wrote: > > > > > I need to run task on remote jenkins, and verify remotely if it > > > > succeed or failed > > > > > how can I do that? > > > > > P.S. > > > > > I have found that I can do that by curl call e.g.: > > > > > curl --silent --user jenkins:password' --head 'http://jenkins.node.com: > > > > > 80/job/api-tests/build' > > > > > this triggers build on project api-tests, but do not found how to > > > > verify if the triggered build was successful or not > > > > > thanks
-- 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]. For more options, visit https://groups.google.com/groups/opt_out.
