artifactFilePublisher file size limitation
I was curious if this limitation was addressed at all. It seems like a 10meg limitation is a little small. From the description of the activity it sounds like it would do what I want which is to publish the build artifacts. One of the files I want to publish is 35mg big. Is there another activity
Thanks!
Thanks!
3 answers
Hi Jeff,
I did not find a property in the CCM application to change that.
I don't think there is another task to upload. Having said that, I would try to avoid uploading a lot of data, even if it gets pruned if you set the option in the build definition.
One way of solving that (which needs a bit more work) would be to provide a file system area that is exposed by HTTP/FTP. For each build copy the relevant output into a unique folder for the build result and publish the link to the folder to the build result using the artefactLinkPublisher http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/topic/com.ibm.team.build.doc/topics/r_artifactlinkpublisher.html.
This scales better. I would agree that it would be nice to have more automation support for that.
I did not find a property in the CCM application to change that.
I don't think there is another task to upload. Having said that, I would try to avoid uploading a lot of data, even if it gets pruned if you set the option in the build definition.
One way of solving that (which needs a bit more work) would be to provide a file system area that is exposed by HTTP/FTP. For each build copy the relevant output into a unique folder for the build result and publish the link to the folder to the build result using the artefactLinkPublisher http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/topic/com.ibm.team.build.doc/topics/r_artifactlinkpublisher.html.
This scales better. I would agree that it would be nice to have more automation support for that.
I am not able detailed specification about size limitation for a single file? Considering I have lots of files including huge binary files around 6G (less or bigger than it), I am wondering RTC supports it or not? Considering there are so many huges files and the total size is increasing to 1-2T, is there any size limitation for RTC respository? I apprecate if there is such specification to refer to?
Thanks for your help in advance.
Thanks for your help in advance.
The post was around build publishing and my suggestion would be https://jazz.net/library/article/797
For other things there are advanced properties you can look at with respect to file sizes. For sizing, here is additional info: https://jazz.net/library/article/551.
There is also work being done for the next release to be able to delete binaries from SCM.
As a sidenote, I personally would try to upload as few binaries as possible. If binaries are created as a result of a build, I don't think they should go into SCM. Sometimes you need 3rd party libraries you want to have in SCM and that is OK. Even having released binaries in SCM might be OK, although I would go the path of the first article in this post.
Last, if you expect huge amounts of data carefully plan network and IO connections for the DB and file systems.
For other things there are advanced properties you can look at with respect to file sizes. For sizing, here is additional info: https://jazz.net/library/article/551.
There is also work being done for the next release to be able to delete binaries from SCM.
As a sidenote, I personally would try to upload as few binaries as possible. If binaries are created as a result of a build, I don't think they should go into SCM. Sometimes you need 3rd party libraries you want to have in SCM and that is OK. Even having released binaries in SCM might be OK, although I would go the path of the first article in this post.
Last, if you expect huge amounts of data carefully plan network and IO connections for the DB and file systems.