Releases: hypothetical-inc/GafferDeadline
GafferDeadline 0.59.0.0
- Breaking Change : Changed plug type of
extraDeadlineSettings
andextraEnvironmentVariables
toAtomicCompoundDataPlug
. This allows the values to be set by registeringuserDefault
metadata and prevents adding non-sensical data such as shaders to these plugs. It will break existing expressions connected to these plugs. The broken expression nodes will still exist and can be reconnected by replacing the__disconnected = IECore.CompoundObjectData( YourCompoundData )
variable assignment withparent[YourNodeName]["dispatcher"]["deadline"]["extraDeadlineSettings"] = IECore.CompoundData( YourCompoundData )
orparent[YourNodeName]["dispatcher"]["deadline"]["extraEnvironmentVariables"] = IECore.CompoundData( YourCompoundData )
GafferDeadline 0.58.0.0
- Add menu entry
/Dispatch/Deadline Dispatch
for compatibility with Gaffer 1.4. - Breaking change : Changed the naming of the temporary files created at submission time to send settings to Deadline. Files are now named by the hash of the task node.
- Fixed error
Context has no variable named "frame"
when dispatching withDeadlineDispatch
. - Breaking change : Changed the API for
GafferDeadlineJob.submitJob()
. It now takes a single directory where the job and plugin submission files will be saved. - Breaking change : Temporary job submission files are given random names by Python's
tempfile
module instead of attempting to use the hash of the dispatch node. - API : Added
GafferDeadlineJob.environmentVariables()
method. - Fixed bug that prevented context variables from being substituted in the
deadlineSettings
andenvironmentVariables
plugs. - Fixed bug that prevented context variables from being substituted into GafferDeadline plugs. (#79)
- Added
extraDeadlineSettings
andextraEnvironmentVariables
plugs. These can be set by an expression to add arbitrary numbers of Deadline settings and environment variables. Entries in these plugs will take precedence over identically named settings / variables in thedeadlineSettings
andenvironmentVariables
plugs. - Breaking change : Changed job names to be
${dispatcher.jobName}.${taskNodeName}
. (#80) - Added
batchName
plug to allow easy customization of the batch name. Previously it would be set to the dispatcher'sjobName
plug value unless overridden indeadlineSettings
. The default value is the same as dispatchers'jobName
default value, so unless you change thebatchName
plug value, batches will be named the same as previously.
GafferDeadline 0.58.0.0b3
- API : Added
GafferDeadlineJob.environmentVariables()
method. - Fixed bug that prevented context variables from being substituted in the
deadlineSettings
andenvironmentVariables
plugs. - Updated supported Gaffer versions to
1.3.16.5
and1.4.7.0
.
GafferDeadline 0.58.0.0b2
- Fixed error
Context has no variable named "frame"
when dispatching withDeadlineDispatch
. - Breaking change : Changed the API for
GafferDeadlineJob.submitJob()
. It now takes a single directory where the job and plugin submission files will be saved. - Breaking change : Temporary job submission files are given random names by Python's
tempfile
module instead of attempting to use the hash of the dispatch node.
Gaffer Deadline 0.58.0.0b1
This release adds support for Gaffer 1.4.0.0, specifically 1.4.0.0b4.
- Add menu entry
/Dispatch/Deadline Dispatch
for compatibility with Gaffer 1.4. - Gaffer.param :
- Drop support for Gaffer versions 1.2.10.5 and 1.3.7.0.
- Add support for Gaffer versions 1.3.14.0 and 1.4.0.0b4.
- Breaking change : Changed the naming of the temporary files created at submission time to send settings to Deadline. Files are now named by the hash of the task node instead of the node name. This is only a concern if you are doing customized processing of the intermediate Deadline submission files.
Gaffer Deadline 0.57.3.0
- Fixed
GafferDeadlineUITest
to pass. - Fixed bug causing an error when dispatching when passing
pathlib.Path
values toGafferDeadlineJob.setAuxFiles()
. - Added support for
GafferScene.RenderPassWedge
. This fixes the errorTypeError: unsupported operand type(s) for -: 'NoneType' and 'NoneType'
raised when attempting to dispatch aRenderPassWedge
.
GafferDeadline 0.57.2.0
This adds a couple of nice new features, most notably registering progress for Arnold renders and compatibility with the latest Deadline Release which only supports Python 3.10.
- Reduced the severity of the check on no-op node batch size from an error to a warning.
- Removed support for Gaffer versions
1.2.1.0
and1.2.6.0
- Added support for Gaffer versions
1.3.7.0
and1.2.10.5
- Added support for Arnold progress updates in the Deadline plugin.
- Update Deadline Plugin to use Python 3.
- Update Deadline Plugin to be compatible with Python 3.10.
GafferDeadline 0.57.1.0
GafferDeadline 0.57.1.0 adds a new node, DeadlineTask
, for submitting native Deadline plugin jobs. Plugin-specific settings can be set via the parameters
plug. Consult the Deadline documentation for a list of required and optional parameters for a plugin.
Note that DeadlineTask
does nothing when dispatched by anything except the GafferDeadline dispatcher.
GafferDeadline 0.57.0.0
This release includes a few user-facing and API improvements.
- Added controls for Gaffer's
-threads
command line parameter.- The GafferDeadline dispatcher plug
threads
can be used to control the thread count on a per job basis. Ifthreads
is set to 0, it will be ignored when executing the Deadline job. - GafferDeadline will also recognize a Deadline Worker's
CpuAffinity
property, if set, and use the number of enabled CPUs as the thread count. - If the
threads
plug is non-zero and a Worker has itsCpuAffinity
property enabled, Gaffer will use the lesser of the two values as its thread count.
- The GafferDeadline dispatcher plug
- Added
logLevel
:- Added plug to the dispatcher settings to control the
IECORE_LOG_LEVEL
environment variable for submitted jobs. - API : Added
GafferDeadlineJob.setLogLevel()
andGafferDeadline.getLogLevel()
methods.
- Added plug to the dispatcher settings to control the
- Added output support :
- Added
outputs
plug to GafferDeadline settings. The values of this plug will use all string substitutions except frame substitutions. This allows Deadline to substitute frame numbers itself. - API :
- Added
GafferDeadlineJob.addOutput()
to add an output with an optional context for substitutions. - Added
GafferDeadlineJob.getOutputs()
to return the current job outputs. - Added
GafferDeadlineJob.clearOutputs()
to remove all job outputs.
- Added
- Added
GafferDeadline 0.56.1.0
This update adds some small fixes and features, and adds support for recent Gaffer alpha releases. Note that the alpha release support will be removed in favor of Gaffer 1.2.0.0, when it is released.
- Added Alfred style progress (commonly used by Houdini renderers) updates in the Deadline plugin.
- Added support for Gaffer 0.61.1.2, 1.2.0.0a1 and 1.2.0.0a2.
- Added the ability to use
pathlib.Path
objects in auxiliary files. This can be done, for example, in a prespool signal handler that modifies the jobs auxiliary files viasetAuxFiles()
. - DeadlineDispatcherTest : Removed support for Python 2.