How to move build outputs instead of copy on a promotion in RTC Enterprise extensions ?
While using the promotion definitions from RTC Enterprise extensions, how can i move the build outputs instead of copying from source to the target libraries ? similar to cut-paste instead of copy-paste.
Thank you,
Ravikanth Chavali
|
2 answers
Promotion (with binaries) is really about 2 builds. Its purpose is to deliver sources & copy binaries to avoid to rebuild at the next level. There are many consistency checks to avoid to have binaries out of synch with the sources.
We have seen customers that implement some kind of additional processing on the binaries being promoted. The promotion process creates a promotionInfo.xml that can be used for such processing. You should delete binaries only if you're sure that you're not going to use the binaries with another workflow (e.g. packaging at dev or promotion to another build def). |
Most customers implement some form of "delete behind" logic that gets executed as part of the post promote process (or post build process if you are building at each stream). It would be hard for the product to know what to do here as it depends on your life-cycle. But, I suppose one choice could be to delete the sources and outputs of the previous stream (if they have not already been modified by new versions).
|
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.