BF build properties are not getting updated at project level in a build.
There are the Environment variables that are passed to BF from RTC.
347 13/09/18 11:44 SET oldsnapshotFile=BuildConfig\BF_PROJECTNAME\RTCStream_xxxHost_oldsnapshot.txt 100 13/09/18 11:44 SET RTCStream=xxx_xxx_03 109 13/09/18 11:44 SET xxxHost=x03 111 13/09/18 11:44 SET BuildConfig=C:\BuildWork\BuildConfig 268 13/09/18 11:44 SET BF_PROJECTNAME=400_xxx Thats how the ENV looks like 415 13/09/18 11:44 ENV oldsnapshotFile=BuildConfig\BF_PROJECTNAME\RTCStream_xxxHost_oldsnapshot.txt 432 13/09/18 11:44 ENV RTCStream=xxx_xxx_03 165 13/09/18 11:44 ENV BuildConfig=C:\BuildWork\BuildConfig 373 13/09/18 11:44 ENV BF_PROJECTNAME=400_xxx 592 13/09/18 11:44 ENV xxxHost=x03 so we are setting oldsnapshotFile=BuildConfig\BF_PROJECTNAME\RTCStream_xxxHost_oldsnapshot.txt And thats what gets assigned after override. 231 13/09/18 11:44 MKDIR [C:\BuildWork\BuildJob\400_xxx\BUILD_02] 232 13/09/18 11:44 RESULT 0 (0) 233 13/09/18 11:44 EXEC EXEC BUILD_02 BUILD_02_400_xxx_x03_xxx_xxx_03_20130920_01 234 13/09/18 11:44 STEP .bset env "oldsnapshotFile=${BuildConfig}\${BF_PROJECTNAME}\${RTCStream}_${xxxHost}_oldsnapshot.txt" 235 13/09/18 11:44 EXEC .bset oldsnapshotFile BuildConfig\BF_PROJECTNAME\RTCStream_xxxHost_oldsnapshot.txt So the override is not getting done by the BF |
2 answers
Zeeshan is correct, an upgrade is the best solution to the problem. I did want to add this document to the question. This document explains how this entire process works in detail. It think that you could find a valid work around from reading this article, in the event that an upgrade is not possible at this moment.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.