Hey Justin, Thanks for your reply, we have about 200 computers for production and around 50 projects on-going at the same time. Not like big studios, most of our projects are part of the full production pipeline, which means project A maybe animation while project B might be only rendering, which confused me a lot since each project has its own naming and file structuring conventions, and most of our projects require us to map a network url as a drive. By mapping the shared storage everyone has the right to get there and work on it, which makes tracking files difficult. I do realize that Git has the ability to track the whole structure and hash each file it doesn't ignore, but my question is, will the reset function that Git offers violate the binary file? And on three approaches you listed on the last email, do you mean using svn or git to track files on a pure file system(with...)? Or add a database to track them? Thanks! Jerry
在 2014年2月17日星期一UTC+8上午3时39分01秒，Justin Israel写道： > > Most of the production application files are binary, and popular version >>> control solutions/ideas are code/ascii-oriected, >>> >> > git tracks ascii or binary files by hashing their content. If the file is > ascii, then it can provide the extra tools for diff, merge, changes, ... > > >> which make them less appliable for production(am I correct?). How do >>> you figure this out? I know lots of big studios have Shotgun or equivalent >>> production management system, but i don't think my supervisor would be >>> willing to pay that much. I heard Tactic is also a good one(and a python >>> one), have you guys ever used Tactic? How good is it? >>> >>> > I haven't had the opportunity to use either Shotgun or Tactic yet, given > the studios I have worked for thus far. But here are the kinds of > combinations I have seen: > > > - Version/Publishing solution is its own service ; Production Tracking > / Assignments is its own service that sources from VnP > - Pure manual file system conventions for storing in a versioned > structure; completely detached production tracking > - Pure manual file system ... ; Separate tools update metadata + > Production tracking sources that metadata > > The one thing I haven't worked with yet is the off the shelf solutions > that set you up with the entire pipeline in one box: Asset and Production > Tracking, Version and Publishing, data management > > Like Marcus was saying, it comes down to: > > 1. how robust of a system you want, for integration > 2. how many areas of the the pipeline it needs to cover > 3. how many people it needs to serve > 4. how much you are willing to spend > 5. do you have on-site developers > > "Rolling your own" can be an endeavor, but then again if your needs are > very small then maybe you only need it to do a few simple things. > > -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/4ba56e4b-a681-4619-a9d7-aa9a8a0a3a07%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
