Hi guys,

thanks for your insights, great explanation Paul.

What size of studio are we talking about here? If it’s about 20 ppl, all
> running Windows then things are likely a little different then if we’re
> talking 500 ppl running Linux.

The pipeline <https://github.com/timmwagener/helga> i'm concerned with
right now is layed out for approx. 20 ppl. running on Windows. Not yet a
studio pipeline, its for our diploma movie, but nevertheless trying to run
this show as organized as possible :D

As a caveat, we don't use windows much at work, and I think Linux is more
> forgiving, in that once a maya plugin is loaded, you can delete the
> underlying binary (.so, in Linux-land) without much issue (or maybe it's
> our NFS-based filesystem which allows this)?

So far Houdini (our Fx & Lighting/Shading Tool) also runs under Linux
within our pipeline. Will test  if i can delete .so files while an instance
of Houdini is running next time i fire it up under CentOS.

Anyway, while we haven't had this exact issue, the solution we use for this
> general class of problems is a combination of versioned release dirs, and
> package-based environment-variable management to control them.  The idea is
> that every time you release a new version of the plugin, it goes into an
> upticked version release dir:

That seems like the best solution. I will have to look into package
management solutions and set it up like this next time.

Our system is just a python module and has a startup method much like
> maya's initialise().  It handles copying plugins  and python / mel files
> from the repository using robocopy.

Before i reorganized our pipeline with wrapper tools to point to a central
location on the server for plugins etc., i was actually doing the same
thing with a startup script that would copy/setup the local environment.
I'm gravitating more towards the env. var. solution with a wrapper that
points to a central location though, feels a little more elegant to me.

Cheers and in case i'm not writing till tomorrow:
Happy new year everybody! ;)

Timm


On Tue, Dec 30, 2014 at 6:14 AM, Jesse Kretschmer <[email protected]> wrote:

> As Paul and Justin have pointed out, version specific release directories
> are a huge help. I would like to note though that transparency is important
> with renders. My studio uses rush but we have a custom render package that
> contains all the relevant environment information. The plugin versions are
> readily apparent. I leave the policing to the TD on the job.
>
> Most of the time, our projects will lock to a specific version early on
> and won't ever change unless there is a huge bug or fix that comes through.
> For this reason, during the rare transitions the TDs can be very attentive.
> Outliers are found and corrected quite quickly.
>
> Your mileage may vary.
> Good luck; Have fun.
>
>  --
> 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/CANESWi0f-RdLQrgBBooZgLvPxY5TqdszqrrmMapFzWYPjJ0JTg%40mail.gmail.com
> <https://groups.google.com/d/msgid/python_inside_maya/CANESWi0f-RdLQrgBBooZgLvPxY5TqdszqrrmMapFzWYPjJ0JTg%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Timm Wagener*
*Technical Artist / 3D Generalist*

*www.timmwagener.com <http://www.timmwagener.com>*

Email:
*[email protected] <[email protected]>*

Phone:
*0178-2810920*

-- 
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/CA%2Bj65irGHpX%3DDqLyS4zv_TW0wK6RQPCmQiDaEHm8%2BKvE5HbkKg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to