If build configuration A depends on B by snapshot dependency you can use the following undocumented property: %dep.<B build conf id>.system.build.number%
You guys are brilliant! That works perfectly. Any chance that property will be documented in the future?
Just for anyone's future reference, the property reference would be %dep.bt85.system.build.number% if the target configuration's buildTypeId happens to be bt85. You can get the buildTypeId from the link to the dependency build configuration. That took me a couple of tries to figure it out.
If build configuration A depends on B by snapshot dependency you can use the following undocumented property:
%dep.<B build conf id>.system.build.number%
--
Pavel Sher
You guys are brilliant! That works perfectly. Any chance that property will be documented in the future?
Just for anyone's future reference, the property reference would be %dep.bt85.system.build.number% if the target configuration's buildTypeId happens to be bt85. You can get the buildTypeId from the link to the dependency build configuration. That took me a couple of tries to figure it out.
Yes it's a good feature!
It should be a good idea to be able to get the build number of the build which has triggered the current build!
something like this :
%trigger.system.build.number%
and/or a pattern : {triggerBuilNumber}
And is there any way to get the build that has triggered the running build programmatically?
something like this : SRunningBuild.getTrigger()
Regards,
Xavier
Hello Xavier,
Regarding the API to access TriggeredBy information, please see SBuild::getTriggeredBy (available only in TC 4.0+).
Good point about trigger.system.build.number. Could you please file this into our tracker?
Kind regards,
KIR