Best option looks to be a bit of a cobbled together solution of : get next build number, curl by posting the file, then using that build number to monitor until it's completed. Feels like a complete hack, but ... so be it :(
On Friday, 6 March 2015 00:27:38 UTC-8, Brantone wrote: > > Hey, looking for a method to remotely trigger a Jenkins job from one > master to another, with file upload/transfer ... and wait for response > (success or failure). > I'm aware there's the plugin > https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Remote+Trigger+Plugin > > however, that doesn't seem to support file upload. > I'm thinking an alternative might be to upload to intermediary location > then trigger the job; however, wondering if other possibilities ... > probably a bunch of script with curl calls might work, but not exactly > eloquent. > I feel like something simple can be done ... 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/e4bf136f-3e3d-4061-a125-818e07490590%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
