Publish separately VS pull newest version

[dshlai]

You guys should also checkout Alembic with Git:

J CUBE Inc — Imagination Engine

This works mainly with Alembic currently. Maybe your system can use this to checkout different Alembic branch where one is the Approved branch while the other one is the latest branch

[marcus]

Yeah that project is pretty interesting, I probably wouldn’t rely on it for pipeline work yet however since it’s so new.

If you are set on Git, then it did recently gain more support for large files which is based on an older and seemingly stable basis called “git annex”.

But I’m sceptical as to whether Git is the right approach here, since the Git methodology is “clone everything” which can be difficult when your asset library is in the terabytes range. SVN, Perforce and the like are on the opposite side of the fence, “clone what you need”, which I think might be better suited for out kind of work. But I don’t know of anyone who has actually tried and I’d be interested in seeing what benefits lie therein, as I’m sure there are many (maybe more than there are downsides!)

[mkolar]

Here is the worksheet, it’s quite in-depth and potentially cryptic. It builds on previous versions that you can also find linked in there.

Magenta 0.6

The idea is to bundle it up and make the proper introductions here on the forums when the time is right (which is why it’s “private” currently), but if you are interested we might be able to do that sooner.

Very very nicely presented. I’ve been toying with versions of similar ideas (just way more scattered around projects), for a while now, but you guys are putting it into a very nice and understandable package. I took a few months break from following magenta development (no dev time on my side currently), but I’ll try to get involved more considering am very much on the same page with you with most of the concepts presented there. I do have a few points for discussion but won’t be spamming this thread with those at this point.

the pushed file is always the same as the newest pulled file

We’ll be trying the same system here, however I want to employ logic where the ‘pushed’ file is always the same as the ‘approved’ file, which is not necessarily the latest. It happens fairly regularly that director eventually decided to unapprove v05 and wants everyone to go back to v03. Code wise I’d run automatic action that copies file that get’s approved and overwrites the ‘pushed’ file with that. Publishing wise on artist side we then only need to deal with creating new versions of assets. The ‘push’ (or what I call ‘master’ version) is then created automatically when supervisor approves some version number. If he accidentally approves 2 of them (totally happens), then the latest one approved becomes the master by definition.

[marcus]

[quote=“mkolar, post:23, topic:97”]
but I’ll try to get involved more considering am very much on the same page with you with most of the concepts presented there. I do have a few points for discussion but won’t be spamming this thread with those at this point.[/quote]

You’d be welcome to, @mkolar. At the moment, I think both me and @BigRoy feel we’re onto something that works; the current status is that he’s set to run it through a couple of projects within the coming days at Colorbleed to work out any kinks.

As soon as he’s back from holidays, we should catch up on where things are at in the Magenta thread.