|
Node State Symbols
|
|
|
The overall revision control state of each node, which combines the status of
each node property, file and upstream link associated with the node, is
indicated by the following symbols:
|
|
None
|
Signifies that no Node State information is available for the node.
This is used for displaying nodes dowstream of the root node of a tree,
since the status of these nodes has not been determined.
|
|
|
|
Checked-In
|
One or more checked-in versions of the node exist in the repository,
but no version of the node has yet been checked-out into the current
working area.
|
|
|
|
Pending
|
The node has been registered in the current working area, but has
not yet been checked-in.
|
|
|
|
Identical
|
The properties, upstream links and associated files of the node in the
current working area are identical to those of most recently checked-in
version of the node in the repository. In addition, the working version
of the node is based on the latest checked-in version of the node.
|
|
|
|
Modified Locks
|
The only difference between the working version of the node and the latest
checked-in version is the locked state of one or more of the upstream nodes.
One of these nodes has been locked or unlocked since the working version was
last checked-out. Alternatively, one or more of the upstream nodes has a
Node State of Modified Locks.
|
|
|
|
Modified Links
|
The upstream links of this node are not identical to those of the latest
checked-in version of the node. This may be due to links which have
been added to or removed from the working version or differences in link
properties. This state may also due to differences in the versions of
the upstream nodes connected to the working version and the latest
checked-in version. Alternatively, this state may be caused by one or
more of the upstream nodes having a Node State of Modified or Modified
Links.
|
|
|
|
Modified
|
The version of the node in the current working area is based on the
latest version of the node in the repository. However, one or more of
the node properties or associated files is not identical to this latest
version.
|
|
|
|
Needs Check-Out
|
The version of the node in the current working area is based on an
older version than the latest version of the node in the repository.
This signifies that a newer version of the node is available. Changes
to the current working version of the node will produce conflicts.
The three symbols associated with this state represent the magnitude
of the difference in revision numbers between the latest checked-in
version and the checked-in version upon which the working version is
based.
|
|
|
|
Conflicted
|
The version of the node in the current working area is different than
the latest checked-in version of the node. These differences are due
both to changes of the working version and the creation of new
checked-in versions since the time the working version was last
checked-out or created. These conflicts between the working version and
the latest checked-in version must be resolved before the node can be
checked-in.
|
|
|
|
Missing
|
One or more of the files associated with the working version are missing
from the current working area.
|
|
|
|
Missing Newer
|
Identical to Missing, except that version of the node in the current
working area is based on an older version than the latest version of
the node in the repository.
|
|
|
|
|
Per-File State Symbols
|
|
|
When indicating the revision control status of individual files associated
with a node, the following symbols may be displayed in addition to the
symbols described above:
|
|
Added
|
The working file exists and is part of a file sequence that was added
or had its frame range expanded since the time that the working version
was checked-out. There is no corresponding file associated with the
checked-in version upon which the working version is based.
|
|
|
|
Obsolete
|
The working file exists and the checked-in file upon which the working
file is based also exists but a new checked-in version has been created
who's frame range no longer includes the file. If the file is part of
a secondary file sequence, then the entire sequence may have been
removed from the new checked-in version.
|
|
|
|
|
Queue State Colors
|
|
|
The overall queue state of each node is indicated by the following
colors displayed in the background of node icons:
|
|
Undefined
|
The state is undefined because no working version of the node exists
in the current working area (Checked-In) or the state of the node is
not known (None).
|
|
|
|
Finished
|
All files associated with the working version of the node exist and are
up-to-date. If there is an enabled action associated with the node,
the last job executing this action completed successfully. Nodes must
be in a Finished state before they may be checked-in.
|
|
|
|
Stale
|
One or more of the files associated with the node is missing or
requires regeneration. Files require regeneration when the node has
an enabled action and one or more of the critical properties of the
node have been modified since the time the file was created. Files
may also require regeneration when any of the upstream file which they
depend upon are newer or are missing. Depending on the link properties,
these upstream files may be associated with nodes more than one link
upstream.
|
|
|
|
Queued
|
A job has been submitted to the queue which will regenerate the files
associated with the node, but has not yet begun execution.
|
|
|
|
Paused
|
A job has been submitted to the queue which will regenerate the files
associated with the node, but was paused before it began execution.
|
|
|
|
Running
|
A job which is currently executing will regenerate the files associated
with the node.
|
|
|
|
Aborted
|
The last job submitted to the queue which would have regenerated the
files associated with the node was aborted (cancelled) before it began
execution.
|
|
|
|
Failed
|
The last job submitted to the queue which would have regenerated the
files associated with the node failed to complete successfully. The
job may have failed during job preparation or one or more OS level
processes started by the job may have exited with a non-zero exit code.
The job may also have been killed manually by a user after it began
execution.
|
|