TeamCity-可用于Build Feature的setParameter值 [英] TeamCity - setParameter value available to Build Feature

查看:197
本文介绍了TeamCity-可用于Build Feature的setParameter值的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一些PS脚本可以编写此TC集成命令:

I've a little PS script to write this TC integration command:

##teamcity[setParameter name='AssemblyVersionString' value='1.0.46.48'

其中设置了一个配置参数,该参数在日志中似乎运行良好.配置参数是在项目级别定义的,具有默认值.

Which sets a Configuration Parameter which appears to run fine in the logs. The Configuration Parameter is defined at the project level and has a default value.

最终,我想使用AssemblyInfoPatcher,但为了进行测试,我添加了一个构建功能来标记git repo,但使用默认值对其进行标记.

Eventually I want to use the AssemblyInfoPatcher but for testing, I've added a Build Feature to tag the git repo but its tagging with the default value.

构建过程中的更改是否应该在构建功能运行时可见"?

Are changes during the build supposed to be 'visible' to the Build Features when they run??

推荐答案

钉了它.

在构建完成后通过查看(非常有用的)Parameters选项卡,将列出所有可用于构建的值,以及一个在构建过程中更改的值的小图标!

By looking in the (very useful) Parameters tab after the build completes, all the values made available to the build are listed, along with a little icon for those that are altered during the build!

我的AssemblyVersionString参数未更改.这使我仔细检查了日志,发现终止的]丢失了!

My AssemblyVersionString parameter was unchanged. This caused me to check carefully the logs and I noticed that the terminating ] was missing!

修复了我的PS脚本及其工作.如果可以的话,我现在去吃午餐.

Fixed my PS script and its working. I'm going to go to lunch now if that's alright.

这篇关于TeamCity-可用于Build Feature的setParameter值的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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