Questions about storing binaries in SCM and as attachments in RTC
We use RTC 5.0.2 with Oracle as the back end DB
We want to do continuous build and store the compiled binaries / libraries as part of streams
Are there any disadvantages of storing compiled binaries are part of streams ?
Oracle sure can hold bigger data size but I would like to know if there are any disadvantages of storing them in streams.
Some time back I read that it is not recommend to store large file sizes as attachments. Both attachments and scm are part of DB so I am curious to know about this
Thank you!
We want to do continuous build and store the compiled binaries / libraries as part of streams
Are there any disadvantages of storing compiled binaries are part of streams ?
Oracle sure can hold bigger data size but I would like to know if there are any disadvantages of storing them in streams.
Some time back I read that it is not recommend to store large file sizes as attachments. Both attachments and scm are part of DB so I am curious to know about this
Thank you!
Accepted answer
You should be very, very careful what you store in an SCM system.
Binaries and object files and the like can be stored in Streams. For example the JKE Banking example stores the ECJ compiler in one component. Some customers also want to store other development tools and libraries there.
This is acceptable if it changes infrequently.
My 2 cent on your case: If you store each build with all binaries in RTC, you will only make the hardware supplier of your hard drives happy. You will fill your database with a lot of data that should not be in there and you will overload your system and make it slow.
I would suggest other solutions solutions like an network storage to store the binaries for each build.
See: Build Artifacts Publishing Using HTTP Servers in Rational Team Concert
and
for some ideas.
Binaries and object files and the like can be stored in Streams. For example the JKE Banking example stores the ECJ compiler in one component. Some customers also want to store other development tools and libraries there.
This is acceptable if it changes infrequently.
My 2 cent on your case: If you store each build with all binaries in RTC, you will only make the hardware supplier of your hard drives happy. You will fill your database with a lot of data that should not be in there and you will overload your system and make it slow.
I would suggest other solutions solutions like an network storage to store the binaries for each build.
See: Build Artifacts Publishing Using HTTP Servers in Rational Team Concert
and
for some ideas.
Comments
1 vote
1 vote
1 vote
1 vote
1 vote
2 votes
showing 5 of 8
show 3 more comments