We’re trying to submit a job to Deadline via the command line, but have it seen as a Nuke job rather than a Command Line job. We’re not using the submission files to do this. I appended -prop Plugin=Nuke to the end of our submission command, but it said that it was already set to a command line job. Is there a way to make it a Nuke job as opposed to a Command Line job without the use of submission files? Thanks again.
The -SubmitCommandLineJob option is only meant to submit arbitrary command line jobs to the CommandLine plugin. If you want to submit jobs to the Nuke plugin, you will have to build up the necessary submission files. The Nuke plugin depends on the contents of the plugin info file (the 2nd submission file) to get the rendering info it needs.
One option you have would be to create a intermediary app/script/batch file that takes your command line arguments, creates the submission files, and then calls deadlinecommand to submit them.
Cheers,
- Ryan
I created the plugin info file but when using deadline command.exe it tells me :
Deadline Command 5.2 [v5.2.0.47700 R]
Error: could not find job info file: Plugin=Nuke (Deadline.Submission.DeadlineSubmissionException)
at Deadline.Submission.SubmissionUtils.SubmitNewJob(String[] args)
at Deadline.Submission.Submit.Perform(String[] args)
I know it’s user error…
what’s the issue?
plugin info file below:
Plugin=Nuke
Name=Ingest:RA036_020_BS2_4K_V02
Comment=
Department=
Pool=
Group=
Priority=50
MachineLimit=
TaskTimeoutMinutes=
EnableAutoTimeout=
ConcurrentTasks=
LimitConcurrentTasksToNumberOfCpus=
LimitGroups=
JobDependencies=
OnJobComplete=
Frames=1001-2051
ChunkSize=20
SceneFile=z:/job/after_earth/shots/ra/ra036_020/plates/images/RA036_020_BS2_4K_V02/4096x2160/RA036_020_BS2_4K_V02.nk
Version=6.3
Threads=0
RamUse=0
Build=64bit
BatchMode=False
NukeX=False
ContinueOnError=False
Can you post the full command you’re trying to run?
It sounds like you are only passing a single file in the command line. When this is the case, Deadline parses that file for command line arguments, which would explain the error you’re getting. When submitting a job, you need at least two files: the job info file and the plugin info file, in that order:
thinkboxsoftware.com/deadlin … o_Deadline
Cheers,
- Ryan
So the plugin info file…what does that contain?
Where can I see an example of such a file?
The docs are really descriptive on the job info file (which I have made) but not so much (in terms of examples) with the plugin info file.
Yes, I am only passing the job info file right now which clearly is the problem 
Rob
The plugin info file is specific to the plugin that the job is using. We don’t have any documentation on the inner workings of our plugins, so the best way to see what a plugin info file looks like is to submit a job using our built-in submitters, and look at the two .job files it creates. There are usually created in the system temp folder.
You could also take a look at the submitter itself. For example, \your\repository\scripts\Submission\NukeSubmission\NukeSubmission.py shows how both files are created before the job is submitted.
Cheers,
- Ryan
Ah, ok, I was putting all that into one file. Ok, good to know. thanks!