{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 Lonely孤独者° 的问题《Validate pull request with jenkins in VSTS》','https://www.manongdao.com/q-916882.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
The only workaround we found for validating pull requests in visual studio online currently is to create a visual studio build definition that triggers our jenkins job, and create a branch policy on that build definition.
But Visual Studio online is able to trigger the jenkins job directly when a git pull request is created / updated.
Is it possible to create a branch policy on the outcome of that jenkins job? The TFS plugin already provides status feedback for the "normal push" build status.
It is impossible now, I submit a user voice here: Branch policy based on jenkins job, you can vote and follow up it.