We have some custom logs output by 3rd party applications, that we would like to be able to browse through deadline if possible.
I was thinking of something like, adding a task script, that would open / reuse the log browser of deadline, but populate it with these other logs. If the log is still being written, displaying a ‘tail’ on the log.
My first thought was just to add a “OpenLogX” script to the tasks, that would open a tail on the active log, but then i realized there could be any number of logs (from say, previously failed renders on the task)… And i cant really add dynamic entries to the right click menu. Or can i?
Any ideas?
There currently isn’t a way to manually create reports for jobs. Maybe that’s something we can look at adding in a future release.
The only customization available at the moment are the right-click script menus. We would like to look at opening up more hooks in the UI, but we don’t have an ETA for something like that at the moment.
Cheers,
Is there a way to have context sensitive scripts? Like a function in the script that gets called, whether it should be displayed for the job/task etc?
Currently no. The script itself can add some logic to see if it should be run or not, and popup a message to the user if it shouldn’t be, but it can’t control whether or not the script is shown in the first place.
In the script setup page in the Repository Options, maybe we could consider adding a text field where you could add some of your own logic that controls if the script is displayed or not. Would something like that be useful?
Yeah basically the use case is something like:
- for fume jobs, we could add a right click option that browses to the internal fume log files, and / or tails the last one
- internal flowline jobs, same thing
- in case the file has a scriptDependency, right click menu options could appear to navigate to the files being monitored by the scriptDependency (which is highly script specific, so probably could not be supported from within deadline)
etc
Ultimately what would be nice if the script itself could have an internal global function something like:
def isHidden(deadlineEntity (deadlineJob or deadlineTask etc)):
… query job/task/slave etc props, and then return True/False based on that
And maybe a way to add sub options, from within the script:
def numSubScripts(deadlineEntity):
… based on the deadline object this script is supposed to handle, return how many subscripts should appear
def subScriptName(deadlineEntity, iIndex):
… the name to display for this subscript
def executeSubscript(deadlineEntity, iIndex):
… exexute the Nth subscript
Does that make sense?
It makes sense, but that won’t perform well over remote connections. The reason we don’t have anything like this in the first place is because it would require executing the python script before building up the right-click menu, and if that script is on a server in another office, that could be slow. That’s why all the script menu configuration settings are stored in the database, rather than in .ini files like they used to be in v5.