teamcity - Least-impact solution to binary references in VCS -


we using teamcity 2017.1 , have been using years great joy. long time ago, decided third-party binaires should put subversion (our vcs of choice).

this has worked fine, on time repos has grown quite large, , combined our being better , better @ using teamcity, have dozens of build configurations all uses third-party binaries.

our third-party folder called department , around 2.6 gb in size. such not bad, remember folder used pretty every single project on build server!

now, agree says should use nugets, network shares etc., , work great new projects. however, have lot of history , cannot begin change every single solution , branch.

a co-worker came idea, if made single build project in reality did nothing keep single folder updated our department stuff. need find way reference this, without have change our projects , solutions.

my initial though using snapshot dependencies , create symbolic link first build step , remove last, in order achieve same relative levels.

but there better way? other people do?

and keep in mind, replacing nugets or else not option.

let me follow idea of colleague , improve it. there build configuration monitors subversion repository , copies packages network share. network share used development teams nuget repository. projects convert dependencies binary reference nuget reference enjoy faster build. when teams use nuget repositories may kill subversion.


Comments

Popular posts from this blog

angular - Ionic slides - dynamically add slides before and after -

minify - Minimizing css files -

Add a dynamic header in angular 2 http provider -