bumping this if possible. I am writing a utility in node.js to do this, but I am sure there is got to be a better way to do this. Please feel free to ask if my question was not clear enough.
thanks - Rajat On Sunday, 11 November 2012 14:39:32 UTC, rp wrote: > > I am trying to do some integration work between TFS and Jenkins using the > build-pipeline plugin. Here is what the workflow would look like: > - Dev commits the code > - TFS calls Jenkins REST api to trigger a job > - The build calls a CLI that will trigger Build on the TFS Server > - When the build completes it will call Jenkins REST API to trigger the > next job > > My problem is that the cli makes an async call. So basically it makes a > request and returns call back. So for the purpose of the job, it has > successfully run and finished. However to represent that on the pipeline I > want the job to continue running till the 'build' has completed on TFS and > calls the API back. > > > One way is to write an application that will be a broker for the TFS > communication and make the job wait till the start and finish has happened. > However I wanted to check the collective wisdom on this group for a better > way (possibly a pre-existing plugin or feature) on jenkins to do this. > > thanks in advance. > > >
