Hi,
I was going to play with this new job type, but really need some docs to get me started!
Any API commands?
Thanks,
Mike
Yeah, we really need to get working on some updated docs…
Here are the flags to add to your job info file:
MaintenanceJob=True
MaintenanceJobStartFrame=0
MaintenanceJobEndFrame=0
The MaintenanceJobStartFrame and MaintenanceJobEndFrame options are actually optional, and will just default to 0. These control which values are returned from the GetStartFrame() and GetEndFrame() functions in the plugin API. The idea is that these frame numbers will be passed to every task so that you can perform the same operation across all machines. If your plugin doesn’t care about frame numbers, then you can just ignore them.
Cheers,
- Ryan
Cool!
-b
Hi
I modified the General Python Submission script (“DeadlineRepository6/scripts/Submission/PythonSubmission.py”) with “MaintenanceJob=True” in the “Create job info file…”-section. But after submission, it’s only executed on one machine even if the job has no limits and can use all the machines on the farm. I have a small python script to do some rsync of our c4d installation that is submitted with the job:
[code]
import subprocess
p = subprocess.call([“mkdir”, “path…”])
print p
q = subprocess.call([“mount”, “-t”, “afp”, “path…”])
print q
r = subprocess.call([“rsync”, “-rtuv”, “–delete”, “path…”, “path…”])
print r
s = subprocess.call([“umount”, “path…”])
print s[/code]
Cheers
Bonsak
When the maintenance job was submitted, how many tasks were created for it? There should be one task for each slave in your farm, so if the correct number of tasks aren’t being created, there must be a bug there…
Only one task is created.
-b
Yeah, that would be a problem. 
Can you zip up and post your modified script? We’ll test it out here and try to figure out what’s going on.
Thanks!
- Ryan