New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ftrack hook #49

Merged
merged 9 commits into from Feb 28, 2017

Conversation

Projects
None yet
2 participants
@tokejepsen
Member

tokejepsen commented Feb 14, 2017

This should make the Ftrack hook easier for other people to use. Its dependent on pyblish-standalone.

@tokejepsen tokejepsen requested review from mottosso and mkolar Feb 14, 2017

@mottosso

This comment has been minimized.

Show comment
Hide comment
@mottosso

mottosso Feb 17, 2017

Member

What is this for? How do I use it?

Member

mottosso commented Feb 17, 2017

What is this for? How do I use it?

@tokejepsen

This comment has been minimized.

Show comment
Hide comment
@tokejepsen

tokejepsen Feb 17, 2017

Member

I just realize now that I'm missing any form of documentation on this 😟

Its an iteration on the ftrack action; https://www.youtube.com/watch?v=g24YzobsHcc, which now uses pyblish-standalone.

Member

tokejepsen commented Feb 17, 2017

I just realize now that I'm missing any form of documentation on this 😟

Its an iteration on the ftrack action; https://www.youtube.com/watch?v=g24YzobsHcc, which now uses pyblish-standalone.

@tokejepsen

This comment has been minimized.

Show comment
Hide comment
@tokejepsen

tokejepsen Feb 24, 2017

Member

I've updated this PR with documentation for the Pyblish action.

Let me know if there are any issues with this.

Member

tokejepsen commented Feb 24, 2017

I've updated this PR with documentation for the Pyblish action.

Let me know if there are any issues with this.

@tokejepsen

This comment has been minimized.

Show comment
Hide comment
@tokejepsen

tokejepsen Feb 26, 2017

Member

A good workflow I have found with this hook, is to serialize the instances I sent off to the farm. Once the farm has processed the instances, I can publish them without having to open the source host again (Maya for example).

Member

tokejepsen commented Feb 26, 2017

A good workflow I have found with this hook, is to serialize the instances I sent off to the farm. Once the farm has processed the instances, I can publish them without having to open the source host again (Maya for example).

@tokejepsen

This comment has been minimized.

Show comment
Hide comment
@tokejepsen

tokejepsen Feb 27, 2017

Member

Any problems with this PR?

Member

tokejepsen commented Feb 27, 2017

Any problems with this PR?

@mottosso

This comment has been minimized.

Show comment
Hide comment
@mottosso

mottosso Feb 27, 2017

Member

Yes well I still don't know what it does, why you did it or how to use it. There are 2,500 new lines of code so I couldn't exactly sift through it and hope to grok.

How about at least an example, a little snippet, along with an explanation of the problem it solves? Why does anyone need this, and why couldn't they accomplish the thing it does before?

Member

mottosso commented Feb 27, 2017

Yes well I still don't know what it does, why you did it or how to use it. There are 2,500 new lines of code so I couldn't exactly sift through it and hope to grok.

How about at least an example, a little snippet, along with an explanation of the problem it solves? Why does anyone need this, and why couldn't they accomplish the thing it does before?

@tokejepsen

This comment has been minimized.

Show comment
Hide comment
@tokejepsen

tokejepsen Feb 27, 2017

Member

I've updated the documentation about this hook; https://github.com/tokejepsen/pyblish-ftrack/blob/master/README.md#ftrack-hook

Why does anyone need this

The hook is a way of publishing any file type directly from Ftrack. This type of publishing can be done with ftrack-connect, but ftrack-connect lacks everything about CVEI and is just a way of ingesting files into ftrack.

why couldn't they accomplish the thing it does before

We used to have this hook working, but it died due to not being used in production very much; #40.
My new motivation to use it more in production, is to serialize the instances I sent off to the farm. Once the farm has processed the instances, I can publish them without having to open the source host again (Maya for example). This means a better separation between what is published (shared) and what is still a work-in-progress (private), because the farm doesn't automatically publish the renders which hasn't been reviewed by an artist.

As for examples, here I traverse the selected folder for json files to create instances from; https://github.com/bumpybox/pyblish-bumpybox/blob/f2aad5b2cac63d3d57ad09e9ce21270f485db481/pyblish_bumpybox/plugins/collect_json.py

Member

tokejepsen commented Feb 27, 2017

I've updated the documentation about this hook; https://github.com/tokejepsen/pyblish-ftrack/blob/master/README.md#ftrack-hook

Why does anyone need this

The hook is a way of publishing any file type directly from Ftrack. This type of publishing can be done with ftrack-connect, but ftrack-connect lacks everything about CVEI and is just a way of ingesting files into ftrack.

why couldn't they accomplish the thing it does before

We used to have this hook working, but it died due to not being used in production very much; #40.
My new motivation to use it more in production, is to serialize the instances I sent off to the farm. Once the farm has processed the instances, I can publish them without having to open the source host again (Maya for example). This means a better separation between what is published (shared) and what is still a work-in-progress (private), because the farm doesn't automatically publish the renders which hasn't been reviewed by an artist.

As for examples, here I traverse the selected folder for json files to create instances from; https://github.com/bumpybox/pyblish-bumpybox/blob/f2aad5b2cac63d3d57ad09e9ce21270f485db481/pyblish_bumpybox/plugins/collect_json.py

@mottosso

This comment has been minimized.

Show comment
Hide comment
@mottosso

mottosso Feb 27, 2017

Member

Perfect, thanks for breaking it down for me. :)

With that, I'm happy with this.

Member

mottosso commented Feb 27, 2017

Perfect, thanks for breaking it down for me. :)

With that, I'm happy with this.

@tokejepsen tokejepsen merged commit 577900a into pyblish:master Feb 28, 2017

@tokejepsen tokejepsen referenced this pull request Feb 28, 2017

Closed

Cleanup dead executable #40

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment