deployment - Version control of deliverables -


we need regularly synchronize many dozens of binary files (project executables , dlls) between many developers @ several different locations, every developer has date environment build , test at. due nature of project, updates must done , on-demand (overnight updates not sufficient). not pretty, stuck time.

we settled on using regular version (source) control system: put binary files, get-latest before testing , check-in updated dll after testing.

it works fine, version control client has lot of features don't make sense , people confused.

are there tools better suited task? or may different approach?

update:

i need clarify it's not tightly integrated project - more extensible system heap of "plugins", including thrid-party ones. need make sure modules-plugins works nicely recent versions of each other , core. centralised build suggested considered initially, it's not option.

i'd take @ rsync.

just create .cmd file contains call rsync correct parameters , let people call that. rsync smart in deciding part of files need transferred, it'll fast when large files involved.

what rsync doesn't though conflict resolution (or detection), in scenario described it's more reading central place rsync designed handle.


Comments

Popular posts from this blog

c++ - How do I get a multi line tooltip in MFC -

asp.net - In javascript how to find the height and width -

c# - DataTable to EnumerableRowCollection -