gpt4 book ai didi

powershell - Teamcity 和 Powershell

转载 作者:行者123 更新时间:2023-12-01 02:29:27 24 4
gpt4 key购买 nike

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

这是 PS 我的脚本:

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

我正在设置以下配置:

enter image description here

但是我在运行 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

最佳答案

格雷默是对的;您可以使用 %build.number%将内部版本号插入到您的脚本中。为了扩展答案,这是 TeamCity 的众多 predefined build parameters 之一。 .如果您在代码文本框中键入开始百分号,TeamCity 将显示一个下拉列表,其中包含您可以插入的所有可能参数。

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

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

该命令将扩展为类似
cp C:\teamcity install\config .\config

这行不通,因为 Powershell 会认为您正在尝试复制文件 C:\teamcity .因此,请确保将整个参数放在引号内:
cp "%agent.work.dir%\config" .\config

作为旁注,使用自定义模板 Configuration Parameters非常有用,因此您可以在多个构建配置中使用相同的脚本。这就像向语言添加函数:您可以重用并且易于修改。

此外,在 7.1.1 之前的 TeamCity 版本中,还有 a bug与运行脚本相关的脚本执行模式设置为 -Command ,因此如果您运行的是 7.0 或更早版本,则使用 -File 更安全

关于powershell - Teamcity 和 Powershell,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/14012318/

24 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com