RTC: where are stored build result attachments?
When you execute a build with the RTC (4.0.6) build environment, the compiled artifacts generated by the build process are attached to the build result and can be downloaded from it.
However, I wonder where they stored before you download them.
If they are they stored in the RTC database, the db will quickly increase its size with lots of mostly useless binary data.
Which is the best practice to avoid this issue?
However, I wonder where they stored before you download them.
If they are they stored in the RTC database, the db will quickly increase its size with lots of mostly useless binary data.
Which is the best practice to avoid this issue?
Accepted answer
When you execute a build, the build process commonly stores its results first in the local file system, and then depending on the state of the build, copies/moves the result into some derived file repository. The build scripts can then decide whether to upload a reference (commonly, a URL) to one or more of these derived files to the RTC build result, or to upload an actual copy of one or more of the derived files to the build result. As you correctly point out, the latter (storing a copy of the derived file) will load the RTC database with lots of mostly useless binary data, so the former approach (copying the derived file to some derived file repository, and then uploading references to those files to the RTC build result) is recommended.