- TEAMCITY SERVICE MESSAGES HOW TO
- TEAMCITY SERVICE MESSAGES UPDATE
Command: /opt/microsoft/powershell/6/pwsh -NoProfile -NonInteractive -File /opt/TeamCity/buildAgent/temp/buildTmp/powershell1234487986819058447.ps1 Working directory: /opt/TeamCity/buildAgent/work/74e814b1d9185321 PowerShell Executable: /opt/microsoft/powershell/6/pwsh PowerShell running in non-virtual agent context Here is the output from the build log: Step 4/4: Putting it together (PowerShell) %pilotName% was one of the pilots of the %starShipName%. PilotName = Write-Output -InputObject $params Write-Output " `n In the film %film% there is a starship called the %starShipName%. $params = are the populated parameters that were set in the build configuration as empty:
Options: Checked Add -NoProfile argument. Script Source: See code under each build step heading below. Execute Step: If all previous steps finish successfully. I’m using PowerShell Core Version 6.1.1 running on Ubuntu but this will work on PowerShell desktop too. Where the steps differ is in the source code box which I’ll set out separately. Here are the general build settings for each step. As noted in the TeamCity documents, the modified values of the parameters will be available in the build steps that follow (if you need to use them in the current build step, assign them to a variable in that script before using that variable to set the system message value). This demo breaks down querying the Star Wars api into different build steps just to demonstrate the passing of parameters (you could easily do this in one step!). "#teamcity" Updating the parameters with PowerShell However, in PowerShell # is a comment so you must enclose the statement in double quotes. The documents show the following example for setting parameters: #teamcity Now the parameters are set up, they can be updated in the scripts or source with service messages. filmUrl - string (used as the first call to the Star Wars API). I have tested and found these work well and you don’t need to prefix them like the environment and system variables. I am using the configuration parameters throughout. There are 3 types of parameter in TeamCity: TEAMCITY SERVICE MESSAGES UPDATE
You can also create empty parameters and update them to pass values between individual build steps.
TeamCity ParametersĬreating parameters is a great way for creating flexible build steps and making them more reusable. It uses retrieving Star Wars data from the swapi Star Wars API as an example of getting data with PowerShell, setting a variable in a build step and using it in the preceding build steps.
TEAMCITY SERVICE MESSAGES HOW TO
This post will show how to set and pass variables in PowerShell TeamCity build steps. Updating the parameters with PowerShell.Updating TeamCity build step parameters using PowerShell
0 kommentar(er)
