Team City 和 Power Shell [英] Team City and Power Shell

查看:56
本文介绍了Team City 和 Power Shell的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我是团队城市的新手,正在尝试使用 REST API 调用部署工具.我正在尝试将来自团队城市的 build.number 传递给 power shell 脚本.我的问题是如何从 TeamCity 运行 PS 脚本并将 $build 参数值传递给它

I'm new to team city and trying to invoke deployment tool using REST API. I'm trying to pass power shell script the build.number from team city. My question is how can I run PS script from TeamCity and pass it the $build parameter value

这是我的脚本:

param (
    [string]$build = "#build#"
)
$cred = New-Object System.Net.NetworkCredential("user", "password")
$url = 'http://server-ip:8080/datamanagement/a/api/create-release'
$request = [Net.WebRequest]::Create($url)

$request.ServicePoint.Expect100Continue = $false
$request.PreAuthenticate = $true

$request.Credentials = $cred
$request.Headers.Add("AUTHORIZATION", "Basic c3VwZXJ7482ewfc3974yOnN1c2Vy"); # user:pass encoded in base 64
$request.ContentType = "application/json"
$request.Method = "POST"

$data = (New-Object PSObject |
    Add-Member -PassThru NoteProperty environment "QA" |
    Add-Member -PassThru NoteProperty template "Regression on AutoNolio" |
    Add-Member -PassThru NoteProperty release "Nolio build: $build" |
    Add-Member -PassThru NoteProperty application "RunAutomation" |
    Add-Member -PassThru NoteProperty version "$build" |
    Add-Member -PassThru NoteProperty doStepsValidation "false" |
    Add-Member -PassThru NoteProperty releaseType "Major"
) | ConvertTo-JSON

Write-Host $data
#   Write-Host $cred.Password


$bytes = [System.Text.Encoding]::ASCII.GetBytes($data)

$request.ContentLength = $bytes.Length

$requestStream = [System.IO.Stream]$request.GetRequestStream()
$requestStream.write($bytes, 0, $bytes.Length)

$response = $request.GetResponse()

[IO.Stream] $stream = $response.GetResponseStream()
[IO.StreamReader] $reader = New-Object IO.StreamReader($stream)
[string] $output = $reader.readToEnd()
$stream.flush()
$stream.close()

# // return the text of the web page
Write-Host $output

我正在设置以下配置:

但是我在运行 buld 时遇到了这个错误:

But I'm getting this errors when running the buld:

[17:43:37]Checking for changes
[17:43:37]Publishing internal artifacts (1s)
[17:43:37]Clearing temporary directory: C:\BuildAgent2\temp\buildTmp
[17:43:37]Checkout directory: C:\BuildAgent2\work\467ac7a3aa06b293
[17:43:37]Updating sources: agent side checkout (3s)
[17:43:41]Starting: C:\Windows\sysnative\cmd.exe /c C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NonInteractive -build 14 -Command - <C:\BuildAgent2\temp\buildTmp\powershell3648184935303703255.ps1 && exit /b %ERRORLEVEL%
[17:43:41]in directory: C:\BuildAgent2\work\467ac7a3aa06b293
[17:43:41]-build : The term '-build' is not recognized as the name of a cmdlet, 
[17:43:41]function, script file, or operable program. Check the spelling of the name, or 
[17:43:41]if a path was included, verify that the path is correct and try again.
[17:43:41]At line:1 char:1
[17:43:41]+ -build 14 -Command -
[17:43:41]+ ~~~~~~
[17:43:41]    + CategoryInfo          : ObjectNotFound: (-build:String) [], CommandNotFo 
[17:43:41]   undException
[17:43:41]    + FullyQualifiedErrorId : CommandNotFoundException
[17:43:41] 
[17:43:41]Process exited with code 1
[17:43:41]Publishing internal artifacts
[17:43:42]Build finished

推荐答案

Graimer 是正确的;您可以使用 %build.number% 将内部版本号插入到您的脚本中.为了扩展答案,这是 TeamCity 的许多预定义构建参数.如果您在代码文本框中输入开始百分号,TeamCity 将显示一个下拉列表,其中包含您可以插入的所有可能参数.

Graimer is correct; you can use %build.number% to insert the build number into your script. To expand on the answer, this is one of many of TeamCity's predefined build parameters. If you type an opening percent sign in the code textbox, TeamCity will show a dropdown containing all the possible parameters you can insert.

您必须小心一些,因为它们是作为裸词插入到您的脚本中的.例如,如果您将常用配置文件存储在 %agent.work.dir% 中,并且您尝试运行以下复制命令:

You have to be careful about some, because they're inserted as barewords into your script. If, for example, you store common configuration files in %agent.work.dir%, and you try to run the following copy command:

cp %agent.work.dir%\config .\config

该命令将扩展为类似

cp C:\teamcity install\config .\config

这行不通,因为 Powershell 会认为您正在尝试复制文件 C:\teamcity.因此,请确保将整个论点放在引号内:

And that won't work, because Powershell will think you're trying to copy the file C:\teamcity. So make sure you put that entire argument inside quotes:

cp "%agent.work.dir%\config" .\config

附带说明,使用带有自定义配置参数的模板 非常有用,因此您可以在多个构建配置中使用相同的脚本.这就像向语言添加函数一样:您可以重用并且易于修改.

As a side note, using templates with custom Configuration Parameters is incredibly useful, so you can use the same scripts in multiple build configurations. It's like adding functions to a language: you get reuse and ease of modification.

此外,在 7.1.1 之前的 TeamCity 版本中,存在与以下相关的一个错误在脚本执行模式设置为 -Command 的情况下运行脚本,因此如果您运行的是 7.0 或更早版本,使用 -File

Also, in versions of TeamCity before 7.1.1, there's a bug relating to running scripts with the Script Execution Mode set to -Command, so if you're running 7.0 or earlier, it's safer to use -File

这篇关于Team City 和 Power Shell的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆