Event Scripting for new pools

Deadline
1

I’m reading on the Event Plug-in Scripting and I’m not seeing a way to run an event script upon creating a new pool. Perhaps its not the intended purpose, but we use pools as jobs. So jobs A gets a pool, job B gets a pool. Is it possible to have an event script run upon pool creation?

If there isn’t, is it possible to script pool creation? In the same script I could accomplish the additional tasks I was interested in running in the event script.

Thanks!
brad

2

Hey Brad,

The event plugins currently only respond to job-related events. That may change in the future, but for now you can script pool creation. See the Pool and Group functions under the RepositoryUtils section here:
thinkboxsoftware.com/deadlin … _Utilities

Hope that helps!

  • Ryan
3

As a novice at scripting, I need to do a LOT of “what does this do” testing. Is there a way to run some of these commands in deadline without having to get a script to a (more or less) completed state. I can test all my non-deadline commands in a Python shell, but deadline specific commands I’m left wondering if its going to do what i think it will do.

Does that makes sense? At the moment I want to test this command: void SetSlavePools( tuple poolNames ) Sets the pools assigned to this slave.

So if I could, I’d fire up a deadline command line and start punching away attempts to try and add computer to a pool via the commands in the manual. Is there such a tool?

4

You can use VS or Eclipse to build a dev environment to help testing the functionality of a particular command within the Deadline environment.
Essentially, you will need to use the “deadlinecommand.exe” in /repository/bin/windows/ to execute a command.
Initial setup can be a little time-consuming, but it makes dev a lot easier in the long run.
HTH,
Mike

5

Thanks, I’ll take a look at that and see if I can’t get something like that setup! Should help me avoid nonsense issues and errors I cause everyone by having broken scripts erroring while artists are trying to render.

6

You can also take a copy of your entire repository and call it say; “dev_repository” and then connect to this version whist you carry out dev. work / test stuff and then when ready, copy the updated py code over to the production repository. Taking this even further, you can also use Source Control such as SVN, GIT or MS TFS to safeguard your dev. time. Eclipse works ok with all 3 Source Control systems and VS prefers TFS, but will work with the other 2 to various levels of sucess.