问题描述
我们最近从导通premises TFS2013升级到2015年UPDATE1，我们已经建立了一个VSO生成代理。
We have recently upgraded from on-premises TFS2013 to 2015 Update1, and we have set up a VSO Build Agent.
现在我想建立一个测试（持续集成）vNext建立在我们的Git仓库的解决方案，但在版本是没有运行和不会产生任何日志。
I am now trying to set up a test (continuous integration) vNext build for a solution in our Git repository, but the builds are not running and not producing any logs.
生成属性被设置为指示正确的Git回购，而以下三个已经被添加到变量：VSO_GIT_USERNAME，VSO_GIT_PASSWORD，DNXPath。 MSBuild的是在present添加到构建的唯一步骤。
The build properties have been set up to indicate the correct Git repo, and the following three have been added to Variables: VSO_GIT_USERNAME, VSO_GIT_PASSWORD, DNXPath. MSBuild is the only step added to the build at the present.
的commit导致建立被触发如预期，但是当一个构建被触发，它只是挂起从代理等待控制台输出：
Pushed commits result in builds being triggered as expected, but when a build is triggered, it just hangs "Waiting for console output from an agent":
似乎没有是什么毛病代理：
There doesn't seem to be anything wrong with the agent:
- 它显示为运行（在SERVICES.MSC选中）
- 它没有SSL依赖
- 端口9191已添加到TFS服务器的防火墙入站规则
- 代理与项目集合构建服务权限运行
- 代理出现绿色Web访问：
当我取消生成并下载日志文件，该压缩文件是空的。
When I cancel the build and download log files, the zip file is empty.
同样的情况：没有建立运行和没有日志文件
The same happens when I queue a build manually (against a specific commit #): no build runs and no log files.
我应该怎么办/检查，要么让我的构建过程，或使之产生的日志文件？
任何人都可以提出一条前进的道路？
Can anybody suggest a way forward?
推荐答案
好吧，解决方案找到了！在我的特殊情况下，我设置端口9191通过防火墙的界面（Windows Server 2012中R2），并为它的入站规则看上去还不错，活跃。但它撒谎了。
Ok, solution found! In my particular case I set up port 9191 using Firewall interface (Windows Server 2012 R2), and the inbound rule for it looked nice and active. But it lied.
当我问我，马克，良好的同事检查该端口是否是真的好了，他跑了获取-NetFirewallPortFilter 在PowerShell中的TFS机器上，并且我的端口被从名单上消失了！
When I asked a good colleague of mine, Marc, to check if the port was really ok, he ran Get-NetFirewallPortFilter in PowerShell on the TFS machine and my port was missing from the list!
他提出的解决方案是运行下面的PowerShell脚本（因为防火墙被打了）：
The solution he suggested was to run the following PowerShell script (since Firewall was playing up):
$port = New-Object -ComObject HNetCfg.FWOpenPort
$port.Port = 9191
$port.Name = 'TFS CI Port:9191'
$port.Enabled = $true
$fwMgr = New-Object -ComObject HNetCfg.FwMgr
$profile = $fwMgr.LocalPolicy.CurrentProfile
$profile.GloballyOpenPorts.Add($port)
一旦被运行，端口9191的入站规则出现在防火墙的入站规则。
Once this was run, an inbound rule for port 9191 appeared in Firewall inbound rules.
然后我手动排队的构建，并在第一时间看到它失败（不会挂！），并在该日志文件！ ：）
I then manually queued the build, and for the first time saw it fail (not hang!), and with log files at that! :)
这篇关于vNext建立在TFS 2015年挂在MSBuild的步骤，并不会产生日志文件的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！