7

在 TFS 2015 新构建系统中，是否在构建完成后自动将构建号添加到全局列表（构建 - 项目名称）的功能？

我是否需要编写自定义 PowerShell 任务来完成此任务？

注意：XAML 构建仍然像以前一样将内部版本号添加到全局列表。

4

2 回答 2

4

由于 vNext 构建系统中仍然缺少许多功能，我制作了一个 PowerShell 脚本来完成这项工作。在不久的将来，我计划更新此脚本以支持 IntegratedIn 字段填充并将脚本转换为自定义构建任务。

[CmdletBinding(SupportsShouldProcess=$false)]
param()

function Update-GlobalListXml
{
    [CmdletBinding(SupportsShouldProcess=$false)]
    param(
         [xml]$globalListsDoc,
         [parameter(Mandatory=$true)][string][ValidateNotNullOrEmpty()]$glName,
         [parameter(Mandatory=$true)][string][ValidateNotNullOrEmpty()]$buildNumber
    )

    Write-Verbose "Checking whether '$glName' exists"
    $buildList = $globalListsDoc.GLOBALLISTS.GLOBALLIST | Where-Object { $_.name -eq $glName }
    if ($buildList -eq $null)
    {
        Write-Host "GlobalList '$glName' does not exist and will be created"
        $globalLists = $globalListsDoc.GLOBALLISTS
        if($globalLists.OuterXml -eq $null)
        {
            $newDoc = [xml]"<gl:GLOBALLISTS xmlns:gl="""http://schemas.microsoft.com/VisualStudio/2005/workitemtracking/globallists"""></gl:GLOBALLISTS>"
            $globalLists = $newDoc.GLOBALLISTS
        }
        $globalList = $globalLists.OwnerDocument.CreateElement("GLOBALLIST")
        $globalList.SetAttribute("name", $glName)
        $buildList = $globalLists.AppendChild($globalList)
    }
    if(($buildList.LISTITEM | where-object { $_.value -eq $buildNumber }) -ne $null)
    {
        throw "The LISTITEM value: '$buildNumber' already exists in the GLOBALLIST: '$glName'"
    }

    Write-Host "Adding '$buildNumber' as a new LISTITEM in '$glName'"
    $build = $buildList.OwnerDocument.CreateElement("LISTITEM")
    $build.SetAttribute("value", $buildNumber)
    $buildList.AppendChild($build) | out-null

    return $buildList.OwnerDocument
}

function Invoke-GlobalListAPI()
{
    [CmdletBinding(SupportsShouldProcess=$false)]
    param(
        [parameter(Mandatory=$true)][Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItemStore]$wiStore,
        [parameter(Mandatory=$true,ParameterSetName="Import")][switch]$import,
        [parameter(Mandatory=$true,ParameterSetName="Import")][xml]$globalLists,
        [parameter(ParameterSetName="Export")][switch]$export
    )

    try {
        if($import)
        {
            $wiStore.ImportGlobalLists($globalLists.OuterXml) # Account must be explicitly in the Project Administrator Group
        }
        if($export)
        {
            return [xml]$wiStore.ExportGlobalLists()
        }
    }
    catch [Microsoft.TeamFoundation.TeamFoundationServerException] {
        Write-Error "An error has occured while exporting or importing GlobalList"
        throw $_
    }
}

function Get-WorkItemStore()
{
    [CmdletBinding(SupportsShouldProcess=$false)]
    param(
        [parameter(Mandatory=$true)][string][ValidateNotNullOrEmpty()]$tpcUri,
        [parameter(Mandatory=$true)][string][ValidateNotNullOrEmpty()]$agentWorker
    )

    # Loads client API binaries from agent folder
    $clientDll = Join-Path $agentWorker "Microsoft.TeamFoundation.Client.dll"
    $wiTDll = Join-Path $agentWorker "Microsoft.TeamFoundation.WorkItemTracking.Client.dll"
    [System.Reflection.Assembly]::LoadFrom($clientDll) | Write-Verbose
    [System.Reflection.Assembly]::LoadFrom($wiTDll) | Write-Verbose

    try {
        Write-Host "Connecting to $tpcUri"
        $tfsTpc = [Microsoft.TeamFoundation.Client.TfsTeamProjectCollectionFactory]::GetTeamProjectCollection($tpcUri)
        return $tfsTpc.GetService([Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItemStore])
    }
    catch [Microsoft.TeamFoundation.TeamFoundationServerException] {
        Write-Error "An error has occured while retrieving WorkItemStore"
        throw $_
    }
}

function Get-WITDataStore64
{
    [CmdletBinding(SupportsShouldProcess=$false)]
    param()

    if($env:VS140COMNTOOLS -eq $null)
    {
        throw New-Object System.InvalidOperationException "Visual Studio 2015 must be installed on the build agent" # TODO: Change it by checking agent capabilities
    }

    $idePath = Join-Path (Split-Path -Parent $env:VS140COMNTOOLS) "IDE"
    return Get-ChildItem -Recurse -Path $idePath -Filter "Microsoft.WITDataStore64.dll" | Select-Object -First 1 -ExpandProperty FullName
}

function Update-GlobalList
{
    [CmdletBinding(SupportsShouldProcess=$false)]
    param()

    # Get environment variables
    $tpcUri = $env:SYSTEM_TEAMFOUNDATIONCOLLECTIONURI
    Write-Verbose "Team Project Collection Url: '$tpcUri'"
    $teamProjectName = $env:SYSTEM_TEAMPROJECT
    Write-Verbose "Team Project: '$teamProjectName'"
    $buildNumber = $env:BUILD_BUILDNUMBER
    Write-Verbose "Build Number: '$buildNumber'"
    $agentHome = $env:AGENT_HOMEDIRECTORY
    Write-Verbose "Agent home direrctory: '$agentHome'"
    $globalListName = "Builds - $teamProjectName"
    Write-Verbose "GlobalList name: '$teamProjectName'"

    # Copy 'Microsoft.WITDataStore64.dll' from Visual Studio directory to AgentBin directory if it does not exist
    $agentWorker = Join-Path $agentHome "agent\Worker"
    $targetPath = Join-Path $agentWorker "Microsoft.WITDataStore64.dll" # Only compatible with x64 process #TODO use constant instead
    if(-not (Test-Path $targetPath))
    {
        $wITDataStore64FilePath = Get-WITDataStore64
        Write-Host "Copying $wITDataStore64FilePath to $targetPath"
        Copy-Item $wITDataStore64FilePath $targetPath | Write-Verbose
    }

    $wiStore = Get-WorkItemStore -tpcUri $tpcUri -agentWorker $agentWorker

    # Retrive GLOBALLISTS
    $xmlDoc = Invoke-GlobalListAPI -export -wiStore $wiStore
    $gls2 = Update-GlobalListXml -globalListsDoc $xmlDoc -glName $globalListName -buildNumber $buildNumber

    Invoke-GlobalListAPI -import -globalLists $gls2 -wiStore $wiStore
}

Update-GlobalList

这是Github repo的链接，欢迎反馈=> https://github.com/GregoryOtt/UpdateWiBuildNum/blob/master/Update-GlobalList.ps1

于 2016-06-08T07:23:25.213 回答
3

[免责声明 - 我在新的构建系统上工作]

工作项上的全局列表是一种可以追溯到 TFS 原始版本的机制。它在那个时代很有效（夜间构建、预 CI 和 CD 敏捷性）。它开始分崩离析，并且在 TFS 中没有显示为适当的关系。我当时在 WIT 工作，我们需要一个可查询的机制，这就是我们所拥有的（怪我 :)

所以，当我们开始一个新的构建系统时，我们不想重建东西并重复同样的错误。我们正在尝试采用敏捷、增量的方法来构建更好的构建系统。

在下一个 sprint (88) 中，我们开始着手在构建和工作项之间建立适当的链接，WIT 团队也在努力使它们更加一流。您将看到的第一件事是 WIT 表格上的一个链接，它也应该是 QU1（至少是其中的一部分）。

我们意识到这确实留下了一些差距，但我们正在努力弥补它们（门控和标签来源是另外两个），并希望以更好的方式获得更好的长期产品。

就解决方法而言，应该可以通过 powershell 和我们的客户实现自动化，但我们没有任何罐头供其他人使用。

于 2015-08-19T13:11:17.460 回答