Deployed a version control system for company, how to use it with binary files -
i tasked setup mercurial version control system our small team of developers (2-3 person). there no version control system before, shared folders , multi-copies. don't have experience in setting version control system except personal projects, happened experienced person in term of version control system in our team. code repository in shared folder in centre server, top leve directory client name, 1 level down project name client.
the problems haven't figure out how deal binary files in our code repository. read, binary files shouldn't version tracked. code repository centralized on server, shouldn't binary in here well? otherwise things image file, , third-party dll files, project wouldn't build or run when cloned centre server. there nice feature mercurial web interface can download whole source package zip or bz2 compressed file, without necessary binary files, download project wouldn't run or compile.
i guess solution including everything version control system except temporary files , files debug purpose, other that, binary files should included? due limitation of version control system, don't think there way them track changes sets binary files, guess have deal version control system.
edit: after more research how setup version-control repository, more recommended way of using version-control "store created manually, , nothing else", quote eric sink.
you want version control can't generate other stuff in version control. source files, , instances of third-party libraries, tools, etc. package relies on.
the binaries built project else entirely, , should treated different sorts of artifacts. if want easy-to-test downloadable archive, adapt build process provide target: should build code, , compress source , built binary desired single file.
Comments
Post a Comment