2012-09-20 6 views
6

Come si ottiene TeamCity per l'output dei messaggi nel registro di build con PowerShell?Richiesta di TeamCity per riconoscere i messaggi PowerShell

Sto utilizzando TeamCity 7.1.

Ecco il mio PowerShell Corporatura Passo: enter image description here

Lo script è:

write-host "##teamcity[message 'Getting production info']" 

if ($LASTEXITCODE -ne 0) { 
    write-host "##teamcity[message 'Production Remote Not Found: Creating Remote']" 

    write-host "##teamcity[message 'Pushing to Remote']" 
    #git push production 

} else { 
    write-host "##teamcity[message 'write-output: Production Remote Found: Pushing to Remote']" 
    #git push production 
} 

E l'unica cosa che sto ottenendo nel registro build è:

[17:02:58]Skip checking for changes - changes are already collected 
[17:02:59]Publishing internal artifacts (1s) 
[17:03:00][Publishing internal artifacts] Sending build.start.properties.gz file 
[17:02:59]Clearing temporary directory: C:\BuildAgent2\temp\buildTmp 
[17:02:59]Checkout directory: C:\BuildAgent2\work\7669b6a04f96908d 
[17:02:59]Updating sources: agent side checkout 
[17:02:59][Updating sources] VCS Root: Portal Master 
[17:02:59][VCS Root: Portal Master] revision: c5c6a9a0d491ee2c64ce98e48b0d67c422237698 
[17:02:59][VCS Root: Portal Master] Resetting Portal Master in C:\BuildAgent2\work\7669b6a04f96908d to revision c5c6a9a0d491ee2c64ce98e48b0d67c422237698 
[17:02:59]Starting: C:\Windows\sysnative\cmd.exe /c C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NonInteractive -File C:\BuildAgent2\temp\buildTmp\powershell1349912883332714566.ps1 
[17:02:59]in directory: C:\BuildAgent2\work\7669b6a04f96908d 
[17:03:00] 
[17:03:00] 
[17:03:00] 
[17:03:00]Process exited with code 0 
[17:03:00]Publishing internal artifacts 
[17:03:00][Publishing internal artifacts] Sending build.finish.properties.gz file 
[17:03:00]Build finished 

risposta

14

Come descritto nella documentation Il messaggio di servizio "messaggio" può avere più argomenti, quindi è necessario specificare almeno l'argomento "testo": "##teamcity[message text='Getting production info']"

Lo script sarà

write-host "##teamcity[message text='Getting production info']" 

if ($LASTEXITCODE -ne 0) { 
    write-host "##teamcity[message text='Production Remote Not Found: Creating Remote']" 

    write-host "##teamcity[message text='Pushing to Remote']" 
    #git push production 

} else { 
    write-host "##teamcity[message text='write-output: Production Remote Found: Pushing to Remote']" 
    #git push production 
} 
+1

+1 @JoeYoung Ho appena stato punto con questo, però, secondo le [documenti] (http://confluence.jetbrains.com/display/TCD8/Build + Script + Interaction + con + TeamCity # BuildScriptInteractionwithTeamCity-ServiceMessages) non dovresti definire esplicitamente l'attributo 'text'; questo viene trattato come un * messaggio di attributo singolo * e dovrebbe funzionare. Tuttavia, non lo fa e l'uso di 'text' fa il trucco. – James