It would be nice if we could add certain job properties that would be picked up by the dependency view, to add more details about what the scriptDependency checker is looking for.
Currently, all our jobs just show the same generic script that handles the dependency checking 
Not very helpful if we are trying to figure out which dependency its still waiting for.
Hey Laszlo,
Could you give an overview (and maybe an example) of how you would see this working? I’m not sure I quite understand what you are requesting.
Thanks!
Basically, our jobs have different types of dependencies. They can have fumefx, flowline, TP cache etc dependencies in any combination.
Our previous setup worked by putting the base path and the type of dependency into an xml file, which is then parsed on the slave (in deadline’s case on pulse), and the dependencies are handled.
Would be great however, if i could somehow display the actual types&paths in the dependency node graph, as opposed to just what we have now, which is just a node link to the central dependency handler script (which is the same for all jobs).
A sidenote: in beta7, the script dependency disappeared from the dependency view, the job shows as if it wasnt dependent on anything:
Thanks for the additional details. Could you perhaps just store that dependency info in the job’s extra info properties? If not, perhaps we could add an “note” field for each script dependency that allows you to enter arbitrary information that would show up in the script node.
Yeah i am about to reimplement it as extra info attributes so that we have some ability to track this through the monitor. But long term, it would be nice to see that in the node view, it looks so fancy and all
