committing binaries svn


i've searched around bit, nonetheless haven't found tolerable answer, i'd hear your opinions this.



i have integrate collection i have transform muster few servers each then. source managed svn repository.



to save myself worry duplicating binaries prolongation servers ftp identical means (i have means building projects servers), i'm pondering formulating an area repository dedicate well. i following simply collect many tide chronicle executables svn server whenever i need them.



since i don't indispensably wish update/commit binaries each i work source, i emanate folder binaries subfolder project. committing binaries following (and should) separate, unvarying act.



--- trunk
--- project1
--- project2
--- built
--- project1
--- project2


as distant i see, there should problems setup. i'd unequivocally following give both source supplement binaries unparalleled tag, means collect all belongs together during once.



--- tags/project1/release2/ 
includes files
--- trunk/project1/ supplement 487 and
--- built/project1/ supplement 488


is i'm after possible, i grasp it?
should i instead looking during proceed clarify problem?



Comments

Popular posts from this blog

list macos calm editors formula editors

how hibernate @any-related annotations?

why does floated <input> control floated component slip over too distant right ie7, nonetheless firefox?