vNext build on TFS 2015 hangs on MSBuild step and produces no log files

前端 未结 2 1214

We have recently upgraded from on-premises TFS2013 to 2015 Update1, and we have set up a VSO Build Agent.

I am now trying to set up a test (continuous integration) v

相关标签:
2条回答
  • 2020-12-11 21:47

    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.

    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!

    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)
    

    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! :)

    0 讨论(0)
  • 2020-12-11 21:48
    1. Make sure the account that the agent is run under is in the "Agent Pool Service Account" role.

    2. Make sure the queue is provisioned in the collection ( https://your-tfs-server:8080/tfs/your-collection/_admin/_AgentQueue ). If not - select "New queue.." and select the existing queue.

    3. Make sure you deploy the Windows build agent by exactly following this article.

    4. Try to change a domain account which is a member of the Build Agent Service Accounts group and belongs to "Agent Pool Service Account" role, to see whether the agent would work or not.

    5. Re-deploy the windows agent.

    0 讨论(0)
提交回复
热议问题